New answers tagged postgis-2.0
I think this might do the trick. Let's say you created your topology like this: SELECT topology.CreateTopology('my_topo', 4326, 0.01); SELECT topology.AddTopoGeometryColumn('my_topo', 'my_layer', 'topogeom', 'MULTIPOLYGON'); where my_layer is an existing table. Remove any data from tables with a TopoGeometry column using this topology. DELETE FROM ...
After all @janechii clues.... and purging all possible residuals, sudo apt-get purge build-essential libgeos-3.4 libgeos-c1 libgeos-dev libxml2-dev libgdal-dev libproj-dev libjson0-dev xsltproc docbook-xsl docbook-mathml sudo apt-get purge postgis I statart with (adapting!) recipes of this link: wget http://download.osgeo.org/geos/geos-3.4.2.tar.bz2 ...
This is how I got around it select * from polygon where st_disjoint( ( select polygon from polygons where id=1), neighbourhoods.polygon) =0 See more details here http://stackoverflow.com/questions/26241751/find-neighbouring-polygons-in-ruby
I had a similar issue. Even recompiling against the new GEOS didn't help when you have 2 versions. It kept trying to use the older version. Firstly, try to uninstall the old library, and see if that works. If not, try to follow this link's instructions using a custom PostgreSQL repository. If all else fails, check your ldconfig to see if older version of ...
You need to cast from the output of ST_MAKE() which is a geometry to the geography data type. This casting is done by using the :: operator. The following command should work: UPDATE customer_campaign set geom=ST_MakePoint(customer_campaign.long, customer_campaign.lat)::geography;
You're confusing the exchange format that the database emits and consumes with the internal format that it uses to store on disk. Check out the serialized format RFC to learn about the on-disk binary form.
I've not got a straight answer for you but some thoughts - apologies if they're too obvious. When you right click on the layer name and select the "Show Feature Count" box does it return the number you expected? When you click on the layer in the Add PostGIS Layer screen, does the geometry column, data type, SRID projection and spatial type (Point, ...
What you need is a general GDAL config option "SQLITE_LIST_ALL_TABLES" You can test what effect it has by comparing these two commands: ogrinfo db.sqlite ogrinfo db.sqlite --config SQLITE_LIST_ALL_TABLES yes The "list all tables" option is listing also such metadata tables which you for sure do not want to export and therefore it is better to explicitly ...
Top 50 recent answers are included