Kovoschiz's Comments
| Changeset | When | Comment |
|---|---|---|
| 84964401 | As for the the definition of `junction:ref=`, I must also point out that I observe the use of `junction:ref=` for entries as well. Clearly, there's something ambiguous about the tag that deserves a critical and productive treatment. |
|
| 84964401 | Let me ask in another way, if I add `junction:ref=` to numbered intersections and traffic circles, would you oppose? |
|
| 84964401 | So I don't see why would you are eager to remove a harmless tag that obviously means something. |
|
| 84964401 | "You can add whatever keys you like, but they are of no use if no other user has the faintest idea what they might mean."
|
|
| 84966552 | This leads to EHC only.
|
|
| 84956811 | The restaurant should be in the mall below. This may look misleading, but you don't need to worry too much about it. You can choose "can't answer" in the app to leave a note. |
|
| 84964401 | I don't see how using `motorway_junction` as the key, that exists in the value of `highway=motorway_junction` would be a problem either. |
|
| 84964401 | I didn't change `junction:ref=`. I add a new tag for the time being to clarify its use locally. It would be misapplied here, as a "junction" can have multiple exits associated with it. |
|
| 84964401 | The proposal itself seems self-contradictory on "Why not deprecate motorway_junction?" and "Why name it junction:ref?" as well. |
|
| 84964401 | Hi. This is to confirm the tag refers to highway exit in the context of `highway=motorway_junction`. In many jurisdictions around the world, only exits are numbered, not the entire junction. It is meaningless to use `junction:ref=` here. Moreover, I find the use of `junction:ref=` dubious, as its proposal (now at undefined status) focusing on exits conflicts with the more established `junction=`. This definition also impedes its use on ordinary roads with named junctions but with no numbered exits. |
|
| 84956811 | This is a restaurant object, and this "name" should be a "description".
|
|
| 84938267 | Wrong `change:lane=` values, and lacking way-based turning restriction.
|
|
| 84937603 | Please at least respond to comments before editing. Don't start an edit war.
|
|
| 84936747 | Please don't degrade information by changing `crossing=traffic_signals` to `crossing=marked`
|
|
| 84934483 | Please don't delete `crossing=traffic_signals`
|
|
| 84923486 | Please don't remove `highway=give_way`, or change `crossing=uncontrolled` to `crossing=unmarked`
|
|
| 84933252 | Please don't change `crossing=traffic_signals` to `crossing=marked`.
|
|
| 84799135 | Do you know what `traffic_calming=table` from iD's "raised crosswalk" preset means? Also, don't make a hook/curve for the end of cycle-path as in node/7491047927 - it should be straight
|
|
| 80746269 | and wrong turning restrictions
|
|
| 80746269 | Wrong tags
|