Kovoschiz's Comments
Changeset | When | Comment |
---|---|---|
133770706 | over 2 years ago | Please don't add estate name on buildings yet. This doesn't fit the most common format used in HK. |
133562560 | over 2 years ago | The fault is on `leisure=track` being used on areas directly. Linear `leisure=track` is still supported, so that's for compatibility. |
133562623 | over 2 years ago | You should not take wiki as iron rules. This is one of the more unclear tags. If you do take it strictly, it only includes " green space" and "pitches, nets ". It is mostly associated with entire grass fields, often containing multiple courts. The cover photo is simply a `=playground` that can be enclosed in it casually, if not excluded.
|
133562560 | over 2 years ago | And you should read osm.wiki/One_feature,_one_OSM_element#Situations_where_multiple_elements_may_be_needed concerning `natural=water` areas enclosing `waterway=` , as well as `area:highway=` for `highway=` lines. |
133562560 | over 2 years ago | Areas also don't explicitly show how the full 400m loop overlaps with the 100m starting line tail. |
133562623 | over 2 years ago | The `=recreation_ground` is used for the entire greass field. `=pitch` has been used for the exact soccer playing area excluding the border. |
133562560 | over 2 years ago | Please read discussion on `aeroway=runway` and `=swimming_pool`. `lanes=` only make sense on a line. They show directions explicitly. |
133498707 | over 2 years ago | Please don't upload personal edits or test on a live public database. This constitutes (accidental) vandalism. You should have upload comments to let others can help if you have mistakenly done something. |
133466433 | over 2 years ago | 1. Please don't change the entire area. Add a new point separately.
|
133424976 | over 2 years ago | Please don't upload duplicate features. If you want to draw sidewalks, they should be drawn alongside at the exact location, not attached on the road. |
133425027 | over 2 years ago | Please don't upload vandalism. |
133381229 | over 2 years ago | Please don't remove the English from `name=`. Spaced bilingualism is the standard in Hong Kong. |
133089923 | over 2 years ago | This already has `=motor_vehicle=yes` |
132957781 | over 2 years ago | The criteria of between junction is because `highway=` is a functional classification. Therefore junctions determine changes in function. Legal and official classification are sufficient but not necessary conditions. They are not the sole criteria, only a correlation. |
132957781 | over 2 years ago | `highway=` classification is determined between junctions. So it can't directly change to another class in the middle.
|
132957781 | over 2 years ago | 1. This is already the case with Tunnel Area. They are not Expressway, but are using `=motorway`. I have suggested to change them to `=trunk` + `motorroad=yes`. For the issue at hand, `=motorway` is a special class that's not defined by function alone. However, it still needs to follow the convention of classification between junctions. It should not suddenly change in the middle, simply because of the Expressway Area limit
|
132957781 | over 2 years ago |
That's why `=motorway_link` has been used as a stop-gap despite its issues. That was a tentative solution for many problems.
`=motorway_link` is to be used where it leads to `=motorway` |
132957781 | over 2 years ago | Otherwise by this logic, `=motorway_link` has to be changed mid-way. This has been raised and opposed explicitly in some public discussions. |
132957781 | over 2 years ago | I already indicated this by `motorway=no`. In OSM, `=motorway` and `=motorway_link` are used between junctions, not the exact location. |
132953596 | over 2 years ago | 3. Tung Wing Road is Tunnel Area. Therefore under existing guidelines, it is `=motorway`. However, this was not followed in Discovery Bay Tunnel. |