Last modified: 2011-03-13 18:06:19 UTC
As reported on the discussion page of the Semantic Maps extension (see URL, Jeroen is aware of the bug, this bug report is so that I can keep track of the bug): The {{#geocode}} parser function doesn't acknowledge that this is a correct input format: N 51° 09.167 E 004° 58.484 When I use it unaltered together with {{#display_address}} or {{#display_addresses}} then it works, however. I just can't get {{#geocode}} to accept it and thus I can't save it as geographic data for SMW. Thus I am unable to build queries with Semantic Maps that display the pages on a map. How come that these GPS coordinates are not valid inputs for {{#geocode}} and how can I fix this?
I see that this bug is now assigned. Since we have been talking about the different formats like DMS ("Degrees, Minutes, Seconds"), DM (Decimal Minutes) and so on, I asked the guy who runs http://boulter.com/gps/ about his code, who has a very reliable parser that takes almost everything. He released his code for it at http://github.com/boulter/GPS-Coordinate-Parser - have a look, it might be of help to you.
Maps 0.6 will suport passing coordinates to #geocode. However, the GPS coordinates type will not be supported. The supported ones are DMS, DD, DM and floats, both directional and non-directional. I might later on add the GPS format though.
The architecture of 0.6 allows for this to be added pretty easily, but there is no demand except for this bug, so wontfix for now.
