OpenStreetMap logo OpenStreetMap

Changeset When Comment
141019431 almost 2 years ago

No problem - and the mistake wasn't really yours, but the design of the editor.

141019431 almost 2 years ago

Many thanks for updating this and other features on Formentera.

If you change the road type to highway=pedestrian or highway=footway, motor_vehicle=no and foot=yes are implied and redundant. Adding access=no may cause it to be rendered as if it were a private road.

It's very poor design of the iD editor to present the most common access tags for highway types where they are unlikely to be correct, as it wrongly gives the impression that they need to be populated when this really isn't the case.

4802995 almost 2 years ago

No problem, it was a long time ago. As you're still an active mapper, I wanted to check before removing those fixme tags.

Removed in osm.org/changeset/141010437

4802995 almost 2 years ago

Nearly every road in Eivissa was tagged with fixme=needs review back in 2010. I've removed these with SCEE while updating any other highway features, but is there any reason to retain any these 13 years later on? Whatever needed reviewing back then has almost certainly been addressed by better imagery and ground surveys and without specifying what needs reviewing, they're just noise.

140899357 almost 2 years ago

Please could you consider making the bounding box of your changesets smaller? Editing on two continents means that people interested in all the areas between Krakow and Charlotte see this.

osm.wiki/Changeset#Geographical_size_of_changesets

112561772 almost 2 years ago

This beach already exists as a polygon, with its name in Catalan (Platja de ses Figueretes). Would it be better to remove this node and add the Spanish name as a name:es tag to the polygon?

osm.org/way/215356050

140798638 almost 2 years ago

Although iD rather unhelpfully presents boxes for all common access modes whether they're relevant to the highway type or not, a highway=footway is implicitly bicycle=no + horse=no + motor_vehicle=no. Adding them does no harm, but it's redundant and usually pointless, unless reflecting an explicitly signed restriction (like a no pedal cycles sign on a footway). The only access tag on this object which has any effect is foot=designated, because it is a public right of way.

140816421 almost 2 years ago

I wonder how many of the other 700+ edits made by that user are real and have OSM-compatible sources?

140703516 almost 2 years ago

Rather than using landuse=grass for gardens, there's the leisure=garden tag. For residential gardens, garden:type=residential and access=private are usually added.

osm.wiki/Tag:leisure%3Dgarden

140614913 almost 2 years ago

Welcome to OpenStreetMap and thanks for adding some much needed detail in Shenfield.

I hope the following are useful. They're not intended as a criticism - after 6 years I'm still finding new or better ways to tag objects on the map.

For residential gardens, rather than using natural=grassland, you can use the tagging combination

leisure=garden + garden:type=residential + access=private

The documentation on leisure=garden is at osm.wiki/Tag:leisure%3Dgarden

When you add private outdoor swimming pools, leisure=swimming_pool is quite correct, but it's worth adding access=private and location=outdoor.
osm.wiki/Tag:leisure%3Dswimming_pool

140599317 almost 2 years ago

Welcome to OpenStreetMap and many thanks for updating this and other features around Gravesend.

Feel free to ignore the following, as the access tagging "should" work for all but the most broken routing software anyway.

If the closure is likely to be for at least several months or indefinite, it might be worth adding changing it to disused using a lifecycle prefix e.g. disused:highway=service

It might also be worth adding the gates, as nodes with barrier=gate + access=no + locked=yes

The documentation on lifecycle prefixes is at osm.wiki/Lifecycle_prefix

140598935 almost 2 years ago

Welcome to OpenStreetMap and thank you for updating this part of Nettleden with Potten End BR 5.

I don't know if you would find it helpful, but there's a resource for checking the mapped status of public rights of way at https://osm.mathmos.net/prow/progress/herts/dacorum/nettleden-with-potten-end/

There are also some suggestions for tagging PRoWs at osm.wiki/Access_provisions_in_the_United_Kingdom#Public_Rights_of_Way

140573957 almost 2 years ago

They're in that changeset if you look at the history of individual objects, but for some reason OSMCha is only highlighting the change to the road.

See (e.g. ) versions 4 and 5 of osm.org/way/1117797720/history

140562152 almost 2 years ago

Many thanks.

140582666 almost 2 years ago

This is a live database and map, not the place for you to experiment. There is a sandbox for that purpose.

osm.wiki/Sandbox_for_editing

Reverted in osm.org/changeset/140583649

140573957 almost 2 years ago

Thanks. I hadn't noticed that SC/SCEE only resolves the construction=* tag, but not construction:* lifecycle tags. It might be worth raising an issue on the StreetComplete Git repository.

(Sadly, there's no point me doing it, there is exactly zero chance of the developer implementing any issue or pull request I raise.)

140562152 almost 2 years ago

Are these roads actually private access (typically gated), or private ownership (unadopted roads owned by the property developer)?

If it's the latter, tagging as ownership=private + access=destination may be a better fit, as they should be available to routing software for visitors, deliveries, taxis, etc.

140528206 almost 2 years ago

Hi, welcome to OpenStreetMap and thanks for updating the map.

If the pétanque terrain is separate from the bowling green, you could consider adding it with the following tags:

leisure=pitch
sport=boules
boules=petanque

osm.wiki/Tag:boules%3Dpetanque

140480748 about 2 years ago

HGVs start at 3.5t, not 7.5t.

Reverted in osm.org/changeset/140481678

140386294 about 2 years ago

Unfortunately, by the time this edit reaches a lot of routing services, the ferry will already have reopened. It's not worth using disused:* for such a short-term closure for that reason. If a closure is known about long enough in advance, a conditional access restriction could be used.