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

Implementing a View service in the same API #37

Open
cportele opened this issue Apr 7, 2020 · 1 comment
Open

Implementing a View service in the same API #37

cportele opened this issue Apr 7, 2020 · 1 comment
Labels
MIG implication Issues to be raised for discussion by the MIG or MIG-T

Comments

@cportele
Copy link
Contributor

cportele commented Apr 7, 2020

This question is not about using OGC API Features for an INSPIRE Download service, but about providing an INSPIRE View service via the same API. Today, the most appropriate mechanism for many feature datasets would be the use of vector tiles (with one or more associated styles) using OGC API Tiles.

However, there is the problem that the network service regulation (not "just" in the technical guidance) has technology-specific requirements which by now are outdated and currently prohibit such an approach (link):

The View Service shall support at least one of the following image formats:

  • the Portable Network Graphics (PNG) format,
  • the Graphics Interchange Format (GIF), without compression.

Has there been any discussion about revising the regulation to update this technical requirement or, preferably, remove such technical detail that is always at risk of becoming outdated?

@heidivanparys
Copy link
Contributor

@alexanderkotsev We need a GitHub label "NS regulation", or something similar.

@alexanderkotsev alexanderkotsev added the MIG implication Issues to be raised for discussion by the MIG or MIG-T label Oct 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MIG implication Issues to be raised for discussion by the MIG or MIG-T
Projects
None yet
Development

No branches or pull requests

3 participants