Closed poplarShift closed 5 months ago
(Almost) everything is possible.
The reason for the GOTM format is that it much, much easy to read using Fortran as it only takes on pass through. In EAT the observations are handled by Python and Python is way better handling text files than Fortran.
But if anybody wants to develop a reading routine that can be used as a drop-in for what we have now - and in addition support the other format it is fine with me. It would be a big advantage/requirement that the correct format is auto-detected.
Karsten
For depth-dependent variables, GOTM uses this peculiar format:
etc,
whereas EAT uses a standard TSV format:
would it be possible to migrate GOTM to such a TSV format as well?