You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: dan[at]karran.net [Submitted to the original trac issue database at 2.41pm, Monday, 12th February 2007]
The recent feed from FreeThePostcode is outputting 'lat' and 'lon' tags but they should be 'lat' and 'long'. I suspect many parsers will look for both, but the [http://www.w3.org/2003/01/geo/ W3C Basic spec] says it should be the latter.
Should we be looking to use [http://georss.org/simple.html GeoRSS Simple] anyway?
Cheers. I only noticed this, by the way, because SimplePie wasn't aggregating the FTP feeds properly - it only looks for lat and long at the moment.
The text was updated successfully, but these errors were encountered:
Reporter: dan[at]karran.net
[Submitted to the original trac issue database at 2.41pm, Monday, 12th February 2007]
The recent feed from FreeThePostcode is outputting 'lat' and 'lon' tags but they should be 'lat' and 'long'. I suspect many parsers will look for both, but the [http://www.w3.org/2003/01/geo/ W3C Basic spec] says it should be the latter.
Should we be looking to use [http://georss.org/simple.html GeoRSS Simple] anyway?
Cheers. I only noticed this, by the way, because SimplePie wasn't aggregating the FTP feeds properly - it only looks for lat and long at the moment.
The text was updated successfully, but these errors were encountered: