Hi, On Thu, Nov 25, 2010 at 7:32 PM, Tobias Schlitt <[email protected]> wrote: > I'm not sure if it is a good thing to couple additional data to a spot > from scratch. Wouldn't it be better to keep this part open to the user, > so that he can extend it to fit his needs?
User can of course implement another way to represent locations, but there is a quite standard DMS representation that I feel should be provided by the library. Internally the library keeps all coordinates in DD system. Third thing we should probably support is DM. All coordinates we handle are in WGS-84. http://www.sunearthtools.com/dp/tools/conversion.php >> Geocoding is a service for converting human-readable locations to >> actual coordinates (spots). > I'm not sure, if the service based stuff fits into a base component, > depending on its focus. I would imagine that the pure Location component > should only deal with mathematical representations of geo-data and maybe > leave the geo coding parts to a tiein. Geocoding could be a tiein, but generally it is quite a common part of geolocation services on other platforms. I'm sort of following GeoClue as the "reference implementation" here: http://en.wikipedia.org/wiki/GeoClue I would draw parallels between different geocoding services supported in this component and for example different feed modules in the Feed component. > AFAIK Derick has also experience in the geo location area from his > latest work with OSM. So I CC him explicitly to get involved here. Great! Additional contributions and ideas are certainly welcome here. That is after all the whole point of moving the geolocation functionality from Midgard to the wider PHP ecosystem :-) > Toby /Henri
