Le 26. 10. 18 à 01:18, Bryan Housel a écrit : > I don’t like `crossing=zebra` either.<...> iD will support these 2 presets: > - `crossing=marked` which is labeled “Marked Crosswalk" > - `crossing=unmarked` which is labeled “Unmarked Crossing”
thanks for understanding that a issue exist, the first step to solve it :) but I don't understand how the new preset will solve the problem since you put the marking information in the key whose main use is to inform the security of the passage (presence or not of traffic lights) We had 2 incompatible schemas, let's avoid to create a third one :) Without wishing to draw too hasty a conclusion from this discussion, a coherent scheme would be to have : crossing with the usual current meaning (traffic lights or not) crossing_ref with the type of marking (this key might need a better name, but I know that osm is very reluctant to change historically bad names...) It is then enough for the preset to ask: marking on the ground or not ? fill corssing_ref protected by traffic lights or not ? fill crossing if a armchair mapper ignore if the crossing is protected by traffic lights or not, don't fill the crossing key. that 'll allow other mapper to see that the info is not filled and they may act in stead of guessing (is marked used to tell that no traffic lights exist ou that's it's unknown ?) Regards, Marc _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
