Still running on MacBook Pro with Apple M1 Pro but under macos Ventura 13.5.2. The problem persists! See attached:
but MeteoIO works. The files are accessible via the following link: lrwxr-xr-x 1 fierz staff 109B Aug 4 14:18 input@ -> /Users/fierz/SWITCHdrive/shareData/data-sD/dataManagementSLF/dmSLF_testResearchStations/dmS_rsCfgFiles/input/
Attached is a CAAML-file with a fake profile located in Leadville, Co, USA, that is, time zone -06:00. Out of this CAAML-file I exported A JSON. Unfortunately, the time stamp is converted to Zoulou time (UTC) but the time zone is lost. Rendering that JSON, I get a time stamp "Date / Time: 2023-01-15 16:45 +01:00", which corresponds to "2023-01-15T15:45:00.000Z" in my time zone, CET (UTC+1) at that datefake-202301150945.SimpleProfile.json
fake-202301150945.SimpleProfile.caaml. fake-202301150945.SimpleProfile.json
When importing JSON-files into niViz, some values, for example neg heights, can lead to errors in exported CAAML-files. A validation of the exported files would help avoid such problems.
Note that the rendering in niViz is not affected by these errors.
Currently, SH is shown in the timeline but not in the corresponding simple profile on the right (test with niviz.org timeline on 2014-10-24T09:00)
... except if a profile (date) is selected.
Confirm erratic behaviour if timeline canvas contains a profile marker.
Note: the CAAML data model always consider the snow surface to be the zero datum and uses increasing positive depth and layer thickness to delineate layers. I can imagine the visualisation to deal with any use case but not currently. It may require the user to set special settings though. I know Thomas will not like this comment ;-)
I agree this could be included in graph but not in CAAML output
Verified that process as described above works. It is a matter of documenting it in the users' help.
Thus the three use cases are:
Fierz (c86e408a) at 18 Feb 09:01
renamed Excel template
Steps to reproduce the problem:
Expected result: The SMP profile included in the CAAML file is correctly exported to JSON
Actual result: The penetration force is missing, only the depth values are found (see attachment).
Attachments:
As of 2023-01-27, the effect is not reproducible. Downloading the caaml-file, opening it in niViz and exporting as JSON ends in a correct file. => close issue
Better: use /Users/fierz/SWITCHdrive/shareData/data-sD/LAR_data/laret_dataProcessing/laret_templates/laret-yyyymmdd_excel2nivizJSON-template.xlsx as a template!