I'm kind of concerned about this. Not because it doesn't work in 3.1.0, but
because in all of our deployments thus far we have had no issues getting ECW
to work on Mapguide 3.1.0.
Would this be a Linux only issue or something else? I looked at what we
install and it's the content of the gdal-1.10-msvc2012-x64.zip and I'm
fairly certain we got it off of the OSGEO website.
Looking at what we deploy, it's the regular 22.214.171.12464 build on 64-bits on
Windows. So it really seems like we're as vanilla as it comes and doing the
steps in the initial link works just fine. Honestly, outside of forgetting
to set the GDAL_DRIVER_PATH environment variable, it was never an issue for
us. Maybe the environment variable isn't set properly or for whatever reason
the Mapguide service process doesn't have access to read it properly?
The GDAL_DRIVER_PATH sort of works. I set it to the Server\Fdo\gdalplugins
directory. But the ECW is in black and white. I guess this is because the
ECW files are in a newer format than the driver can handle.
Looks like you got it working better, but I will confirm that we do point to
\OSGeo\MapGuide\Server\Fdo\gdalplugins for the GDAL_DRIVER_PATH.
I do recall some weirdness happening when the alpha band was used in the
past. I'm going from memory, but I could be wrong. An ECW had 4 color bands,
so ARGB. Our issue was that the alpha band wasn't properly managed so they
appeared with 100% transparency. So this isn't exactly what's happening to
you. I can confirm, however, that an ECW generated with FME Desktop 2013 SP4
are properly handled by Mapguide as long as it's a 3-band RGB image.
I would look into what color bands your ECWs are using maybe?
Are you going to release a more 'official' 3.1.1 build?
We found that 3.1.0 on Windows 2016 server does not show ecw's, but version
3.1.1 does. It however has the word 'Test' in the service name...