rskedgell's Comments
| Changeset | When | Comment |
|---|---|---|
| 140114217 | Please don't use OSM for testing - and if you say you'll revert something, then do it. I have reverted this and your other edits to node/2088449681 #DWG |
|
| 145863756 | Please explain why you are making these edits and what you hope to achieve by doing so. The bus station was already accessible to buses. By changing it to access=bus (an undocumented value which is unlikely to be recognised by routing software), you may have just made it accessible to all transport modes, which is extremely unhelpful. Recognised values for the access=* key are listed at the link below. access=*#List_of_possible_values The bus=* key should actually be bus=designated or bus=yes rather than bus=only, which I have now updated. You have changed the roads from highway=busway to highway=unclassified (presumably tagging for the renderer). Neither of these appears to be correct and I have changed it back to highway=service. osm.wiki/Tagging_for_the_renderer The turn restrictions which you added were unnecessary, as the streets are already one way. Repaired in changeset/145878108 Please DO NOT make any further edits to bus infrastructure until you understand how OSM access tagging works. |
|
| 106249392 | It's a residential street with no sidewalk, but also no additional restrictions for motor vehicles. It's almost the opposite of a living street, as there is no consideration of or provision for pedestrians. In the UK, a highway=living_street is signed as "Home Zone", "Share space", or "Quiet Lane". They are fairly uncommon - there is only one Home Zone in Newham which I can think of (although, Newham being Newham, the 30mph speed limit there tends to upset validators). highway=living_street
|
|
| 145818453 | Thanks for updating this. We have a lot of this, which is essentially tagging for the renderer and doesn't work properly for routing where there isn't a highway=footway/cycleway way. However, rather than deleting the surrounding footway areas, could I suggest replacing them with area:highway=footway (areas around a linear way) or area:highway=traffic_island? area:highway=footway
|
|
| 145754560 | Thanks for updating the speed limit. The access was already tagged correctly: access=private + bus=yes means that only buses (and vehicles explicitly authorised by the operator) may use the road. access=bus has no defined meaning and might be ignored by routing software entirely, effectively making the road accessible to all. This is the opposite of your stated intent. Access tags corrected. |
|
| 145754729 | Reverted. |
|
| 145747496 | Reverted. |
|
| 145754668 | Again, you have deleted a restriction relation which did allow buses to proceed ahead and replaced it with a new restriction which prohibits this. Please don't delete relation unless you fully understand what they mean, particularly the except=* key. Reverted in changeset/145759312 |
|
| 145754581 | Documentation here osm.wiki/Relation:restriction |
|
| 145754581 | Yes, they are. That's what "except=psv" meant in the restriction relations you deleted, so the net effect of your edit is to allow *everything* to enter the bus station. Please familiarise yourself with the documentation on restriction relations before you start deleting them. Reverted in changeset/145759048 |
|
| 145716298 | Thanks for spotting and fixing that, that was rather careless of me. |
|
| 144867302 | Reverted by another user in changeset/145707221 What does "busmiles snap to road" mean? If you explain what you are trying to achieve in your changeset description and reply to comments, other mappers may be able to help you. If you don't reply, your changes may be reverted in order to fix errors. |
|
| 141674599 | The tags added were all present on the surrounding leisure=stadium polygon. I have restored way/190137168 to leisure=pitch in changeset/145698568 |
|
| 145646589 | To add the business to the map, you will need to add it as a POI (a point in the iD editor which you used) at its physical location, rather than adding descriptive tags to the road. You also need a tag to tell data consumers what sort of POI it is, which would probably be something like craft=plumber. There is a link to the documentation below. |
|
| 132963588 | Incorrectly. Reverted. |
|
| 132963557 | Correct use of highway=living_street is quite rare in the UK and in urban areas is designated (and signed with TSRGD diagram 881) as a Home Zone. This is not the case here, as it is explicitly signed as a pedestrian zone (TSRGD diagram 618.3, pre-2016) in the Bing street side imagery. The argument in your early changeset #132874014 the a pedestrian way cannot have separate sidewalks seems a little flawed. Adding access=yes and motor_vehicle=designated to an explicitly signed pedestrian zone, will have caused routing errors. Fixed in changeset/145649086 |
|
| 145110614 | Could you explain how "busmiles snap to road" means "effectively removed a road from the map by deleting the highway=* tag"? |
|
| 145632324 | Is Fastrack now open to all traffic, as implied by access=yes? What does "busmiles snap to road" mean anyway? |
|
| 145582520 | Thanks for updating this. I've slightly tweaked the tagging in changeset/145616125 |
|
| 121358390 | These might have been more helpful if you had checked the imagery in order to put them in the right places, which was certainly not the case for node/9763878445. |