emma_simon's Comments
| Changeset | When | Comment |
|---|---|---|
| 143290728 | about 2 years ago | Had to wait an extra day for geofabrik to pick up the changes, but the issue is is resolved now. Thanks again for your help! |
| 143290728 | about 2 years ago | That looks amazing, thank you so much! I'll check the behavior in OTP tomorrow once the changes have been published to geofabrik, but this should definitely resolve it. We've had similar issues at a few other stations and I've resolved them like you did in this changeset, by adding footpaths within (or around) stations, but this was one of the first ones we discovered, so I was a bit less comfortable with OSM changes. It'd be greatly appreciated if you could keep an eye out for this sort of thing in future MBTA station edits! And please always feel free to reach out to notify us of any issues or have any questions, either through messaging here, or I can give you my email, or we have a Google Group you can drop messages in: https://groups.google.com/g/massdotdevelopers |
| 143290728 | about 2 years ago | Hello! As part of this changeset, you removed the highway=footway tag on Red Auerbach Concourse. I understand why, it seemed like maybe not the best way when I added it, but I wasn't sure what the ideal way would be. I work at the MBTA and the trip planner on our website uses OpenTripPlanner, which consumes OSM data. It requires unbroken walking pathways to connect platforms to the outside street network. So without the concourse tagged as a way to connect the platforms to the pathways within the station, it will say to take the commuter rail to North Station, then leave on another CR train from the same platform out of the city, to connect to a Red or Orange line station, then take the subway back to North Station. So I'm unsure what the best solution is. I agree that having the concourse tagged as a way is strange, but it also seemed weird to add ways going through the concourse just to connect the platforms. |
| 141737988 | over 2 years ago | Yeah, I confirmed with the devs that it's not doing anything to check relations of separate ways. So yeah the streets in Davis Sq I saw it working with were routing using the sidewalk=both named road, and not the footpaths. I checked and Harvard St in Allston also just shows up as "Turn right onto path" 🥲 |
| 141737988 | over 2 years ago | Made the change in changeset/141780262#map=16/42.3709/-71.1039&layers=N |
| 141737988 | over 2 years ago | Thank you for the feedback! I made this change to try to troubleshoot an issue I was seeing with OpenTripPlanner, where when routing down sidewalk ways, the name of the associated street is lost, and I noticed that other streets with separate sidewalk footpaths were named properly and had `sidewalk=both`, but now I'm curious if OTP was ignoring those footpaths and just using the street itself because of that tag, I reached out to the devs for clarification. |