Hey dear Lists
(apologies for cross post).
We are *looking for an intern* (4-6 months) to work on PostGIS topology in
our research lab near Paris.
We are in a *hurry*.
The subject is about facilitating *user editing **of a PostGIS topology*
base trough triggers, same for topogeometries, then the
Hi Ramon,
I am not an expert on this by any measure. Better to check with the postgis
user group (cc'd). I know the better size choices have changed a lot since
Bborie optimized / rewrote in C.
Best,
Steve
On Mar 16, 2015 4:24 AM, Ramon de Leon r.a.deleo...@gmail.com wrote:
Hi Steve,
Ramon,
It really depends on whether the rasters are stored in the database (in-db)
or out of the database (out-db)
If out-db, I recommend using the block size returned when running gdalinfo
on the raster...
# gdalinfo raster/test/regress/loader/testraster.tif
Driver: GTiff/GeoTIFF
Files:
Users,
Per this ticket:
http://trac.osgeo.org/postgis/ticket/3061
We currently strip out repeated points from GML, KML and GeoJSON inputs. We
allow them on WKT and WKB input. This seems arbitrary (probably it is, just a
random development choice at the time).
Would anyone have a problem w/
If you're storing the raster in the database, I have no specific suggestions.
The reason for no suggestion is that it really depends on the characteristics
of the raster (number of bands, pixel type of each band) and the server
environment.
You normally want to store in-db because you want to
