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

For MapML client proxy, allow GetFeatureInfo to be directed locally and transformed from application/vnd.ogc.gml to text/mapml #79

Open
prushforth opened this issue Jan 10, 2025 · 0 comments
Labels
enhancement New feature or request GetFeatureInfo

Comments

@prushforth
Copy link
Member

Currently the generated <map-link rel="query" tref="https://mapserver.example.org/wms_cgi?request=GetFeatureInfo&...&info_format=text/plain"> is fully directed by default at the remote WMS, using the info_format=text/plain GetFeatureInfo parameter by default, since it's unlikely that the remote WMS supports text/mapml yet.

There should be a way to obtain the MapML response containing a <map-link rel="query" tref="https://my-geoserver.example.net/geoserver/.../?request=GetFeatureInfo&info_format=text/mapml...">

This could be done via a checkbox in the MapML layer Publishing panel, and it could be represented dynamically via a format_options mapml query link control parameter (name tbd).

@prushforth prushforth added enhancement New feature or request GetFeatureInfo labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request GetFeatureInfo
Projects
None yet
Development

No branches or pull requests

1 participant