Skip to content
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

OPACITY not working with GetMap Requests for 7.0.2 #5343

Closed
jmckenna opened this issue Oct 31, 2016 · 7 comments
Closed

OPACITY not working with GetMap Requests for 7.0.2 #5343

jmckenna opened this issue Oct 31, 2016 · 7 comments
Labels
Milestone

Comments

@jmckenna
Copy link
Member

jmckenna commented Oct 31, 2016

  • small mapfile (and data and commands) to reproduce problem: https://gatewaygeomatics.com/dl/ticket-opacity-wms.zip (400 KB)

  • no problems using normal CGI

  • however, using 7.0.2 opacity is not applied for a GetMap request

  • GetMap output for 7.0.1 (notice parks polygons are transparent)
    mapserv1

  • GetMap output for 7.0.2 (parks polygons are not transparent)
    mapserv2

  • interesting, if I try to execute the same GetMap request at the commandline....

mapserv -nh QUERY_STRING="MAP=opacity-wms.map&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&BBOX=50.43646181818179741,-137.2127006060605936,81.69507636363634617,-85.115009696969679&CRS=EPSG:4326&WIDTH=990&HEIGHT=594&LAYERS=bathymetry,park&STYLES=,&FORMAT=image/png&DPI=96&MAP_RESOLUTION=96&FORMAT_OPTIONS=dpi:96&TRANSPARENT=TRUE%20HTTP/1.1" > test.png

the following message is returned (only with 7.0.2), and a map image without transparency is generated:

*** BUG ***
In ???: The expression bits == NULL || (rowstride_bytes % sizeof (uint32_t)) == 0 was false
Set a breakpoint on '_pixman_log_error' to debug
@jmckenna jmckenna added this to the 7.0.3 Release milestone Oct 31, 2016
@jmckenna jmckenna added the Bug label Oct 31, 2016
@rouault
Copy link
Contributor

rouault commented Oct 31, 2016

@jmckenna Your request works for me with latest state of branch-7-0 (so nearly identical to 7.0.2) on Linux with cairo-1.10.2 (the polygons are transparent both in standalone mode "mapserv -nh" or within mongoose web server).
Running it under Valgrind doesn't show any problem reported. Reviewing (quickly) changes between 7.0.1 and 7.0.2, nothing strikes as being related. Could it be that something else than MapServer changed between your 7.0.1 and 7.0.2 build, like the cairo version used ?

Hum, I just found #5181 which seems related. Is it possible that your build have pixman enabled ? (my build has pixman disabled)

@jmckenna
Copy link
Member Author

Indeed my builds have pixman enabled

@jmckenna
Copy link
Member Author

wow good find that related issue even has similar error message

@jmckenna
Copy link
Member Author

i will disable pixman and report back....

@jmckenna
Copy link
Member Author

jmckenna commented Oct 31, 2016

@rouault that was it! disabling pixman gives the proper map image, and no more error at the commandline. yikes!

I guess this is a 'won't fix', but wow many will hit it with pixman in their builds.

@elzouavo
Copy link

Pixman is an CAIRO library dependency. I've compiled MapServer with Cairo. So I've got this issue. I think more and more people are going to use Cairo. So this problem will become increasingly embarrassing for the community. But I could be wrong ;-)

@jmckenna
Copy link
Member Author

Here again. I wonder if for MapServer 7.6.0 we should either 1) fix Pixman support, or 2) completely remove Pixman from the MapServer codebase. I'm open to hearing thoughts on either option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants