ArcGIS Pro 2.4, Create locator.
In this post, Bryan Lynn describes a problem locating point addresses with units. He experienced it in an Oracle enterprise geodatabase; today I discovered the same problem using a file geodata base. Here are the field mapping parameters I use :
fieldMapping = "'PointAddress.HOUSE_NUMBER AddPntsProtected.ADDR_HN';"\
"'PointAddress.STREET_PREFIX_DIR AddPntsProtected.ADDR_PD';"\
"'PointAddress.STREET_NAME AddPntsProtected.ADDR_SN';"\
"'PointAddress.STREET_SUFFIX_TYPE AddPntsProtected.ADDR_ST';"\
"'PointAddress.STREET_SUFFIX_DIR AddPntsProtected.ADDR_SD';"\
"'PointAddress.SUB_ADDRESS_UNIT AddPntsProtected.UNIT_DESIG';"\
"'StreetAddress.STREET_NAME_JOIN_ID Centerlines.JOINID';"\
"'StreetAddress.HOUSE_NUMBER_FROM_LEFT Centerlines.FROMADDR_L';"\
"'StreetAddress.HOUSE_NUMBER_TO_LEFT Centerlines.TOADDR_L';"\
"'StreetAddress.HOUSE_NUMBER_FROM_RIGHT Centerlines.FROMADDR_R';"\
"'StreetAddress.HOUSE_NUMBER_TO_RIGHT Centerlines.TOADDR_R';"\
"'StreetAddress.STREET_PREFIX_DIR Centerlines.PREDIR';"\
"'StreetAddress.STREET_NAME Centerlines.NAME';"\
"'StreetAddress.STREET_SUFFIX_TYPE Centerlines.POSTTYPE';"\
"'StreetAddress.STREET_SUFFIX_DIR Centerlines.POSTDIR';"\
"'POI.PLACE_JOIN_ID Parcels.parcel_id';"\
"'POI.PLACE_NAME Parcels.parcel_id'"
Notice in line 6 the field UNIT_DESIG is used.
If I use the unit a given address this way, it ignores it:
Where as if I use # in front of the unit designator, I'll get the unit as the secondary hit (B):
Is this expected behavior? We do carry a field called 'FullAddress' that carries the unit with # but I'm not referencing that field at all in my parameters (Notice it's # (space) Z1):
That should just about do it....