Geocoding Address Table with Mulitiple Input Address Fields
Accepted Solutions
The locators created with the Create Locator tool support three address input fields, so if your table has a field with the address and field with the parcel number, you can map both of them in the batch geocoding tools. Below is an illustration using a multirole locator that includes point address, streets, and parcels.
The locators created with the Create Locator tool support three address input fields, so if your table has a field with the address and field with the parcel number, you can map both of them in the batch geocoding tools. Below is an illustration using a multirole locator that includes point address, streets, and parcels.
@ChelseaRozek I think a better solution would be to build the multirole locator that included point addresses and parcels, then set up the table you are geocoding with a single field that contains the full address (380 new york st, redlands, ca) or Parcel ID and use this single field when geocoding the table. You can also use an address field that contains the ParcelID or address (380 new york st) and use the city, state, zip fields, which could be empty for the Parcel ID records. Does that make sense? The following image shows different table formats.
@ChelseaRozek If we use the data from my reply on 12/3/2020 and created a multirole locator that include PointAddress and Parcel role, the input table could look like the following. Then you could use multiple input fields and map Address, City, State, Zip or use single input field and map FullAddress. You could even use multiple fields and just map FullAddress to Address. The same would go for your composite. In both cases you don't need a ParcelID field for input, the parcel is considered the address and does not need it's own input field. If you used the Locate pane to search for the address or parcel PIN you will get candidates back. Is this more clear with the illustration?
In the Geocode Addresses tool the first field to map is called "Address or Place", so the field that you map to it can contain only addresses, only places, or a mix of addresses, places, asset IDs, etc.
Hi @ShanaBritt, Sorry, but I still don't understand the best practice. Your example has addresses, however sometimes we're locating tables without addresses, only parcel PINs like this:
It does work when I geocode, but for best practice, I would want it to match automatically if the table has a "PIN" field. When setting up the locator, "Parcel Name" is required so I assume "PIN" would go under that. However, I don't see an option to give alternate names for "Parcel Name" on that second screen. Should I just put all the alternate names (like PIN, Parcel ID, PID...) under Address?
@ChelseaRozek The new locators do not have an option to specify additional recognized input field names. I'd suggest submitting/posting an enhancement on Ideas thread. Since it's not possible to add more recognized field names for the input field names of the locator, you will have to manually select the field that contains the data (address, parcel PIN) that you want to geocode in the table when using the Geocode Table or Geocode Addresses tool. If you build a multirole locator with PointAddress and Parcel role, the input address field is always going to be 'Address' in the batch geocoding tools.
If you wanted to add recognized field names for input fields, so that Geocode Addresses tool automatically populates the 'Address' input field, create a composite locator that contains individual role locators or a multirole locator and modify the recognized field names for 'Address'. I would also update Region to add 'State' and Postal to add 'zip' , 'zipcode' , and 'zip5', or whatever field name is used for the postal values in your data.
