michaelcox wrote:I guess I'm a slacker as I have never gone into LDS Maps and done anything with Geocoding.
Actually, we don't do much either, and our stake does not require it.
The reason is simple: The "verification" process in LDS Maps is very labor-intensive -- needlessly so, IMHO -- for too little benefit. Precisely because there is not yet any leadership functionality that uses the LDS Maps data for boundary analysis, HT/VT routes, fast offering routes, emergency preparedness districts, etc., our leaders don't see a good reason to do the work.
We have done a lot of ambitious geographic work for most of these functions at the ward level at various times, but we do it outside MLS and lds.org because we have better tools than the church provides. We used to have a ward clerk who maintained the LDS Maps verification as a labor of love, but that practice lapsed a couple of years ago when we lost him to a boundary split. Today, the nice-to-have feature of simply eyeballing the whole ward on a map online is not sufficiently compelling to justify the effort. Our membership clerks are already swamped with higher-priority duties.
However, in the long run, the church is supposed to be planning (if not actively developing) at least some of the higher functionality I am talking about, which then would make the LDS Maps data an important asset. Right now, boundary analysis uses the ancient "Geo Code" fields in MLS, which are inherently dumb geographically. But my bet is that the migration of the function to lds.org will use the real geocoding from LDS Maps somehow.
michaelcox wrote:I do have 100% of my ward geocoded in MLS. Its pretty easy to maintain once its done. This has always been the one the Stake asks for and its always one of those late Wednesday things that they need done by Sunday morning.
Sounds like somebody is actively contemplating a boundary adjustment.
That's when stakes tend to care about getting this data on a tight deadline. I doubt that many stakes require such near-realtime updating of the MLS "Geo Code" fields routinely.