I changed the proposal at [1] to have "l/min" instead of "lpm". While "gpm" is often used, "lpm" isn't. Rationale: According to [2] "km/h" should be preferred over "kmph" (which is highly discouraged).
Additionally I added "survey:date", which should be included as well. Regarding the count: I'm on the same page as Alberto: I don't see any advantage of having just a count. As a result I'd recommend removing "fire_hydrant:count=#" from the wiki page. If we gonna change the couplings tag naming, we should adapt: https://wiki.openstreetmap.org/wiki/Proposed_features/Dry_riser_inlet The fire_hydrant:type values without "pond" are still unclear to me: How would I tag this one [3] Moreover how useful is "pillar" if there is "dry_barrel" and "wet_barrel"? How would non-fire-fighters or non-local fire-fighters tag such pillar hydrants? [1] https://wiki.openstreetmap.org/wiki/Proposed_features/Fire_Hydrant_Extensions [2] https://wiki.openstreetmap.org/wiki/Map_Features/Units#Explicit_specifications [3] https://upload.wikimedia.org/wikipedia/commons/thumb/6/62/Dry_hydrant.jpg/150px-Dry_hydrant.jpg taken from [4] [4] https://wiki.openstreetmap.org/wiki/Tag:emergency%3Dfire_hydrant#Types On 2017-06-16 19:42, Viking wrote: >> for flow_capacity, should m3/h be preferred instead of lpm ? > Normally, the best unit for fire purposes is lpm (or gpm), because you can > easily determine how many minutes it takes to refill e.g. a 4500 litres fire > engine. Also fire pumps specs are in lpm or gpm. > >> fire_hydrant:coupling_type -> fire_hydrant:coupling:type >> fire_hydrant:couplings -> fire_hydrant:couplings:size > Then couplings, plural: > fire_hydrant:couplings:size = 45;45;70 / ... > fire_hydrant:couplings:type = UNI / Storz / ... > >> for people unable to recognize coupling diameters, is it useful to tag >> their count ? Or this information has no utility ? > Well, I think that inserting only the number of couplings would complicate > the tagging scheme and would have a very little utility. I wouldn't do that. > > Alberto > > > --- > Questa e-mail è stata controllata per individuare virus con Avast antivirus. > https://www.avast.com/antivirus > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
