-
Notifications
You must be signed in to change notification settings - Fork 362
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
wms getlegendgraphic does not include custom parameters #7198
Comments
Currently you need to tell Terria which style to use for the layers for it to pick the correct legend URL from the getcap response. {
"type": "wms-group",
"url": "https://maps.isric.org/mapserv?map=%2Fmap%2Faf250m_nutrient.map",
"name": "Datasets",
"itemProperties": {
"styles": "default"
}
} Note the Here's a test link to see it working - http://ci.terria.io/main/#share=s-kQIzjq2NX3icLFxujghRGyJcg0y&clean Let me know if that works for you. |
Hi Nanda, thanx for having a look. the problem seems a bit different from how you assessed it. (although maybe i'm looking at it incorrectly) The layer was added without any reference to a style or legend, I assume internally terriajs calculates the url of the legend by concatenating the wms url with ?request=getlegendgraphic. unfortunately it strips the required map=example parameter in that process, which is essential for this mapservice backend.
Also consider that the WMS capabilities advertises the legend url, so there is actually no need to assemble it by terria Maybe @sidneygijzen, you can also have a look at this issue, to see if you can prepare a PR |
Yes, I think there are two issues here:
|
hello Nanda and Paul, Thanks a lot for the detailed information. I will have a look. |
our wms service https://maps.isric.org/mapserv?map=%2Fmap%2Faf250m_nutrient.map has a custom url parameter
map
, when this layer is added to the terria map, the legend graphic is not shown because the getlegendgraphic request does not include the custommap
parameter.This is quite unexpected, because the getcapabilities actually lists the correct legend url
The text was updated successfully, but these errors were encountered: