This is the priblem i have. I'm trying to export some huge data (few GB)
from a database to shape-zip. So i issue the standard GetFeature as
shape-zip as format to geoserver. This works for smaller exports, but with
this export all i get back from server (after some time) is the 500 error.
Why is that? Is it some sort of read or connect timeout? (since it takes
some time for geoserver to start streaming, oh btw, geoserver is 1.7.7)
--
View this message in context: http://old.nabble.com/shape-file-export-problem-tp30594275p30594275.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
On Wed, Jan 5, 2011 at 10:16 AM, GeoUser <blazrepnik@anonymised.com> wrote:
Hey!
This is the priblem i have. I'm trying to export some huge data (few GB)
from a database to shape-zip. So i issue the standard GetFeature as
shape-zip as format to geoserver. This works for smaller exports, but with
this export all i get back from server (after some time) is the 500 error.
Why is that? Is it some sort of read or connect timeout? (since it takes
some time for geoserver to start streaming, oh btw, geoserver is 1.7.7)
I can't think of any specific limitation.
It would be useful to see the stack trace, though it would be better to have
one generated by a GeoServer 2.0.x nightly or even better by GeoServer
2.1 beta3 (since that's where the current development is happening)
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
One possible reason for the problem is file size of uncompressed shapefile parts increasing over 2 GB or 4 GB limits. Especially .shp part cannot even theorically be bigger that 8 GB but I have faced problems with some programs even at the 2 GB.
-Jukka Rahkonen-
Andrea Aime wrote:
On Wed, Jan 5, 2011 at 10:16 AM, GeoUser <blazrepnik@anonymised.com> wrote:
Hey!
This is the priblem i have. I'm trying to export some huge data (few GB)
from a database to shape-zip. So i issue the standard GetFeature as
shape-zip as format to geoserver. This works for smaller exports, but with
this export all i get back from server (after some time) is the 500 error.
Why is that? Is it some sort of read or connect timeout? (since it takes
some time for geoserver to start streaming, oh btw, geoserver is 1.7.7)
I can't think of any specific limitation.
It would be useful to see the stack trace, though it would be better to have
one generated by a GeoServer 2.0.x nightly or even better by GeoServer
2.1 beta3 (since that's where the current development is happening)
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Wed, Jan 5, 2011 at 6:16 PM, Rahkonen Jukka
<Jukka.Rahkonen@anonymised.com> wrote:
Hi,
One possible reason for the problem is file size of uncompressed shapefile parts increasing over 2 GB or 4 GB limits. Especially .shp part cannot even theorically be bigger that 8 GB but I have faced problems with some programs even at the 2 GB.
Hum, actually the .shp limit is 2GB as far as I know. The offsets in
the .shx file are, to memory, 32bit signed integers, so the limit
should be 2GB.
At the WMS Shootout 2010 we actually had to split a detailed isoline
layer, spain wide, in 8 parts to overcome this problem and make sure
all of the .shp files were smaller than 2GB.
And then we had some fun with another that had a larger than 2GB dbf
file, but in that case it was legit (though basically everyone had
to update their software to cope with it).
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
One possible reason for the problem is file size of uncompressed shapefile parts increasing over 2 GB or 4 GB limits. Especially .shp part cannot even theorically be bigger that 8 GB but I have faced problems with some programs even at the 2 GB.
Hum, actually the .shp limit is 2GB as far as I know. The offsets in
the .shx file are, to memory, 32bit signed integers, so the limit
should be 2GB.
At the WMS Shootout 2010 we actually had to split a detailed isoline
layer, spain wide, in 8 parts to overcome this problem and make sure
all of the .shp files were smaller than 2GB.
And then we had some fun with another that had a larger than 2GB dbf
file, but in that case it was legit (though basically everyone had
to update their software to cope with it).
Cheers
Andrea
Hi,
All I know is that with ogr2ogr it used to be 2 GB but I have created something between 2 and 4 GB .shp parts with recent versions and documentation says the limit is 8 GB http://gdal.org/ogr/drv_shapefile.html.
Thanks a lot. So the problem might be in final shapefile size.
Rahkonen Jukka wrote:
Andrea Aime wrote:
On Wed, Jan 5, 2011 at 6:16 PM, Rahkonen Jukka
<Jukka.Rahkonen@anonymised.com> wrote:
Hi,
One possible reason for the problem is file size of uncompressed
shapefile parts increasing over 2 GB or 4 GB limits. Especially .shp
part cannot even theorically be bigger that 8 GB but I have faced
problems with some programs even at the 2 GB.
Hum, actually the .shp limit is 2GB as far as I know. The offsets in
the .shx file are, to memory, 32bit signed integers, so the limit
should be 2GB.
At the WMS Shootout 2010 we actually had to split a detailed isoline
layer, spain wide, in 8 parts to overcome this problem and make sure
all of the .shp files were smaller than 2GB.
And then we had some fun with another that had a larger than 2GB dbf
file, but in that case it was legit (though basically everyone had
to update their software to cope with it).
Cheers
Andrea
Hi,
All I know is that with ogr2ogr it used to be 2 GB but I have created
something between 2 and 4 GB .shp parts with recent versions and
documentation says the limit is 8 GB http://gdal.org/ogr/drv_shapefile.html.
-Jukka Rahkonen-
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment,
and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users