I have seen two distinct naming conventions for IRIS files used by Environment Canada, and I have adapted the code to work with either of them. Here are two examples:
- DOPVOL1_A:20130720135127
- 201607202330~~DOPVOL1_C:URP:XAM:RADAR:IRIS
Currently, the code handles either of these naming conventions. However, neither of these work on Windows, as colons are a reserved character, and cannot be used while naming a file.
In order to fix this issue on Windows, we will need to agree on a third IRIS file naming convention that does not involve special characters. My suggestion is the following:
Proposed convention: YYYYMMDDHHMM-TYPE
For example: 201607202330-DOPVOL1_A or 201607202330-CONVOL
Note: This is currently only an issue for IRIS files, as the naming conventions for NEXRAD and ODIM_H5 files do not contain any special characters.
I have seen two distinct naming conventions for IRIS files used by Environment Canada, and I have adapted the code to work with either of them. Here are two examples:
Currently, the code handles either of these naming conventions. However, neither of these work on Windows, as colons are a reserved character, and cannot be used while naming a file.
In order to fix this issue on Windows, we will need to agree on a third IRIS file naming convention that does not involve special characters. My suggestion is the following:
Proposed convention: YYYYMMDDHHMM-TYPE
For example: 201607202330-DOPVOL1_A or 201607202330-CONVOL
Note: This is currently only an issue for IRIS files, as the naming conventions for NEXRAD and ODIM_H5 files do not contain any special characters.