Latest Contributions by ShanaBritt

@Ragavi , have you tried specifying the category as Street Address, which will return a candidate at the street level? For example: https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=37%20Dover%20Street%2C%20SUMMER%20HILL%2C%20NSW%2C%202130&category=Street%20Address&outFields=addr_type&f=json&token= The other options is to specify the locationType as 'street', but if only rooftop location coordinates are available for an address, the rooftop geometry will be returned for the geocoded address even when locationType=street is requested. It looks like for the address in your example only rooftop coordinates are available in the data for the World Geocoding Service. https://geocode-api.arcgis.com/arcgis/rest/services/World/GeocodeServer/findAddressCandidates?address=37%20Dover%20Street%2C%20SUMMER%20HILL%2C%20NSW%2C%202130&locationType=street&outFields=addr_type&f=json&token= More info about locationType parameter can be found on this page, https://developers.arcgis.com/rest/geocode/api-reference/geocoding-find-address-candidates.htm.   -Shana ... View more

@JuneAcosta What happens when you search for an address with a unit? Are you trying to get suggestions for all of the units at the address? If so, you must have a record in your feature class for the address w/o any unit info in the UnitID and UnitType fields. Review the subaddress suggest options to know which setting you want to use in the locator properties. The 9 digit zip code should be broken up into multiple fields, the 5 digit in one field and the zip4 in a separate field. Try the following field mapping when building the locator House Number = ADDRNUM StreetName = STREETNAME Suffix Type = ADDRNUMSUF City = MUNICIPALITY Unit = UNITID Unit type = UNITTYPE State = STATE Zip = field with 5 digit zip Zip4 = field with zip4 values ... View more

There are no custom roles for the Create Locator tool. What value would be in the field for "building entrance"? Would this value be used for search or part of the output in the geocode result? ... View more

Are you geocoding with your own custom locator or the ArcGIS World Geocoding Service? Which tool are you using in ArcGIS Pro to geocode with? If you wanted to search for the block the input would need to be in the following format, "700 block of Peachtree St NE, Atlanta, 30308". ... View more

What was the procedure used to geocode the table? Add item or drop the table on to the map? ... View more

Could you provide an example of the input address and what the reference data used to build the locator looks like for that address? ... View more

@SheriNorton Is creating a locator to search for the parcel number not an option for your organization?You could use the Create Locator tool with the  Parcel or POI role or Create feature Locator to build a locator that is saved with the project or published as a service and added as a utility service to the active portal ArcGIS Pro is connected to. Adding it as a utility service means it will be available to everyone that has privileges to the service when signed into the portal. Another option is to configure the parcel layer for search as a locate provider and create a project template from the project that references the parcel layer. ... View more

@ShaundaDevenport The definition query is done at the layer level in the layer properties of the reference data used to build the locator. It may be beneficial to do this in a model so that you can keep track of the query used when building the locator. 1. Create the definition query in the layer properties 2. Create the locator with the Create Locator tool in ArcGIS Pro. The definition query details are not part of the locator properties.   -Shana ... View more

@RonnieRichards , Thanks for the additional info, however, I still do not know what the reference data used to build the locator looks like and it seems like I am missing some other details about the composite locator. Based on the info you have provided the address "4791 PELL DR STE 1" does not exist in your reference data, so the next best match is to the base address of "4791 PELL DR", where 'Ste 1' is ignored and may possibly show in the ExInfo output field as a part of the string that was not used or could not be matched to any part of the address. Since "4791 PELL DR" exists in the data the input address matches every other part of the address when 'Ste 1' is ignored. This is expected behavior. If you set the Out Fields parameter to all (asterisk) in the findAddressCanidates REST request you will get all of the output fields from the locator, which includes the ExInfo field. Does the composite contain the same locators that references the same data with just Subaddress category disabled or enabled? What is the Result Order used by the composite? Does your data contain any subaddress features? If not, any input address with a subaddress will get matched to the base address if it exists in the reference data. What version of ArcGIS Pro and Enterprise are you currently using? -Shana ... View more

@JohnNergeBrooklynPark The only other option would be to create a multirole locator instead of a composite locator. After looking at the contents of the composite, the creator may need to combine the two datasets that would use the PointAddress role and the two datasets that would use the Parcel role, then the Category parameter would be available to you.  Below are the participating locators of the composite service that is available from your source. If they are unable to merge the data together, then they will continue to create composite locators. "locators": [ {"name": "HC_POINTS_ADD"}, {"name": "METRO_POINTS"}, {"name": "HC_CENT_THEOR"}, {"name": "METRO_CENT_CTU"}, {"name": "METRO_CENT_POS"}, {"name": "ECNdata"}, {"name": "HC_PARCEL_PID"}, {"name": "HC_POINTS_PID"} ], related resources: https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/tutorial-create-a-locator-with-more-than-one-dataset-of-same-role.htm https://pro.arcgis.com/en/pro-app/latest/help/data/geocoding/combine-multiple-layers-into-a-single-locator.htm -Shana ... View more

Thanks @ScottFedak2085 , I really appreciate feedback. 😊 ... View more

@JohnNergeBrooklynPark My screenshot shows the Category parameter, but my locator is not a composite. The parameter does not show for you in 3.0.3 because it is a composite; however, it does show in 3.1, but is not working as expected. This is the issue that we are aware of and looking to fix in an upcoming release. Once the Category parameter is available for composite locators, you will be able to specify that you only want PointAddress matches returned. ... View more

@JohnNergeBrooklynPark Thanks for the service, it looks like the participating locators were created with the Create Locator tool in ArcGIS Pro. Which version of ArcGIS Pro are you using? Below is from ArcGIS Pro 3.1, which shows the Category parameter I was speaking of earlier when using a non-composite locator. This is what you should see in the tool when using a composite locator; however in some versions of ArcGIS Pro the parameter is not showing up or is just a blank box. This is something we are aware of and looking to resolve in a future release of the software. The category parameter will give you what you are looking for, you check the boxes for the categories you want returned ( the match level the search is limited to). You will get candidates that are only Point Address matches for example.   ... View more

@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