Talk:Proposed features/Dry riser inlet
Ad Tagging: relation
A relation with the corresponding outlet (could be a fire_hydrant:type=wall) on a different level of the building could help to explicitly define where the dry riser goes.
- Why can't we link inlets with outlets with man_made=pipeline ?
- A relation wouldn't force us to know the whole indoor pipeline circuit prior to map it, but it may be hard to maintain. Fanfouer (talk) 22:02, 5 April 2017 (UTC)
- I have looked at actual usage and while fire_hydrant:diameter=* is currently used 365.000 times, the simpler key diameter=* is used only 10.000 times, so I will go with the more established tag. Also, the key diameter is not well defined (it doesn't specify if this is about the nominal (inside) diameter of the actual (outside) diameter. --Dieterdreist (talk) 08:14, 6 April 2017 (UTC)
- Wouldn't be the occasion to improve diameter=* instead of letting it down ? I think overused fire_hydrant namespace is a bad thing and according to you, it should be encouraged because people use to use it.
- Diameter can be read on the hydrant itself and it's not about inner or outer side but about standards, which depend on location or hose coupling type at least
- Finally, fire_hydrant:diameter=* isn't precise about which side it describes. Fanfouer (talk) 20:57, 6 April 2017 (UTC)
Hydrant Typ better than emergency=
emergency dry_riser_inlet is very bad. It would be better to take a Hydrant attribute. The reason. In the area the difference between the hydrant and the dry user inlet is often 500m or more. All the fire apps including openfiremap and osmhydrant can find that. So that way is unusable.