On Tue, Jun 26, 2012 at 7:41 AM, Martin Vonwald <imagic....@gmail.com> wrote: > > Why do I think that maxspeed=signals is a bad idea? Because it doesn't > carry a lot of useful information. The speed limit is especially > important to routing applications. For such an application > maxspeed=signals is no information at all and it might fall back to > the country-specific default limit - and this may (and will quite > often) be wrong.
+1 The place I've seen this is on parts of I-80 in Wyoming where the speed limit is 75 mph but can be lowered in bad weather. Since specific weather conditions are generally out of scope for a routing engine, it should assume you can drive 75 here so that's what I put in the maxspeed tag. The other place where a variable speed limit applies is school zones where it drops to 20 mph. I think I have mapped some of these as: maxspeed=30 mph maxspeed:variable=school_zone It is a bit incomplete as I haven't recorded the lower speed limit or the times during which it applies. But I have captured the maxspeed, the fact that it sometimes varies and the reason for the variability. It looks like I'm the only one to have used this tag so if there is a better suggestion, I am certainly open to changing it. I do see a couple hundred uses of things like maxspeed:summer, maxspeed:children_present, maxspeed:night, etc Toby _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
