[Geoserver-users] Does DDS/BIL extension only serve Big Endian?

Hi,iuses

I am seeing conflicting views regarding usage of the Bil extension. Some say
it only uses big endian and others little endian. If only Big Endian why
does the settings for it have both Big Endian and Little Endian??

Also, has anyone gotten that extension to work with a client (like WWJ)? And
if so what settings did they use and why? If you have say a 16 bit geotiff
why would you use 32 bit bil?

Thanks,
-Tony

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Does-DDS-BIL-extension-only-serve-Big-Endian-tp5248575.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Tue, Feb 2, 2016 at 10:09 PM, adanecito <adanecito@anonymised.com> wrote:

Hi,iuses

I am seeing conflicting views regarding usage of the Bil extension. Some
say
it only uses big endian and others little endian.

Who says that? Do you have links?

If only Big Endian why
does the settings for it have both Big Endian and Little Endian??

Because the code is using it to set the byte order:
https://github.com/geoserver/geoserver/blob/master/src/community/dds/src/main/java/org/geoserver/wms/worldwind/BilMapResponse.java#L224

Also, has anyone gotten that extension to work with a client (like WWJ)?
And
if so what settings did they use and why? If you have say a 16 bit geotiff
why would you use 32 bit bil?

I know we have used it to serve elevation to Cesium with success.
The format was chosen because Cesium can barse BIL, but not GeoTiff (BIL is
way simpler to parse, especially in a browser).

Never tried WWJ myself

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

Thanks geowolf. I found the client code had BIG_ENDIAN and once I fixed that
I got rid of the peak issue I had but now it is all flat elevation because
bil is returning all zeros for elevation. I posted a question about that
just now. I looked at the source code you pointed out am wondering if the
stream feeding the bil extension is the issue somehow.

Thanks for the help. The reason I said BigEndian is a blog mentioned it was
only serving Big Endian. Yet the panel for the extension can use both and
the code seemed to support both. I also saw a email thread here that
indicated that person had to select Big Endian to get their data back
correctly.

Thanks!
-Tony

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Does-DDS-BIL-extension-only-serve-Big-Endian-tp5248575p5249357.html
Sent from the GeoServer - User mailing list archive at Nabble.com.