Closed aezell closed 14 years ago
This is expected behavior. We're conforming to the GeoJSON standard, which dictates that we return in lon,lat. Anywhere in the API where we're not conforming to specifications we use lat,lon (which is more widely used).
It's an interesting debate that's been raging in the geo community for quite some time now. Sorry for the confusion. I'll add this to the FAQ.
Thanks for the explanation, Joe. I wasn't aware of the GeoJSON standard. I'll check it out.
Yeah, sorry. We should add this to the docs. GeoRSS is coming soon as well. Actually, it might be in production now (just replace .json with .rss). We'll be supporting a number of GIS serialization standards.
Thanks again! Great feedback!
I created a new record with something like this:
yet, when I query for that record, like this:
the resulting record tells me that the coordinates are:
Is it understood that the first value should be lat and the second lon? If so, then line 58 in init.py (the to_dict method) would seem to be the issue. The values should be reversed: