Tag Info

Hot answers tagged

3

Use ST_Snap http://postgis.net/docs/ST_Snap.html as the final step. As input geometries you need your original polygon and extra vertices to be added as MultiPoint. The third term of the function is snapping tolerance. SELECT ST_Snap( ST_GeomFromText('POLYGON (( 7 7, 7 11, 11 11, 11 7, 7 7 ))'), ST_GeomFromtext('MULTIPOINT (( 11 9 ), ( 7 9 ), ( 9 11 ), ( ...


2

You need to make sure your set search_path call always includes the schema postgis is installed in. So instead of doing: SET search_path=vmplan201506; Make sure you are doing SET search_path=vmplan201506,public,tiger; If you have other tables in public you don't want seen, then move postgis into another schema and make sure that schema is always ...


1

Something like this? -- s1: the point WITH s1 AS (SELECT ST_SetSRID(ST_MakePoint(9.116447, 60.548203), 4326) AS geom), -- s2: polygon(s) where the point is in s2 AS (SELECT p.geom FROM s1, polygons_wgs84 p WHERE ST_Intersects(p.geom, s1.geom)), -- s3: polygon(s) which touch s2 s3 AS (SELECT p.geom FROM s2, polygons_wgs84 p WHERE ...


1

Bounding box is rectangular and therefore ST_DWithin gives wrong result by using a circle for making the selection. Your workflow could be: Define a point Buffer the point and create a circle Make minimum bounding box around the circle Use this newly build box for selecting the features Thus, if we forget the trouble with geometric coordinates, the SQL ...


1

Your expression works on one line compared to one polygon only: The black line touches Polygon 1 and doesn't intersect Polygon 1. In more detail: SELECT x FROM line, polygons WHERE ... means: Build a case from every pair of a line and a polygon, so number of cases is n_lines x n_polygons. Do the WHERE clause for every case and keep cases where it is true. ...


1

I think I got it work now. This was pretty easy actually. I had to restart tomcat by using /bin/shutdown.sh and startup.sh instead of service tomcat7 restart. After deploying geonetwork.war from scratch, my geonetwork UI was reset and database was filled with tables, so I guess that's it.



Only top voted, non community-wiki answers of a minimum length are eligible