The proposed system for traffic_enforcement has two premises:
1) The direction is pretty vague - it's defined as a 90 degree arc for
traffic_enforcement
2) The node isn't necessarily on a way - therefore you can't use forward and
backwards as suggested (mobile cams on bridges, for example, aren't on the
way they're checking anyway)
This problem also chimes (with me at least!) with the speed datatype
problem.
Perhaps a new structure for data_type ?
We could define a list of data_types in the wiki such as:
int (all numeric, no dots, commas or whitespace)
float (numeric, with one optional dot)
speed (defined as int and a string one of ("","mph","kmh","knots") )
direction (defined as string one of ("N","NE","E","SE","S","SW","W","NW") )
This would:
1) be easy to check both on entry ("this doesn't match a datatype... are you
sure you meant this?" dialog in JOSM, for example)
2) be a good machine-readable source for not-in-map-features to verify tag
values (requested on the speed discussion)
3) mean that renderers could be more easily coded to deal with the types
specified (rather than having to work out what someone meant by "30 miles
ph")
4) be easy sources for RegExp checking of entered/encountered/output tag
values
Tristan
2008/10/17 Mike Collinson <[EMAIL PROTECTED]>
> At 03:07 PM 17/10/2008, Xav wrote:
> >Hi
> >
> >
> >Some waypoints needs to be described with direction.
> >
> >Some examples :
> > - viewpoint
> > - bus stop
> > - surveillance
> > - traffic enforcement
> >
> >Is it possible to make it consistent ?
>
> Add a tag degrees=xxx where xxx is approximate bearing in degrees true
> north?
>
> Mike
>
>
>
> _______________________________________________
> talk mailing list
> talk@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk
>
--
Tristan Scott BSc(Hons)
Yare Valley Technical Services
www.yvts.co.uk
07837 205829
_______________________________________________
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
