Data Model

The core resources in EOxServer are coverages, more precisely GridCoverages. The EOxServer data model adopts and strongly relates to the data model from EO-WCS (OGC 10-140) as shown below in Figure: “EO-WCS Data Model from OGC 10-140”.

../../_images/EO-WCS_Data_Model.png

EO-WCS Data Model from OGC 10-140

Core

Figure: “EOxServer Data Model for the Core” below shows the data model of EOxServer’s core.

../../_images/model_core1.png

EOxServer Data Model for the Core

Data Integration Layer

Figure: “EOxServer Data Model for Coverage Resources” below shows the data model of the coverage resources. Note the correlation with the EO-WCS data model as shown above.

../../_images/model_coverages.png

EOxServer Data Model for Coverage Resources

Data Access Layer

Figure: “EOxServer Data Model for Back-ends” below shows the data model of the back-ends layer.

../../_images/model_backends.png

EOxServer Data Model for Back-ends

Task Tracker Data Model

Asynchrounous Task Processing (ATP) uses its own DB model displayed in Figure: “EOxServer Data Model of ATP Task Tracker” to implement the task queueu, store the task inputs and outputs and track the tasks’ status. (For more detail on ATP subsystem see “Asynchronous Task Processing”).

../../_images/model_processes.png

EOxServer Data Model of ATP Task Tracker