Discussion #2620

Orthophoto mosaic - One coverage of 10500 coverages?

Added by Jukka Rahkonen almost 5 years ago. Updated almost 5 years ago.

Status:New
Priority:Normal
Assignee:-

Description

I have an orthophoto mosaic that covers the whole Finland with 10418 physical orthophoto files from years 2000-2015 with no gaps nor overlaps. Now I wonder if I have one big coverage with a time dimension, or 10418 coverages.

Having each orthophoto file as a separate coverage would give a handy way for downloading predefined datasets from WCS. However, GetCapabilities would be huge and downloading imagery from an area that intersects footprints of several orthophotos would be tedious for the users.

Would it be possible to have a top level coverage that consists of other coverages? The lower level coverages (orthophotos) may have also other attributes than just acquisition year and it could be useful to have some method for accessing their own metadata.
 

History

#1 Updated by Jukka Rahkonen almost 5 years ago

Jukka Rahkonen kirjoitti:

I have an orthophoto mosaic that covers the whole Finland with 10418 physical orthophoto files from years 2000-2015 with no gaps nor overlaps. Now I wonder if I have one big coverage with a time dimension, or 10418 coverages. Having each orthophoto file as a separate coverage would give a handy way for downloading predefined datasets from WCS. However, GetCapabilities would be huge and downloading imagery from an area that intersects footprints of several orthophotos would be tedious for the users. Would it be possible to have a top level coverage that consists of other coverages? The lower level coverages (orthophotos) may have also other attributes than just acquisition year and it could be useful to have some method for accessing their own metadata.  

 

I suppose that the answer is in the Orthophoto document http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_OI_v3.0.pdf. The  Annex E "is intended to help the  reader to  clearly  understand  this  INSPIRE  data  specification  and  in  particular,  to  show  data providers the simplest way of making their data INSPIRE compliant".

#2 Updated by Peter Baumann almost 5 years ago

First, I must say that I prefer the single coverage solution - IMHO it is what users understand easiest. That does not exclude an implementation based on some internal tiling, be it based on the incoming file structure, or some chopping into suitable sizings.

That said, CIS 1.1 allows a "partitioned" coverage where a partition can contain (even recursively) sub-coverages, as long as some homogeneity constraints are fulfilled (range type, same CRS, not overlapping). But then again, delivering this to an innocent user as-is would likely make their favourite GIS tool frown.

-Peter

 

 

Also available in: Atom PDF