OpenStreetMap logo OpenStreetMap

Changeset When Comment
161587587 6 months ago

osm.org/way/1063722878

161587587 6 months ago

Please pay attention it has already been added osm.org/node/5787083212

161549442 6 months ago

Or the area should be on water for berthing. Not what it is berthed to.

161587405 6 months ago

`=visitor_berth` is used for a berth for visitors in facilities eg marinas. It's not standalone.

161585783 6 months ago

osm.wiki/Talk:Tag:leisure=slipway#This_tag_is_also_used_on_ways_and_as_areas

161585783 6 months ago

It's not not allowed, but something other than `=slipway` should be used. Please research before deleting others' work.

161549442 6 months ago

Please read carefully before you use tags randomly. `=berth` is used for individual berths, where there can be many at piers or quays. It is a point feature.

161555418 7 months ago

Please pay attention this is overridden by `motor_vehicle=no` + `bus=`

161513501 7 months ago

1. Please see the `=pedestrian` has `motor_vehicle=yes` already. The `highway=` class reflects the functionality.
2. `=track` should not be used for "single-track" roads. It's not physical, but functional for "wild" land access roads.

161402025 7 months ago

0. Please use more descriptive comments, and upload them in different changesets
1. Please don't blindly accept any editing software suggestions. That's lying to validators. You should at least read the "warning", which tells you Mei Foo Roundabout should be split. `layer=1` at the same time conflicts with many bridges along.
2. Why are you changing `=viaduct` to `=yes` as well?

161378230 7 months ago

Please don't draw a separate line for cul-de-sac without raised islands. It's considered a `=turning_circle` point.

161371704 7 months ago

Please don't use `=apron` for what's not an entire apron, or draw arbitrary areas. This duplicates the `=parking_position` line.

161366096 7 months ago

Please don't add descriptor labels to `name=` , which is for proper names only. This is not a printed paper map. They are harmful to a geographical database. `=aquaculture=` etc already expresses this.

161373500 7 months ago

`level=` should not be changed to `layer=` inside `building=`

161347413 7 months ago

In this case, it would be more straightforward to argue it's not `covered=yes` from how narrow and curved it is. But other cases, some users may find splitting `footway=sidewalk` to add `covered=yes` easier than drawing the entire `man_made=bridge` , then you have to ask why should the roadways not get `covered=yes` together.

161347413 7 months ago

In Germany, someone used 1 `covered:by=bridge`

161347413 7 months ago

It depends on what you mean by that. Certainly drawing a `building=` doesn't prevent `covered=yes` from being added.
The issue is there's no differentiation on when you should do that, and for long or wide bridges. Walkways can be specifically designed under viaducts to be sheltered. Then you have an arbitrary distinction on why roadways shouldn't get it.

161329927 7 months ago

Why did you delete a sidewalk section?

161279619 7 months ago

These don't show the exact reason, but it's critical for `*:lanes=` when `destination:ref:lanes=` and `destination:lanes=` have freeform text in `ref=` and basically `name=` . Using `none` would be interpreted literally as a `ref=none` or `name=none` there, so 0-length must be used.

161279619 7 months ago

I don't know what's the origin or authority, but it's used in `destination:*=` osm.wiki/Key:destination:symbol#Destination_with_multiple_symbols