Proper use of Unit and Unit Type in Point Address Role
ArcGis Pro 2.5
I was into Create Locators pretty hot and heavy, but in my most recent position, I've not been dealing with locators. What I am dealing with is deploying the ESRI Data Management Solution; I'd like to have a schema for my address points that will be optimal when used with an Address Point Role locator.
The Solution has a field called Unit Type and provides a Domain with entries like APT, Unit etc. It also has a field called Unit ID which presumably would hold a value like A,B or C; 101,102,103 etc. Here is a snapshot of some addresses I'm working with. Unit_Designator is our current field for unit and I added UnitType for this test:
Using the Create Locator tool, I map the fields as shown above to in their respective roles. However when I search for the address 3694 S BLAZING OAK DR Apt A, all it returns is 3694 S BLAZING OAK DR . Out user base typically uses # in front of a unit number like this: 3694 S BLAZING OAK DR #A and at one time (an earlier version of Pro, 2.4.?) that worked. I have never used the unit type field before today.
I must be missing something here as I cannot resolve for a sub unit with an address point role locator. What is considered best practice for an address point schema to support new style locators?
Thanks Shana-
...assign UNIT_DESIG to the 'Unit' locator role field and UnitType to the 'Unit Type' locator role field in the Field Mapping... Check.
Is the reference data to build the locator in a file gdb or SDE? FGDB (at least for now...)
If there is an address id for the base address that links to the subaddresses, it would be good to assign that field to the Address Join ID locator role field in Field Mapping. I'll add one, but given I'm not using a separate table for them, I never thought that to be necessary.
However following your suggestions, I still get the same results:
The labels indicate the House Number, UnitType and UnitDesiginator. These are just a test sample of points and I purposely put Apt A away from the the base address point. Here are the tool parameters I used:
Country or Region USA
Primary Table(s) TestAddressPoints PointAddress
Field Mapping
'PointAddress.ADDRESS_JOIN_ID TestAddressPoints.JoinID';
'PointAddress.HOUSE_NUMBER TestAddressPoints.ADDR_HN';
'PointAddress.STREET_PREFIX_DIR TestAddressPoints.ADDR_PD';
'PointAddress.STREET_NAME TestAddressPoints.ADDR_SN';
'PointAddress.STREET_SUFFIX_TYPE TestAddressPoints.ADDR_ST';
'PointAddress.STREET_SUFFIX_DIR TestAddressPoints.ADDR_SD';
'PointAddress.SUB_ADDRESS_UNIT TestAddressPoints.UNIT_DESIG';
'PointAddress.SUB_ADDRESS_UNIT_TYPE TestAddressPoints.UnitType'
Output Locator C:\GIS\AddressDataManagement\Address Data Management\TestAddressPoints_03
Language Code ENG
Joe:
I mocked up some data based on your screenshot and cannot reproduce the behavior you described. I get match results for each unit whether I use # or Apt as the unit indicator. Below is the field mapping from the locator properties.
Do you get different results when you compare the locators with and without the JoinID mapped?
Well.... I don't know what the difference is, perhaps sun spots? I created a brand spanking new point feature class with 3 points shown in the attribute table below. I get the correct return for each. In fact, I can enter # or Apt for those two with Units and get the correct return...
