Does plugin utilize OSM input data highway width tags values?

[zder]

Kauê,

Will the SidewalKreator plugin use highway width tags values (if they exist) from input OSM line data, overriding default highway tag width values manually entered in the plugin interface? You seem to indicate that it does in your OSM SidewalKreator - Basics YouTube video. Please confirm.

Thank You.

[kauevestena]

Yes, that's exactly the expected behavior!

It's also possible for the user to modify the "width" field in the middle of the processing (best moment is right after "data cleaning" step!

[zder]

Interestingly, some of the width values I manually edited in the Splitted_OSM_Lines intermediate processing layer are changed at the end of the plugin process in the Splitted_OSM_Lines layer,

• width values of 15.958 m in 2 street block records for the same street, changing to 16.3184 m and 16.6106 m
• width values of 13.156 m in 2 street block records for the same street, changing to 15.7358 m in 1 record and staying the same in the other
• width value of 9.257 m for another street block changing to 11.9206 m
• 3 street blocks records have no width value change after plugin processing completion

This results in sidewalk centerline coordinate errors, visible in the Splitted_OSM_Lines.

[kauevestena]

Thank you for your feedback, I'll test what's going on and I'll patch a fix!

Can you export the layers in each step and share them here?