Dataset Open Access

RAPID input and output files corresponding to "RAPID Applied to the SIM-France Model"

David, Cédric H.; Habets, Florence; Maidment, David R.; Yang, Zong-Liang


Citation Style Language JSON Export

{
  "DOI": "10.5281/zenodo.30228", 
  "abstract": "<p><strong>Corresponding peer-reviewed publication</strong></p>\n\n<p>This dataset corresponds to all the RAPID input and output files that were used in the study reported in:</p>\n\n<ul>\n\t<li>David, C\u00e9dric H., Florence Habets, David R. Maidment and Zong-Liang Yang (2011), RAPID applied to the SIM-France model, Hydrological Processes, 25(22), 3412-3425. DOI: 10.1002/hyp.8070.\u00a0</li>\n</ul>\n\n<p>\u00a0</p>\n\n<p>When making use of any of the files in this dataset, please cite both the aforementioned article and the dataset herein.\u00a0</p>\n\n<p>\u00a0</p>\n\n<p><strong>Time format</strong></p>\n\n<p>The times reported in this description all follow the ISO 8601 format.\u00a0 For example 2000-01-01T16:00-06:00 represents 4:00 PM (16:00) on Jan 1<sup>st</sup> 2000 (2000-01-01), Central Standard Time (-06:00).\u00a0 Additionally, when time ranges with inner time steps are reported, the first time corresponds to the beginning of the first time step, and the second time corresponds to the end of the last time step.\u00a0 For example, the 3-hourly time range from 2000-01-01T03:00+00:00 to 2000-01-01T09:00+00:00 contains two 3-hourly time steps.\u00a0 The first one starts at 3:00 AM and finishes at 6:00AM on Jan 1<sup>st</sup> 2000, Universal Time; the second one starts at 6:00 AM and finishes at 9:00AM on Jan 1<sup>st</sup> 2000, Universal Time.</p>\n\n<p>\u00a0</p>\n\n<p><strong>Data sources</strong></p>\n\n<p>The following sources were used to produce files in this dataset:</p>\n\n<ul>\n\t<li>The hydrographic network of SIM-France, as published in Habets, F., A. Boone, J. L. Champeaux, P. Etchevers, L. Franchist\u00e9guy, E. Leblois, E. Ledoux, P. Le Moigne, E. Martin, S. Morel, J. Noilhan, P. Quintana Segu\u00ed, F. Rousset-Regimbeau, and P. Viennot (2008), The SAFRAN-ISBA-MODCOU hydrometeorological model applied over France, Journal of Geophysical Research: Atmospheres, 113(D6), DOI: 10.1029/2007JD008548.</li>\n\t<li>The observed flows are from Banque HYDRO, Service Central d\u2019Hydrom\u00e9t\u00e9orologie et d\u2019Appui \u00e0 la Pr\u00e9vision des Inondations. Available at http://www.hydro.eaufrance.fr/index.php.</li>\n\t<li>Outputs from a simulation using SIM-France (Habets et al. 2008).\u00a0 The simulation was run by Florence Habets, and produced 3-hourly time steps from 1995-08-01T00:00+02:00 to 2005-07-31T21:02+00:00. \u00a0Further details on the inputs and options used for this simulation are provided in David et al. (2011).</li>\n</ul>\n\n<p>\u00a0</p>\n\n<p><strong>Software</strong></p>\n\n<p>The following software were used to produce files in this dataset:</p>\n\n<ul>\n\t<li>The Routing Application for Parallel computation of Discharge (RAPID, David et al. 2011, http://rapid-hub.org), Version 1.1.0.\u00a0 Further details on the inputs and options used for this series of simulations are provided below and in David et al. (2011).</li>\n\t<li>ESRI ArcGIS (http://www.arcgis.com).\u00a0</li>\n\t<li>Microsoft Excel (https://products.office.com/en-us/excel).\u00a0</li>\n\t<li>The GNU Compiler Collection (https://gcc.gnu.org) and the Intel compilers (https://software.intel.com/en-us/intel-compilers).\u00a0</li>\n</ul>\n\n<p>\u00a0</p>\n\n<p><strong>Study domain</strong></p>\n\n<p>The files in this dataset correspond to one study domain:</p>\n\n<ul>\n\t<li>The river network of SIM-France is made of 24264 river reaches.\u00a0 The temporal range corresponding to this domain is from 1995-08-01T00:00+02:00 to 2005-07-31 T21:00+02:00.</li>\n</ul>\n\n<p>\u00a0</p>\n\n<p><strong>Description of files </strong></p>\n\n<p>All files below were prepared by C\u00e9dric H. David, using the data sources and software mentioned above.\u00a0</p>\n\n<ul>\n\t<li><em>rapid_connect_France.csv.</em>\u00a0 This CSV file contains the river network connectivity information and is based on the unique IDs of the SIM-France river reaches (the IDs).\u00a0 For each river reach, this file specifies: the ID of the reach, the ID of the unique downstream reach, the number of upstream reaches with a maximum of four reaches, and the IDs of all upstream reaches.\u00a0 A value of zero is used in place of NoData.\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The values were computed based on the SIM-France FICVID file.\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>m3_riv_France_1995_2005_ksat_201101_c_zvol_ext.nc.\u00a0 </em>This netCDF file contains the 3-hourly accumulated inflows of water (in cubic meters) from surface and subsurface runoff into the upstream point of each river reach. The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005/07/31T21:00+02:00.\u00a0 The values were computed using the outputs of SIM-France.\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>kfac_modcou_1km_hour.csv.</em>\u00a0 This CSV file contains a first guess of Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>.\u00a0 The values were computed based on the following information: ID, size of the side of the grid cell, Equation (5) in David et al. (2011), and using a wave celerity of 1 km/h.\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>kfac_modcou_ttra_length.csv.\u00a0 </em>This CSV file contains a second guess of Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>.\u00a0 The values were computed based on the following information: ID, size of the side of the grid cell, travel time, and Equation (9) in David et al. (2011).</li>\n</ul>\n\n<ul>\n\t<li><em>k_modcou_0.csv.</em>\u00a0 This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n</ul>\n\n<ul>\n\t<li><em>k_modcou_1.csv.</em>\u00a0 This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_2.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_3.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_4.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_a.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_b.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>k_modcou_c.csv.\u00a0 </em>This CSV file contains Muskingum k values (in seconds) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_0.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_1.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_2.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_3.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_4.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_a.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_b.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>x_modcou_c.csv.</em>\u00a0 This CSV file contains Muskingum x values (dimensionless) for all river reaches.\u00a0 The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>.\u00a0 The values were computed based on Table (2) in David et al. (2011).\u00a0 This file was prepared using a Fortran program.</li>\n\t<li><em>rivsurf_France.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the SIM-France domain.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_adour.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Adour River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_allier.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Allier River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_ardeche.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Ardeche River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_dordogne.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Dordogne River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_garonne.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_garonne_reste.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne River Basin, downstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_garonneariege.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne and Ariege River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_herault.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Herault River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_loir.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loir River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_loire.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_loire_amont_nevers.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin, upstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_loire_reste.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin, downstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_lot.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Lot River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_meuse.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Meuse River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_oise.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Oise River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_rhone.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_rhone_reste.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin, downstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_rhone_suisse.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin, upstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_saone.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Saone River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_seine.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_seine_amont.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin, upstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_seine_reste.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin, downstream.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_tarn.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Tarn River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>rivsurf_vienne.csv.\u00a0 </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Vienne River Basin.\u00a0 The river reaches are sorted from upstream to downstream.\u00a0 The values were computed using the ID field.\u00a0 This file was prepared using Excel.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_p1_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_p2_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_p3_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_p4_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_pa_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_pb_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_3653days_pc_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_366days_p0_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_366days_pb_dtR1800s.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). \u00a0This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>Qout_France_201101_c_zvol_ext_366days_pb_dtR1800s_pougny.nc.\u00a0 </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach.\u00a0 The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>.\u00a0 The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011).\u00a0 This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li>\n\t<li><em>gage_id_1995_1996_full.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with full daily data record.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>gage_id_1995_1996_full_nash.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with full daily data record and for which RAPID simulations led to a positive efficiency value.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>gage_id_1995_2005_70.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with 70% daily data record.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 2005-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>Qobs_1995_1996_full.csv. \u00a0</em>This CSV file contains daily averaged measured stream flow (in cubic meters per second).\u00a0 The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full.csv</em>.\u00a0 The time range for the daily values is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID, and the observations from SCHAPI.\u00a0\u00a0 This file was prepared using a Fortran program and Excel.</li>\n\t<li><em>Qobs_1995_1996_full_nash.csv.\u00a0 </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second).\u00a0 The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>.\u00a0 The time range for the daily values is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID, and the observations from SCHAPI.\u00a0\u00a0 This file was prepared using a Fortran program and Excel.</li>\n\t<li><em>Qobs_1995_1996_full_nash_93.csv.\u00a0 </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second).\u00a0 The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>.\u00a0 The time range for the daily values is from 1995-11-01T00:00+02:00 to 2005-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID, and the observations from SCHAPI.\u00a0\u00a0 This file was prepared using a Fortran program and Excel.</li>\n\t<li><em>Qobs_1995_2005_70.csv.\u00a0 </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second).\u00a0 The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_2005_70.csv</em>.\u00a0 The time range for the daily values is from 1995-08-01T00:00+02:00 to 2005-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID, and the observations from SCHAPI.\u00a0\u00a0 This file was prepared using a Fortran program and Excel.</li>\n\t<li><em>Qobsbarrec_1995_1996_full_nash.csv.\u00a0 </em>This CSV file contains the reciprocal of the averaged measured stream flow (in cubic meters per second).\u00a0 The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>.\u00a0 The time range for the computation of the average is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID, and the observations from SCHAPI.\u00a0\u00a0 This file was prepared using a Fortran program and Excel.</li>\n\t<li><em>forcingtot_id_1995_1996_full.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the SIM-France domain.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>forcinguse_id_garonne_reste.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Garonne River Basin, downstream.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>forcinguse_id_loire_reste.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Loire River Basin, downstream.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>forcinguse_id_rhone_pougny.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Rhone River Basin, downstream of Lake Geneva.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>forcinguse_id_rhone_reste.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Rhone River Basin, downstream.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>forcinguse_id_seine_reste.csv.\u00a0 </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Seine River Basin, downstream.\u00a0\u00a0 The river reaches are sorted in increasing value of ID.\u00a0 The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00.\u00a0 The values were computed using the following field: ID.\u00a0 This file was prepared using a Fortran program, and Excel.</li>\n\t<li><em>Qfor_1995_1996_full.csv.\u00a0 </em>This CSV file is identical to <em>Qobs_1995_1996_full.csv.</em></li>\n\t<li><em>Qfor_1995_1996_full_93.csv.\u00a0 </em>This CSV file is identical to <em>Qobs_1995_1996_full_nash_93.csv.</em></li>\n\t<li><em>Qinit_93.csv.\u00a0 </em>This CSV file contains the final state of RAPID after a simulation ending on 1995-11-31T00:00+02:00</li>\n</ul>\n\n<p>\u00a0</p>\n\n<p><strong>Known bugs and limitations in this dataset or the associated manuscript.</strong></p>\n\n<p>A small bug in RAPID v1.1.0 was discovered and fixed on 2011-07-16 that had an impact on the optimization of parameters when using forcing data to replace upstream simulations.\u00a0 This bug led to erroneous results for only two of the basins where upstream forcing was used: Garonne River Basin, downstream; and Rhone River Basin, downstream.\u00a0 The bug had no influence on: Loire River Basin, downstream, and Seine River Basin, downstream; or on any of the other simulations.\u00a0 \u00a0This should not affect the conclusions of David et al. (2011) since only a few locations were impacted.\u00a0</p>\n\n<p>\u00a0</p>\n\n<p><strong>Funding</strong></p>\n\n<p>This work was partially supported by the French Mines Paristech, by the French Agence Nationale de la Recherche under the Vuln\u00e9rabilit\u00e9 de la nappe du Rhin (VulNaR) project, by the French Programme Interdisciplinaire de Recherche sur l\u2019Environnement de la Seine (PIREN-Seine) project, by the U.S. National Aeronautics and Space Administration under the Interdisciplinary Science Project NNX07AL79G, by the U.S. National Science Foundation under project EAR-0413265: CUAHSI Hydrologic Information Systems, and by the American Geophysical Union under a Horton (Hydrology) Research Grant.</p>", 
  "author": [
    {
      "family": "David, C\u00e9dric H."
    }, 
    {
      "family": "Habets, Florence"
    }, 
    {
      "family": "Maidment, David R."
    }, 
    {
      "family": "Yang, Zong-Liang"
    }
  ], 
  "id": "30228", 
  "issued": {
    "date-parts": [
      [
        2011, 
        10, 
        30
      ]
    ]
  }, 
  "publisher": "Zenodo", 
  "title": "RAPID input and output files corresponding to \"RAPID Applied to the SIM-France Model\"", 
  "type": "dataset"
}
74
10,652
views
downloads
All versions This version
Views 7474
Downloads 10,65210,652
Data volume 852.0 GB852.0 GB
Unique views 7373
Unique downloads 119119

Share

Cite as