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. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
