I successfully overlayed a WMS layer in google maps v3, however, as the information on tiles is black on transparent, it is not well seen on dark background (like satellite map), see some tile for example:
(This was the WMS link to retrieve that tile)
Question: how to modify the above WMS request to change the foreground color (currently black) to some custom color (e.g. red)? In other words, how to style the layer? The server is apparently able to do it for this layer, since it is possible to do it via their web map application (which works in IE only), where you can select the color. See this map image for example:
(The following link was used to retrieve the image - note that it contains scale and logo, so it's not a proper tile.)
Unfortunatelly, this web application doesn't use WMS to get this styled map so I can't just copy the styling parameters to WMS request. I must do the styling via the WMS request (because this other request format is proprietary, retrieves whole map - not designed for tiles - and it doesn't seem to support WGS coordinates) - how shall I do it?
I tried to:
- look at the WMS documentation, especially version 1.1.1
- look at the SLDs, but it seems pretty complex thing to grasp...
- look at the GetCapabilites command output for the WMS server
- Also, having look at DescribeLayer and GetStyles command outputs for my desired layer (HLMCR) I don't even know if this layer will support styling over WMS...
I got lost, I'd be grateful if you point me to the right direction - or information if it's even solvable in WMS (for this layer).
"It's not possible" is also a useful answer for me!
Thanks in advance.
At first glance, it looks like this is a Mapserver 5.x implementation, and getCapabilities notes that UserDefinedSymbolization SupportSLD="1" is enabled at the Map level, which IIRC means that all Layers should inherit it.
So in theory you should be able to supply SLD either in the GET request or in a file somewhere and supply the URL of your SLD to the GET request, and be all set.
Writing the SLD will be the annoying bit, but if you think you have some SLD that should work but doesn't, paste it here.
Use a wrapper script that reads the image from the WMS and recolorizes it:
Wrapper
Here is an example written in PHP:
<?php
$url = $_GET['url'];
$im = imagecreatefrompng($url);
if($im && imagefilter($im, IMG_FILTER_COLORIZE, 255, 0, 0, 0)){
// this line is only needed if original image has transparency (32bit/pixel)
// and you want to preserve that transparency
imagesavealpha($im, true);
header('Content-type: image/png');
imagepng($im);
}else{
echo 'Conversion failed.';
}
imagedestroy($im);
exit;
?>
Then instead of calling your WMS link, you call the wrapper and pass the WMS link as a parameter (recolor_png.php?url=...). The wrapper reads the original image and returns a new PNG with a colorized version. Don't forget that the link that you pass as a parameter must be urlencoded to work correctly (all special characters replaced by their %XX hex notation). In JavaScript you can do that using the encodeURIComponent() method.
Here is a working example using your link and the above wrapper on my server:
This is the resulting image (semi-transparent version):
(source: digilog.de)
The same wrapper without semi-transparent output (imagesavealpha deleted from code):
And the resulting non-transparent image:
(source: digilog.de)
I will leave that wrappers online for some days for you to test.
Caching
As this conversion is processor intensive, it might be wise to add some caching code to the wrapper:
- create a hash code from the give URL, e.g.: $hash=md5($url)
- check whether an image named $hash.png exists in a storage subfolder
- if so: read the image from file and return it
- otherwise: create image, save it as $hash.png in subfolder and also return it immediately
If you expect your WMS content to change over time: Also check the creation date of cached images and purge them if they are too old (like a month or so). So any changes to the WMS maps will ripple into your system after a maximum time of one month.
The WMS link already has some custom params that allow you to do exactly what you ask for. The link is the following:
http://geoportal2.uhul.cz/mapserv/php/mapserv3.php?project=oprl_2011&mode=map&mapsize=256%20256&layers=HMLCR%20&x=1322616184548&map_SMO_class_0_color=0%200%200&map_HMLCR_class_0_color=255%200%200&mapext=-679915.1258015268%20-1062651.2224427482%20-679660.3694656485%20-1062461.062442748
If you inspect it you will notice that between all the url encoded parameters there is a parameter interestingly called: map_HMLCR_class_0_color
If you change its value to, say green (whose RGB code is 0,255,0), the layers are rendered in green. The color is expressed as an RGB code. There is also another parameter map_SMO_class_0_color but I don't understand what that does. Perhaps it styles some feature which is not visible in that request?
Example for green color:
http://geoportal2.uhul.cz/mapserv/php/mapserv3.php?project=oprl_2011&mode=map&mapsize=256%20256&layers=HMLCR%20&x=1322616184548&map_SMO_class_0_color=0%20100%20200&map_HMLCR_class_0_color=0%20255%200&mapext=-679915.1258015268%20-1062651.2224427482%20-679660.3694656485%20-1062461.062442748
which produces the following:
A note con rgb color representation in Mapserver
the RGB triplet must be written as follows in the request:
R G B
(note that the blanks are required). Whose URl encoded representation is:
R%20G%20B
because %20 is how space is encoded in URLs.
来源：https://stackoverflow.com/questions/8320512/how-to-style-transparent-overlayed-wms-layer