Alliegaytor's Comments
| Changeset | When | Comment |
|---|---|---|
| 168991716 | Unfortunately this hasn't fixed it, there still is a gap in the route, but also the platform/stop members are without roles. Like I said in one of my previous comments, the platforms and stops need to have the platform and stop roles to be treated as such in the route (Please see here: route=train#Members). They also have to be in order (which they are currently not). I may be able to fix this some time later, but you should ideally be able to do this by yourself as you've been adding lots of broken route relations lately and it would be good if they were not needing of fixing in the first place. If there is something that is confusing about this please let me know and I'd gladly try and help explain it better! |
|
| 168951959 | Hi, are you going to fix the errors in these route relations? |
|
| 168898503 | Hi, Thanks for your contribution and welcome to OSM. In this changeset you accidentally dragged this fence node 670m to a footway node/8200436876/history/2
I've moved it back in this changeset: changeset/168901038 Please take care in checking your changes for accidentally dragged nodes before uploading. Happy mapping! |
|
| 168776761 | Hi, Just a few things that might be of use: 1. You may want to add `public_transport:version=2` to the route relations so that editors and error checking tools can better understand which pt version is being used. (public_transport:version=*) 2. The platform and stop members in the relation should have the platform and stop roles respectively, and are usually ordered as the first members of the relation in this sequence; stop, platform, stop, platform... from where the route starts to where it ends. This helps keep the stops grouped together and also signifies that they are stops and platforms rather than ways the train would traverse on (i.e. ways with no roles). E.g.: in relation/19343119 at the top of the relation: West Footscray stop as the role *stop* followed by the respective platform as the role *platform*, then the Middle Footscray stop and platform, and so on until the last station Westall. 3. To understand which relations are route variations of a "master" route they are added as members to a super relation called a route_master osm.wiki/Relation:route_master . This helps a lot when editing and can save a lot of time figuring out which relations exist for a particular route. 4. I'd probably use different names to what you've used for the routes, but I'm not sure what the general consensus is for what the name should be for a train route (at least here in melb). Generally having what the route is actually called is a good start. (For instance, the Sunbury Line is generally called the Sunbury Line rather than *Start* => *Destination* like what you changed its name to. So I changed it to Sunbury Line: *Start* => *Destination* here changeset/168814202)) Feel free to reach out if you have any questions about routes. I can send some more documentation if that would be helpful :) |
|
| 168542843 | Hi, I'm not aware of any Sunbury line trains originating from Sunshine. Do you have a source for this? If this line variant does exist it should be added to the route_master for the Sunbury line. Also, the route relations have members in the wrong order. Please read here osm.wiki/Relation:route#Order_matters |
|
| 168375733 | I didn't touch the Hurstbridge replacement bus as I'm not sure if that should even be mapped, but it currently has `route=train` which should be changed to `route=bus` |
|
| 168375733 | I've also noticed that the rail replacement bus is tagged as a train route, its stops were not in order at the top of the relation, and it was not continuous (had gaps). I've since those issues in changeset/168470267 It also appears that this arrangement will only last a few weeks? If it's temporary and short lived it doesn't need to be mapped as it can be hard to update it whenever it changes. The information will quickly become out of date. It does seem that this route is used quite a bit without it changing so it's probably fine to map, but it should have some description or conditional tag to show that it is in use temporarily and only under certain circumstances. |
|
| 168375733 | Hi Lachlan,
In this changeset you've duplicated (19312176) the route_master relation for the Hurstbridge Line (1830850). Was this intentional? There doesn't need to be a new route_master for this line, the route variations can just be added to the old one. Also, route_master relations should not have nodes or ways in them, these should be removed. relation/19312176 (duplicated)
Feel free to check the wiki for guidance osm.wiki/Relation:route_master :) |
|
| 164918689 | Hi Tadhg, Thanks for contributing to OpenStreetMap. Just letting you know that in this changeset you broke the order (osm.wiki/Relation:route#Order_matters) of ways in the 411 and 412 bus route relations (i.e. the ways in the relation were not continuous and had gaps). I've fixed the issue in changeset/164920068. As I understand it, iD editor doesn't do a good enough job warning you if you've broken routes, so you might want to take care and manually double check the order of ways in the bus routes after editing them. |
|
| 104932352 | Hi alisaluk, just letting you know that platform node/4427569779 was also mistakenly moved in this changeset. I've restored the node's location in #164795619 Happy mapping! |
|
| 164532006 | Hi rtaylor4, The correct tagging for a private driveway is as follows: access=private
oneway=no is not needed as it is assumed to not be a one way unless otherwise specified (i.e. oneway=yes) I've fixed the tagging in changeset/164534137 Everything else you've done seems completely fine, thanks for helping map this area! Please let me know if I've made any mistakes as I'm the active contributor here and not many people review what I do here. |
|
| 164532087 | Hi rtaylor4, Thanks for contributing to OpenStreetMap. I've noticed in this changeset you have added a waterway relation to where a building is (relation/18944157). I assume this was a mistake, so I removed it in this changeset (changeset/164534069). Happy mapping :) |
|
| 162990275 | Hi giarcnomis, Thanks for contributing to OpenStreetMap. I reverted this changeset as well as the following ones you made in this area (163142614, 163139129, 163139008, 162990332, 162990275) as I believe that the intersection wasn't mapped properly. It had a missing piece of highway, had each unseparated turn lane mapped, and broke the following bus route relations: 902, 901, 477, 953, 532, 959 My changeset which I reverted your changes: changeset/163187869 A note I opened about the issue a few days ago (sorry I didn't comment here then, I was busy and must have forgotten to): note/464481 I do think that the intersection can be improved by adding the two one ways that the buses use, but the individual turn lanes needn't be mapped. I made sure to only revert the changesets to do with this intersection, if someone else got removed I'm sorry, it can be readded. I wanted to make sure I didn't break things more. |
|
| 162915299 | Hi, Thanks for your reply. I had a quick look at the tram route in question and saw that the route relation had ways not ordered properly as well as some ways missing. I've fixed those issues in this changeset: changeset/162954477 , but I'm unsure whether the routing application you mention uses those relations or not, so it might not fix this specific issue. Nonetheless, it's good practice to make sure the route relations are done properly as it can cause routing issues on routers relying on them. Hopefully you can find a solution to the problem. You haven't broken anything from what I can tell barring some minor issues with the route relations. |
|
| 162915299 | Hi Geo_Gunzel I can see that you have made 13 changesets here attempting to fix a "routing error". I'm curious what the issue is and I'd be happy to have a look at it and help if needed! I just don't see what the problem is after glancing at your changesets, and am unsure why you're deleting a bunch of nodes to fix it. It might make the issue worse if you delete too many nodes, especially if deleting nodes didn't fix it the first few times. Appreciate the work you're doing on public transit here. Happy mapping! |
|
| 159832515 | Hi, Thanks for contributing to OpenStreetMap :) Just letting you know that there were quite a few duplicated segments of roundabout in this (and potentially other) chanegset(s). Might be a bug in relatify? I have (hopefully) fixed those issues. Might be worth checking to see if you have accidentally duplicated segments of roundabouts in other changesets! Fixed in: changeset/160050163 changeset/160050057 changeset/160049989 changeset/160049960 Anyways, have fun mapping! ~Allie |
|
| 158778357 | Hi Liden, Welcome to OpenStreetMap! You've added a bunch of building nodes to the SRL East. They do not need to be connected as the railway will be underground. Could you please remove these nodes from the railway: node/12314247407
*and any others I may have missed* Thanks for mapping, have fun :) |
|
| 157649353 | Hi, Welcome to OpenStreetMap. I can see that you have edited the SRL East in this changeset. You added these house nodes to it: 12236606341, 12236581442, 12236606400, 12236606376, 12236606374, 12236581497. node/12236581442
The railway does not need to be connected to the houses as it will be underground. Could you remove those nodes from the railway please? |
|
| 158679558 | I'm pretty sure they are using this one geojson: https://tasks.smartcitiestransport.com/api/v2/projects/71/tasks/?as_file=true from https://tasks.smartcitiestransport.com/projects/71#description I just checked and the buildings are cutoff exactly along the borders of "taskId=172" |
|
| 158680724 | Hi, Thank you for contributing to Open Street Map. I can see you added the name "Residential Dwelling" to the houses in this changeset. That's not necessary to do as the houses are almost certainly not all called / are known by "Residential Dwelling". Please see the wiki page about names I've linked below. If you could remove those names that would be great! Happy mapping! |