On Thu, 25 Nov 2010, Tobias Schlitt wrote: > On 11/24/2010 01:03 PM, Henri Bergius wrote: > > Spot > > ---- > > A spot is an actual location on a map. This consists of WGS-84 > > latitude and longitude. Optionally spots may have an altitude, > > timestamp, accuracy and a human-readable description. > > > > Spot should also be able to calculate distance and direction to other > > spots, and to provide a bounding box around them at a given radius. > > > > For display purposes spots also need to provide a way to convert them > > to pretty-printed human-readable coordinates. > > 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?
Additional data in OSM land are called "tags". Which can be on: nodes (points), ways/areas as well as on relations. I think it'd be a good idea to try to follow their data model, so that the points we have can be easily used with (or extracted from) OSM data. > 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. If you want to the maths, things get a lot more complicated. THen you need to deal with different projections and coordinate systems and conversions as well. I would like to see something like that, but I'd rather have that in an extension as it can be quite slow. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug
