Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SMUSI REG format: dry periods not properly recognized? #82

Open
jamaa opened this issue Oct 25, 2022 · 0 comments
Open

SMUSI REG format: dry periods not properly recognized? #82

jamaa opened this issue Oct 25, 2022 · 0 comments
Labels
fileformats question Further information is requested

Comments

@jamaa
Copy link
Member

jamaa commented Oct 25, 2022

When reading the SMUSI REG format Wave expects empty lines in the file to denote dry periods. Wave then adds a node with the value of 0 before and after each dry period while reading the file.

I have encountered a file where dry periods are not empty lines, the time just skips forward. Wave does not insert 0-values between the gaps which leads to a misinterpretation of the values e.g. when changing the timestep.

Niederschlagsdaten der Station Frankfurt-Eckenheim
hN = 626 mm/a - 01.01.1966 - 23.08.2007
=============
F-EH  1  1 1966    0    0    6    6    6    6    6    6   25   28   28   28   28
F-EH  1  1 1966    1   28   50   51   51   60  118  118  118   87   87   87   87
F-EH  1  1 1966    2   87   92   98   98   98   98   98   96   94   94   94   94
F-EH  1  1 1966    3   94   94   94   87   53   53  142   83   49   49   49   49
F-EH  1  1 1966    4   49   49   49   89  103  103  103  103  103  100   82   82
F-EH  1  1 1966    5   82   82   94  117  117  117  117  117  117   13    0    0
F-EH  1  1 1966    6    0   25   49    3    0    0    0    0    0    0    0    0
F-EH  1  1 1966   14    0    0    0    0    0    0    0    0   51   19    8    8
F-EH  1  1 1966   15    8   88    0    0    0   86   54   20   97  114  114  605
F-EH  1  1 1966   16  141    3    0    0    0    0    0    0    0    0    0    0
F-EH  1  1 1966   22    0    0    0    0    0    7   39   39   25    9    9    9
F-EH  1  1 1966   23    9    9    9    9    9    9    9    2    0    0    0    0
F-EH  2  1 1966    8    0    0    0    0    0   35   89    6    6    6    6    6
F-EH  2  1 1966    9    6    6    6    6    6    6    6    6    1    0    0    0
F-EH  2  1 1966   10    0    0    0    0    0    0    0    0    0    0  154    0
F-EH  2  1 1966   12    0    0    0   77  224  224  110    0    0    0    0    0
F-EH  2  1 1966   14    0    0    0    0    0    0    0    0    0    0   40   22
F-EH  3  1 1966    7    0    0    0    0    0    0    0    0    0   77   84   84
F-EH  3  1 1966    8   84   61    0    0    0    0    0    0    0    0    0    0
F-EH  3  1 1966   11    0    0    0   48  190   45   14   14   14   14   88   53
F-EH  4  1 1966    6    0    0    0    0    0   75   40   22    0    0    0    0
F-EH  4  1 1966   23    0    0    0    0    0    0    0    0   14   25   14    0
F-EH  9  1 1966   15    0    0    0    0    0    0    0    0  128   34   10   10
F-EH  9  1 1966   16   87    0    0    0    0    0    0    0    0    0    0    0
F-EH  9  1 1966   17    0    0    0    0    0    0    0    0    0    0    0   30
F-EH  9  1 1966   18  437  469  422   39   33    7    7    7    7   14   23   23
F-EH  9  1 1966   19   23   11    0    0    0    0    0    0    0    0    0    0

Not sure whether this is "normal" for the REG format, but if it is, Wave should be able to deal with it, by checking the time difference between lines and inserting 0-values whenever there is a gap.

@jamaa jamaa added the question Further information is requested label Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fileformats question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant