Tag Info

New answers tagged


Very interesting answer from Mark, thanks ! As the initial message asks for alternative solutions, you can also use FME to upload your data in PostgreSQL/PostGIS and use the pgRouting extension. There is a specific function pgr_trsp that deals with turn restrictions. Thanks to the dynamic definition of the network and turn restriction using SQL queries, ...


OK, I had a think about this. With the current functionality, it is possible, but I don't think you're going to like how! What you would need is for your network junctions to look like this: Basically turns become a separate network line/link/edge. Black circles are nodes and the red lines are the main network. You would need separate features for the ...


If you have a dataset of the tight turns, I would suggest to remove the connections between (read: vertex creating the connection => filter roadsegments intersecting the turn > chop them to vertices > remove turn vertice > rebuild paths) those roads. If it is a turn in a roadsegment you can filter those out segments from your dataset.


I've had this problem some time ago, and took some effort to solve, at least partially. In my case, the street network was spltted in segents, so first I joined them. You could use a merge by filed in Qgis, or use postgis. Then I used Postgis to remove duplicate fields based on the point of intersection (the_geom). Hope it helps


A check of the input line topology using v.build -e map=lines@agraser revealed WARNING: Number of lines of length zero: 140 After removing those with v.clean "remove lines/boundaries of zero length", network creation succeeded.


You are describing things that are actually handled in a couple of different ways in the network. First, one way (also known as direction of travel) is handled by a one way attribute for the network edge (the lines). You can get more info about that from my answer at Does OSM data contain the direction of travel? Next, when you talk about modeling ...

Top 50 recent answers are included