We had this situation last year, when Flanders (northern part of Belgium) decided to change the speed limit from 90 km/h to 70 km/h. Brussels and Wallonia kept the default on 90 for rural roads. Not only was this for a part of the country, but many roads already had signs for maxspeed 70 or zone 70 before the change. So we had to change the source:maxspeed as well for all roads, to indicate that it is now on regional level. Some roads that were 90 remained 90 after the official changes, but got (or already had) signs.
So many more changes were needed than just retagging roads with source:maxspeed=BE:rural from 90 to 70. regards m On Wed, Jan 17, 2018 at 12:33 PM, Martin Koppenhoefer <dieterdre...@gmail.com> wrote: > 2018-01-16 23:03 GMT+01:00 Kevin Kenny <kevin.b.kenny+...@gmail.com>: >> >> ...I've never tried to tag any of that sort of regulatory information, but >> I can imagine that applying it to all the streets in the town would be both >> tedious and unmanageable (the latter because if the town were to change the >> ordinance, it would mean updates to many hundreds of highway segments). > > > > > While I agree it is not the perfect solution, we are trying to deal with > similar provisions (default implicit maxspeed by context) through additional > tags which refer to the legislation. E.g. we add explicit maxspeed tags to > roads inside settlements where the maxspeed is implicit (within the city > limit signs), and add source:maxspeed tags (e.g. value IT:urban in this > case) for the unlikely case, that the law changes, so we can automatically > select all ways with this referrer and change their maxspeed in one go, > without needing to care for signedposted maxspeeds with the same value > (because they should have source:maxspeed=sign or maybe nothing). At least > this is the theory, so far we haven't needed it. > > Even if your regulations are not national or by the state but only in your > county or township, you could add some additional tag that refers to the > ordinance, so if it changes you can change all those cases in one go. > > Cheers, > Martin > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
