Closed Robinlovelace closed 1 year ago
Road with quietness of 40: https://www.google.com/maps/@55.9576566,-3.2309974,3a,75y,240.16h,67.73t/data=!3m6!1e1!3m4!1sDpOCJePwhxD7BTW9CsVADA!2e0!7i16384!8i8192
That's not a cycle lane. It's a B road with car parking. I really can't imagine a parent with child cycling along there, can you? I'd say 40 is very slightly on the low side but not that far off.
Road with quietness of 81 that I walked on with @mem48 ealier this week: https://www.google.com/maps/@55.951296,-3.200337,3a,75y,82.33h,76.97t/data=!3m6!1e1!3m4!1sAF1QipM9lxoDRK3T39AJ4C4WTQdIf9sFvBVQSTN60HHl!2e10!7i11000!8i5500
The issue here is trams support, which we need to sort out. In general trams have not been a high priority for implementation as there's so little infrastructure in the UK. In practice the infrastructure in central areas with a tram line is going to be pretty location-specific. Key issues are whether the amount of space aside from the tram lines themselves is sufficiently wide, and other traffic taking up the space. Princes Street I agree in my experience isn't that nice to cycle on, though arguably I'd say it's better than many similar roads in city centres where cars are permitted.
That's not a cycle lane. It's a B road with car parking. I really can't imagine a parent with child cycling along there, can you? I'd say 40 is very slightly on the low side but not that far off.
I can and would. The point is the relative quietness and cyclability for people who are not confident. I'm confident most people would want to cycle alongside a child in this example, with a CycleStreets quietness of 40, more than on Princes Street.
With Princes Street it's not just the trams, it's also all the fast moving double deckers and other heavy traffic going up and down. As you say, Princes Street is clearly a busy (not to mention scary) central road with heavy traffic that should not have a quietness score of 80. The question is how to tweak the score based on OSM tags, not sure of the best solution there.
@mvl22 A thought on the bus/tram issue is that https://github.com/creds2/CarbonCalculator/releases/download/1.0/PBCC_transit_stop_frequency_2020.zip contains a measure of service frequency for all public transport stops in GB. Perhaps we could tag up roads with a frequent service and reduce the quietness a bit. Not sure how you would detect the roads between bus stops though. I haven't used it but https://github.com/ad-freiburg/pfaedle might be a solution.
We've discussed the tram case and the quietness will be adjusted. As I say, this issue is rather location-specific. @si-the-pie will reply when done.
Another issue where we have the opposite problem, a road with light segregation that is down as very unpleasant to cycle, streetview:
Here it is in our tool: https://www.npt.scot/#16.57/55.931991/-3.172892/-50.4
Any ideas of the cause, a problem with OSM tagging I guess, although I've heard OSM is good in Edinburgh so not sure.
The Princes Street, Edinburgh tram sections have now been hacked so that the ways along there have quietness of 40%. This should be live by Friday afternoon. This is a temporary measure until support for roads with trams is available.
Mayfield Gardens, A701 has lanes=3 and so is capped at quietness 20%.
Mayfield Gardens, A701 has lanes=3 and so is capped at quietness 20%.
Could you please revisit this rule in cases where there is separation between the cycleway and motor traffic, in this case light segregation with wands? Also, according to @joeytalbot, there are examples in the outskirts of Dublin on roads with 3+ lanes and high quietness scores.
This is the example I was thinking of. It's one that I told you about previously, where a cycle path on the pavement of an 8 lane highway has a high quietness rating. The quietness rating was originally 85%, but you reduced it after our conversation and now it's 42%.
https://www.cyclestreets.net/journey/88843644/ https://www.openstreetmap.org/way/945978382#map=16/53.3527/-6.4390
Good point about Mayfield Gardens where the light segregation offers some protection.
The rule that picks up lanes > 2
now avoids ways that have cycleway=track
.
Most of that row now comes out at 40% apart from https://www.openstreetmap.org/way/3993998 where the busway is shared, and is still 20%. This will be live on Saturday afternoon on the main site.
Could you please revisit this rule in cases where there is separation between the cycleway and motor traffic, in this case light segregation with wands?
Yes, the issue here is the relatively unusual cases where cycleway=track is added as part of the road itself. It's sufficiently rare it's not been high up enough on my list to think about fully. There is a bit of a holy war in OSM as to whether these should be part of the road or separately-drawn, mainly because this kind of segregation is highly ambiguous as to whether it is part of the road or not. The new separation=* standard should start to resolve this.
Ultimately I think the correct processing here would be to pull this type out and consider it separately, as it's not really a full track and it's not a major road in the normal sense for cycling, but these don't happen often in OSM anyway.
PS I think the OSM data may be wrong here anyway - I suspect the lanes count is wrong following the addition of the cycleways. Lanes count does not include lanes not accessible to motor vehicles, which is easy to forget. I contacted the person that updated it.
They cycleway by the Lucan bypass Is scored as quietness 50% because it has width=1
.
The bit of that path that is used by the route Joey mentioned came out as 42% because of the hill climbing effect.
The hack for Princes Street has now been changed to quietness = 50%, which will be live from tomorrow afternoon.
Daily updates to UK & Ireland on www.cyclestreets.net complete by around midday everyday.
Thanks for the updates @mvl22 and @si-the-pie. I think those changes will fix the issue, will keep this issue open and close when we have the update route networks in the app at www.npt.scot.
Good news, these are fixed in the latest route networks uploaded to our releases, many thanks @mvl22 and team!
Illustration below for Princes Street in context.
This is fixed in terms of data but we need to update the production website before we can close this issue. Assigning to @mem48 accordingly.
New route network is quite different and I think better in many ways, after https://github.com/nptscot/nptscot.github.io/pull/56 is merged.
Before
After
Importantly the new quietness scores are up, you lovely new data will be on www.npt.scot soon @mvl22 thanks for the build! Can you let us know when the next build based on the latest OSM data is scheduled?
We can close this issue when the new network data is deployed on the production branch and visible to users on npt.scot.
Fixed on production also, great work Malcolm on getting the tiles up there!
Very happy about this.
Good example of where quietness scores are way out below. Heads-up @mvl22 please take a look:
Source: https://nptscot.github.io/#14.01/55.95428/-3.2096
Road with quietness of 40: https://www.google.com/maps/@55.9576566,-3.2309974,3a,75y,240.16h,67.73t/data=!3m6!1e1!3m4!1sDpOCJePwhxD7BTW9CsVADA!2e0!7i16384!8i8192
Road with quietness of 81 that I walked on with @mem48 ealier this week: https://www.google.com/maps/@55.951296,-3.200337,3a,75y,82.33h,76.97t/data=!3m6!1e1!3m4!1sAF1QipM9lxoDRK3T39AJ4C4WTQdIf9sFvBVQSTN60HHl!2e10!7i11000!8i5500
Not sure how best to deal with this: post-processing fix or can it be fixed upstream, e.g. shared use busway and lots of bus stops -> not quiet?