Latest Contributions by ShanaBritt

@ScottFedak2085 I just randomly selected the name "StreetNameID" in the explanation to you. The field could be named anything. Each role in the Create Locator tool has a Join ID field used to link to an alternate name table or to another role, like PointAddress and Parcel. These role fields are described in https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/locator-role-fields.htm. You can still build the locator with the alternate street name table using your current workflow and continue to get the warning, and the alternate name an preferred street name will continue to work. Glad I could help. -Shana ... View more

@ScottFedak2085 , The help topic for the 003106 warning you are getting describes what is going on, but the best option to optimize the locator performance and size is to have a Many-to-One or Many-to-Many relationship between the primary StreetName  and the alternate street name table using a StreetNameID in both tables. The same principle would apply to alternate city names, neighborhood, or county names (Los Angeles County vs Los Angeles) or any of the other supported alternate name table roles. Here is an illustration of what I'm describing. -Shana ... View more

@JohnNergeBrooklynPark The setting I mentioned above is something that you can do in Pro at the time of batch geocoding the table. Were you looking for something else? You cannot adjust the properties of the locator once it is published as a geocode service in Pro. If the composite locator was local you would have to remove the participating locator you don't want from the composite. If you are able to provide me with the URL to the service you are using I can illustrate for you or determine if their service is a composite of classic locators or the new locators.   -Shana ... View more

@BlakeTerhune In ArcGIS Pro 3.1 Minimal plus custom output fields was added as an option for the Output Fields returned when geocoding the table. You would select 'Minimal and User Fields' as the Output Fields option. Some additional details can be found in the note at the top of the following help topic. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm   -Shana ... View more

@JohnNergeBrooklynPark , Do you know which locator building tool was used to build the participating locators in the composite? If you wanted to limit which match level the addresses are geocoded to you can limit the search to a specific category like Point Address, then no matches are returned at the street level (Street Address, Street Name, Street Intersection). You can specify this in the Category parameter of the Geocode Addresses tool or Geocode Table pane. This is described at step 8 of the following workflow topic https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/convert-a-table-to-locations-on-the-map.htm.   Does this work for your workflow? Can you provide the composite service your county published?   -Shana ... View more

@DanielBorden @ScottFedak2085 , Since ArcGIS Pro 2.6 there has been the ability to specify which street name is returned either the name from the primary data or the matched name, which could come from the alternate name table using the Preferred Street Name property  If the reference data is normalized and the primary table does not contain street name values, but the alternate name table does, the Primary Name Indicator field can be mapped to a field in the alternate name table that contains a value indicating whether the record is the primary name. The Street Name role field must be mapped because it and the Primary Name Indicator value are used to define the Preferred Street Name that is returned when geocoding. If this field is not mapped, the first record in the alternate name table will be used as the primary value. An illustration of the Primary Name Indicator in an alternate name table can be found at the bottom of the following topic https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/fundamentals-of-alternate-name-tables.htm. At ArcGIS Pro 3.1 similar functionality was added for when you have duplicate features in the primary reference data for the alternate street names and you want to specify which street name is the primary name, the reference data must have a field that contains a flag that indicates which street name is going to be the primary name returned when geocoding. This field must be mapped to the Primary Street Name Indicator field from the locator role, such as PrimaryStreetFlag. If the Feature ID is mapped, the Primary Street Name Indicator field is used to define Preferred Street Name of features with the same Feature ID. If the Feature ID is not mapped, each street name from the primary reference data is marked as Primary because de-duplication will not work and each street name is stored independently. (https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/collapse-duplicate-features-in-the-data.htm) If you build the Atlanta locator with the alternate name table from the Create Locator tutorial  you can test the Preferred Street Name settings using the address '30 Atlanta Blvd, Atlanta, 30309', where "Atlanta Blvd" is the alternate name and the street name from the primary data is "Old 10th St".   Please let us know if these settings do not meet your needs. -Shana ... View more

@JasonBritton1  Are you signed into arcgis.com as the active portal or are you signed into your organizations Enterprise portal?  Do you have any additional locators that are automatically loaded when signed into your active portal? What version of ArcGIS Pro are you using? Have you lost internet access when the Locate button is disabled? Are there other portal related buttons that are also grayed out like on the sharing ribbon? ... View more

@jzcgis , Is the Minimal Output Fields option in the Geocode Addresses or Geocode Table tools not working for your workflow? You need to have ArcGIS Pro 2.7 or later, a locator created with the Create Locator tool or Create Feature locator tool and if its a service it needs to be on Enterprise 10.9. The note at the top of the following topic describes what is added to the geocode result and the fields that are returned with the various Output Fields parameter option. https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/what-is-included-in-the-geocoded-results-.htm If you are wanting to rematch your unmatched results with a different locator, that option is available in the Rematch Addresses pane, where you can change the locator as well as some geocoding options like score and categories. See the 'Match with new locator' section in https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/rematch-locations-converted-from-a-table.htm#ESRI_SECTION1_092AD2A116A84598A29BD5639C87AC33 What version of ArcGIS Pro are you using? -Shana ... View more

@WalidAlmasri1 , did you have specific categories selected and not the default of all supported categories? In the current released versions of ArcGIS Pro, StreetMidBlock is not listed as a category you can select in the 'Categories to support' property; however, it is something we are looking into for a future release. Thanks for the update on your situation. -Shana ... View more

@WalidAlmasri1 , Just to clarify, are you saying that whenever you try to search for an address in one of the following street block formats that the Addr_type value returned is not "StreetMidBlock"? 100 block of New York St, Redlands, CA 1600 blk E Cliff Dr, El Paso 200-500 block Taylor St, San Francisco 1700-1900 blk of Locust St, Philadelphia, Pennsylvania   Or are you asking about the reference data to build the StreetAddress role locator? -Shana ... View more

@SheriNorton When you submit the case to Support provide as much info about the creation of the project initially (version of Pro the project created in, number of maps in the project), where the locators are stored that are referenced in the project and everything that you've tried to remove and persist the removal of the locators in the projects. I've not been able to reproduce the behavior in-house, so it would be helpful in finding a better solution/workaround to the issue. The locators added to the project are linked to the maps in the project as you can have multiple maps that have different locators enabled in them. If your project has multiple maps, check the Locate pane provider settings when each map is the active view to see if there are still any references.  ... View more

@SheriNorton , When you remove the older locators from your project do you save the project before refreshing the Locators folder? ... View more

Chelsea: Are you able to provide more details about your locator and data? What is the behavior you are encountering? Which version of ArcGIS Pro are you using? Was your locator built with city, state, zip mapped? Are you entering the address with the zone (city, state, zip) or without the zone?   -Shana   ... View more

Are there any warnings or error messages in the case where you have renamed the exported layer? What version of ArcGIS Pro are you finding this behavior in? In your workflow is your layer configured and you are using the Locate tab of the Locate pane or are  you using the Layer Search tab of the Locate pane?   -Shana ... View more