Lockstar's Comments
| Changeset | When | Comment |
|---|---|---|
| 142179639 | I've worked out what happened here. Where footways cross through or under buildings, OSM prompts a response (above or below) and setting the layer. Ways need to be split so only the section under/within the building is layer=-1 |
|
| 155553077 | My apologies. I do not recall deliberately deleting existing bus stop data. Whenever adding or supplementing these, I add to or edit the existing node. If I have inadvertently deleted existing nodes, it has been accidental and unintentional. In the instances you've identified, this deleted information should be reinstated. |
|
| 143889108 | Comments noted - thanks for the feedback. The data held is compatible with and the same as the digital spatial data you've referenced. My work involves a gradual review and update rather than a bulk upload. The majority of the data is existing in OSM with only minor tweaks/updates required to align it with the open data. |
|
| 147921577 | Agreed - placed in error, should be deleted. Thanks. |
|
| 152488183 | OK - agreed. I'll leave the v2 tag off new routes until I'm completely finished and satisfied it's compliant. Sometimes there's a time gap from when I start entering to when I finish, unfortunately. Cheers. |
|
| 151138409 | No, I didn't - but another user created edits at the same time resulting in the mess. It's fixed now. |
|
| 143889108 | Hi, thanks for the feedback - this information is data I've held for a long time originally obtained from the DMR/RTA in the 1980s and gradually added to over time. The reference to "Traffic Controlled Site #" is how RTA/RMS/TfNSW have typically referenced them hence my use of it. I started entering the data as a way of ensuring it is in common use/access, also makes it easy to look up in the field via mobile device. OK with your suggestion to apply the tags to the actual signal locations rather than centre of the intersection. I've entered data for about 1600 sites, only have about 2500 odd more to go. Cheers. |
|
| 146884704 | My apologies - was not aware of this. Thanks for the info. Happy for you to correct. Might need to check bus route details to make sure they are changed over. Thanks. |
|
| 149341621 | Fixed - thanks |
|
| 149258035 | Noted thanks - reviewed and edited res area boundaries |
|
| 149294807 | My error - thanks for fixing |
|
| 149115090 | Was removed in error - thanks for fixing |
|
| 148450136 | Most of these should be fixed now. As I've said before, these breaks are often a result of works in progress. Unfortunately sometimes in repairing one route, I end up breaking another and have to return to fix. Thanks for pointing them out. I'll keep checking the OSM inspector to find any missed breaks. |
|
| 144541598 | Thanks - I've checked this and I don't think it was my changeset that added the incorrect connection from the escalators to the street sidewalk. I've fixed the error anyway and have removed the connections from the station platform escalators to the street |
|
| 147644677 | This should be fixed now - hopefully |
|
| 147210968 | Yes - I will and I do edit/check these in JOSM - just don't always get to them in one sitting and have to come back to it. In this case you beat me to it. Most of these routes are missing heaps of stops and even the route ways are incorrect and need fixing in some cases |
|
| 147046310 | Thanks - most of these missed ones are existing bus stops with outdated tags that I've missed in my updates. I'll try to make sure I catch and fix all these for any further updates done. |
|
| 147040364 | Fixed. The land use areas in this town are a shambles. I spent hours yesterday updating some them. This one slipped through the cracks. |
|
| 146814464 | Connection missed - now fixed |
|
| 146700165 | Yes - fixed |