nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro Geocoding Bug

JasonBritton1

Hey everyone! I encountered an issue with two different custom built, single field address locator failing in ArcGIS Pro yesterday. One uses address points as its reference and the other uses 911 Centerlines as a reference. I then tried them in ArcMap and the both worked. Anyone else having a similar issue?

Thanks!

Find more posts tagged with

Accepted answers

All comments

SharonSchulte

I did some testing with our address locators and they do need to reside just in a folder. Also, in ArcMap, we could pull in any tables that had spaces in the table names (like in excel). In Pro, table names have to be clean, no spaces or character. Once I tested this, the locator worked without needing rebuilt.

JasonBritton1

They worked fine. They still work fine in ArcMap. Which sucks because I'm trying to quit ArcMap...

mvolz47

Were these address locators working before yesterday?

JasonBritton1

ArcGIS Pro is 2.1.2

ArcMap is 10.5

The locators are stored in folders on a local server.

KoryKramer

What version of ArcMap?

What version of Pro?

Are the address locators stored in a geodatabase or file?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.