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

Web metadata ows_schemas_location is not respected for OGC API Features, and appears to not be documented #7036

Open
ejn opened this issue Mar 4, 2024 · 3 comments · May be fixed by MapServer/MapServer-documentation#892

Comments

@ejn
Copy link
Contributor

ejn commented Mar 4, 2024

It looks like the references to the OGC API yaml schema files are currently hardcoded to http://schemas.opengis.net here

For other services there is / should be a (currently undocumented?) web metadata ows_schema_location (see reference in the change log and reference in code (note type in comment!)).

At the very least, hardcoding a http:// link prevents a browser parsing the linked schema when the OGC API service itself is running on https:// such that it should be considered to change all references to OGC schema files to default to https://, but that is outside the scope of this ticket.

TODOs:

  • The OGC API Features service should use the setting from ows_schema_location to reference the OGC yaml schemas
  • ows_schema_location should be documented
@ejn
Copy link
Contributor Author

ejn commented Mar 4, 2024

I guess the solution is to use msOWSGetSchemasLocation() in processApiRequest().

@ejn
Copy link
Contributor Author

ejn commented Mar 6, 2024

ows_schemas_location is sufficiently documented for the other services (e.g. https://www.mapserver.org/ogc/wms_server.html#index-21), just my search-skills let me down - once the PR for the docs for OGC API is merged then no more action should be required here.

@ejn ejn changed the title Web metadata ows_schema_location is not respected for OGC API Features, and appears to not be documented Web metadata ows_schemas_location is not respected for OGC API Features, and appears to not be documented Mar 6, 2024
@ejn
Copy link
Contributor Author

ejn commented Mar 6, 2024

Now I realised why I didn't find the documentation for the other services: The parameter name is ows_schemas_location (note plural schemas), and not ows_schema_location as recorded in the old changelog entry.

Irritatingly my new commit also records adding support for ows_schema_location for OGC API, but hopefully this comment may help any users in the future who are as confused as I was.

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

Successfully merging a pull request may close this issue.

1 participant