1. Please don't use upload comments to debate. Actually reply on changesets.
2. What's not represented by relation/13324778/ ?

2. Also please don't delete casually. You didn't transfer all the info. Eg the `=traffic_signals`

Sorry please ignored. Confused who did this.

Please don't draw a circle for `=turning_circle` . It and `=mini_roundabout` are transversable, and only represented by points.

Again, turning restrictions are indicated by `type=restriction` . Please check them carefully by clicking on the intersecting points. Physical layout has no raised sepation.

Please don't split when there is no raised physical separation.

Please don't draw a circle for `=mini_roundabout` . They are transversable.

2. Double solid line is indicated by `change:lanes=`

Please understand that roads should only be split into a pair of lines when there is raised physical separation. Turning restrictions are shown by `type=restriction`

It should be `level=-3` , but you should not add that to `route=light_rail` etc when they don't have such a concept. It's only refers to physical structures and functions on them.

It's the software's fault. Not designed properly.

Another thing: `level=` corresponds to `building:levels=` which is above-ground only. The actual level numbering should use `level:ref=` .
Here it is `building:levels=5` + `building:levels=3` , not `building:levels=8` . The ground floor is `level=0` + `level:ref=4` for remote stands access.

Btw need some time to fix the whole thing.. So you can work on elsewhere first.

The problem with not using `=multipolygon` and creating a new `way` for the same outline is the copies easily and eventually becomes misaligned. And the points on one area or `level=` doesn't get referenced back in others and the `building=` .

Also don't make 2 `aeroway=gate` for each `=level` , which result in duplication. It is 1 `aeroway=gate` spanning `level=5;6` .
https://framagit.org/PanierAvide/osminedit/-/issues/24
https://framagit.org/PanierAvide/osminedit/-/issues/34
There seems to be critical flaws with OSMInEdit, although JOSM isn't great either. The `indoor=` features don't snap to the `building=` , creating a mess.

1. As I have said, please don't delete then recreate the same thing. You can modify it directly.
2. Please don't add land info to the `building=` . That's irrelevant.

I can do it later. The alignment of the whole thing needs to be fixed first before you work on it more. You can work on other concourses for the day.

1. Please check carefully before creating. There were already `aeroway=gate` here.
2. Don't add `Gate` to the `ref=` . Only the number should be used.

Reverted /changeset/147922918,147914469 Shatin mountains: Needs more discussion

changeset/148004479

Reverted /changeset/147922918,147914469 Shatin mountains: Needs more discussion

changeset/148004479

1. Please don't spam hashtags. `description=` is not for advertising. I can very seriously explore the coverage with `service_area=` but it needs to be geographical.
2. `wikidata=` and `wikipedia=` are only used for the unique entity. `brand:wikidata=` and `brand:wikipedia=` has already been added.
3. `branch=` is for the branch name only. `brand=` already covers the other part.