Latest Contributions by ShanaBritt

Which version of ArcGIS Pro are you geocoding the csv table in? Does the error occur via Python with a StreetAddress role based locator created with the Create Locator tool? ... View more

@Michael_VanHatten I would consider creating a multirole locator with the Create Locator tool using the StreetAddress role for the street data you have and POI role for the point assets, where you can use the PropertyID as the string to map to PlaceName when building the locator. If you were to reverse geocode you could get either the street address or the asset that was closest to the picked location on the map. It would be easier to provide a more specific answer if I was able to look at a sample of the data you were working with. Below are some help topics you should find helpful. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm https://pro.arcgis.com/en/pro-app/3.1/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/3.1/help/data/geocoding/fundamentals-of-reverse-geocoding.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm#ESRI_SECTION1_CE2B24E7AC144C71B645937363ECBCE5 https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/locator-role-fields.htm ... View more

@AshlieVinzant Are you signed into ArcGIS Online? Do you have batch geocoding permissions in the ArcGIS Online organization?   -Shanan ... View more

@jlchamber Based on the following description, what about the fields that are returned presents a problem for you? Does 'Location Only' work for your workflow? "Minimal returns following fields that describe the location and how well it matches information in the locator in the geocode results: Shape, Status, Score, Match_type, Match_addr, and Addr_type. The original field names from the input address table are maintained." Location Only returns the Shape field plus the original field names from the input address table.   -Shana ... View more

@PatrickMcKinney99 Thank you for providing the workflow you are using. It took a bit for me to find the name, but when you add a csv directly to the map, like in your workflow a feature collection layer is created in the map. These type of layers are only stored in the map and cannot be shared outside of the map. It is the generate request that creates it.  https://enterprise.arcgis.com/en/portal/latest/use/feature-layers.htm#GUID-304463C0-25BD-4FEA-8DD6-AD82F2C96B56   Viewer role: Viewer—View items such as maps, apps, demographics, and elevation analysis layers that have been shared by other ArcGIS users. Those assigned the Viewer role can join groups owned by the organization, as well as use geocoding, geosearch, and network analysis (routing and directions). Members assigned the Viewer role cannot create or share content or perform analysis or data enrichment. I hope this information helps. -Shana ... View more

Do you get the same behavior when you save the output to a file geodatabase? ... View more

Which version of ArcGIS Pro is used by your University? Are you saving the geocode result out to a shapefile or geodatabase? Are you saving the geocode results to your local machine or network location? -Shana ... View more

@JoshBillings The locator you created is with zones (city, zip) and the 'Match with no zones' setting is set to "No", which means you need to provide a zone or location when entering an address when the service is not used with a map. When using the service with it's current settings via the REST endpoint requires that you include a zone or use the location parameter to get results returned. The locator works as expected in ArcGIS Pro because the center of the map is being used as the location or zone when entering the address w/o city or zip, but you should also get suggestions as you type the address in the Locate pane in ArcGIS Pro. We have made improvements to the way the locator behaves when built with zone and 'Match with no zones' is set to "Yes" in ArcGIS Pro 3.1and Enterprise 11.1. Patches exist for Enterprise 11.0 and the latest ArcGIS Pro 3.0.x patch. Enterprise 10.9.1 is the last version that supports publishing classic locators created by the Create Address Locator tool. Does the site that uses this geocode service allow for suggestions when typing the address? ... View more

Are you still using ArcMap 10.5 or are continuing to get the same inconsistent behavior when using the ArcGIS World Geocoding Service? Does your organization have plans to move to ArcGIS Pro? -Shana ... View more

@JoshBillings Was the FirePaySiteLocator created with city,state, or zip code mapped when you built the locator with the Create Locator tool in ArcGIS Pro? If so, if you enter one of those do you get results? Of if you populate the location parameter with a coordinate pair that is in the same unit of the coordinate system of the data  used to build the locator? Is the input always going to be without city or zip code? A screenshot of the Reference Data Table section of the locator properties page and geocoding options would be helpful in figuring out what's going on with the locator or confirming what I think is wrong. ... View more

@JoshBillings Based on the product versions you mentioned, it sounds like you used the Create Address Locator tool to build the locator in ArcMap 10.6 or ArcGIS Pro 2.6 or earlier. The Create Locator tool is only available in ArcGIS Pro and does not have a spelling sensitivity property to adjust. Are you able to provide a screenshot of the locator properties to confirm the version of the locator? You could use an alternate name table to account for the prefix direction and street type abbreviations when building the locator. If you have ArcGIS Pro available to you, you can build a locator with the Create Locator tool using the point address data you have with the the PointAddress locator role, then publish the locator to Enterprise 10.6 and use the service in ArcMap, but you wouldn't have all of the new locator functionality in this version of Enterprise.  ... View more

@JoshBillings  What tool was used to build the locator? What version of Pro was used to build the locator? What version of Enterprise did you publish the locator to? Will users enter the address with or without the city or zip code? Have you attempted to create the locator with the Create Locator tool to see if you get better results? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator.htm -Shana ... View more

@RoderickPearson Which application were you using when you geocoded your table with the ArcGIS World Geocoding Service when  you encountered the inconsistent behavior?   -Shana ... View more

@Ragavi , have you tried specifying the category as Street Address, which will return a candidate at the street level? For example: https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=37%20Dover%20Street%2C%20SUMMER%20HILL%2C%20NSW%2C%202130&category=Street%20Address&outFields=addr_type&f=json&token= The other options is to specify the locationType as 'street', but if only rooftop location coordinates are available for an address, the rooftop geometry will be returned for the geocoded address even when locationType=street is requested. It looks like for the address in your example only rooftop coordinates are available in the data for the World Geocoding Service. https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=37%20Dover%20Street%2C%20SUMMER%20HILL%2C%20NSW%2C%202130&locationType=street&outFields=addr_type&f=json&token= More info about locationType parameter can be found on this page, https://developers.arcgis.com/rest/geocode/api-reference/geocoding-find-address-candidates.htm.   -Shana ... View more