New answers tagged topology
I'm trying to give a brief reply to your questions: The topology function assigns a source and a vertex ID for each road segment. To do this a vertex table is created, which contains all source and target IDs. You can use this vertex table, but it's not required. If there is no shared node at an intersection, then the topology script will not connect these ...
It would have been more reasonable to put these into separate questions. You also might benefit from the topology part of the PGRouting Workshop docs. The topology is not created by magic. You either need to provide it (where the topology is provided by identifiers), or you you need to have pgrouting create it (which is what pgr_createTopology() is for). So ...
A quick and dirty solution that does not utilize scripting would be to import your polyline and point layers into a geodatabase, create a topology with the "Must Be Covered By Line" rule, and validate topology. The check will insert vertices at intersections where they do not already exist.
Your search_path in the new database probably does not include the 'topology' schema, try adding it.
I recommend this post and this one. Generally, our data should go through to two main Quality Assurance (QA) prisms: 1.Automatic – Checking rules that don’t require the human eye, and, oblige to preordained rules. All those rules you want your data to fit. For example, for the road layer, no dangles. Or buildings shouldn’t intersect roads unless the roads ...
Top 50 recent answers are included