Find address candidates - Geocodeing

303
1
Jump to solution
02-13-2019 02:45 PM
forestknutsen1
MVP Regular Contributor

We are wondering if there is a standardized output for geocoders. We noticed that an out of the box 10.6 single house with subaddress has a fair amount of variation from our older custom style single house with units. I think the only thing that is custom is the attributes UnitType and UnitNumber.

10.6 single house with subaddress json response 

{
"spatialReference": {
  "wkid": 102634,
  "latestWkid": 102634
},
"candidates": [
  {
   "address": "3850 TAIGA DR, Anchorage, AK, 99516",
   "location": {
    "x": 1674055.943784937,
    "y": 2594838.6101037711
   },
   "score": 100,
   "attributes": {
    "Score": 100,
    "Match_addr": "3850 TAIGA DR, Anchorage, AK, 99516",
    "Addr_type": "SubAddress",
    "AddNum": "3850",
    "Side": "",
    "StPreDir": "",
    "StPreType": "",
    "StName": "TAIGA",
    "StType": "DR",
    "StDir": "",
    "SubAddType": "",
    "SubAddUnit": "",
    "StAddr": "3850 TAIGA DR",
    "City": "Anchorage",
    "County": "",
    "State": "AK",
    "StateAbbr": "AK",
    "ZIP": "99516",
    "Country": "USA",
    "LangCode": "",
    "Distance": 0,
    "X": 1674055.9437849999,
    "Y": 2594838.6101040002,
    "DisplayX": null,
    "DisplayY": null,
    "Xmin": null,
    "Xmax": null,
    "Ymin": null,
    "Ymax": null
   },
   "extent": {
    "xmin": 1673399.7771182703,
    "ymin": 2594182.4434371046,
    "xmax": 1674712.1104516038,
    "ymax": 2595494.7767704376
   }
  }
]
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

custom style single house with units json response 

{
"spatialReference": {
  "wkid": 102634,
  "latestWkid": 102634
},
"candidates": [
  {
   "address": "3850 TAIGA DR, Anchorage, AK 99516",
   "location": {
    "x": 1674055.9457335561,
    "y": 2594838.6066555073
   },
   "score": 88.840000000000003,
   "attributes": {
    "Loc_name": "ARCFM8CW_Parce",
    "Score": 88.840000000000003,
    "Match_addr": "3850 TAIGA DR, Anchorage, AK 99516",
    "House": "3850",
    "PreDir": "",
    "PreType": "",
    "StreetName": "TAIGA",
    "SufType": "DR",
    "SufDir": "",
    "UnitType": "",
    "UnitNumber": "",
    "City": "Anchorage",
    "State": "AK",
    "ZIP": "99516",
    "User_fld": "0",
    "Addr_type": "Address",
    "Side": "",
    "FromAddr": "",
    "ToAddr": ""
   }
  },‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

We have a vendor asserting that our coder in returning poor information for  3850 Taiga Dr.

The variation is in the field names. For example, StreetName vs. StName. Is StreetName an old standard from the 10.0 days and now it is StName. I am guessing that the output field names are driven by the geocoder style xml. Is that right?

0 Kudos
1 Solution

Accepted Solutions
ShanaBritt
Esri Regular Contributor

The custom single house unit locator you are referencing was created back at version 10.0 or 10.1 and shared on the forums and was not an official out of the box address locator style shipped with ArcGIS Desktop. The out of the box locator styles have changed since that custom single house with units locator style was created and the Single House Subaddress locator style that is included with ArcGIS 10.6.1 has different output fields that more mimic the output fields of the World Geocoding Service. You are correct that the output field names come from the locator style.

Is the poor information that the vendor is referring to the field names or something else?

View solution in original post

1 Reply
ShanaBritt
Esri Regular Contributor

The custom single house unit locator you are referencing was created back at version 10.0 or 10.1 and shared on the forums and was not an official out of the box address locator style shipped with ArcGIS Desktop. The out of the box locator styles have changed since that custom single house with units locator style was created and the Single House Subaddress locator style that is included with ArcGIS 10.6.1 has different output fields that more mimic the output fields of the World Geocoding Service. You are correct that the output field names come from the locator style.

Is the poor information that the vendor is referring to the field names or something else?