1 / 24

June 12 th 2007

Storing data for integrated 1D, 2D, 3D models of rivers, estuaries and seas. June 12 th 2007. Bert Jagers. general intro Delft Hydraulics. Independent research foundation since 1927 about 300 people

william-garza
Download Presentation

June 12 th 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Storing data for integrated 1D, 2D, 3D models of rivers, estuaries and seas June 12th 2007 Bert Jagers

  2. general intro Delft Hydraulics Independent research foundation • since 1927 • about 300 people • research and expert advise projects worldwide: Europe, Asia (Japan, Hong Kong, Singapore, China, Middle East, …), Africa (Egypt, South Africa, …), America (USA, Panama, …), Australia • numerical simulation models and operational systems

  3. modelling system 1 Delft3D: Windows & Linux, parallel • Characteristics: 2D or 3D curvilinear model • Multi-domain (multi-tile), sigma- or z-layer • Application areas: ocean, sea, coast, estuary, river • Hydrodynamics, waves, meteorological forcing • Morphodynamics, stratigraphy • Ecology, water quality Many users around the world: research institutes, universities, and consultants

  4. Delft3D from global scale modelling … Aceh earthquake, Dec ‘04

  5. … and long time scales … 50 – 1000 years

  6. … via storm surge predictions … Typhoon Frankie Vietnam (’96)

  7. … to detailed engineering studies … 10 m – 10 km, 1 hour – 10 years Dubai

  8. … and flume experiments

  9. netCDF/CF issues Curvilinear, multi-tile, clipped coordinates Staggered Arikawa-C style scheme: storing restart data versus generic output

  10. netCDF/CF issues Local features: weirs, dykes, dams, bridges, … Staggered Arikawa-C style scheme: data located at cell centres, cell interfaces and some at the original grid points

  11. GIS integration preprocessing: grid generation data interpolation feature mapping

  12. GIS integration postprocessing online visualisation netCDF support by GIS systems (ArcGIS 9.2) will it be CF aware?

  13. German part  Dutch part  netCDF/CF issues regional models: 1) use coordinate systems of local data providers (grid mapping) & keep track of coordinate system used throughout modelling system 2) use global coordinates (like netCDF/CF) & use GIS for the projections (keep track of accuracy for local detailed models!) deal with vertical datums Dutch NAP = Belgian TAW + 2.32 m

  14. netCDF/CF issues Generalised sigma, mixed sigma-z-coordinates: extra vertical coordinate options Aggregation table: data provided on irregular “subgrid”

  15. … to be integrated with …

  16. modelling system 2 SOBEK : Windows & Linux • Characteristics: integrated 2D & 1D (open channel & sewer) • Multi-domain (multi-tile) • Application areas: river, rural, urban • Hydrology, hydrodynamics, groundwater • Morphodynamics, real-time control • Emissions, ecology, water quality Many users around the world: research institutes, universities, and consultants

  17. 1D channels and levees 2D plains overlap with Delft3D applications flooding, shallow lakes, …

  18. regional scale applications albufera lake melbourne

  19. flood early warning systems from meteo data to flood prediction (as local as realistically possible) operational aspects: 24 hours, 7 days per week distributed data access

  20. netCDF/CF issues Again • Multi-tile, staggered scheme • Regional models, coordinate systems, GIS integration Additional • Combined 1D-2D, cross-sections • Naming conventions (water level in pipe = sea_surface_height_above_geoid?)

  21. … gives an generally unstructured code …

  22. netCDF/CF issues How to store unstructured grids and the associated data?  finite volume approach: distinguish volumes & fluxes multiple associated GIS expressable one grid one topology data location sets Why not use the same approach for LRG?

  23. the end Questions? bert.jagers@wldelft.nl

More Related