prop_info.prop_sector |
RESIDENTIAL ,COMMERCIAL , LAND , AGRICULTURE, INDUSTRIAL |
prop_info.prop_type_group |
LANDED ,NON-LANDED , OTHERS |
prop_info.prop_type_name |
FLAT,SHOP UNIT,TERRACE HOUSE, SHOPLOT, APARTMENT, CONDOMINIUM ,DETACHED PLOT, SEMI-D,BUNGALOW, "SERVICE RESIDENCE", OFFICE , TERRACE FACTORY, DEVELOPMENT LAND, TOWN HOUSE, VACANT LAND , CLUSTER HOUSE, TERRACE PLOT, SEMI-D FACTORY , RETAIL UNIT, SEMI-D PLOT , DETACHED FACTORY, MULTI-STOREY FACTORY, INDUSTRIAL COMPLEX , WAREHOUSE,STALL , OTHERS. |
full_address |
Full address of the matched property |
es_prop_radius |
The radius in which the matched property was found [100m, 300m, 1000m, >1000m] |
prop_chubb_st_distance |
Straight line distance between the lat/long of the subject property and the lat/long of the matched property, in meters |
transaction_match |
How accurate the match between the subject property and matched property is. Examples: * No Match: the subject property could not be matched * LatLong: the properties are close to each other, but the project, city, and unit do not match * LatLong+Project: the properties are in the same project |
transaction_score |
Score given to the accuracy of the property match. Examples: * LatLong: 10 * LatLong+Project: 30 |
project_name_found |
Indicates the input field in which the project name of the property was found. Examples: [City, County, District, Project] |
latlong_used_risk_attributes |
* “Input”: the input lat/long matches (rooftop-level) the location of the input address, so it was used to find a matching property. * “Google”: the input lat/long is not an exact match to the location of the input address. Therefore, the location of the input address was used to find a matching property. |
address_lat |
Latitude coordinate of the matched property (up to 6 decimal points) |
address_long |
Longitude coordinate of the matched property (up to 6 decimal points) |
h3_index |
Encoded lat/long in the form of h3_index (15 digits), a geospatial system to index spatial data. |