... | ... | @@ -33,7 +33,7 @@ The specification of these keys also implies a certain standard for the header q |
|
|
* [GRIS](standards_and_recommendations/Instrument-Specific Fields for GRIS Observation Descriptions)
|
|
|
|
|
|
## Links
|
|
|
This block contains a lists of ObjectIds linking to specific binary files in GridFS collections. The struchture is as follows:
|
|
|
This block contains a lists of ObjectIds linking to specific binary files in GridFS collections. The structure is as follows:
|
|
|
|
|
|
``` yaml
|
|
|
type_name: [list of object_ds]
|
... | ... | @@ -41,6 +41,19 @@ type_name: [list of object_ds] |
|
|
|
|
|
The `type_name` keys may only be valid binary resource types as defined in the list of [binary resource types](standards_and_references/Resource-Types). This list is extensible by request and gives an impression over what resources the archive can ingest and visualize.
|
|
|
|
|
|
Interestingly, trials show that retrieving the objects from the database in this scheme is considerably fater than querying a linkage key such as the old approach where a `observation_id` was added to every binary file's entry. Queries to get these files can be performed like:
|
|
|
``` python
|
|
|
import gridfs
|
|
|
from kis_tools.generic import get_sdc_connection
|
|
|
sdc = get_sdc_connection()
|
|
|
gfs = gridfs.GridFS(sdc.sdc_test, "gris_l1_data")
|
|
|
|
|
|
file_ids = [ObjectId(str1),ObjectId(str2),...]
|
|
|
gfs.find({"_id":{"$in":file_ids}})
|
|
|
grid_out_objects = [*gfs.find({"_id":{"$in":file_ids[:50]}})]
|
|
|
|
|
|
```
|
|
|
|
|
|
## Flags
|
|
|
This section contains binary flags that are used for the archives backend or for querying. The following flags are defined:
|
|
|
|
... | ... | |