The fix is always the same: delete the bogus footways.

Fixing broken routers by altering the data is not an encouraged behavior.

If the sidewalk is mapped correctly there’s no reason a router should not assume that you can cross the road at any point, as long as the road has sidewalk:right/left=separate tags.

Hey une abeille,

true, it’s redundant if the curbs are mapped. But that’s only the case if the crossings are created as ways in addition to the nodes - as explained before. If there’s just a single node on the street marking a crossing, then only this quest will show up.

I don’t understand why you think that’s not aligning with the OSM wiki, could you explain what you mean by that? 🤔

@westnordost thanks for the effort!

Given my idea of the link between crossings and sidewalks: If you define a sidewalk as just beeing mapped by a center line and a crossing by ending at the curb, you could actually not connect both. So using a link for this (following this definition) not existing path.

In reality I prefer tagging a sidewalk as long as it’s not physically separate from the road - e.g. by grass. But this has certain downsides too. 🤷‍♂️

However mapping intersections as areas - where enough data is available to do so - is by all accounts the best solution, and results in nice renderings like this:

https://twitter.com/RubenKelevra/status/1673050940163645440

Hey une abeille,

the SC team fixed the description field of the quest to make it clear that the tactile pavements on the end of the crossings are meant:

https://github.com/streetcomplete/StreetComplete/commit/a7119ca57b8b3a37c1b3fa759ac68fdbaa8ab551

I like to ask you to adjust your blog to avoid further confusion.

Do you need help reverting your changes to the map in the past?

Best regards,

Ruben

MxxCone I have no idea why you would dig out an proposal for a value of an established tag, which lists this value as a “common value”.

It’s been well documented.

As you seem to be here just to pick a fight, that’s also my last comment here to you.

Hey une abeille,

I’m sorry for the confusion the current description field for the quest in StreetComplete caused.

I’ve created a ticket to improve it on the project in Github - if you wanna take a loon, please?

https://github.com/streetcomplete/StreetComplete/issues/5173

Thanks!

MaxxCon, I’m not using them on sidewalks, but to link sidewalks with other parts of the road.

That’s the purpose of this category and how it’s documented in the wiki.

Feel free to create a new standard so we can discuss over it. But just blaming people for doing exactly what we documented, is not how to improve anything.

Which is what I have been doing.

This is unlikely, because StreetComplete in not capable of asking for ways which are highway=footway and footway=crossing.

Instead it will only search for nodes with highway=crossing.

I’ve checked that.

Hey und abeille,

sorry if this sounded hostile - guess that’s because of the language barrier. This wasn’t my intention.

The issue is: The same tag has different meanings regarding nodes and ways.

If there’s a footway with highway=footway; footway=crossing and you add tactile_paving=yes, it means that there’s a tactile border on both sides of this way.

However if you have a point on a road with highway=crossing, tactile_paving=yes means if there are tactile markings on both edges where the crossing meets the curb.

The OpenSidewalks Schema defines Crossings as existing only on the street surface and Sidewalks as describing only the sidewalk centerline. There must therefore always be space between a Sidewalk and a Crossing. A Sidewalk and Crossing should be connected by a plain Footway.

This makes actually perfect sense. I use highway=footway plus footway=link for those links.

One important note about the question regarding tactile paving on sidewalks: it is not asking if there is tactile paving on either end, ie. at the curb, but rather if there is tactile paving along each side of the crossing, helping visually-impaired pedestrians to stay within the lines. This is very, very rare in Montréal and can almost always be answered “no.”

You got that wrong, and everything you tagged that way. It’s exactly what you don’t think it is.

Nun das klingt so als wenn ich nochmal die doppelten Knoten weltweit aus den Wegen entfernen sollte. Braucht deine Korrektur einen Vorlauf damit wir uns nicht in die Quere kommen?

Dü könntest noch das löschen von Wegen mit nur einem Knoten einbauen, und im Anschluss alle Knoten ohne Tags und Verbindungen.

Lg Ruben

But the download size would increase dramatically ... it would take about 34 hours for me to download it. The current bz2 compressed one take 16. And the traffic on the servers would increase also raise by 215%.

Well ... the trails don't reach any street, is this correct? I think not, you should connect them =)