I think using flood_prone on places designed to handle water (like a ford) is incorrect. The sections of a freeway that are closed off during flooding (a lane is closed because storm waters cannot properly drain away, or cuttings under train crossings with flood level markers because the road floods - both are flood prone, but their job isn’t to let you cross a waterway.
Fords can be dangerous to cross in storms, but their job is to let you cross in the presence of water. The flood prone areas are not designed to let you cross a river, they just end up being flooded because of inadequate drainage. a ford https://goo.gl/maps/aBWlg <https://goo.gl/maps/aBWlg> flood prone (with a warning sign with lights when it is flooded) https://goo.gl/maps/9aFXV <https://goo.gl/maps/9aFXV> doesn’t seeing a ford automatically mean it’s flood prone? it handles river crossings ^_^ Javbw > On Jan 20, 2015, at 8:38 AM, johnw <jo...@mac.com> wrote: > >>>> Some part of road have >>>> concrete parts that are flood_prone during cyclone. >>>> >>>> How can we (or not) extend it to roads? >>> >>> >>> access:conditional = no @ flood >> >> I'm using flood_prone=yes. With surface=concrete. >> >> But I was looking for some method to unify intermittent aspects of rivers >> and roads that are related when roads are crossing river or vice versa. > > > > the ford=* key might be useful. They suggest to also tag depth=0 if it is > usually dry year round. I think this is the tag you are looking for, > especially since the road section is designed to be submerged (the concrete > sections) which means it is a ford (as emergency or very large vehicles, like > a bulldozer, could still cross on the road). > > > In San Diego, there are several large roads that are built with fords, as > access lost during flood conditions is merely an inconvenience. > > I think this applies to any roadway *designed* to let you cross a river by > going through it, even if it is low/dry most of the time (otherwise, > floodwaters would easily destroy the crossing). > > Also, because of the wadi problem, i will be making up a new “wash” proposal > - as it seems wadi is completely generic now. > > > Javbw > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
