OpenStreetMap logo OpenStreetMap

Changeset When Comment
148321371 almost 2 years ago

This still cause a mismatch between the primary section. and name of the lower forms. Please lookup how `landuse=education` is used. Separate features is used when they have a separate identity.

148365784 almost 2 years ago

`landuse=brownfield` already means it's "former". Descriptive labels should not be added to `name=` , which is proper names only. The lack of the PoI icon already shows it's not a `=school` as well. osm.wiki/Names#Name_is_the_name_only

148191159 almost 2 years ago

Please don't merge arbitrarily. You removed the tapering section with `placement=transition` , and caused `turn:lanes=` to only appear downstream of the stopping line.

148162243 almost 2 years ago

2. The original works fine
osm.org/directions?engine=fossgis_osrm_car&route=22.34210,114.19834;22.34234,114.19904
osm.org/directions?engine=fossgis_valhalla_car&route=22.34210,114.19834;22.34234,114.19904

148162243 almost 2 years ago

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

148135712 almost 2 years ago

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

142857261 almost 2 years ago

Sorry please ignored. Confused who did this.

142857261 almost 2 years ago

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

148135712 almost 2 years ago

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

148135197 almost 2 years ago

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

148134201 almost 2 years ago

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

148128152 almost 2 years ago

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

148128152 almost 2 years ago

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`

148087849 almost 2 years ago

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.

148016236 almost 2 years ago

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.

148016236 almost 2 years ago

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

148016236 almost 2 years ago

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=` .

148016236 almost 2 years ago

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.

148040455 almost 2 years ago

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.

148016236 almost 2 years ago

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.