Nicolas VILA

Hi, I will share my experience as I have a very close HP (EKHBX008AA3V3) I had several issues at the same time and you need to check them also 1)...

> @nicolasvila Your post made me review this again, and I realized that I am still using my old code while it seems by now the S-protocol got merged into...

Hi, I have a question regarding my HP unit (EKHBX008AA3V3) which seems to accept PROTOCOL_S_ROTEX and PROTOCOL_S. (I believe parameters from PROTOCOL_S_ROTEX make more sense for my unit) Whatever the...

Yes, I understand. I'll stick with PROTOCOL_S_ROTEX then. For DHW, I guess this value is unreliable as my HP is not used for DHW :-) Back to the different protocols,...

This bug is really annoying. I'm getting multipart content in WCS 2.0.1 and not in WCS 1.0.0 which is fine... Is this bug fixed or not?

My Mapserver instance produces map tiles for elevation with BIL16 format, which is used by a 3D globe, but that's not the point. The source files that I'm using behind...

@jratike80 , thanks for your reply. My issue was more about inconsistency between WCS 1.0.0 and WCS 2.0.1. In the first whatever GDAL produce more than 1 file, only the...

Please give details about hardware (device/model) and software version (kernel, Android OS versions) Could be related to the same Mali bug described here? https://community.arm.com/support-forums/f/graphics-gaming-and-vr-forum/5469/glteximage2d-memory-leak