When rematching geocoding results, a user notices that E St Is being interpreted as East St. How snould a user resolve this Issue for future geocoding?
Option B is the way to go. Rebuilding the address locator with new reference data is the only way to ensure the issue is fully resolved. Anything else is just a band-aid, and we all know how well those work in the real world.
Haha, I bet the person who wrote this question is laughing at us right now. 'E' for east, seriously? That's like naming your kid 'U' and expecting everyone to know it's pronounced 'you'. Option D all the way!
I'm leaning towards Option C. Creating a composite address locator that doesn't recognize 'E' as 'east' sounds like a more robust and future-proof solution to me. Who knows what other abbreviations might cause issues down the line?
Option D seems like the easiest solution. Why go through the hassle of recreating the address locator or messing with the XML files when you can just fix the input table? Simple and straightforward.
Option D seems like the easiest solution. Why go through the hassle of recreating the address locator or messing with the XML files when you can just fix the input table? Simple and straightforward.
Carma
1 months agoLang
1 months agoBea
9 days agoSamira
1 months agoLaura
7 days agoIlene
13 days agoDaren
14 days agoShantay
2 months agoDong
9 days agoCelestina
14 days agoTu
16 days agoIlda
17 days agoDottie
1 months agoLouvenia
1 months agoGennie
2 months agoAdelle
2 months agoMarci
2 months agoBen
2 months agoWillard
2 months agoMee
2 months agoCheryll
3 months ago