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)
I'm happy to see that you aligned additional tags with new hydrants tags. According to this approach, I suggest you to explain that in couplings:diameters=* you should insert each coupling diameter, separated by semicolons and always specifying the unit of measure (e.g. couplings:diameters=45 mm;70 mm;70 mm). Normally use mm, for inches use ". In some countries characters A, B, C are used to specify the connector size instead of its diameter. --Viking81 (talk) 23:43, 16 November 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.
- I am sure that all the fire apps will catch up and use the new tag as soon as it is used. These are not "hydrants" because a hydrant is a place where water comes out, not where it goes in.--Dieterdreist (talk) 08:16, 6 April 2017 (UTC)
Number of connecting pipes
What is the best way to give the number of connecting pipes for a given inlet?
capacity=* or subset would be good, wouldn't it ?
The same question can rise for the maximum flow allowed in the inlet.
This question can be shared to ongoing proposal for fire hydrants.Fanfouer (talk) 10:49, 21 August 2017 (UTC)
A Dry Riser is Not A Hydrant
A hydrant is a source of water, whereas a Dry Riser (Inlet) is where you have to pump water in - to reach upper floors of a building.
There are also Wet Risers, which are kept full of water so you don't have to wait for them to fill before you can use them. Diagrams and explanations here:
I think this is a really important point. I can see a data consumer knowing about the fire_hydrant key but not dry_riser_inlet, and these ending up getting mapped as regular fire hydrants. This could cause an actual safety problem.
Pressure and flow rate
Nominal pressure and nominal flow rate could be specified if known.
In Italy for example on dry risers signboard sometimes there is written the maximum working pressure.
I think that pressure=* tag could be used, because for a dry riser nominal pressure could be intended as its maximum working pressure.
Similarly flow_rate=* tag could be used for nominal flow rate.
--Viking81 (talk) 23:29, 16 November 2017 (UTC)