Latest Contributions by ShanaBritt

Are you still getting the behavior if you have upgraded to ArcGIS Pro 2.1 when you create the locator with the Single Field locator style and the feature class from the file geodatabase? Does the same error occur if you create the locator using the General - Gazetteer locator style and use the PlaceName field to map the field in your data that you would have used as the KeyField in the Single Field style? Does the feature class in the geodatabase contain global ids? -Shana ... View more

Joe: I believe the behavior you ran into is related to NIM095011: An address locator based on reference data with Z or.. , which includes a workaround to remove the m or z from the feature class. Once removed, the data could be used as the reference data to build the address locator.  -Shana ... View more

Does the address in the FullAddress field contain city, state, or zip? Does your single line csv look similar to below? ID,FullAddress 1,"380 New York St, Redlands, Ca" 2,"Nevada St & Redlands Blvd, Redlands, Ca" ... View more

What data format is the output getting written to (shp, file geodatabase..)? Does outputting to a different data format get the results showing on the map? What is the value in the Shape field of the reference data that was used to build the 3 participating locators in the composite? I've seen this type of behavior when the reference data geometry has M or Z values. What version of ArcMap or ArcGIS Pro did you find this behavior? -Shana ... View more

Do you get the same behavior if you make the same changes to <mapping_schema name="Gazetteer" in the same General.lot.xml file as SingleField and create a geocode service from a locator based on the Gazetteer style? There was a memory leak with the Single Field style as a service at 10.5, so that's why I'm suggesting you use the Gazetteer style. ... View more

Brandon, we are looking to resolve the problem (NIM076288) with Global IDs in a future release of ArcGIS Pro and ArcMap, which will be beneficial to those using feature service tables or data that requires Global IDs for use in other applications and workflows throughout the ArcGIS Platform. https://support.esri.com/en/bugs/nimbus/TklNMDc2Mjg4 . ... View more

I couldn't reproduce the behavior you described with Subaddress and Placename alias table in version 10.4.1 and 10.6, which has an updated Subaddress style template. The input fields that the help exert mentioned in your original post is referring to the items in green in the screenshot below and how they should match the fields of the placename alias table. When testing the locator are you typing "Mikeburg" and expecting the match to be a unit at "316 Washington Street"? The workaround of creating a SingleField or Gazetteer based locator for place locations and adding it to a composite with the Subaddress is the next best option. If you want to provide the data you are actually working with so that I can look at it, feel free to send me an email. ... View more

The Esri World Geocoder has been updated several times since your question was first posted. Below are the results for the same coordinate with the current release of the Esri World Geocoder. {  "address": {   "Match_addr": "65-99 Edison Dr, Augusta, Maine, 04330",   "LongLabel": "65-99 Edison Dr, Augusta, ME, 04330, USA",   "ShortLabel": "65-99 Edison Dr",   "Addr_type": "StreetAddress",   "Type": "",   "PlaceName": "",   "AddNum": "83",   "Address": "83 Edison Dr",   "Block": "",   "Sector": "",   "Neighborhood": "",   "District": "",   "City": "Augusta",   "MetroArea": "",   "Subregion": "Kennebec",   "Region": "Maine",   "Territory": "",   "Postal": "04330",   "PostalExt": "",   "CountryCode": "USA"  },  "location": {   "x": -69.81843118824392,   "y": 44.313088731759194,   "spatialReference": {    "wkid": 4326,    "latestWkid": 4326   }  } } ... View more

To geocode parcel numbers create a locator based on the General - Single Field mapping the parcel number to the "Key Field" or General - Gazetteer style mapping the parcel number to the "Place Name" field. If the locator will be published as a geocode service, it's recommended to use the General - Gazetteer style. ... View more

I have a few questions and comments... Are you creating your own address locator to geocode the customers and offices in the spreadsheet? If you did you could use the General - Gazetteer locator style to build an address locator to search for office name, Dual Range or Single House style to search for addresses, then combine the two into a composite locator that could be published as a geocode service that the web app can use. Will you be using the World Geocoding Service and an ArcGIS Online subscription for geocoding the addresses? You would need a geocode service to be able to have the web application make REST calls to the geocode service and return matches for the address. What are you going to use to host the web map (app)? Is the database part of an enterprise geodatabase? What licence of ArcGIS Desktop do you have? You maybe able to make use of the dynamic feature class mentioned at step 7 in this help topic, Geocoding a table of addresses in ArcMap—Help | ArcGIS Desktop . This would require that the table (database) of addresses and the geocode result be stored in the same geodatabase as a composite relationship class between the table and output feature class is created when the dynamic feature class option is selected. The idea is that if the input address table is updated within ArcGIS Desktop manually or pragmatically that the address will get automatically geocoded and added to the output feature class in the geodatabase. ... View more

Afizah: There is a setting in the address locator properties that you need to turn on so that the information that was mapped in the Additional Field when the locator was built is returned in the User_fld. Set "Write user-specified additional output fields" to 'Yes'. -Shana ... View more

Based on your post I don't have all of the information about the other locators that are participating in the composite locator with the Gazetteer locator to give more detailed response to your question about the General.lot.xml file. However, I would suggest that when you build the address locator(s) based on styles not the Gazetteer, build the locator without mapping city and zip. This will allow you to enter an address w/o city or zip code, but you will need to follow the steps in the following article to modify the locator properties to allow searching for addresses without a zone like city or zip. Bug: Dual Ranges address locators created with ArcGIS for Desktop 10.1 and higher do not return matches  The suggestions functionality does not index the house number, only the street name, and is not correlated to the house number. More discussion about suggestions can be found at this thread https://community.esri.com/thread/164282  -Shana ... View more

Here is the documentation that outlines the limitations for using Excel spreadsheets in ArcGIS Pro https://pro.arcgis.com/en/pro-app/help/data/excel/work-with-excel-in-arcgis-pro.htm. You can use the Table to Excel conversion tool in ArcCatalog or ArcMap to export the sheet to a new Excel .xls file to use in ArcGIS Pro if you need to keep the data in Excel format. ... View more