What formats to be included as an output for WCS?
#1 Updated by Peter Baumann over 4 years ago
What we found practically relevant:
- GeoTIFF for (referenced(nonreferenced) imagery
- NetCDF for general data (such as 3D x/y/t image timeseries cutouts)
- GML (because of canonical metadata and for 1-D extracts - in future: JSON for the same reasons)
- PNG for browser display of 2D data
But others may or may not share opinions on this slate.
#2 Updated by James Passmore over 4 years ago
- Status changed from New to Feedback
Why do we need to restrict the formats that a WCS can supply, isn't that going to be an implentation decison for any piece of software.
The formats cited as being required in the data specs is wider than that listed by Peter, so if we are to go for some recommendation of what a WCS implementation should support perhaps we might suggest all GDAL supported formats
#4 Updated by Ilkka Rinne over 4 years ago
I suppose the real issue here is if we can/should mandate each INSPIRE WCS to provide data encoded at least in one general-enough encoding/format. Personally I think it's difficult to mandate that across all INSPIRE WCS services, but it would have to be done in each Data Specification.
#7 Updated by Jukka Rahkonen over 4 years ago
I have been reading
and it seems to me that TIFF/GeoTIFF could be the preferred WCS format for both orthoimages and ElevationGridCoverage. It fulfills the Inspire requirements and all WCS servers can produce it. With LZW compression the file size is not much bigger than with lossless JPEG2000 which is also accepted in the orthophoto specifications, but not for elevation data.