GitLab 14.5 is now available. 🚀 Learn what's new.

Commit ed7f7373 authored by Timm Schoening's avatar Timm Schoening
Browse files

Update README.md

parent 1fef17ca
......@@ -5,7 +5,7 @@ Achieving FAIRness and Openness of (marine) image data requires structured and s
## Delicious (marine) image data
iFDOs consist of sections. Some are required, some are recommended, some are optional. You will only have FAIR image data with the required sections. You will only gain visibility and credit for iFDOs with the recommended sections populated. And you will only have awesome image data in case you also populate your domain-specific optional sections.
![Delicious iFDOs](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-profiles-fdos/-/raw/master/graphics/delicious_iFDOs.png "Delicious iFDOs" \| width=500px)
![Delicious iFDOs](https://gitlab.hzdr.de/datahub/marehub/ag-videosimages/metadata-profiles-fdos/-/raw/master/graphics/delicious_iFDOs.png "Delicious iFDOs"){:height="36px" width="36px"}
The iFDO sections can consist of header and item information subsections. For the core iFDO, the header subsection contains all information that is identical for all the image items. The image item information subsection contains all the information where the individual images require their specific metadata value. An example is the coordinate: for a moving camera, all image items require their own image-latitude value. In case of a stationary camera, the image-set-latitude value can be used instead.
## iFDO sections
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment