OK.. I will explain this one at a technical level at least, so you can see why this is happening. (and this actually applies to a few of the relevancy issues you see here)

I believe what you are seeing here is a decision we made on the backend dealing with the geo-coding of addresses from a provider. Based on an address, and piping that to the mapping system, we have confidence levels (hidden from you) that let us know how confident we are in the plotting on the map. If we are lower in confidence, in some cases, we decide to NOT plot based on the thresholds in our system. Check out the example on our web site for the same query you provided..

CLICK HERE TO SEE EXAMPLE: DATA SAMPLE


Notice how it shows an Asterisk next to the address. This means, at least on the web side, we are not plotting because we felt that based on the confidence threshold, we could not plot this accurately. On the mobile side, we err on the side of providing a map, where at least you can get your bearings. This is obviously an example where the plotting on the map did not occur correctly based on the geo-coded data.

Now, with all that said, and not sounding like an excuse, we are always trying to improve the data in the system. This is a prime example (and thanks for providing the details for this) where we can shoot for improvements. As you can see, we are commited to making this work as well as we can for our users. Great feedback like you are all giving on this forum is second to none. You are a great community for honest feedback and we appreciate it.

OK, sorry for the long-winded response.. but i wanted to at least give you an understanding of WHY it was happening. (if you cared enough to read all of this)

Moving on to hopefully a shorter response on the next one.