Changeset 980

Timestamp:

Mar 1, 2005, 1:10:12 PM (20 years ago)

Author:

ole

Message:

Comments

Location:

inundation/ga/storm_surge/pyvolution

Files:

• data_manager.py (modified) (1 diff)
• documentation/assumptions.txt (modified) (1 diff)

inundation/ga/storm_surge/pyvolution/data_manager.py

@@ -20 +20 @@
 .tsh: ASCII format for storing meshes and associated boundary and region info
 
-
-#Not yet implemented
 .nc: Native ferret NetCDF format
 
-
-FIXME: What else
+A typical dataflow can be described as follows
+
+Manually created files:
+ASC, PRJ:     Digital elevation models (gridded)
+TSH:          Triangular meshes (e.g. dreated from pmesh)
+NC            Model outputs for use as boundary conditions (e.g from MOST)
+
+
+AUTOMATICALLY CREATED FILES:
+
+ASC, PRJ  ->  DEM  ->  PTS: Conversion of DEM's to native pts file
+
+NC -> SWW: Conversion of MOST bundary files to boundary sww
+
+PTS + TSH -> TSH with elevation: Least squares fit
+
+TSH -> SWW:  Conversion of TSH to sww viewable using Swollen 
+
+TSH + Boundary SWW -> SWW: SImluation using pyvolution
+
 
 """

inundation/ga/storm_surge/pyvolution/documentation/assumptions.txt

@@ -3 +3 @@
 If one wished to recreate scenarios prior to that date it must be done 
 using some relative time (e.g. 0).
+
+
+All spatial data relates to the WGS84 datum (or GDA94) and has been 
+projected into UTM with false easting of 500000 and false northing of
+1000000 on the southern hemisphere (0 on the northern).
+
+It is currently assumed that all computations take place within one UTM zone. 
+
+DEMs, meshes and boundary conditions can have different origins within 
+one UTM zone. However, the computation will use that of the mesh.
+
+The dataflow is: (See data_manager.py)
+
+
+ 
+
+