-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback #4
Comments
Hello,
Geoserver uses less ressources to create a BIL format and it's easier for client javascript to process an array of data rather than to process an image which needs to be converted into a bigger array (twice size of bil array). Nevertheless, the net cost is bigger like you said. I cope with bad BIL in the plug in: The style in mySLD.xml defines a ramp where a height of -32768m is converted into color #000000 and a height of 15000m is converted into color #00BA98. I don't think it's needed to select an image format because from the point of view of the plug in, it's a poor workaround to directly work with images not associated with a SLD (less precise than BIL array or an image associated with mySLD.xml) The plug in request the description of layer from geoserver and choose the proper format to use (BIL first, png and finally jpeg) |
Hello, in my update of GeoserverTerrainProvider for cesium V1, For now I test my improved version. On 13/06/2014 17:24, gberaudo wrote:
|
Hello, Thank you for informing me. I have been trying to have my BIL patch merged in geoserver but there Regarding BIL size, I guess they are not served gziped, which would Cheers, Guillaume |
Hi,
First, thank you for maintaining this plugin.
I have been experiencing with it and would like to share my feedback and also ask questions ;).
It works using BIL/PNG, style, on top of one geotiff.
PNG tiles only weight 3K when BIL are using 8K.
So why do you advice the use of BIL format?
Is it taking more resources on the client or server?
Have you done some measurements?
I found two situations where geoserver would serve bad BIL:
Return empty BIL image on non intersecting box geoserver/geoserver#616);
You fallback on PNG if you cannot decode the BIL.
Do you also have these issues?
For the record, I used gdal_retile.py -v -r bilinear -levels 4 -ps 2048 2048 -co "TILED=YES" -targetDir bmpyramid srtm90.tiff.
Regards,
Guillaume
PS: maybe you could explain in the README how to select a request image format (copying the image descriptor).
The text was updated successfully, but these errors were encountered: