I see. We sometimes apply compression to some large data sets to avoid
excessive disk I/O (which was the main bottleneck in some cases). Of
course, the decision depends on the data and geoserver's hardware.
Cheers,
Matthias
Am 15.11.2011 08:33, schrieb Andrea Aime:
2011/11/14 Matthias Müller
-dresden.de]
Sent: Thursday, November 17, 2011 5:30 AM
To: Andrea Aime
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] how to use SRTM data in GeoServer?
I see. We sometimes apply compression to some large data sets to avoid
excessive disk I/O (which was the main bottleneck
On 17/11/11 14:49, Stephen V. Mather wrote:
In my limited experience, even with a not-so-exciting storage solution, file
I/O has not been a limiting factor in rendering raster in GeoServer. So we
store everything-- overviews too-- uncompressed. I know others apply jpg
compression to their
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] how to use SRTM data in GeoServer?
On 17/11/11 14:49, Stephen V. Mather wrote:
In my limited experience, even with a not-so-exciting storage solution,
file
I/O has not been a limiting factor in rendering raster in GeoServer
On 13/11/11 23:58, s...@clevelandmetroparks.com wrote:
I would suggest you do a conversion of the SRTM files to GeoTIFF. Chances
are very good you can do this with gdal utilities
http://www.gdal.org/gdal_utilities.html .
thanks for the tip. I tried, and it doesn't really look good - after the
On Mon, Nov 14, 2011 at 11:01 AM, Ákos Maróy a...@maroy.hu wrote:
On 13/11/11 23:58, s...@clevelandmetroparks.com wrote:
I would suggest you do a conversion of the SRTM files to GeoTIFF.
Chances
are very good you can do this with gdal utilities
http://www.gdal.org/gdal_utilities.html .
This gdal command mosaics all SRTM-Tiles into on bi geotiff. This is
what I use for SRTM-Display. Performance is good (equla to using tiles),
and you don't need to care about managing all the tiles on your server:
gdal_merge -of GTiff -co TILED=YES -co COMPRESS=LZW -co
BIGTIFF=YES -ot Int16
2011/11/14 Matthias Müller matthias_muel...@tu-dresden.de
This gdal command mosaics all SRTM-Tiles into on bi geotiff. This is what
I use for SRTM-Display. Performance is good (equla to using tiles), and you
don't need to care about managing all the tiles on your server:
gdal_merge -of
On 14/11/11 13:30, Andrea Aime wrote:
BigTiff is available in GeoServer startig with the 2.2.x series, which
is trunk, current development version (not stable).
There has been talks have GeoServer 2.1.x upgrade the imageio-ext
dependency to 1.1.0, but so far we lacked the
time to properly
On 14/11/11 14:39, Ákos Maróy wrote:
On 14/11/11 13:30, Andrea Aime wrote:
BigTiff is available in GeoServer startig with the 2.2.x series, which
is trunk, current development version (not stable).
There has been talks have GeoServer 2.1.x upgrade the imageio-ext
dependency to 1.1.0, but so
On Mon, Nov 14, 2011 at 2:39 PM, Ákos Maróy a...@maroy.hu wrote:
On 14/11/11 13:30, Andrea Aime wrote:
BigTiff is available in GeoServer startig with the 2.2.x series, which
is trunk, current development version (not stable).
There has been talks have GeoServer 2.1.x upgrade the
Andrea,
A tiff with elevations normally needs to be colored with an external
color map.
I see. is it possible to have a 'linear grayscale' color coding, that
is, provide the same level/value of 'greyness' as reflected in the
GeoTIFF image?
the samples I saw in the documentation you sent
On 14/11/11 14:48, Andrea Aime wrote:
Daily builds here:
http://gridlock.opengeo.org/geoserver/trunk/
thanks. BTW, how do you create the release packages that are bundled
with a jetty instance? is it done through maven, as the other
compilation steps?
Hi Akos,
gdaladdo doesn't generate any extra files - it just stores the pyramids
in the original tiff file. if you issue the command for the first time
you will notice an increased file size.
cheers,
matthias
Am 14.11.2011 14:35, schrieb Ákos Maróy:
Matthias,
This gdal command mosaics all
Hi Andrea,
I wasn't aware of that.
Is there also support for GeoTiff Compression Predictors in the 2.2.x?
GDAL supports predictive compression but Geoserver didn't like those
files when I tried it the last time.
Cheers,
Matthias
Am 14.11.2011 13:30, schrieb Andrea Aime:
2011/11/14 Matthias
Matthias,
gdaladdo doesn't generate any extra files - it just stores the pyramids
in the original tiff file. if you issue the command for the first time
you will notice an increased file size.
oh, I see. thank you for the info. as I'm new to this territory, I
didn't know, and sorry for
2011/11/14 Matthias Müller matthias_muel...@tu-dresden.de
Hi Andrea,
I wasn't aware of that.
Is there also support for GeoTiff Compression Predictors in the 2.2.x?
GDAL supports predictive compression but Geoserver didn't like those
files when I tried it the last time.
I would not know,
Hi,
I'm a newbie to GeoServer, and I'm trying to find out how to use
elevation data with GeoServer. I downloaded SRTM data version 2.1 from
here: http://dds.cr.usgs.gov/srtm/version2_1/ , which brings in a lot of
.hgt files, some in 1 arc degree resolution, some in 3, some in 30 arc
degree
1. how can I make GeoServer use these files as raster data sources? I
looked at the GeoServer documentation and did some online search as
well, but it is not clear to me if these files fall into any of the
supported raster data source categories:
ArcGrid - Arc Grid Coverage Format
On Sun, Nov 13, 2011 at 10:25 AM, Ákos Maróy a...@maroy.hu wrote:
Hi,
I'm a newbie to GeoServer, and I'm trying to find out how to use
elevation data with GeoServer. I downloaded SRTM data version 2.1 from
here: http://dds.cr.usgs.gov/srtm/version2_1/ , which brings in a lot of
.hgt files,
20 matches
Mail list logo
