Latest Contributions by ShanaBritt

Emily, You would want to reduce both the max and suggested, which would reduce the maximum amount of records that can be sent in one batch. However, this will not limit the total number of geocodes that the user can do, because they can send many batches. Another way to limit the server usage is to reduce the min and max number of instances (SOCs). If set to 1, only one user at a time can use the service. ... View more

You're welcome. Have you considered using the General - Gazetteer style to create a locator for your structures and landmarks, then adding the Gazetteer type locator to a composite with your other address locator(s)? Then publish the composite, which will allow you to search for addresses, intersections, structures and landmarks. ... View more

You're welcome. Have you considered using the General - Gazetteer style to create a locator for your structures and landmarks, then adding the Gazetteer type locator to a composite with your other address locator(s)? Then publish the composite, which will allow you to search for addresses, intersections, structures and landmarks. ... View more

Phil: Development is aware of the limitation in the current technology regarding suggestions for geoocde services and have plans to address the behavior in a future release. Currently, the suggestion index is only built for street name and no suggestion index is built for house number or subaddress unit. Because of this, there is no correlation between the street name and house number or subaddress unit. ... View more

The place-name alias table mentioned in the original post is for things like being able to type "City Hall" and have it match to the address for City Hall. This is currently not supported by a geocode service, however, the alternate name table is what you need for alternate street names where you can have a 1-to-Many relationship between the features in the primary table and the alternate or abbreviated street names. The alternate street name table is supported when publishing the locator as a geocode service. ... View more

The place-name alias table mentioned in the original post is for things like being able to type "City Hall" and have it match to the address for City Hall. This is currently not supported by a geocode service, however, the alternate name table is what you need for alternate street names where you can have a 1-to-Many relationship between the features in the primary table and the alternate or abbreviated street names. The alternate street name table is supported when publishing the locator as a geocode service. ... View more

Bendicht: We are aware of this behavior and will try to address the problem as soon as we can. In the meantime, I would suggest creating a Project Template ( the button is next to Map File on the Share tab) instead of the Map File and use the Project Template to create projects from that contains the feature and layer provider. See the following help topics: Create a project template—ArcGIS Pro | ArcGIS Desktop  Create a new project—ArcGIS Pro | ArcGIS Desktop  ... View more

Julia: The side offset setting only applies to address locators based on the Dual Ranges and One Range styles that use lines as reference data. It would not apply to a locator that was based on points or polygons, which is the reference data used by the General - SingleField and General - Gazetteer styles. If you knew the distance and direction of the tree from the address or center of the parcel you could use spatial offset to search for the address as described in this help topic. About finding an address—Help | ArcGIS Desktop  ... View more

If you are able to upgrade to 10.5 or higher, there is only one pair of Subaddress elements for field mapping when building a locator with the US Single House Subaddress style. ... View more

The "Match with no Zones" setting was originally default to 'Yes' at 10.0, but since 10.1 it's been 'No' as the default. It affects performance for large areas (Regions, Nationwide), not so much for small areas like city or county. ... View more

What is the error that you receive? What locator are you using to geocode the table when the error occurs? What version is the locator used when the error occurs? (open the locator properties for this info) What format is the table you are using? Does the error occur if the table is converted to a different table format? What error was returned when standardizing the table? Was this with the Standardize Addresses tool? -Shana ... View more

It is not possible to rematch with a different locator than the original locator in Pro or ArcMap. I would suggest creating a composite address locator with the point locator listed first and the street locator listed second, then geocode the table and whatever is unmatched should be because an address was not matched to either the point or street locators within the composite locator. https://pro.arcgis.com/en/pro-app/help/data/geocoding/create-a-composite-locator.htm ... View more

Does the behavior with the intersections occur when batch geocoding the table in Pro with either the locator created in ArcMap or in Pro 1.4? I'd like to determine if this is locator or application specific. I've not heard anything from Support regarding this behavior. Are you able to send a sample of the data to me or contact Support for further investigation? ... View more

Do you get the same behavior if you build the locator in ArcGIS Pro 1.4 and use it in ArcMap or ArcGIS Pro? Does the behavior occur when using the Find tool in ArcMap or is it limited to batch geocoding with the 10.5 Dual Ranges locator? ... View more

Kathleen: The results were the same using all three methods and spelling out the subaddress element types returned the expected results. Entering a different unit type from the reference data returned matches as well. If you’d like to see the locators I built I can send them to you off the thread. -Shana ... View more