You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The unlinks layer results shows dozens of unlinks where there should only be a handful.
After inspecting the result I notice that unlinks are created on segments that after cleaning are (correctly) split. These segments were not broken originally but shared nodes with an incident segment.
I suspect that the identification of unlinks has to happen at the end of the process, after cleaning. Not before.
The text was updated successfully, but these errors were encountered:
If creating unlinks happens after the breaking and merging of the lines, this will cause an issue for the OS data. In OS data unlinked segments share a vertex and therefore the lines are broken at those vertices.
So it seems that in OS the creation of unlinks has to happen at the beginning of the cleaning process whereas in OSM at the end of it.
To get correct unlinks with OSM data, clean the layer twice. The second set of unlinks can be used . However, it needs to be verified with the Unlinks Verification of the SSxToolkit.
The unlinks layer results shows dozens of unlinks where there should only be a handful.
After inspecting the result I notice that unlinks are created on segments that after cleaning are (correctly) split. These segments were not broken originally but shared nodes with an incident segment.
I suspect that the identification of unlinks has to happen at the end of the process, after cleaning. Not before.
The text was updated successfully, but these errors were encountered: