Temporary (mid-term) closure for forest-fire not allowed? - eviltoast

Hey guys.

There’s a highway that connect the coast to inland, and without it drivers have a 4-hour detour. It has been closed for the past month while a forest fire has been fought by lots of fire crews. It’s been burning since August 15th, so over a month now actually.

They’ve finally mitigated the fire enough that they are temporarily re-opening the highway, however it’s remaining closed 8am - 4pm Mon-Fri so that the firemen are not blocked by congestion. When it’s not closed between those hours, only 1 lane is open and traffic is led by patrol cars. There is no ETA for a full re-opening.

I went to go apply a condition, when I realized that no one had actually closed the road in the first place. So I added something like “conditional=no @ (Mon-Fri 8:00-16:00)” (I forget the exact syntax).

A day later, someone came in and reverted the change saying “the consensus is that only changes lasting 3 or more months should be made. There are people who download these maps for offline use. So no temporary closures.”

But, the DOT of both states this fire is affecting are begging drivers to stop using GPS to the coast on this route - people are driving into active fire zones.

Does concession for offline users actually supersede safety?

  • pootriarch@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    i am not sure it’s a flaw at all. the conditional tag syntax is based on opening_hours, which should be able to express ‘closed at these times until that date’. there are ways to finesse this. but as long as the published guideline is ‘don’t do this’, there’s little point pondering practical solutions.