Latest Contributions by ShanaBritt

I tried to reproduce the behavior in the 2.5 release we are working on and was not able to reproduce. The Locate pane has a different look for the next release so it may not be a problem there. If you are part of the Early Adopter Program you can test out beta versions of ArcGIS Pro. ... View more

Curtis: Using the ArcGIS World Geocoding Service from the Locate pane in ArcGIS Pro will not charge credits. You will be charged credits if you batch geocode a table of addresses or locations using the ArcGIS World Geocoding Service in either Geocode Table or geocoding geoprocessing tools. -Shana ... View more

Sharon, which version of ArcGIS Pro were you using when encountering this behavior? ... View more

Bennett, which version of ArcGIS Pro are you using? ... View more

Joe: In your example above are you using a single locator or a composite locator? You can get suggestions from the classic locators that are created with the Create Address Locator tool, but they aren't validated against the house number or street name. The logic behind the subaddress results between the classic locators and the new locators is different and they are designed differently. If the locator mentioned above is a composite, I suggest that you combine all of the features, with and without subaddress units, into a single feature class and build the locator using the PointAddress role. Make sure the base address is part of the feature class so that if you search for a subaddress unit and it's not found you can return the base address.  If you create a multirole of PointAddress and StreetAddress, if there is a street segment id that exists in both the point and street data, they should be used to join the roles together using the 'Street Join ID' field from the locator role. This will keep from getting multiple candidates for the same location and if the base address didn't exist in the point data, searching for the base address of the subaddresses will return a match from the StreetAddress locator instead of no result from the PointAddress locator. ... View more

Using the Planarize tool can help with ensuring the lines are snapped together where they intersect. I would select the line features that represent the intersection, run Planarize, then create a locator based on the planarized lines to see if the behavior changes. https://desktop.arcgis.com/en/arcmap/10.6/manage-data/editing-existing-features/splitting-lines-at-intersections-with-planarize.htm.   ... View more

Cynthia: What version of ArcMap are you using? Is using ArcGIS Pro an option for the dispatchers? Must the dispatchers use a local locator or can they use a geocode service if you were to publish your locator to ArcGIS Server? Does the same behavior occur if you build the locator without mapping the street type address component? ... View more

I have a few questions to help figure out a solution 1. What application and version are you using or have available for this task? ArcMap, ArcGIS Pro 2. Do you have spatial features that represent the step tank? If so, does it include the same step # that is in the spreadsheet? If yes, you could build a locator based on the step # or if you combined the step # and the lot # into a new field and use that to build the locator and search on. 3. Do you need to geocode to the lot level or step tank level? 4. What attributes do the subdivision and parcel features have that would help? ... View more

Stephen: Have you had a chance to upgrade your Pro? If so, do you continue to get the same behavior? ... View more

Susan: If you have ArcMap available to you, create the locator in ArcMap and add the locator to Pro. Do you get the same behavior accessing the Properties? Also, for the existing locator created in Pro, if you have ArcMap, you should be able to adjust the setting you need and use the locator in Pro. Do others in your organization have the same problem? If a different user signs onto your machine do they encounter the same problem? ... View more

John: How will you be using the locator the you create with the Distance Marker role? What problem are you trying to address by creating a locator based on the Distance Marker role? What is an example of the address you tried to find after creating the locator? ... View more

Andrew: Based on the path in the error message it looks like you are using an ArcGIS Server connection that was created in ArcMap. Please try creating a new ArcGIS Server connection in ArcGIS Pro 2.4 to your ArcGIS Server using the steps described in this help topic and try geocoding the table again. https://pro.arcgis.com/en/pro-app/help/projects/connect-to-a-gis-server.htm#GUID-E3F3174D-3895-4BFC-9443-8676D2D4964B Once you have made the connection, you can expand the server connection, right-click the locator ans select add to project. Or when in the Geocode Table pane browse to the Servers folder in the browse dialog for the input locator. ... View more

The behavior in the original post is expected behavior for subaddress addresses, a unit indicator (#, APT, UNIT...) is required to return address matches. This is noted in the Subaddress section in the help, https://pro.arcgis.com/en/pro-app/help/data/geocoding/introduction-to-locator-roles.htm#GUID-BA06C3FE-2210-4634-9E61-CA5BAA6E2E5E. Suggestions for subaddresses are currently not supported for locators based on the PointAddress role created with the Create Locator tool whether local or as a service. It would be great to understand the use case for providing suggestions for subaddress, as well as, returning all units associated with the base address when searching for the base address. At what point in typing the address do you expect the unit suggestion be returned? If you are searching an address for a building with 1,000 units, are you expecting to scroll through all 1,000 unit candidates to find what you are looking for?  The PointAddress role does require one of three field mappings outside of street name: building name or house number, or house number to and from fields. This is why you are getting the error when only mapping street name. I'm not sure what values you had in the street name field, but the PointAddress role requires the address components to be separated just like street centerlines. See link to help topic above.  ... View more