Skip navigation
All Places >

Addressing

Log in to follow, share, and participate in this socialgroup.

Recent Activity

jborgion
Click to view contentarcgis Pro 2.4.3   I have geocoded a table of addresses with a multirole locator.  A couple of addresses didn't match so I manually rematched them and something isn't quite right. Two of the addresses are 12800 SOUTH HIGHWAY 111, which is not correct. (See illustration 1)   Everybody knows at that house number the real name of the the highway is… (Show more)
in Addressing
reecekCOT
Struggling with issues of standardizing street type for a dual range address locator. One of the analysts noticed that many records have values of "Parkway" or "PW" instead of "PKWY" which is preventing our locator from finding them. I've spent quite a bit of time searching for a solution and the closest thing I have found is the following link,… (Show more)
in Addressing
jborgion
ArcGIS Pro 2.4.0   In our county we have both incorporated cities as well what we call Metro-Townships.  When creating the street address role with create locators, you are given the opportunity to provide field mapping for Left City, Right City, Left Metro Area, and Right Metro Area.   I have filled in the field mapping fields appropriately but… (Show more)
in Addressing
jborgion
Click to view contentArcGis Pro 2.4.3   When geocoding within an ArcGIS Pro session, it's easy to limit the output fields: The geocoding tool does not have a parameter (yet?) to do this behind the scenes in arcpy.  I could create a list of all the fields I don't want and delete them after the fact, but I'm hoping there may be a way to limit them up front.
in Addressing
KMyers@mesaaz.gov_MesaAZ
I have a composite address locator that has the following participating locators: - Full Address (points) - Street Centerline (for when an exact address match isn't found) - Parcel APN (used when an address field isn't populated) - Historical Parcel APN (when a record needs to be matched to an old parcel number)   I have a dataset with about… (Show more)
in Addressing
jborgion
Click to view contentArcGis Pro 2.4   With the create locator tool, I can create a single role Point Address.  As discussed in Address point role with Units  as well as Provide Units In Suggested Addresses , I'm confounded by the inability to offer suggestions for addresses that contain unit numbers.   But wait, what's this?  A work around?! Yes! Our data has a… (Show more)
in Addressing
jborgion
ArcGIS Pro 2.4.0, ArcGIS Desktop 10.6.1., ArcGIS Server 10.6.1   I'm running into some problems trying to publish locator services and I wonder if I upgrading to Pro 2.4.2 will take of things. (I'm hesitant to upgrade just because I have my python env just how I like it, and I've been holding out for 2.5).   Some of the issues are security… (Show more)
in Addressing
jborgion
Click to view contentArcGIS Pro 2.4.2   I have a multi role locator with point address, street address-alt name and poi-altname roles.  The locator it self works great but I'm getting inconsistent returns when I add it as a published service.  When I use the multi role locator in the locate pane, I get one hit: It's matched on the point address role, and that's… (Show more)
in Addressing
jborgion
For as long as I can remember (which any more isn't that far back) the rule of thumb for creating geocoding locators was to use data that had all the address components in separate fields.  Is that still the case?   For example; if you are matching against centerlines, you want the pre_dir, name, suf_dir & street type all in separate fields. … (Show more)
in Addressing
jborgion
Click to view contentArcGIS Pro 2.4.0   I have created a series of address locators using the ArcGIS Pro create address locator tool syntax in python.  In each of them I set set the enable_suggestions option to 'ENABLE'.  However, when I add any of them to an ArcGIS Pro session, the Use Suggestions check box is grayed out.  Is it possible to actually use suggestions… (Show more)
in Addressing
Load more items