ENS Virtual paths (Virtual path to products)
The backend storage contains millions of products. It cannot be believable to display the entire list of products to the end-user via ENS interface into a unique directory container.
The ENS solution is to spread products into directories hierarchy based on the anticipated usages of the end-users.
At the ingestion time, ENS extracts a set of metadata from products. These metadata are used to organize the ENS directory tree.
The hierarchy tries to define some systematic mechanisms. It has been defined “What/When/Where” organization, where the first set of directories and sub directories concerns what kind of data is exposed; the second set of sub directories regard when are acquired the data; and the last matches where data are located.
Each level is optional, but order is always abided by the system.
Metadata names defined here are conform to the OGC/HMA standardized naming conventions.
What level
The following list defines the set of possible paths to recover products within ENS directory tree.
- sensorType/processingLevel
- platformShortName/platformSerialIdentifier/instrumentShortName/processingLevel/productType
- platformShortName/platformSerialIdentifier/processingLevel/productType
- platformShortName/instrumentShortName/processingLevel/productType
- platformShortName/processingLevel/productType
- platformNSSDCID/instrumentShortName/processingLevel/productType
- platformNSSDCID/processingLevel/productType
When Level
Quite simplier than the previous directory set, these directory names are based on time information of the products:
- beginPosition:year
- beginPosition:year/beginPosition:month
- beginPosition:year/beginPosition:month/beginPosition:day
Where level (under development)
Where level aims to split the products by predefined area. These area are predefined into ENS system to allow resolving intersection between area footprint and product footprint when exists.