[OSM-dev] webservice to collect traffic messages

Floris Looijesteijn osm at floris.nu
Mon Apr 20 16:24:20 BST 2009

maybe also include a (optional) last modified date for the id's so you can
check if they have been changed?

road construction can take a long time.

when osm-er changes the road that might be the new situation.


> Hello,
> I'd like to experiment with Google AppEngine for a bit and
> set up a hosted service to collect traffic messages
> (traffic jams, road obstructions, constructions sites, slow
> moving traffic,...)
> What could be a good data-format for such information, so that
> it is usefull to more then just my own navigator?
> I'm thinking about:
> * required: (enum) event-type
> * required: (string) event-description
> * required: (long) OSM WayID of primary location
> * required: (long) OSM NodeID of primary location
> * required: (datatime) expiration date of the event
> * optional: (long[]) additional affected nodeIDs
> * optional: (long[]) additional affected wayIDs
> * optional: (time) expected delay
> * optional: (string[]) additionalData
> Are OSM nodeIDs and wayIDs a usefull reference for other (OSM-)
> applications
> or shall I add required lat + lon + ref/name -attributes?
> Marcus
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev

More information about the dev mailing list