Search Results

my guess is that you have some locking issue in the database. If renaming the table takes time it is not because the renaming takes time but the db waits for something. Have you tried restarting the …

If it isn't huge tables it should be no problem to just create a view and use that in QGIS: CREATE VIEW range50 AS SELECT a.gid, b.gid, a.the_geom, b.the_geom FROM the_table a INNER JOIN the_table b … This table is also the right place to put information about how to style the result in QGIS like size of markers. …

The position is fixed in QGIS, it is not "walking around" as expected. I see the altitude is changing though, but not lon lat. … In gpsmon, and Foxtrot gps I get another position than in QGIS and the position in the other clients is moving around. …

an alternative approach would be to move the data to postgis. you can read the csv-file directly with the postgresql copy-command. then you can create points fom the xy-fields. then if you want to u …

I think ST_Transform is your friend.

my guess is that you get invalid polygons because one or more groups only have one or two points. that can not make a convexhull polygon. if that is the problem you can exclude the problematic groups …

Then you can open that view in QGIS and get your distances. When the tables changes the view will be updated. /Nicklas …

What you need to do is first find the closes geometry, and then find the closest point on that geometry. This can be done in a few ways: select st_closestpoint(a_geom, b_geom), a_id, b_id from ( …

Hallo Is it the QGIS rendering that makes things slow or the PostGIS query. Is the query in the definition of a view or why does it need to med evaluated more than once? …

Yo can use ST_DumpPoints(geom) to get the points listed. Look at the example how to use it. The result contains both the geometry and a path telling where in the polygon the point belongs. So to j …

As you say yourself I think all this can be done in QGIS. … at storing your data in PostGIS. when postgis 2 is out you will have rastersupport in the database and you will be able to do a lot of raster analysing directly in the database. and show the result in qgis …

I think it sounds like what you want to do is a grouping on more than one field. you want to group the points by both their polygon belonging and their company belonging. If that is what you want it …

The best approach I guess is using real topology data. Then you can share the edges between data sets and simplify as much as you want. Here is an example from the man behind the topology impliment …