Nice writeup, thanks !

Merci pour les vidéos !

I have feedback for you : That’s neat, thanks !

Here’s an example of the change, although probably not the best one.

Belle initiative, merci !

Thank you mate !

Hi, thank you for the script, it’s pretty useful !

Thank you for your project and writeup !

Thank you PierZen for compiling and sharing thoses stats !

Good writeup, merci !

I fully endorse Data Items, I’ve tried pushing their usage a bit, but was met with pushback by some (mainly one) contributors.

Here’s to hoping that they take off like they should !

Forgot about bicycle=dismount, which may be more adapted here. Thanks !

IMHO, this is problem with BRouter If I look at way osm.org/way/53015601, it is clearly marked as “bicycle=no”. Not sure why BRouter is routing through here.

Because bicycle=no means that you can’t ride the bicycle there, not that you can’t have a pushed or carried bicycle there.

In this case, the profile used in Brouter is for mountain bikes, so carrying the bike is not unheard of. This profile also allows specifying whether bicycle=no path are taken with the “StrictNOBicycleaccess” variable.

Most routers route through stairs for example with a high penalty to avoid a longer detours, as a lot of users can carry the bike. As not all can, it should be customizable.

Thanks for sharing !

Pretty much agree with everyone above. The intention is good, the workflow is quick and to the point, but I sadly think it will provide the expected effect.

Thank you for this write-up and fixes !

I assume you mean it is not showing up in Instagram’s map ?

That’s because data (through the Mapbox map platform) are refreshed only after some time. Be patient and it’ll come :)

Bonjour, les notes OpenStreetMap sont plus adaptées si vous souhaitez référencer votre commerce :

osm.wiki/FR:Notes

Ou encore mieux, n’hésitez pas à créer votre compte et contribuer, c’est assez rapide :)

it can be argued that they shouldn’t have individual names

On the other hand I don’t think larger parts of the community are actually uncomfortable with adding a name tag to a McDonald’s and I would speculate that this is what in common usage would be considered its name

You’re right, but it looks like your opinion (and therefore suggestion) seem clear to me with this wording.

Not a huge deal, it’s just that this issue has and still cost me (and surely others) a lot of contributor time to remove/fix names that are only brands.

Anyway thank you for the data !

Thank you for your analysis !

I see that you suggest, with the fast-food example, to use the brand name as the name=*. Wouldn’t the name used in the chain’s website, bills, internal and communication be better suited ?

I’m of the opinion (and the Osmose QA project) that names should be in most part unique. Outside OSM, that’s precisely the goal of most names : to differentiate things/persons.

To be throrough, it would be best to map each variant. But if it takes too long for the time you have available, you can start with the longest (A-F) segment, that will help anyway.

Maybe just don’t specify interval on the longest (A-F) segment, as it does not run every 60 minutes.

You can link to the timetable with the website=* tag.

Thank you for this tool and presentation. I hope you had a good time too :)