Latest Contributions by ShanaBritt

For stacked addresses, you could cartographically disperse them using https://pro.arcgis.com/en/pro-app/latest/tool-reference/cartography/disperse-markers.htm.   -Shana ... View more

Nicole: If you have geocoded with a composite locator, the Loc_name field in the output geocode feature class will display the locator in the composite that returned the match. This field is returned when geocoding with a local composite locator or composite geocode service in both ArcMap and  ArcGIS Pro. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm If you are trying to figure out which geocode service or locator was use to create the geocode result feature class you can look at the properties of the result in ArcMap and the properties dialog would have a Geocoding tab. This is not available in ArcGIS Pro. If you'd like this functionality in ArcGIS Pro, please submit an idea here or enhancement request through Support.   ... View more

If you run into something while upgrading your locators to those created with the Create Locator tool that is not clear or works unexpectedly please post a question here or submit something to Support. I would encourage you to review the help section for Geocoding, below are some to get started.  https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/fundamentals-of-creating-a-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-preparing-reference-data.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/display-geocode-results-on-the-map.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/benefits-of-using-polygons-versus-points-for-areas.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/introduction-to-locator-roles.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/locator-role-fields.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/fundamentals-of-intersection-geocoding.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/fundamentals-of-reverse-geocoding.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tips-for-improving-geocoding-quality.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm ... View more

You can increase the minimum match score and minimum candidate score to 96 and this intersection wouldn't match during batch geocoding or return as a candidate when searching in the Locate pane. You may want to consider submitting this as an idea for an enhancement so that it can be evaluated.   -Shana ... View more

@ScottFedak2085  If the subaddresses are stacked (same geometry) we will return a range of subaddresses at that location.  If they aren’t stacked (different geometry) we will return the closest one to the input location.   -Shana ... View more

@JoyetaChowdhury The error you are getting is because you are using an Excel spreadsheet as the primary data, which needs to be a feature class (shapefile, file geodatabase, sde). If the data in the spreadsheet was exported from a feature class, you need to break up the string in the Address field into multiple fields that contain the individual address components (house number, street direction, street name, etc...). If you have ArcGIS Pro 3.0 or later you can use the Split Address Into Components tool, otherwise the Standardize Addresses tool is available in ArcGIS Pro 2.9 and earlier. Both tools output a new feature class and splits the address components into individual fields that are necessary to build a locator with the Create Locator tool.   The following tutorials are available, which should help you with creating the locator. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-multirole-locator.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm   -Shana ... View more

@LorindaGilbert  I would start by looking at the geometry (shape field) of the data used to build the locators in the participating locators. It sounds like the locators in the composite might reference a mix of 2D and 3D geometry. If for instance the street layer to build the locator has geometry that is PolylineZ the geocode result will be PointZ. The locators built in ArcGIS Pro with the Create Locator tool always returns 2D features when the reference data is PolylineZ,  PolygonZ, or PointZ. If you have ArcGIS Server the locators can be published from ArcGIS Pro and the service can be used in ArcMap.   -Shana ... View more

@KeithJ Any locator created with the Create Locator tool or Create Feature Locator tool support suggestions by default and cannot be disabled. Auto-complete suggestion functionality is not available in ArcGIS Pro outside of the Locate pane. The ArcPy Geocoding Module has geocoding methods such as suggest, does your model use a script that includes methods from the Geocoding Module?  Please elaborate on the following statement regarding the match results returned by the composite used in the model and how it relates to the suggestions returned in the Locate pane.  "I use this locator in a model and I am not aware of any way to turn off suggestions when the model runs, which sometimes causes differing results (matches town and/or street, I need the locator to match both or fall out). " Which result order are you using in the composite locator? Are you not able to build a multirole locator and get the results you are looking for? - 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/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm -Shana ... View more

@Brian_McLeer  In ArcGIS Pro, the new > locator option launches the Create Locator geoprocessing tool. Are you just looking for a shortcut to launching the Create Composite Address Locator tool instead of going to the Geoprocessing pane? ... View more

@MohammedDessouky Are you still encountering this behavior? ... View more

@ScottFedak2085 Are your stacked points subaddresses at a single location? ... View more

@Ranga_Tolapi Do you get any candidates for the places that have the same name, but a different address? What happens when you search for these locations in the Find tool? ... View more

Amanda: You would have to stop the service before rebuilding the locator in ArcMap. If you are using ArcGIS Pro 3.0 or later, you would not be able to add the locators created in ArcMap with the Create Address Locator tool to publish them from ArcGIS Pro. However, if you have locators built with the Create Locator tool in ArcGIS Pro you an publish it to your standalone Enterprise 10.8 server using the steps described in the following topic, https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/publish-a-geocode-service.htm. This service can be used in ArcMap through and ArcGIS Server Connection. The following topic is for ArcGIS Pro, but the same concept can be applied to ArcMap. https://pro.arcgis.com/en/pro-app/3.1/help/data/geocoding/keep-your-locator-up-to-date.htm ... View more

@MichaelVolz As far as the alternate name table I would create a StreetNameID field in the primary reference data and give each record/feature with the same street name the same ID, so if you have 10 'E Orange Lane' features they will get the same ID. Then in the alternate street name table you would have a StreetNameID field and record1 for 'E Orange La' would get the same ID as the 10 features in the  primary data layer. Then record2 for 'E Orange Lan' would get the same ID as the 10 features in the primary data layer. You data would have a Many (primary)-to-Many (alternate table) relationship and look similar to the image below. The most common and I believe the USPS street types are already included in the geocoding rules and any abbreviation you have that is not working by default should go in the alternate name table. Then the Preferred Street Name settings in the locator properties you can specify which street name will be returned.   ... View more