correcting unit boundaries shown in lds.org "maps"

How might we go about correcting the boundaries shown in "maps" for two of our units? While looking up some member location information during a stake meeting, my stake president noted that two ward boundaries are incorrectly drawn in the "maps" section.

I am the stake clerk. Who should I contact to go about correcting the boundaries?
thank you

I've been told the only way to change this is to submit a boundary change request... the official document.

wow, ok... thanks

I don't know colbyj, and as far as I know, we're not in the same unit, but I'd like to try reposting colbyj's question, but possibly in a different format. :

When looking up addresses on the map, I note that addresses across the street, that are not in our ward, come up showing that they are in our ward. The street numbering sequence is very basic and simple in Brigham City. I would think there is a way to correct the logic in the church mapping system to reolve the issue without submitting a boundary change. I'm not looking for a boundary change, only a correction on the maps for the sake of those looking for the correct unit related to a specific address.

bishopbarber wrote:I would think there is a way to correct the logic in the church mapping system to resolve the issue without submitting a boundary change. I'm not looking for a boundary change, only a correction on the maps for the sake of those looking for the correct unit related to a specific address.

So are you saying that the boundary is correct, but the Church's system is incorrectly determining that an address is on the wrong side of that boundary line? Because that would be a significant problem that should be fixed in the system -- it wouldn't be related to your particular boundary, but would be a bigger issue.

But if the boundary line is incorrect, then it has to be changed by submitting the boundary change paperwork. There's simply no other way to do it.

Grrr. By the time I typed my reply, the system had autologged me out...

Yes, I am saying the Church's system is incorrectly determining that an address is on the wrong side of that boundary line.

However, upon further testing, I note that inputting a correct address yields a correct response. Inputting a "guess" that is not correct, but in the correct numbering sequence for that side of the street, it shows the wrong ward.

Example: 475 E 600 S shows Brigham City 11th ward. 473 E 600 S shows Brigham City Mountain View Ward. 335 E 600 south shows 11th ward. 337 E 600 S shows Lake View. Odd umbered houses are all on the 11th ward side.

I realize this is a little picky, but the issue came to our sttention when we received a membership record with an "estimated" address that was actually in the 11th ward, but because it was looked up using what they thought was a correct address, it was sent to our ward. Hope I'm making sense..

Why does this silly system kick me out so quickly?....?

We have the same issue in our stake and were told to submit a boundary change request too -- the same paperwork required to actually change a ward boundary. It seems odd that the only way to update the online map to reflect the original boundaries is to submit a request that would eventually go across the First Presidencies desk. It only affected a few houses so we decided to let it be.

bishopbarber wrote:Why does this silly system kick me out so quickly?....?

If you go to a church site with "http" and not "https", you'll be kicked out. (Yes, it's a pain.)

Arrgh... I'm in https://tech.lds.org/forum..... Still drops me like a bad investigator..

It makes zero sense to request a ward boundary change if no boudaries need changing. This appears to be a bug in the addressing system of the lds maps application. Address rules, especially in Utah, are generally pretty basic and should easily be coded into the search parameters.

bishopbarber wrote:Arrgh... I'm in https://tech.lds.org/forum..... Still drops me like a bad investigator..

But if you go to maps.lds.org and don't use https *poof*

bishopbarber wrote:It makes zero sense to request a ward boundary change if no boudaries need changing.

It's a procedure to make sure it gets to the right people.

bishopbarber wrote:This appears to be a bug in the addressing system of the lds maps application. Address rules, especially in Utah, are generally pretty basic and should easily be coded into the search parameters.

Well, except I doubt if the church is "programming" it. It's probably coming from some type of GIS system that gets confused when it's given an address that doesn't really exist. To hand program that stuff in this day and age is silly. It's cheaper to buy a detailed database.

The issue in my stake is that ward assignments of an Apartment Complex were made in 2005 when the Apartments were assigned to our stake. Current membership assignments made by the Church Mapping system have been sending records to incorrect units in our stake. Of the 26 apartment buildings in this particular complex, only 11 are correctly assigned by the 'map' system. Can I submit a list of apartment building addresses and their correct ward assignment (with incorrect and corrected unit numbers) to have this fixed in CDOL?

DWMoore46 wrote:Can I submit a list of apartment building addresses and their correct ward assignment (with incorrect and corrected unit numbers) to have this fixed in CDOL?

You can call Local Unit Support and see if they'll accept that information. I suspect the system is geo-location based - meaning that both your unit boundaries and their "address to location" mapping software have to be current for things to work properly.

It's possible you'll have to submit a boundary change in bl.lds.org to make sure the lines cut through that complex correctly.

DWMoore46 wrote:Can I submit a list of apartment building addresses and their correct ward assignment (with incorrect and corrected unit numbers) to have this fixed in CDOL?

You can, but you need to tie it to the latest boundary change and inform them that the boundaries have been improperly mapped. If there has been no formal boundary change since 2005, and the units involved have just divided up the apartment complex on their own, you will need to submit a formal boundary change request with all of the statistics.

If there was a formally approved change, and the map is wrong, you will only need to submit the corrected map (or in this case, list of apartments) and ask them to correct the "boundaries".

Best case, and hopefully, your list of apartments and units corresponds with the list of apartments and units in the latest boundary proposal that was approved by Church headquarters. If it does, it will be a simple matter of correcting the database.

I'm curious whether the system looks at apartment numbers at all. In my stake, there are four wards that cover my apartment complex. The whole apartment complex has the same street address, and apartment numbers are appended to the street address. We often have records transferred into my ward for people who live in other wards in the apartment complex – my ward starts at apartment 1. I figured it was because whatever mapping system they're using doesn't have enough information to put apartment numbers on a map (even Google Maps doesn't map specific apartment numbers, just street addresses, so all apartments are mapped to the same spot).

Obviously there's a record of which apartment numbers are in which ward somewhere (for example, on the original boundary proposal) but I don't know if these are accessible to the mapping / record transferring database.