-
Notifications
You must be signed in to change notification settings - Fork 0
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
Legend URL missing version information from Capabilities document in GeoServer 2.20.0 #10
Comments
Linked to #7 |
Documentation about GetLegendGraphic: https://docs.geoserver.org/stable/en/user/services/wms/get_legend_graphic/index.html |
Upstream issue: https://osgeo-org.atlassian.net/browse/GEOS-5472 |
And this is the line where all happens: |
@grigoriouelena shall we add a custom URL so we can test the validator? |
Reported upstream here: https://osgeo-org.atlassian.net/browse/GEOS-10336 |
After various tries I come to the conclusion that the provision of an image URL in the Styles GUI is independent of the LegendURL that geoserver forms for the legend graphic in the getcapabilities response. By that I mean that whatever legend the user defines in the Styles GUI, geoserver will still provide a GetLegendGraphic request to the WMS, omitting the version parameter. Relevant issue in the INSPIRE validation helpdesk here: INSPIRE-MIF/helpdesk-validator#680 @kalxas I guess that we should try to find the template that geoserver uses to form the capabilities response and add the version parameter. How feasible is this? |
I guess this one is also to be closed @grigoriouelena ? |
The text was updated successfully, but these errors were encountered: