Latest Contributions by ShanaBritt

@AaronManuel2 You can create a multirole locator using the Parcel role for the PIN and POI role for the owner name. You would be able to search for either PIN or Owner Name. You can also use your original idea of creating a Parcel role locator  for PIN and POI role for Owner Name locator and adding them to a composite locator. Is your goal for the locator to use it for single address/owner name search or for batch geocoding a table? ... View more

@Robin Have you tried with a feature class in a file gdb? What locator are you using to search for places in the Locate pane? What happens at Step 4 if you select 'Create new feature class` that is in a file gdb. ... View more

@ChelseaRozek Thanks for sharing the field mapping and coordinate system of the street centerline data used to build the locator. I see that you have a multirole locator in the screenshot, does it also include any alternate name tables that would be listed on the Alternate Name Tables tab in the locator properties? If there are no alternate name tables that are part of the locator there is no need to map the Street Join ID locator role field. Including the FeatureID role field is only necessary when you have duplicate geometry in the primary reference data that have different attributes like different street names. When you do use the FeatureID field the field  you map to it should not contain unique IDs like the ObjectID field. Mapping the FeatureID field when you do not  have duplicate features with different attributes will increase the size of the locator, impact the time it takes the build the locator, and can affect the performance of the locator. See the following topics for more info: - 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/locator-role-fields.htm The Full Street Name field is also not necessary to map when building a locator for the USA as this field is not used for address matching. 1. What is the Precision type of the locator? This is on the 'About the locator' tab of the locator properties. 2. Have the side and end offsets been modified? This is on the Geocoding options tab > Match options section 3. Is the multirole locator from the screenshot added to a composite? 4. Does the same behavior occur with a single StreetAddress role locator? 5. Is all of the data used in the multirole locator in the same coordinate system? ... View more

Does the locator view you created in ArcGIS Online work in the MapViewer as expected? ... View more

@ChelseaRozek Can you provide me more details about the locator you created and the version of ArcGIS Pro used to build the locator? 1. What is the coordinate system of the street data used to build the locator? 2. Can you provide a screen shot of the field mappings for the StreetAddress role? This can come from the locator properties dialog on the Reference Data Tables tab ... View more

@CRossNSDA When was the last time that you created the locator view in ArcGIS Online and it did not work as expected? The reason I ask is because a member of the Survey 123 team asked the same question the week of July 7th, which was not long after the June update to ArcGIS Online. This issue was resolved by the end of the week and definitely by last Monday. If you create a new locator view in ArcGIS Online that is filtered to just Canada today, are you still getting addresses outside of Canada? Yes, unfortunately, the locator views created in ArcGIS Pro do not work outside of ArcGIS Pro.  ... View more

@CRossNSDA Do you get the same behavior when you create a locator view in ArcGIS Pro? https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/add-a-locator-view-to-a-project.htm Where will you be using the locator view? (map viewer, web app, ArcGIS Pro, mobile) ... View more

@Matt-Goodman @MichaelVolz Just for your awareness modifying the .loz file violates the use agreement and support for locators created with the modified .loz file. Where did you find those steps documented? Was it on Community or Tech Support knowledge article? All that was needed was to remove the following field mappings from the script. { "role_field":"FULL_STREET_NAME", "mapped_field":"LST_CONCAT", "display_field":"LST_CONCAT" } and  { "role_field":"PARCEL_JOIN_ID", "mapped_field":"PropertyID", "display_field":"PropertyID" }    ... View more

@JoshBillings Are you creating a locator for addresses in the USA? If so, not all input locator role fields apply to all countries, but all locator role fields are returned in the output for all countries because the same template is used for all countries and the Create Locator tool only shows the input locator role fields specific to the country the locator supports. What type of information are you trying to display in the District field? If you are going to add a custom output field it has to be unique and cannot be the same name as an existing output field. You could use "_Distric"t or "Districts" or anything that is not "District" as the custom output field name. https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/001001-010000/tool-errors-and-warnings-02776-02800-002791.htm ... View more

@SLouq For those addresses that are placed along the street centerline it sounds like they were matched to the street data and not the point address data. For the addresses in question, check the values in the Addr_type field. This will tell you if the address is a PointAddress or StreetAddress (StreetName, StreetAddressExt) match. If a point for the address does not exist in the point address data to build the locator, then the address will be matched to the street data and interpolated long the line based on the house number range of the street in the data. As far as the format of your spreadsheet is concerned it should look similar to one of the following:     If you'd like for me to take a look at your data, you can send it to me in a private message if you like. I think at a minimum it would be helpful to see the reference tables from the locator properties dialog for both the PointAddress role and StreetAddress role.       ... View more

Thanks for the update @JoeHeggenstaller ! ... View more

@BobBoutiette, it would be helpful to see the data for the problematic addresses and subaddresses to help identify the cause of the behavior you are experiencing. Or at a minimum the Reference Data Tables section of the locator properties for the locator you created for the Point Address role. Here are a few things to check: 1. Ensure that there is a feature for the base address and that it does not have any subaddress values in the subaddress element fields used to build the locator. 2. Ensure that the base address and subaddress have the same city and zip code values. 3. Ensure that the unit type and unit number are in two separate fields and have been mapped to the Unit and Unit Type locator role fields. 4. Ensure that the FeatureID role field was not mapped when building the locator,  unless you have duplicate features with different street attributes. 5. If you enable the property "Show summary of subaddresses with base address suggestion" in the locator  properties dialog, what is the suggestion that is returned for the base address where you had to include the unit type and partial unit number? -Shana ... View more

If you are trying to attach the polygon info to the geocode result, check out the Add Polygon Fields To Locator tool. ... View more