Absolutely Steva. Better routers make better decisions. But yeah Graeme, my preference would be a router to read live GeoJSON sources, for the most accurate "what's happening on the ground right now" when considering traffic hazards. This is (relatively) easier for websites and smartphone apps than simple car head units.
Baking seasonal hints into OSM, such as access:conditional=seasonal @ (dry_season) (or similar - I'm sure there's a better way) can definitely be done. However we need to consider a lot of factors, such as are these definitely closed reliably each season and by enforced signage, or are closures subject to the prevailing weather conditions. If a road has definitive closure dates we might be able to utilise opening_hours. I tried to start something similar on Victorian Alps seasonal road closures, for example https://www.openstreetmap.org/way/105842220. However these closures are usually described something like "closed to vehicles from Queens Birthday weekend to Cup Weekend" and are proving difficult to describe in OSM tag format without having to upload new dates each year. On Wed, 9 Feb 2022 at 15:18, stevea <[email protected]> wrote: > On Feb 8, 2022, at 8:08 PM, Graeme Fitzpatrick <[email protected]> > wrote: > > Do routers "read" such things as flood-prone, intermittent & seasonal? > > My "quick, off-the-cuff" answer would be: "better routers SHOULD." The > real answer is very much "check your particular router." > _______________________________________________ > Talk-au mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-au >
_______________________________________________ Talk-au mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-au
