OpenStreetMap logo OpenStreetMap

Changeset When Comment
82113110 over 2 years ago

2. You have to rely on the `=stop_area` which is not always created for every one. And it's less straightforward to process. As I have discussed elsewhere, there is a non-ignorable need for this across different features.

82113110 over 2 years ago

1. And `object:street=` doesn't appear at all.
2. It's not here, and can be uncertainty in many cases. How do you know it is for the `=primary` here, not the `=residential`?
The other purpose I'm looking into is associating it with the CA07-N prefix on this direction.

82113110 over 2 years ago

If you have checked the usage, `addr:street=` already have a significant number. So don't ask me. https://taginfo.openstreetmap.org/tags/highway=bus_stop#combinations
I don't believe `object:street=` or other existing solutions are better. osm.wiki/Talk:Tag:parking=street_side#Relating_to_street

134881761 over 2 years ago

`place=` is for existing concepts. Please use OpenHistoricalMap for the full history.

134881580 over 2 years ago

`name=` is the most common name in existing public use. Please don't remove other names. Use `alt_name=` etc.

134881168 over 2 years ago

`=village` is used for large ones with their own facilities. Use `=hamlet`, and if only a few houses `=isolated_dwelling`.

134881626 over 2 years ago

Please notice that they represent different things. One is the existing community at the center. The other is a `=locality` for the reclaimed island and cape.

134463002 over 2 years ago

What are you reading?
1. Yes, they are supposed to be on `=ridge`.
2. Yes, they must not be attached to `highway=`

134495490 over 2 years ago

It's very obvious `=path` is not the same as `=ridge`. The middle section deviates significantly.

134495490 over 2 years ago

Upload comments are not for arguing either.

134495490 over 2 years ago

6. You have not asked beforehand though? Simply coming in and deleting everything.

134495490 over 2 years ago

1. Explain how they are wrong? Iterative refinement, mate.
2. Have you read what `=ridge` is for?
3. This is renderer problem then. Complain to them if you want them less visible. Or in your application, reduce their visibility. You are also deleting this for everyone. And , ah yes, you are using "hack tools" too now. iD is also "3rd party" if you claim this way. Are you uploading to the APi directly?
You are committing vandalism by mass deleting while claiming others are graffiti.
5. One Feature One Object. You have not added `=ridge` to `=path` either, which is still wrong. A `=ridge` is more continuous and longer. A `=path` has many attributes that can be split.
6. EDM is not the same as `=ridge`. SRTM is not the most accurate. Moreover, the contour is also generated artificially.

134463002 over 2 years ago

You yourself have attached a `=peak` to `=path`. So I don't know what you are complaining.

134463309 over 2 years ago

1. `=ridge` and `=path` are different things.
2. `=peak` are supposed to be on `=ridge`.

134463002 over 2 years ago

Other features should not be attached to roads. This makes editing difficult, and doesn't represent reality.

134463309 over 2 years ago

Please always improve objects. This is a continously refined process about increasing quality over time. Never delete them without replacement.

134463002 over 2 years ago

Pleae explain what you are doing.

134369862 over 2 years ago

The entire outline being `building=apartments`. The podium/base `building:part=` `=commercial` or `=retail`.

134369862 over 2 years ago

Please use `building:part=` when it is a single tower.

134333943 over 2 years ago

Also that's a `crossing=traffic_signals`, not `crossing=uncontrolled`.