Changes between Initial Version and Version 2 of Ticket #374


Ignore:
Timestamp:
Jan 10, 2013, 6:13:44 PM (13 years ago)
Author:
steve
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #374

    • Property Owner changed from ole to steve
    • Property Summary changed from consistent use of csv files to Consistent use of csv files

  • Ticket #374 – Description

    initial v2  
    11Just wondering if there is any scope for you to fix the way we import a time series into ANUGA.
     2
    23 
    34At the moment for a hydrograph or rainfall, we have to create a space separated time series (.asc format) and then convert it to a binary (.tms format) before we can call it.
    45 
     6
    57This used to be the case with your digital terrain data where one would have to create a csv (x,y,z) and then convert it to a .pts file so ANUGA could read it in. Now we can just specify the .csv and ANUGA does it during the intial setup stage which is better as there is less user input.
     8
    69 
    710Is there any chance of getting all the other time series inputs (eg boundary, rainfall, hydrographs) to be done the same way? So the user would just create a .csv of their rainfall (or hydrograph or tide) data and instead of specifying a .tms file, ANUGA just reads the .csv and converts it to a .tms during the set up stage?