Hi all
we are building a postgis db to store shared data to e used in my agency.
While for the vectorial part of our data I'm convinced of the advantage to
store them into a geodb, for the raster part of data I'm not so convinced.
I took a look at postgis raster reference page and I realized that p
Il 06/02/2013 13:20, Pietro Rossin ha scritto:
> But If the raster we use is only for base/coreographic pourpose, to be
> loaded mainly in desktop mapping applications, is it worth to use postgis?
IMHO: no; consider the -R option to use them both inside and outside the
db, without duplicating them
Hi,
I've got some problem for achieving what you said.
I've got a lot of cases where the linestring is intersected by 2 points. I
would need to have 3 linestrings as a result of the split operation and as far
as I can understand St_split only cuts a geometry with another geometry.
Maybe
Pietro,
Just two questions:
-What advantages did you find in storing vector data in the DB?
-Why each of those advantages do not apply to raster?
Pierre
> -Original Message-
> From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users-
> boun...@lists.osgeo.org] On Behalf Of Pie
