Hi,

2017-09-04 10:49 GMT+02:00 marc marc <marc_marc_...@hotmail.com>:

> > I think we should find a solution also for 10% of hydrants that don't
> have a type/pressure/water_source, or we will never have a definitive
> solution.
> > Considering that in some countries pressurized hydrants are not
> distuinguishable from not pressurized ones, I'm starting to think that the
> only way is to revert to the previous approach and define:
> > - hydrant: a device with couplings used to take water, pressurized or
> not. pressure=* will distinguish among them. water_source=* can complete
> the information.
> > - suction point: a place to park the fire engine and put down your hoses
> and pump.
> > I would prefer to have only pressurized hydrants in
> emergency=fire_hydrant, but there are too many cases that can't be easily
> handled.
> > Anyway fire_hydrant:type=pond should be deprecated in favour of
> water_source=pond.
> It look like fine for me.
> what do others think? if somebody find it is not appropriate,
> I think that it would be desirable to split out the "meaning change"
> to validate the rest of the proposal.
>

I agree with the idea to group all water sources under fire_hydrant term.
Nevertheless, as Marc said, the change would be more bearable if voted step
by step
There was proposals completely rejected just because of one or two
particular point without consensus.


>
> Le 01. 09. 17 à 23:08, Viking a écrit :
>  > If we want to remove fire_hydrant: namespace, what's about transform
>  > fire_hydrant:diameter=# in diameter=# ? It is already documented
>  > its use with hydrants: [0]
> yes the prefix in "fire_hydrant:diameter" is bad
> it is not the diameter of fire_hydrant.
> the wiki said it is the diameter of the underground pipe.
> and is this tag well used? I am not able to judge whether values
> are realistic
> https://taginfo.openstreetmap.org/keys/fire_hydrant%3Adiameter
> It look like however that a lot of value concerns the diameter
> of the coupling
> water_source:diameter <> coupling:diameter could make
> confusion impossible
>

water_source sounds like virtual concept, can it have a diameter ?
It would be nicer to deal with "input", not source.
I agree for couplings:diameter.

The same question had been asked in dry riser proposal
https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Dry_riser_inlet#Add_diameter


>  > fire_hydrant:count=# ?
> same question, do we often have several hydrants in the same place
> that are mapped with only one node? or people are mistaken
> and indicates the number of coupling? I have never yet met the case.
> maybe we need to ask mapper that use it.
>

More generally, a current proposal aims to introduce devices=*
https://wiki.openstreetmap.org/wiki/Proposed_features/Transformer_extension_proposal#Transformer_sets

It is actually possible to factorize features with same figures and
functions on a single node, but it have to be well documented in wiki
That's what devices=* is intended for.



>
>  > I would keep these tags as they are now.
> I think it is useful to stop the list of changes otherwise
> it is a work without an end.
>


These changes had been waited for years. A few weeks is an appropriate
delay to improve a bit
This pleasant discussion is a great step IMHO.
Even in "simple" proposal with only a few tags, months are needed to make
all things clear and let everyone test what is proposed.
We need to review everything before voting


All the best

François
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to