[Geoserver-users] Serving SRTM1 data with GeoServer

[Barry Carter]

I'm trying to provide SRTM1 (1 arcsecond resolution elevation) images and data
using GeoServer, but can't figure out how to serve such a large dataset
efficiently. Here's what I've done so far:

  - Downloaded the 1 degree squared HGT files. The Earth is 360*180 = 64800
square degrees, but only 14295 HGT files since the other square degrees
are 100% water. The HGT files are uncompressed and 25,934,402 bytes each.

  - I then used commands like:

gdal_translate -co TILED=YES -co COMPRESS=DEFLATE N58W122.hgt N58W122.hgt.tif

to convert these HGT files into TIFFs. The TIFFs vary in size, but are much
smaller.

  - I then imported the directory with the TIFFs as a store using
ImageMosaic. This took a while, but appears to have worked, since "srtm1"
(the name I gave it) now appears in my list of stores.

  - I then created a layer using this source, but when I use "OpenLayers"
preview, the server hangs for a while and ultimately dies with "too many
open files" (or similar). This seems odd, since my Linux OS had
fs.file-max set to 13063650. I even tried doubling it to 26127300, but
that didn't help.

At this point, I suspect I need to create an image pyramid or something so
GeoServer can handle the data efficiently, but I'm not sure exactly what to
do. I've used 'gdal_retile.py' previously to create pyramids from one large
image into tiles at various zoom levels, but I think I want to do the opposite
here (merge smaller images for lower zoom levels). The gdal_retile.py option
-pyramidsonly seems to say it does that, but I can't get it work (it just
hangs and creates no files)



___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] /data directory not writeable

[Russ Hore]

draug...@gmail.com mailed me privately

The solution he described is as follows;

———
looks like i got the same "data directory not writable" error and look what i 
found:

there is a file /lib/systemd/system/tomcat9.service

and it has lines:
ReadWritePaths=/etc/tomcat9/Catalina/
ReadWritePaths=/var/lib/tomcat9/webapps/

i just added new line with my path to it and it worked

maybe it will help ya too

sorry for my eng it isn't my native language
and good luck (:
———

I added the path to mt /data/ directory and all is working fine now. GS2.15.1 
on OpenJDK 11

Russ


> On 26 Apr 2019, at 10:25, Andrea Aime  wrote:
> 
> Strange... the error message comes from GeoWebCache:
> 
> https://github.com/GeoWebCache/geowebcache/blob/5e913193ff50a61ef9dd63a87887189352fa6b21/geowebcache/core/src/main/java/org/geowebcache/storage/DefaultStorageFinder.java#L124
>  
> 
> 
> but a "blame" shows this code has not been touched in 10 years:
> 
> https://github.com/GeoWebCache/geowebcache/blame/5e913193ff50a61ef9dd63a87887189352fa6b21/geowebcache/core/src/main/java/org/geowebcache/storage/DefaultStorageFinder.java#L124
>  
> 
> 
> So yes, maybe a java 11 thing, though I don't know what exactly.
> 
> Cheers
> Andrea
> 
> 
> On Fri, Apr 26, 2019 at 11:00 AM Russ Hore  > wrote:
> OK. I have not solved it but have done some research;
> 1) Installed clean Ubuntu 18.04.2
> 2) apt-get update / upgrade etc
> 3) Installed tomcat9
> 4) Copied 2.15 GeoServer.war to /var/lib/tomcat9/webapps
> GeoServer started
> 5) created /data, chown tomcat:tomcat /data/
> 6) restarted tomcat9, and got the original error “which is not writeable”
> 7) Installed GeoServer 2.14
> 8) It won’t run under java 11 I assume
> 9) Installed OpenJDK 1.8.0_191
> 10) Installed tomcat8
> 11) Installed GeoServer.war
> 12) Edited web.xml to set DATA_DIR
> 13) GeoServer started and used /data as DATA dir.
> 
> I am not sure where to look now but if anybody has things they want me to 
> look at I have some spare time.
> 
> I may try tomcat8/Java 8 on Ubuntu 19.04 later.
> 
> Russ
> 
>> On 26 Apr 2019, at 08:42, Russ Hore > > wrote:
>> 
>> Hi Benoit,
>> 
>> Good suggestion, (and I might be missing something obvious),  but I am using 
>> an absolute path.
>> 
>> /data exists under the root filesystem
>> 
>> This is the way I have set up GeoServer before so I can easily upgrade. 
>> Maybe something has changed between Ubuntu 18 & 19
>> 
>> I am about to do a clean install of Ubuntu 18 so will ley the list know.
>> 
>> Russ
>>> On 26 Apr 2019, at 08:18, DEGRÈVE Benoît >> > wrote:
>>> 
>>> Hi all,
>>>  
>>> Russ, I would like to help but I may be wrong : have you already tried an 
>>> absolute path instead ?
>>>  
>>> I say that because I’ve recently change my web.xml to direct Geoserver to 
>>> save cached tiles in a geoserver (+tomcat) subdirectory and I used an 
>>> absolute path, and it works without changing anything else.
>>>  
>>> And if you want to use a relative path, maybe you should use « ./data/ » 
>>> instead of « /data/ »
>>>  
>>> Hope it helps,
>>>  
>>> Benoît DEGRÈVE
>>> Risques sous-sols et cartographie
>>> 
>>> Bachelier en gestion de données et cartographie
>>> 
>>> 
>>>  
>>> De : Russ Hore [mailto:r...@russ-hore.co.uk ] 
>>> Envoyé : jeudi 25 avril 2019 18:52
>>> À : Ian Turton
>>> Cc : geoserver-users@lists.sourceforge.net 
>>> 
>>> Objet : Re: [Geoserver-users] /data directory not writeable
>>>  
>>> # ls -ld /data
>>> drwxrwxrwx 2 tomcat tomcat 4096 Apr 25 15:10 /data
>>>  
>>>  
>>> For info.,
>>>  
>>> # ps -efl |grep tomcat
>>> 4 S tomcat1232 1 49  80   0 - 1716271 futex_ 16:49 ?  00:00:46 
>>> /usr/lib/jvm/default-java/bin/java 
>>> -Djava.util.logging.config.file=/var/lib/tomcat9/conf/logging.properties 
>>> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
>>> -Djava.awt.headless=true -XX:+UseG1GC -Djdk.tls.ephemeralDHKeySize=2048 
>>> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources 
>>> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 
>>> -DGEOSERVER_DATA_DIR=/data -Dignore.endorsed.dirs= -classpath 
>>> /usr/share/tomcat9/bin/bootstrap.jar:/usr/share/tomcat9/bin/tomcat-juli.jar 
>>> -Dcatalina.base=/var/lib/tomcat9 -Dcatalina.home=/usr/share/tomcat9 
>>> -Djava.io.tmpdir=/tmp org.apache.catalina.startup.Bootstrap start
>>>  
>>> Russ
>>> 
>>> 
>>> On 25 Apr 2019, at 17:22, Ian Turton >> > wrote:
>>>  
>>> can you paste the result of "ls -ld /data" in 

Re: [Geoserver-users] WFS cascade : impossible to publish a layer

[bendeg]

As you get the same error on your side, and before assuming our partner
(indeed, we've been given temporary access to external data to implement and
test an application concerning emergency public services) server setup is
broken, there's one more thing to mention : 

I think features are *complex features*, not simple ones : when trying to
get the features directly from an Openlayer application, the JSON formated
features received from their server is invalid because there's a property
that contains something like an ID which is between curly braces.

Seeing those curly braces the parser fails because what's between them
doesn't respect the JSON syntax, it's just an ID...

And if I try to get a GML format, whatever the wfs service version or the
GML format used in Openlayers, all points are "inverted" (Y X instead of X
Y). I can't get it right.




--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html


___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] White pixel (nodata) along footprint

[HSt]

Hello all,

we are currently serving many tiff files (ca. 4000 per layer) as ImageMosaic
via WMS and WMTS (scale-dependent). 
These tiffs are heterogeneous (=true), i. e. mix of RGB and RGBI, various
resolutions. Therefore we use coverage view and we only display RGB (channel
selection in .sld).

One image can have two footprints (because the original image is composed of
two different dates, when the photo was taken, each footprint represents one
date, but referring to the same image). We've generated unique IDs in the
shapefile table, where the footprints.properties is pointing to
(footprint_filter = FID = granule.FID --> shapefile for ImageMosaic =
footprint_source). Footprint behavior is set to CUT.

All in all this works perfectly, but along the footprint line within one
image (remember, exact same image is used twice in the ImageMosaic, each
time with a different footprint), white (nodata) pixels appear and only
occur if the footprint lies exactly in the pixel (divides pixels into 50-50
pieces).

 

 

 


I don’t know if this is a bug. But is there a possibility to adjust the
tolerance of the footprint behavior or another way to avoid these pixels?
Wasn’t there an option that the footprints can cut through pixels instead of
omitting/picking entire pixels? 
Cutting the images beforehand or interpolation (bicubic) are not an option
because the original images should be untouched.

Thanks,
HSt




--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html


___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users