[OSM-dev] Relationships - working prototype

[Martijn van Oosterhout]

On 8/16/07, David Earl <david at frankieandshadow.com> wrote:
> One thing I would like to see is a (possibly optional) lat/lon for the
> entity. (To be consistent, this would have its own distinct property,
> rather than a lat=, lon= tag, like a node, but it could be done with
> tags) This means you could have something visually to select in JOSM
> representing the entity, even if the lat/lon doesn't have any
> geographical significance in its own right;

FWIW, I think this is a very good idea. In some games when you work in
the level editor the triggers and other script-type objects also have
coordinates. They don't appear in the game obviously but it's *very*
useful during editing because the trigger object will be in the area
of the objects they manipulate and, more importantly, the editor can
give a visual indication of what triggers affect what objects.

To look at it in OSM terms, that means the turn restrictions would be
near the intersection they relate to and while editing the
intersection you can see them.

So I suggest something stronger: all "restrictions" must have lat/lon
(not optional) and should be returned as part of the bbox request.

Have a nice day,
-- 
Martijn van Oosterhout <kleptog at gmail.com> http://svana.org/kleptog/