Meetinghouse locator map lookup seriously broken.

Discussions about the Maps Tool on lds.org.
rpyne
Member
Posts: 227
Joined: Fri Jan 19, 2007 1:13 pm
Location: Provo, Utah, USA

Meetinghouse locator map lookup seriously broken.

Postby rpyne » Mon Aug 29, 2011 4:39 pm

I have run into this problem several times and it create a serious problem when trying to direct someone to their correct ward.

The address look up makes assumptions and changes the address to what it thinks might be correct.

For example, try to look up the ward for 90 S 400 E, Provo, Utah 84606. The Meetinghouse Locator changes the address to 90 N 400 N, which is in a completely different ward.

Google Maps and USPS Zip Code Lookup both correctly recognize 90 S 400 E.

crislapi
Senior Member
Posts: 1265
Joined: Mon Jul 07, 2008 3:05 pm
Location: USA

Postby crislapi » Mon Aug 29, 2011 7:24 pm

rpyne wrote:The Meetinghouse Locator changes the address to 90 N 400 N, which is in a completely different ward.

Some address errors may be due to new streets, etc that are not in the map system maps.lds.org uses. However, your error is worse - that address is impossible. Have you sent feedback to the developers?

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Mon Aug 29, 2011 9:28 pm

crislapi wrote:Some address errors may be due to new streets, etc that are not in the map system maps.lds.org uses. However, your error is worse - that address is impossible. Have you sent feedback to the developers?


I think he meant 90 N 400 E, which is a possible address, and is what I get when I enter 90 S 400 E. But it's still wrong.
Questions that can benefit the larger community should be asked in a public forum, not a private message.

rpyne
Member
Posts: 227
Joined: Fri Jan 19, 2007 1:13 pm
Location: Provo, Utah, USA

Postby rpyne » Mon Aug 29, 2011 11:01 pm

aebrown wrote:I think he meant 90 N 400 E, which is a possible address, and is what I get when I enter 90 S 400 E. But it's still wrong.


Yes, that is what I meant.

It is not due to new streets in the map system, These streets have existed for well over 100 years (my ward which is only a few blocks south celebrated our sesquicentennial 10 years ago).

User avatar
Mikerowaved
Community Moderators
Posts: 3132
Joined: Sun Dec 23, 2007 12:56 am
Location: Layton, UT

Postby Mikerowaved » Tue Aug 30, 2011 3:09 am

I've run into this as well. On one occasion, I entered a "properly" formatted Utah residential address (including ZIP) and it took me to an entirely different STATE. I forget which one, but I remember it was somewhere on the East Coast. It took me several tries to purposely mangle the address so it would finally be recognized by the Meetinghouse Locator for what it was. Most addresses I enter are fine, but once in a while it really gets confused.
So we can better help you, please edit your Profile to include your general location.

User avatar
ffrsqpilot
Member
Posts: 247
Joined: Fri May 09, 2008 7:51 am
Location: Montrose, Colorado

Postby ffrsqpilot » Wed Nov 16, 2011 4:21 pm

Is there indeed a problem with the Meetinghouse locator program in LDS.org?

I ask this question because one of our unit's clerks had problems giving a member the correct unit that they would be moving into. The clerk in question used the meetinghouse locator map to find the proper unit for an address in Richfield, Utah. The new address was used but the wrong unit was identified. I tried on my own computer and ended up with the same results - address not matching the unit correctly. I then tried an old address that I lived at in Oregon and while locating the correct street on the map it put me in a unit that was miles away. However, when using the locator feature for my current address in Colorado it correctly identified my home ward. So somewhere along the line there seems to be a disconnect between what the mapping feature thinks is the correct meetinghouse and what the actual correct meetinghouse should be.

Is this something that the progammers are looking into or just one of the issues that we will have to live with?

russellhltn
Community Administrator
Posts: 20777
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Wed Nov 16, 2011 5:13 pm

That seems to be a two-part question. First, where does the map think the new address is physically located? No geocoder is perfect. If it places it wrong, it's going to point you to the wrong ward.

Second, is the boundaries for the unit in question accurate?

I doubt if there's a widespread issue, but I'll bet there will always be issues somewhere in the world between the geocoder and a boundary error.
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

crislapi
Senior Member
Posts: 1265
Joined: Mon Jul 07, 2008 3:05 pm
Location: USA

Postby crislapi » Thu Nov 17, 2011 9:53 am

FFRsqpilot wrote:The clerk in question used the meetinghouse locator map to find the proper unit for an address in Richfield, Utah. The new address was used but the wrong unit was identified. I tried on my own computer and ended up with the same results - address not matching the unit correctly. I then tried an old address that I lived at in Oregon and while locating the correct street on the map it put me in a unit that was miles away. However, when using the locator feature for my current address in Colorado it correctly identified my home ward.

Reiterating what has already been said, it comes down to 1) either the program not recognizing the address, so it is just going off the city and/or zip or 2) There is confusion somewhere on what the boundaries really are. Can you actually see the street/intersection on the map? If you can see ward boundaries, is the address inside the correct boundaries but the system is telling you it is another?

I would suggest using lds.org feedback. Set "Regarding" to maps and meetinghouses. For the message, give them the specific example(s) you tried so that they can duplicate the problem on their end.

davesudweeks
Senior Member
Posts: 550
Joined: Sun May 09, 2010 8:16 pm
Location: Owasso, OK, USA

Postby davesudweeks » Thu Nov 17, 2011 11:30 am

We recently moved a less-active family to an adjacent ward who had been at the edge of our ward for some time. They showed on the LDS Map function right on the edge our ward boundary. They showed in the same location on Google Maps and Bing Maps. There were some distance away so I had not taken time to drive out to their home to verify their location.

In discussion with the HPGL, I learned that when you actually go to their home, the road turns south into the adjacent ward and that is where their home is. I moved their pin, then transferred their record and sent a note to the other ward clerk warning him that LDS Maps may again incorrectly show them in our ward. A later check revealed that LDS Maps again incorrectly shows them in our ward boundary.

The lesson? Systems are not perfect and sometimes they make errors. It's still much, much better than what we had before!

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Thu Nov 17, 2011 11:46 am

davesudweeks wrote:I moved their pin, then transferred their record and sent a note to the other ward clerk warning him that LDS Maps may again incorrectly show them in our ward. A later check revealed that LDS Maps again incorrectly shows them in our ward boundary.


There was no reason to move their pin just before transferring the record, since pin locations get reset when a record is moved. What this shows us is that the other ward clerk has not moved the pin to match the actual location. He really needs to do now what you did just before you transferred the record out.
Questions that can benefit the larger community should be asked in a public forum, not a private message.


Return to “Maps”

Who is online

Users browsing this forum: No registered users and 1 guest