Opened 10 years ago

Last modified 10 years ago

#374 new enhancement

Consistent use of csv files

Reported by: steve Owned by: steve
Priority: normal Milestone:
Component: Functionality and features Version:
Severity: normal Keywords:

Description (last modified by steve)

Just wondering if there is any scope for you to fix the way we import a time series into ANUGA.

At 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.

This 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.

Is 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?

Change History (2)

comment:1 Changed 10 years ago by steve

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

comment:2 Changed 10 years ago by steve

  • Description modified (diff)
Note: See TracTickets for help on using tickets.