Has anyone tried to apply this geometric problem to street networks? Specifically, where road ends are points, trying to find minimal path connections? I’ve found a research paper on this script but can’t make too much sense of it. Perhaps there is a similar thread?

@TomTom Thanks for the insight. While the paper doesn’t mention these two things specifically, most of the technical language remains absent. I’m fairly new at grasshopper and haven’t had the chance to jump into graph theory and programming. Sounds like your an expert in this area?

Getting closer here but does anyone know how to adjust this so that the connecting lines stay inside the polygon shape? And the points should be road connections?

I’m using plugins: 1. kangaroo physics 2. karamba 3. human

I wouldn’t consider myself being expert. Generally spoken graph theory is a big topic in many disciplines, in programming its widely used. Many search algorithms are based on graph theory. If you use google you basically apply graphs. Part of the graph theory are route problems, steiner tree is one example. Another is the shortest path or traveling salesman. Often route problems are explained with street networks. So its natural using it for city planning. However a real application is found in programming.

If you don’t know about the basics you won’t understand it, that’s was the intention of my first post.

Edit: I saw the Python script. If you already know programming and how to write graphs, then just google for it. There are many implementations around.

You must program something to suppress curves going out of the perimeter.
With 60 iterations it took 3 minutes here. The more iterations the less roads.

@laurent_delrieu Thanks! I’m not sure that the kernel edge bundling was what I had in mind but i’m going to try and play with this a little further. Ultimately, would like to bake the generative options as street centerlines. Tough learning curve on my part but seems like I need to dive into programming a bit more? The attached image is what I had in mind. (image: Lopes J., Paio A., Sousa J, 2014)

You don’t need to learn anything. Just beg or google for a script and give your optimisation a meaning. That’s it, you’ll pass the exam and probably never ever use this again. That’s the truth about this pseudo-blabla you hear about in any university nowadays. I wonder if there is anyone out there planning streets with these algorithms anyway.

This is a very good question. Space Syntax has done some extremely relevant/successful work using graph theory…as a PART of their analysis/design process. On the other hand, In my experience sitting on some juries for academic urban planning studios…it often falls into the “voronoi syndrome”, (improperly/overly used with out a fundamental understanding of the underlying methodology).
For example, one could argue that more connections to a street/path can indicate a “positive” metric. While this is often true, it CANNOT be considered the only metric. While many graph theory approaches have some type of weight for nodes/connections, it becomes all the more important to understand why you, (the designer of the implementation of the chosen graph theory approach), need to understand…or theorize, what the quality of the street/path the theory is proving or disproving.
Ugh…quite a large discussion, and perhaps not unique to the application of graph theory, but perhaps applicable to any parametric design approach.
Shortest path is not always the “best path”…because you need to decide what “best” is. Distance? Ease of access? Quality of experience?
:: need more coffee…end tangent.