rskedgell's Comments
Changeset | When | Comment |
---|---|---|
157235609 | 11 months ago | 1) Please don't delete and replace OSM objects, as this loses the editing history.
2) The layer=* tag probably does not mean what you think it does. High Street 3) High Street's pedestrianised areas have signs prohibiting all vehicles (which includes bicycles) and additional signs explicitly and redundantly prohibiting bicycles. It CANNOT be a highway=cycleway. It's a pedestrianised street, which is literally what highway=pedestrian is for (as opposed to mis-tagging pavement/sidewalk areas so that they render on the map). This was explained in the comment I made on your earlier changeset:
|
157208565 | 11 months ago | The warning in iD about a highway crossing a railway didn't mean "just add a non-existent level crossing to make the warning go away". It was generated because the part of the footway you added over the bridge on Railway Street needs to be tagged as a bridge, like the adjacent highway, i.e. layer=1 + bridge=yes |
157185947 | 11 months ago | No, it was correctly mapped by someone who had actually read the wiki: "Roads are not to be mapped as dual carriageways if the two directions are only separated
You didn't even tag the pretend separate carriageways as oneway=yes Please stop tagging for the renderer, you're breaking things which you have not taken the trouble to understand. |
157156102 | 11 months ago | Damn, sorry I missed that. Is there any chance you could edit the offending section of road so that it's fixed in tonights planet.osm extracts? I won't have access to a decent editor until tomorrow afternoon. |
157173227 | 11 months ago | * times in the above tagging examples should of course be 17:30, not 19:30 |
157173227 | 11 months ago | None of those roads would ordinarily be tagged as highway=cycleway. They are pedestrianised streets, which is exactly what a highway=pedestrian way is intended to represent. I concede that access on the section of High Street between Skinner Street was already poorly tagged in respect of access, but this is not an improvement. Assuming that the signage in the Bing street side imagery is still current: East of the junction with Skinner Street:
West of the junction with King Street:
The effect of this is that the correct tagging on that part of High Street should include: oneway=yes
https://www.bing.com/maps?cp=51.387485%7E0.544781&lvl=20.3&mo=om.1&pi=7.2&style=x&dir=302.4
I haven't reverted your changeset, as it is possible that access provisions have changed since the imagery was collected. Please can you confirm whether or not this is the case? |
156957312 | 11 months ago | Reverted in osm.org/changeset/157156679 This and subsequent edits to the junction of High Street and Queens Avenue deleted traffic calming information and mapped a lane without physical separation as a separate way. |
156967760 | 11 months ago | Reverted in osm.org/changeset/157156679 |
157114276 | 11 months ago | Reverted in osm.org/changeset/157156679 |
157126891 | 11 months ago | Reverted in osm.org/changeset/157156679 |
157037651 | 11 months ago | Reverted in osm.org/changeset/157156197 |
157080088 | 11 months ago | Reverted in osm.org/changeset/157156102 |
157113853 | 11 months ago | Reverted in osm.org/changeset/157156042 |
157117029 | 11 months ago | For areas like this, an alternative is to map the area as area:highway=footway together with a linear highway=footway through the centre. Although pedestrian areas are rendered on the "default" OSM Carto map tiles, they're really intended for areas where routing should be omnidirectional rather than linear (although it doesn't actually work with many routers). Although area:highway=footway isn't rendered by OSM Carto, it is by some 3D renderers. If you add a footway for a pavement, you'd need to add footway=sidewalk to it and sidewalk:*=separate to the parent road. osm.wiki/Tag:area:highway%3Dfootway
|
157113525 | 11 months ago | If you've set access=private, you don't really need to set private for other transport modes, as the access tag applies to all transport modes. It doesn't need to be changed, as the extra tags don't have any effect. |
157013719 | 11 months ago | Is there an OSM-compatible source for which (if any) of the streets in Britannia Village have since been adopted by Newham? |
157030270 | 11 months ago | Thanks for confirming. |
157030270 | 11 months ago | Iron Square was originally tagged (not by you) as access=private, which would have been correct during construction. I've added ownership=private, but if it isn't gated it should probably be access=destination so that it's reachable by routing software. |
157036563 | 11 months ago | Thanks for updating this. Although the restaurant has closed, the building will still be there. Rather than deleting a closed business, an alternative is to change the name tag to old_name, use a lifecycle prefix on the "main" tag (in this case amenity=restaurant) and remove the tags which applied only to the closed business. You could also add a check_date tag if appropriate. The advantages of doing this are that the history of the object is preserved and users of apps like StreetComplete will be prompted to check if there is a new business operating there. I've undeleted the building and updated the tags in osm.org/way/487028114 |
157030465 | 11 months ago | Welcome to OpenStreetMap and thanks for adding your business. There are a couple of things you might want to change: 1) position - you are unlikely to be in the middle of the junction of Balloch Road/Ardoch Road and POIs which are "obviously" in the wrong place might get deleted by other mappers 2) business type - data consumers will probably process office=fence_supply_shop as if it were office=yes. If it's your office location, then office=company might be the best fit. If it's the location of a physical shop which customers can visit, you may want to add a shop tag.
I've made a couple of minor tweaks to tags so that they will be parsed correctly by data consumers. |