tsmock / sidewalks Goto Github PK

Here's another place I have to keep doing little corrections for. The roadway has surface=asphalt but the footways don't. Clicking 1,2,3,4 as depicted ends up with 2 segments. The short stub on the bottom that is footway=sidewalk with no surface tagging and the upper portion that is footway=crossing, surface=asphalt the whole way.

I can split these up and get it patched but perhaps it can be a bit smarter about continuing the crossing after correctly placing the kerb.

When in normal draw mode, you can press the draw mode shortcut again to enter angle snapping mode. It'd be really nice if Draw Sidewalks mode also supported that, along with picking a reference way with CTRL.

For anyone unsure of what I'm talking about, check out this showcase video on the OSM World Discord server: https://discord.com/channels/413070382636072960/782592789284257813/843180400603037728

It doesn't make a lot of sense to add kerbs and a crossing for an intersection with highway=steps.

It's very common here in Seattle for a small junction to have a mini roundabout drawn into it. This causes the plugin to find a nearest node for the crossing that happens to be on the roundabout. These are all tagged as highway=roundabout so maybe don't attach to them? Maybe it should be? Dunno.

I had an area where the sidewalks were already in place but the crossing did not exist. I entered sidewalk mode and clicked the nodes in order 1,2,3,4. I has missed making crossing nodes for the north/south roadway.

This is probably because you want it to be a replacement for the general draw but here's a situation I've hit a few times where I think it could do the right thing.

I draw things in this order and the third way doesn't end up with any tags.

This way:

This crossing:

The weird result:

My JOZ file with the layer in it:
SidewalkPlugin-WeirdDelete.zip

My current work pattern is to add surface tagging and fix alignment of roads, then work on sidewalks. Occasionally I will miss a roadway surface tag and it (obviously) won't get picked up on the crossing node. Maybe it's better as a validator step but it could be nice to have surface tags from roadways proactively applied to crossings.