Is this the scenario when percentage of nodes greater than 90% but less than 100%? Sometimes there also can be false positives on completion when nodes are oddly placed or unevenly spaced out.
I kept track of such streets manually under a “unsatisfactory completion” header. I like the idea of total completion as the road isn’t really done until it is ALL done. I never considered it a big issue as the number of streets that fell into this category generally stayed pretty low.
In terms of improving the viewing of un-run nodes, it would be nice to sort by the percentage of completion. I wouldn’t think it is a priority.
I don’t think this is a priority either. Total completion is sometimes difficult or impossible to achieve because of issues with the dataset such as nodes being located in the wrong place. Or having bad GPS data in an area with tall buildings and missing one node. That said, I’m guessing it wouldn’t be that hard to code in the % completed to the list of streets completed under a city, but since I don’t (usually) chase 100% completed, it doesn’t really matter.
Wondering if you can add an option or setting that would require that ALL nodes be complete to 100 %? I really don’t need to see the individual nodes, or sort by % complete, but I’d definitely prefer a “strict mode” where it requires that every single node be covered.
My before last activity was particularly bad, large sections are missing but streets were marked as complete. With Vancouver having so many streets, I’ll never find these again unless you add a missing nodes view, or I manually document every ‘false completion’.
I have not been paying much attention to the completed streets honestly. I just look at the map of my city and plan routes to hit all the streets that are not complete, in the sense of there is a line that I have run down 100% the length of the street.