Naar mijn idee is er in ieder geval iets te veel weg gehaald, alleen het brugdeel is weg, niet de aanbruggen en daar is wel een deel van verwijderd.

Hi Strubbl,

I see there is also a discussion on this on osm.org/changeset/102796204#map=14/48.1339/11.6174 and I think that is the better place.

I did document the reason for my changes in the description and checked bicycle access is still possible as there is a bi-directional cycleway on the other side of the road.

I did react in osm.org/note/2644552 but this is once more a side effect of moving the name tag from the outer way to the relation.

If you are sure things are incorrect and know how to correct it, please do so.

Hoi Jasper,

De Kabouterroute lijkt compleet maar heeft nog steeds "fixme=incomplete"

Is dat het geval of kan "fixme=incomplete" verwijderd worden?

Groeten,

Martin.

Inderdaad echt moeilijk is het niet, inmiddels weer ingecheckt: osm.org/changeset/102820360

Ik denk dat beginnende mappers niet aan z'n fietsroute herleggen beginnen ;-)

Goed, bedankt voor je oplettendheid!

Leo,

Op osm.wiki/JOSM/Plugins/Reverter lees ik:

Do not revert changes by other users without contacting them first in a polite way and giving them enough time to reply (one week minimum). Broken data can be fixed easily, but a broken community is not so easy to restore. :)

Dat had ik liever gezien, ik had vrij makkelijk die ene weg kunnen corrigeren en rest van de data nog even dubbel nakijken. Nu is dat allemaal een stuk moeilijker geworden.

Bedankt, okay, ik zie het osm.org/way/527960151. Niet gezien.

Ik denk dat ik ga proberen de changeset er weer in te hangen met deze weg gecorrigeerd.

Sorry @Noudejans, I only did read your reply after writing the reply above.

Good you check the local infrastructure and update OSM on it!

Currently the "Avenue Van Praet - Van Praetlaan" is completely mapped with "bicycle=use_sidepath" so I think that covers "not suited"

FYI: What triggered me initially is an Osmose warning saying there was bicycle=use_sidepath and cycleway=track, see http://osmose.openstreetmap.fr/en/errors/?item=3032&class=30329 Currently there are no problem detected for whole Belgium.

When I edited 317100591 I only added segregated=yes and changed the geometry

For 317100584 you are correct, I made an error adding lanes:forward=2.

I see you corrected things, osm.org/changeset/101094463, thanks!

Thanks for sharing that link @Thierry1030.

Yes, that looks quite unsafe, if you follow Mapillary you see the cyclist, filipc did make the choice to cross the road to the other side where the is some path that is not clearly signed but mapped as cycleway.

Just checked and there is a main road that is mapped as "bicycle=use_sidepath". I am not 100% that is 100% correct as the path has no sign as far as I can see but it looks appropriate here.

Where filipc did cross the road looks unsafe but 40 meter before it there is a crossing with traffic light that seems like a good choice.

Looking at the details it looks to me things are correctly mapped, good bicycle routers will take the correct roads.

NB: My mother language is Dutch, so feel free to switch, but English is also perfectly fine.

Which roads that are too dangerous to cycle on are we talking about? I had a look at Mapillary images yesterday and see there was a separated track and that looks safe enough for me, see for example https://www.mapillary.com/app/?lat=50.88914293777776&lng=4.35706397499996&z=17&pKey=z2n2LHt5-zqbSfMHn81EwQ&focus=photo

So either you are talking about another road (please share a Mapillary link if possible) or your standards on what is safe to cycle are different.

In this changeset osm.org/way/356366271 bicycle=yes has been removed and bicyle=no and access=no added.

I think that is strange:

1) is the road really not accessible to all users? (access=no)
2) bicycle=no does in combination with cycleway=track does not make sense.

Can you indicate what is the real situation?

Thanks,

Martin.

I have corrected things in https://overpass-api.de/achavi/?changeset=101007397

Please let me know if you have further questions.

On using bicycle/foot=use_sidepath, see osm.wiki/Tag:bicycle%3Duse_sidepath

I am sure the current situation with cycleway=track + bicycle=use_sidepath is not correct. You can only use bicycle=use_sidepath if the cycleway is mapped as a separate way in OSM.

Hi Bobby,

I found this changeset because of http://osmose.openstreetmap.fr/en/errors/?source=16352&item=3032&class=30329 and see the changes in this changeset (adding bicycle=no) are triggering many of them.

I find it strange to add "bicycle=no" to a road with cycleway=* but if you are really sure of your case, it would be good to have also these cycleway tags removed. I know of few bicycle route planners that give priority to cycleway tags over bicycle=no assuming "bicycle=no" was added in error.

Thanks,

Martin.

Toch weer typisch, je maakt denk ik beter een bij OSMand, https://github.com/osmandapp/OsmAnd/issues want een fietsrouteplanner zou niet highway=footway moeten nemen tenzij het heel veel korter is, dan is de aanname dat je het stuk gaat lopen. In dat geval "helpt" bicycle=no ook niet.

Hi Brandon,

Thanks for following up, I was not sure and I am glad you took it up and corrected things.

Thanks!

Martin.

Hi,

This route included osm.org/way/404061194 but that way got "bicycle=no" so I removed it from this route.

If this is not correct, please let me know or correct it.

Thanks,

Martin.

> For the tags, I merged them where :left: and :right: is the same. Not sure if that's advisable or how it's intended.

There is no hard truth, but I know route planners typically support the "common" case, after that :left and :right and after that :both

Yes, I see, Bing is pretty good, but you still need more details to fix the rest of Ansbach...

Checking https://cycling.waymarkedtrails.org/#?map=15!49.2996!10.5685 I see there is even a cycle route through Ansbach so maybe one day I plan my cycling holiday through Ansbach ;-)