On 2014-03-11 20:23, Ben Laenen wrote : > On Tuesday 11 March 2014 02:21:28 André Pirard wrote: > > NGI rules: > > N#, N##, R#, R##: primary > N###: secondary Not exactly. on the TOP10R map I've shown, N633 (Ourthe), N678, N30 (Beaaufays-Aywaille), N3 (Liege-Germany) are all in red, that's "national", but of different widths. Administrative classification. ... > So, drop all the "making sense" bits in the OSM rules, and we get the NGI > rules :-) > > But the wiki page should be adjusted to get the above rules, as that's how > almost all of Belgium is currently mapped... That's almost fine. But if I look at N674, one part linking N30 and N62 is primary, the next part going west is secondary, *and that makes sense*, But the third part called "route de Méry" is not to be recommended for secondary traffic in my opinion. It's 5 m wide, winding and as a moderate size lorry can be 2.5 m wide, they can hardly cross one another, not speaking of agricultural/farming vehicles that are frequent on that road.
And all those classifications are subject to discussion and hence imprecision. This is why I believe that an *additional* classification would be much beneficial to routing. If the map contained road width, and road surface, routing software can compute altitude and rectitude and it would have *objective* (not subject to personal feelings or any national convention) data to use for optimal routing (as long as mappers can understand that restrictions are mapped for routers to understand and not people). And as road width is the easiest thing to measure on Bing with a JOSM tool, and as road surface is something that someone living no more than 10 or 20 km away knows or can know, Belgium could be optimally mapped for routing in a short time. And OSM routing developers would certainly be happy to use that data. Cheers, André.
_______________________________________________ Talk-be mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-be
