Search Results

This post http://traviscline.com/blog/2010/04/28/moving-postgis-databases-between-machines/ seems to indicate that pg_dump -Fc is what you want. …

Another way to do this is to use SSH tunnels - use putty (or other SSH client) to log in to the remote machine and set a tunnel from localhost:5433 to remotemachine:5433. See http://howto.ccs.neu.edu/ …

That seems reasonable as EPSG:2262 is measured in feet. Either use ST_Transform to reproject your coordinates on output in the data base or use ogr2ogr to reproject the shapefile to EPSG:4326 to get a …

A point to the north will give an azimuth near 0 or 360. When it is exactly to the north it will be 0 as it moves to the east it will become larger until is is 45 a NorthEast of your point, if you p …

Please, please make sure you add a spatial index to your table, then you can use the && operator. SELECT ST_X(geom) as longitude, ST_Y(geom) as latitude FROM stores WHERE geom && ST_MakeEnvelope(lef …

You can find a list of all indexes on a table with: SELECT indexname, indexdef FROM pg_indexes WHERE tablename = 'name' AND schemaname = 'schema'; which will give a result like: "brownsh_pkey" "CREA …

It looks like your data is not in decimal degrees, ie. it should be between +/-180 longitude and +/-90 latitude. You probably need to reproject your input data to EPSG:4326 before geohashing it.

Try densifying your lines using ST_SEGMENTIZE: select st_astext(st_intersection( st_segmentize(ST_GeographyFromText('LINESTRING(-118.4079 33.9434, 2.5559 49.0083)'),10) ,st_segmentize( …

You can look at the postgis source code to pull out the relevant geos functions to reproduce it, whether that's worth your time or not is another question. …

Postgis is trying to use peer authentication but failing, so I suspect that you are not logged in as user _rendered so when postgis checks with the system it rejects the login. …

In fact provided you always store your points as lon/lat (4326) then just st_x(geom) as lng, st_y(geom) as lat should work.

It's a shell variable - but in this context it just means replace $TRAINING_ROOT with where ever you unpacked the data.

PostGIS should stay in the public schema (then everyone can see it) while your data can live in individual schemas. … This allows you to upgrade PostGIS without needing to backup, drop and restore the data tables since only public needs to be changed. …

When you create a JDBCDataStore on a PostGIS database you specify the database and schema, then you create FeatureSources (and FeatureStores if you want to write) using a FeatureType (confusingly often …

I don't really understand what you are trying to do but the new SQL views datastore in GeoServer 2.1beta may be what you are looking for. See http://gridlock.openplans.org/geoserver/trunk/doc/en/user/ …