[postgis-users] may have postgis store limits for a big project?
Pierre.Racine at sbf.ulaval.ca
Mon Jul 19 09:00:20 PDT 2010
What kind of query are you planning on the raster? You know you can also use WKT Raster to simply "register" filesystem rasters, creating a king of geospatial catalog, without actually storing them in the database...
How many 16GB raster do you have? Are your raster all representing the same theme? Are they overlapping (or they form a regular grid)?
We don't know of that many users cases up to now, but WKT Raster prooved to be very stable working on 1 GB raster coverage (see the tutorial).
From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Sebastian E. Ovide
Sent: 19 juillet 2010 11:34
To: PostGIS Users Discussion
Subject: Re: [postgis-users] may have postgis store limits for a big project?
I am interesting too... I am considering PostGIS+WKTRaster instead of Oracle GeoRaster... but for that can happen, Postgresql must be able of managing some simple tables of 30+M (Millions) rows plus a lot of Rasters of 16GB each... (16GB not compress data... so are huge images !). Each query (simple look up) must response in a fraction of second....
any successful case ?
On Fri, Jul 16, 2010 at 1:13 AM, salas <fsalas at geocuba.cu<mailto:fsalas at geocuba.cu>> wrote:
Hello to all:
I am working in a project where they are managed more than 20 geoespatials thematics. Each thematic one has a considerable volume of since information it is of the whole country (I am speaking of a lot more than a million of records). In the project we need to make (mostly) intersection consultations keeping in mind literal attributes.
I need to know the experience of somebody in a project of this span and if PostGIS would present some limitation therewith.
postgis-users mailing list
postgis-users at postgis.refractions.net<mailto:postgis-users at postgis.refractions.net>
Sebastian E. Ovide
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-users