While reviewing today, I encountered a nomination which had the location correct but the street address wrong.
Tbh, I probably only noticed because I had to go digging to verify the store, a new(ish) nifty local art /craft/book store. While reading up about the store, I realized that the address Google gave for the location matched the location on the review map, but not the street address given by the submitter.
As a data scientist, I can only say “why, Niantic, why would you not catch this error at submission time, and make the submitter fix it?”
Exploring under Accuracy, I realized that I could only reject the submission based on location, not street address.
I decided to take Niantic at their word, as it were (it’s a pretty spiffy shop) and approved it. I can always go back and submit an edit for the address.
Ok, so, wth, Niantic?
What do the rest of you do in these situations? Does it depend (as it did for me) on the overall quality of the submission?
I did see some back context on street address, but it felt all over the place.
The address shown on the review is automated and can cause problems if your nomination is near a junction and you take the image from the other road.
I did have a problem when nominating “The Old Rectory” but as I took the image from the other side of the drive it insisted on “The New Rectory” as the address
At a guess… Niantic / Scopley gets the street names via an API call with whatever accuracy it can attain at the cost they pay Google. This won’t be the fault of Niantic / Scopley, as checking every single street name for accuracy would mean that every nomination could take about 10 or 20 years to appear in our contributions list.
The address data is provided by Google and can sometimes have errors, but that is not a reason to reject the nomination. If the pin is in the correct location and this can be verified to be the case, that’s all that matters.
I’ll have to submit a couple of the wayspots I have been thinking about submitting, so that I am familiar with the flow through the game and through the website.
It isn’t clear to me whether the street address given for the wayspot is entered by the submitter or filled by API.
I’ve run into this with my own submits. The system never asks for an address; the address shown is automatically added. For example I have one recently approved stop that is near the back of a large apartment complex; the address given is actually for a house that is on the next street, whose back yard is against the apartment complex’s back parking lot…. probably because the pin is closer to that street than the one the apartment complex is actually on.
It might be that the street name changed, or is an alternate designation. I have a street in my neighborhood which has both a name and (separately) a county numbered route number. The postal addresses always use the name, but some GPS systems use the route number, and I have had mixed results with submits along that street.
