-
Notifications
You must be signed in to change notification settings - Fork 13
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
Coverage representation in HTML #14
Comments
Teleconference 20190426: It's agreed that HTML is not a suitable format for coverage's range set. |
Here is a sample HTML frontend for coverages, is that what you have in mind with an HTML delivery? |
when noticing this discussion, i wondered if the use case "browsing the api through a browser" has been considered. To me it makes sense to have a html representation for any api-level, with option to drill down to lower levels. I agree that representing actual pixel values as a html-table may not be very sensible, but one level up would make sense to have a html page with links to the actual grids as image |
That assumes that the coverage is 2D and a grid and/or can be represented as a 2D image, and that isn't true for all coverages. I think there would be an issue too for very large coverages, you'd want some sub-setting, or scaling operations rather than the whole coverage. I was thinking that by links you meant like |
this reminds me of WCPS which could be typed into a form, or as part of a prefabricated link. Here is a demo (select a query from the bottom of the page, then press "execute"): |
@pvgenuchten One possibility would be an HTML page (or pages) for the collection a thumbnail for each coverage. Only works for 2-D images, but it is a common approach we should consider. |
who decides when a practice is best? ;-) |
Current version (12/30/19) treats the range set (pixels) different from the other content. |
Can you please point us to where exactly that different behavior is specified? |
Currently discussion of HTML seems to mostly concentrate on encoding coverage metadata in HTML, ie: not the range set. If we talk about encoding a complete coverage we need to establish an HTML encoding including the range set. (Sometimes an image can be rendered: if the coverage is 2D and contains 1 or 3 integer bands.)
The text was updated successfully, but these errors were encountered: