I know the suggested method is to use Placemaker to reverse code a lat/lon pair to get a WOEID for the postal code. This seems like a hack in the first place. But it also doesn't work for a significant number of lat/lon pairs. For example, consider the lat/lon pair (40.8375565, -73.9985568). This is located in the city Ridgefield, NJ, postal code 07657. When you use Placemaker to do a reverse code, you get the following data:
This is incorrect (different postal code), and this WOEID does not provide access to the town in question. Doing the lookup via Placemaker results in a significant loss of resolution.
Flickr, on the other hand, has implemented this exact method in flickr.places.findByLatLon (http://www.flickr.com/services/api/flickr.places.findByLatLon.html).
When you query this method with the same latitude and longitude, it returns the WOEID for the corresponding neighborhood, which has the town as a parent. This kind of query by latitude/longitude seems basic enough that it should be part of GeoPlanet itself. What is the outlook for adding this feature to GeoPlanet?