Open simonw opened 6 years ago
Looks like the API is (incorrectly) PIPing using a deprecated feature's polygon.
That particular feature is superseded, and the new feature's polygon is correctly in SF. The old feature was wrong on several different levels! I don't think we backfilled a new feature polygon there, so I'd only expect Marin to be returned as the init feature hierarchy for that lat/lng.
Deprecated features shouldn't be available for PIPing by default (unless deprecated features are allowed in a request param?).
This is the same problem as https://github.com/whosonfirst/whosonfirst-www-api/issues/63
The short-term solution is to request ?extras=edtf:
and filter on things with a non-null or non-uuuu
(it's an EDTF thing...) cessation or deprecated date.
http://whosonfirst-api.mapzen.com/?method=whosonfirst.places.getHierarchiesByLatLon&latitude=37.8376611&longitude=-122.47937719999999&api_key=mapzen-XXX&spr=1
That's this point here: https://www.google.com/maps/search/37.8376611,-122.479377
That's definitely not in San Francisco, so that first returned hierarchy (around Fort Winfield Scott) appears to be incorrect. I'm not sure if this is an API bug or a data bug or both.