Tag Info

New answers tagged

2

I guess it's better to answer here than comments on your question: 1) As mentioned source and target are integers that are unique identifiers for starting and ending points of your edge. So if an edge joins with another they share a point in common and you'll see the id repeated. This is a very fundamental piece of routing since travel stops are at the ...


0

This doesn't explain or fix anything, but you could try using a temp table: create table temp_for_export as select * from table1 where id < '20' Then pgsql2shp -f [path] -h [myhost] -p [port] -u [user] -P [password] [database] temp_for_export and see what that does. Is there any chance your host, user or database is incorrect on the pgsql2shp command ...


0

You can use ST_Collect to do this, you just need to break apart the inputs first using ST_Dump: CREATE TABLE new_table AS SELECT 1::int AS id, ST_Collect(geom) FROM (SELECT (ST_Dump(geom)).geom FROM oldtable) sq;


2

The most robust strategy for determining a geometry intersection is to use ST_DWithin(g1, g2, dist). But if you are using geometry overlay tools like ST_Difference or ST_Intersection, then the nodes need to be "snapped" to each other, so try ST_Snap(geometry input, geometry reference, float tolerance). Here is a an example of several techniques. SELECT ...


1

You can try ST_CollectionExtract to extract [Multi]Polygons from GeometryCollections. Use ST_Multi to force them as MuliPolygons. UPDATE public.valid_lcmsouthshapefile SET geom=ST_Multi(ST_CollectionExtract(ST_MakeValid(geom), 3)) WHERE NOT ST_IsValid(geom); After your done, use a CHECK constraint to ensure they stay valid. See details here.


2

If you only want Polygons or Multipolygons from ST_MakeValid you can use ST_Dump to extract the constituent geometries and then test for the geometry type. ST_MakeValid will sometimes produce Points or LineStrings which is where the GeometryCollection is coming from. Try something like: SELECT g.geom, row_number() over() AS gid, FROM (SELECT ...


0

The Issue was resolved with a fresh installation of OSGeo



Top 50 recent answers are included