![]() My problem with the workflow you suggested is that my dataset is basically a bunch of bike paths in a city and I want all the paths that touch (like in link I cited) to be merged so snapping would be great if it was a few paths but I’ve got maybe hundreds or even thousands of paths that I would need to do this to so ideally I would need a tool to automate this. So what I actually have is one line layer with multiple attributes and there are many attributes where, as you described, lines may not have overlapping endpoints even though it really seems like they do. Thank you for such a detailed response, really nice of you to put things together. ![]() You can look here how to use snapping to edit features: Īlso, to try and keep you away from errors, creating buffers (polygons) and then trying to create again lines from that will lead you to data consistency issues. You only need to do this for one of the two lines that you need to merge into one. You can fix this by Editing the features, and in the edit session, you activate snapping. What I suspect your problem is that in fact, the lines do not have overlapping endpoints. (here is an example: - all polygons are one feature in a feature class but several polygons) - apologies in advance if you already knew this and I misunderstand your explanation. Basically, each of your lines is a separate feature. ![]() First to give you one clarification - Multi-Part to single part is meant for a multi-part feature in the same layer, and I am not sure this is what you have. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |