the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Cartino2D: Scalable and Automated 2D Shallow Water Rainfall-Flood Inundation Modeling up to Very High Resolution for Large Domains
Abstract. While 2D shallow water models with rainfall and infiltration provide a physically consistent framework for flood inundation modeling, their automated application at large scales remains constrained by challenges related to unstructured mesh generation, parameter specifications, and the integration of heterogeneous geospatial and hydrological datasets. This study presents Cartino 2D (C2D), a novel automated framework that enables the large-scale deployment of the well-established Telemac2D model, for solving the complete 2D shallow water equations, with flexible, spatially distributed hydrological forcing—either from rainfall fields or discharge hydrographs. C2D features topography-aware unstructured mesh generation, optional automated handling of hydraulic structures, and spatial parameter estimation from diverse datasets, including land use. It supports multi-resolution simulations up to very high (metric) resolutions and includes optional automated flow analysis at user-defined transects. The framework also features an automatic subdomain sectorization step, based on preliminary simulations on a regular grid, to delineate hydrologically-hydraulically consistent regions and inform targeted unstructured meshing procedures. The framework is successfully applied at the national scale across France, using 100-year return rainfall and discharge values from the SHYREG database, as well as at very high resolution in the complex metropolitan area such as the Aix-Marseille Provence or Grabels City, demonstrating both scalability and robustness. Model outputs are evaluated using flood marks and firefighter intervention records, showing encouraging hydrological and hydraulic consistency. This advancement opens new opportunities for large-scale flood hazard pre-assessment in France and can be transposed to other countries using global and/or national data. Future work will focus on improving culvert representation, testing alternative infiltration models, and extending the framework for model parameter optimization, coastal flooding and real-time applications.
- Preprint
(27778 KB) - Metadata XML
- BibTeX
- EndNote
Status: final response (author comments only)
-
CEC1: 'Comment on egusphere-2025-3333 - No compliance with the policy of the journal', Juan Antonio Añel, 11 Feb 2026
-
CC1: 'Reply on CEC1', Frédéric Pons, 13 Feb 2026
Dear Juan A. Añel,
Thank you for your message and for bringing these important compliance points to our attention. We have carefully reviewed your comments and are committed to addressing them in full to ensure our manuscript aligns with Geoscientific Model Development’s Code and Data Policy. Below, we provide detailed responses and propose specific corrective actions.
A complete version of the Cartino2D source code is already archived in the Zenodo dataset associated with this paper at https://doi.org/10.5281/zenodo.17778609, specifically in the folder "Cartino2D_Github.zip". This reference is cited on line 370 (Pons and Hocini, 2025) and in the “Code and Data Availability” section.
Following your feedback, we propose updating the text in the “Code and Data Availability” section to explicitly mention the inclusion of the source code (which was already available in the Zenodo archive and has been successfully downloaded and used based on recent feedback):
The current text in the Code and Data Availability section reads:
“To facilitate reproducibility, a dataset is provided to run Cartino2D v1.0, available in the GitHub repository above. This dataset includes all input data required to execute Cartino2D (see Section 3), as well as reference outputs for the two cases described in the article (see Figure 3 and Figure 12). These cases cover both a ‘coarse’ 25m resolution and a finer resolution, with an overlap on Grabels areas. The dataset is permanently archived on Zenodo and accessible at https://doi.org/10.5281/zenodo.17778608 (Pons and Hocini, 2025).”
We propose clarifying this to state that the code archive of Cartino2D is available in Zenodo, along with the required data to run it:
“To facilitate reproducibility, the source code and a dataset are provided to run Cartino2D v1.0 in the Zenodo repository (https://doi.org/10.5281/zenodo.17778609). This source code and dataset include all input data required to execute Cartino2D (see Section 3), as well as reference outputs for the two cases described in the article (see Figure 3 and Figure 12). These cases cover both a ‘coarse’ 25m resolution and a finer resolution, with an overlap on Grabels areas. The dataset is permanently archived on Zenodo and accessible at https://doi.org/10.5281/zenodo.17778608 (Pons and Hocini, 2025).”
As already stated in the manuscript:
“The ANTILOPE J+1 product by Météo-France (Champeaux et al., 2009) is a commercial product, and access is restricted to authorized users. An alternative open dataset is available at https://www.data.gouv.fr/datasets/reanalyses-comephore/.”
The link on data.gouv.fr provides equivalent spatial and temporal coverage but does not include the exact commercial data used in our study. For the 6–7 October 2014 event (Grabels case), we have already included one input file for the Telemac2D code in the Zenodo dataset (10.5281/zenodo.17778608). The file name is: Cartino2D_Github/France_Pluie/Grabels/spatial_C0005_861143km_X765440Y6284136_Evts201410061700_08h15min_AMC2_ProjMF_Evt_Anti_15min_J1_MFCerema_2014.txt.
We tested the SHYREG webpage on 13 February 2026 and confirm that it is accessible, though it requires authentication. To ensure full reproducibility, we have already included one input file containing processed statistical SHYREG rainfall data for the Telemac2D code in the Zenodo dataset (10.5281/zenodo.17778608) for the coarse case study: Cartino2D_Github/France_Pluie/EAIM/C6147_733929km_X789149Y6302130/shyreg_spPB_C6147_733929km_X789149Y6302130_T0100_D24_PIC08.txt.
Please let us know if any further clarification or adjustments are needed.
Best regards,
Frédéric Pons and Pierre-André Garambois
Citation: https://doi.org/10.5194/egusphere-2025-3333-CC1 -
CEC2: 'Reply on CC1', Juan Antonio Añel, 13 Feb 2026
Dear authors,
Thanks for the clarifications. The rewording of the Code and Data Availability section that you propose makes it easier to assess the compliance with the the policy of the journal. It is unfortunate that your work depends on proprietary data that are not widely available and properly stored, but we understand it, and we do not consider a violation of the current policy of the journal. That said, we can consider the current version of your manuscript in compliance with the policy of the journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2025-3333-CEC2
-
CEC2: 'Reply on CC1', Juan Antonio Añel, 13 Feb 2026
-
CC1: 'Reply on CEC1', Frédéric Pons, 13 Feb 2026
-
RC1: 'Comment on egusphere-2025-3333', Brett Sanders, 25 Jun 2026
Summary
This article describes a framework to carry out flood hazard mapping at the national scale with a 2D hydrodynamic flood inundation model as the final step of a modeling chain. The framework is presented for France, it includes a 25 m resolution application at the national scale and a more refined model down to 3 m resolution covering a domain 800 km2 in size.
National scale flood hazard modeling at fine resolution is a significant undertaking. Considerable work has to go into planning the representation of hazard drivers (e.g., rainfall, streamflow), accessing the data sources needed to represent rainfall, infiltration and flood infrastructure, and building the modeling stack that pulls all of this information together in a systematic manner. The demands on computing and data management are also substantial. Alas, new efforts to pull together available models and create frameworks capable of flood hazard mapping are a good topic for research and development.
This paper builds out a system that relies on the unstructured grid model Telemac 2D for inundation modeling, which has been available for decades and used extensively for 2D hydraulic modeling. Telemac relies on an unstructured grid of triangular cells, and thus the modeling framework presented her includes a mesh generation element whereby topographic features constrain mesh edge locations and resolution with the aim of optimizing accuracy relative to computational effort.
Critique
This paper is long and reads as though it was somewhat hastily pulled together. The writing is fragmented, lacking flow and cohesiveness of ideas. Sentences are incomplete. Ideas are not fully formed. In terms of purpose, it’s almost as if the authors are caught between an effort to write a user manual and an effort to report on nationwide flood risks.
The work can be viewed as a major accomplishment based upon the scale of hydrodynamic flood modeling, but I don’t see it as an elegant solution. In particular, the nationwide application of the model relies on a structured grid whereby every Cartesian grid cell is divided into two triangles. If the national scale flood model is best achieved with a structured grid, then why not use a Cartesian grid of rectangles? The paper could potentially be far shorter and more concise without all of details on mesh generation. Another factor to consider is that the use of two triangles in place of every square or rectangular cell leads to a doubling of the number of compute cells, and a significantly higher compute cost. Kim et al. (2014) compared various types of unstructured grids including grids with all triangular and all quadrilateral and combinations of the two, and a takeway from that paper is that grids with only triangular cells are not the most efficient and should be avoided. That can be tough pill to swallow because meshing with triangular cells is very easy, and meshing with quadrilaterals is more difficult to automate. In our lab, we’ve gone away from unstructured grids and adopted Cartesian grids for the sake of simplified data management and high-performance computing with GPUs (Sanders and Schubert 2019, Sanders et al. 2025).
The city-scale application in this paper relies on unstructured grids and thus it manifests the modeling framework (data/meshing/modeling) in its totality. But by the time the reader arrives to this section, his or her concentration will likely be exhausted.
So to summarize, I applaud the authors on this accomplishment – it’s no simple task to pull together a large scale, fine-resolution flood inundation modeling framework and apply it both national and city scales. However, I encourage the authors to prepare a manuscript with scope and content that is more appropriate for digestion by scholars in the field: a clear purpose, a straightforward presentation, and a reasonable length.
My sense is that the authors could go two different directions for a more concise contribution: a) focus on the nationwide hydraulic flood inundation model without concern for the meshing, since regular grids are preferred, and feature the comparisons to observec claims and so forth, or b) focus on regional scale modeling (say ~1000 km2) where the unstructured grid is demonstrated and may be advantageous – including test results where these advantages are shown. Indeed, it would be a valuable contribution to compare the unstructured grid with variable resolution against the regular grid approach at the regional scale. And if the advantages are not shown, then that would be a valuable result as well.
Kim, B., Sanders, B. F., Schubert, J. E., & Famiglietti, J. S. (2014). Mesh type tradeoffs in 2D hydrodynamic modeling of flooding with a Godunov-based flow solver. Advances in Water Resources, 68, 42-61.
Sanders, B. F., & Schubert, J. E. (2019). PRIMo: Parallel raster inundation model. Advances in Water Resources, 126, 79-95.
Sanders, B. F., Schubert, J. E., Martin, E. M. H., Wang, S., Sukop, M. C., & Mach, K. J. (2025). A fast flood inundation model with groundwater interactions and hydraulic structures. Advances in water resources, 105057.
Citation: https://doi.org/10.5194/egusphere-2025-3333-RC1 -
AC1: 'Reply on RC1', Frédéric Pons, 03 Jul 2026
Dear Dr. Sanders,
Thank you for your careful reading of the manuscript and for the constructive, detailed feedback. We are grateful that you recognize this work as a major accomplishment in bringing together data and models for flood hazard mapping over large areas, and we welcome the suggestions for improving the clarity and focus of the paper. Below we address each of your comments in turn and describe the changes we propose for the revised manuscript, which we expect to submit within two months.
The proposed revisions summarize as follows:
- Rescope the manuscript to give more weight to the national-scale and local-scale applications presented concisely and with additional quantitative results.
- Move the technical details of automatic mesh generation and model setup to an appendix, keeping the main text focused on the pre-/post-processing framework itself; the core contribution of this work.
- Clarify and strengthen the justification for the meshing choice, and better emphasize the generalizability of the framework to other hydraulic solvers and data assimilation approaches.
Kind regards,
Frederic Pons, Pierre-André Garambois and Nabil Hocini
In details
RC: This paper is long and reads as though it was somewhat hastily pulled together. The writing is fragmented, lacking flow and cohesiveness of ideas. Sentences are incomplete. Ideas are not fully formed. In terms of purpose, it’s almost as if the authors are caught between an effort to write a user manual and an effort to report on nationwide flood risks.
AR: Regarding the length of the paper and its objectives, we initially targeted Geoscientific Model Development (GMD) due to its unique focus on methodological descriptions and new open-source tools. However, we take your point that the current structure affects readability. In the revised manuscript, we will heavily streamline the main narrative by shifting the dense technical meshing algorithms to the appendices. This allows us to keep the main text sharply focused on the core framework, while expanding the national and local sections with the quantitative results you suggested. This restructuring will ensure the paper reads as a cohesive research contribution rather than a hybrid technical manual.
RC: The work can be viewed as a major accomplishment based upon the scale of hydrodynamic flood modeling, but I don’t see it as an elegant solution. In particular, the nationwide application of the model relies on a structured grid whereby every Cartesian grid cell is divided into two triangles. If the national scale flood model is best achieved with a structured grid, then why not use a Cartesian grid of rectangles? The paper could potentially be far shorter and more concise without all of details on mesh generation. Another factor to consider is that the use of two triangles in place of every square or rectangular cell leads to a doubling of the number of compute cells, and a significantly higher compute cost. Kim et al. (2014) compared various types of unstructured grids including grids with all triangular and all quadrilateral and combinations of the two, and a takeway from that paper is that grids with only triangular cells are not the most efficient and should be avoided. That can be tough pill to swallow because meshing with triangular cells is very easy, and meshing with quadrilaterals is more difficult to automate. In our lab, we’ve gone away from unstructured grids and adopted Cartesian grids for the sake of simplified data management and high-performance computing with GPUs (Sanders and Schubert 2019, Sanders et al. 2025).
AR: Thank you for recognizing the national scale of this hydrodynamic flood modeling as a major accomplishment, and for raising these excellent points regarding grid efficiency.
We completely agree with the reviewer's assessment: splitting a Cartesian grid into triangles doubles the element count, increases computational overhead, and is less inherently efficient than a native Cartesian or quadrilateral solver. However, our choice of discretization was strictly dictated by our target hydraulic engine, TELEMAC-2D, whose finite-element formulation is natively hardcoded for unstructured triangular meshes and cannot operate on quadrilateral or Cartesian rectangular grids. To achieve an automated, national-scale application within the TELEMAC ecosystem, splitting the structured Cartesian cells into triangles was the most robust operational path.
We will clarify this solver constraint in the revised manuscript and explicitly emphasize that Cartino2D is designed as a solver-agnostic pre- and post-processing framework, rather than an advocate for a specific mesh type. While this initial implementation targets TELEMAC's triangular structure, the underlying pipeline is highly flexible. As evidence of this flexibility, elements of our pipeline are already utilized by DasFlow2D for inversion of infiltration parameters within a shallow water model at the basin scale (Pujol et al., 2025) and are being adapted for a GPU-based, differentiable physics-AI finite-volume solver operating on diverse mesh types (Colleoni et al., in prep).
Following your excellent suggestions, we will significantly revise the manuscript to:
- Streamline the main text by reducing the dense algorithmic details of the meshing process, moving technical specifics to an appendix.
- Incorporate a dedicated discussion on grid trade-offs, explicitly citing Kim et al. (2014) regarding triangular vs. quadrilateral efficiency, and Sanders & Schubert (2019) / Sanders et al. (2025) regarding the clear data-management and high-performance benefits of modern GPU-accelerated Cartesian grids.
This framing shifts the focus of our paper away from defending triangular meshes, positioning it instead as an adaptable pipeline that bridges data management and large-scale hydraulic modeling across different discretization choices.
RC: The city-scale application in this paper relies on unstructured grids and thus it manifests the modeling framework (data/meshing/modeling) in its totality. But by the time the reader arrives to this section, his or her concentration will likely be exhausted.
AR: We agree that keeping the reader engaged is essential. Because the city-scale application demonstrates the framework in its totality, we want to ensure it stands out. To prevent reader fatigue, we will heavily streamline the preceding sections and move the technical meshing details to an appendix. This will make the manuscript significantly more concise, allowing the reader to reach this final application section much more quickly.
RC: So to summarize, I applaud the authors on this accomplishment – it’s no simple task to pull together a large scale, fine-resolution flood inundation modeling framework and apply it both national and city scales. However, I encourage the authors to prepare a manuscript with scope and content that is more appropriate for digestion by scholars in the field: a clear purpose, a straightforward presentation, and a reasonable length.
AR: Thank you for your encouraging remarks and for recognizing the scale of this accomplishment.
In the revised version, we will heavily streamline the text to achieve a more concise length and a straightforward presentation. Specifically, we will:
- Refocus the narrative on our core contribution: a scale-adaptable framework that bridges national and local applications via hydrological sectorization. This approach enables an iterative workflow where coarser national-scale models logically partition the domain to guide high-resolution, local-scale simulations.
- Remove dense algorithmic descriptions from the main text, moving specific meshing details to an appendix to significantly improve readability and flow.
We believe these adjustments will deliver a much more digestible manuscript that clearly highlights the practical value of our framework for scholars in the field.
RC: My sense is that the authors could go two different directions for a more concise contribution: a) focus on the nationwide hydraulic flood inundation model without concern for the meshing, since regular grids are preferred, and feature the comparisons to observec claims and so forth, or b) focus on regional scale modeling (say ~1000 km2) where the unstructured grid is demonstrated and may be advantageous – including test results where these advantages are shown. Indeed, it would be a valuable contribution to compare the unstructured grid with variable resolution against the regular grid approach at the regional scale. And if the advantages are not shown, then that would be a valuable result as well.
AR: We thank the reviewer for proposing these two clear directions for a more concise manuscript.
Regarding the paper's scope, our goal is to present the Cartino2D framework itself rather than just a single model application. Retaining both the national and local applications is essential to demonstrate the scalable nature of the tool, which aligns directly with the scope of Geoscientific Model Development (GMD). To ensure a more concise contribution as requested, we will shift the dense algorithmic meshing details to an appendix, allowing the main text to focus strictly on this multi-scale versatility. We plan to publish deep-dive, separate papers on the individual hydraulic findings at each scale in future journal articles.
Regarding your specific suggestions for Directions A and B:
- On Direction A (National-Scale Validation): We agree that more comprehensive comparison adds value. While insurance claim data is strictly confidential and unavailable in France, we will strengthen the national-scale section by incorporating a comparison of simulated discharges across approximately 5,000 control sections (leveraging measurement gauges and 100-year return period flows from national hydrological models), alongside our existing spatial comparisons with historic flood markers.
- On Direction B (Unstructured vs. Structured Grid Discrepancies): The reviewer makes an excellent point regarding grid comparisons. While structured grids at 25m or 5m resolution adequately preserve macro-scale flood patterns for extreme events, they deviate significantly from unstructured meshes in complex environments. Unstructured grids allow us to explicitly account for micro-topography, urban layouts, and small hydraulic structures.
- On the Challenge of Local Data: We will add a discussion acknowledging that the bottleneck for high-resolution, unstructured local modeling is often data availability. For example, at a departmental regional scale of approximately 5,000 km2, the dimensions of roughly 5,000 hydraulic structures remain unknown in public databases. Conversely, where highly detailed datasets are available, such as in our work within the Montpellier urban area, where over 200 buried structures greater than 800mm and low-lying road crossings were explicitly integrated, the advantages of an unstructured mesh become indispensable.
By restructuring the paper to highlight this continuum, using national-scale structured setups to identify regions and local unstructured meshes to capture complex structural hydraulics, we believe the manuscript will offer a straightforward, balanced contribution that addresses both of the reviewer's core insights.
Citation: https://doi.org/10.5194/egusphere-2025-3333-AC1
-
AC1: 'Reply on RC1', Frédéric Pons, 03 Jul 2026
-
RC2: 'Comment on egusphere-2025-3333', Anonymous Referee #2, 31 Oct 2026
The paper describes a software package for automated flood-inundation modelling. The backbone model for solving the shallow-water equations is the well-known Telemac-2D model and the described software package (Cartino-2D) provides utilities for processing input data and model building.
Generally, I really appreciate the efforts the authors made to establish a software package that eases the way to build complex, high-resolution flood-inundation models which often is a cumbersome and labour-intensive process. The software package seems to provide a lot of features and is able to handle various input datasets with a dedicated focus on French national databases.
However, one of my major concerns with the paper is that details on the technical architecture of the software package are completely missing. Cartino-2D (C2D) heavily relies on a variety of well-established software packages (e.g. GRASS-GIS, Gmesh, R, just to name a few) and also some other less-known components but it is never clear which software component is doing what and was is the exact role of C2D. In fact, it is not even quite clear what C2D actually is (on a technical basis). Is it "just" a collection of scripts (in which language(s)?), or is it one master script that performs all the described processing steps, or does it have a GUI? This is all pretty unclear but this information should be definitely well-adressed in a GMD paper. I pointed out some examples in my main comments below. In my opinion, the authors should definitely adress this missing information either in a separate chapter on the technical architecture of C2D and/or by revising the paragraphs on the feature descriptions (chapter 3). In general, these descriptions are always a mixture of features, examples, specific settings/recommendations and the mentioning of different third-party software components which makes it quite difficult to get the overall picture. As a potential user, I would probably be interested in using the different features that C2D provides, but I would probably be reluctant to actually try to download/ install and use it, because I don't know what is is, how it is used, how much effort it takes for installation (because of the various third-party software) and what is actually "new" compared to build-in terrain-correction or meshing functions, e.g. in GRASS-GIS or Gmesh. The latter point should also be emphazid more, e.g. by pointing out which functionality is a call to already established functions in GRASS-GIS, Gmesh, etc. and what is done by C2D itself.
In addition, Chapter 4 provides three illustrative test cases where C2D was obviously used for model development. In each test case, some general information is provided on the motivation, input data generation, modelling challenges and some selected results. However, what I miss here is a clear structure, key messages and most importantly a clear relation to the contribution of C2D. In the end, much of the provided information (e.g. motivation, model performance) can also solely be related to Telemac-2D test cases, but the important point for this paper is how C2D helped to solve these test cases. So in my opinion, this chapter should be much more streamlined towards the contributions of C2D.
Main comments:
Line 80-82: It is stated that C2D builds upon several open-source packages, e.g. GDAL, R etc., but it never becomes obvious throuhout the paper how they interact, how they are connected and which package is doing what. In addition, three software packages with graphical-user interfaces are mentioned (RStudio, QGIS, GRASS-GIS). So that means that (potential) users need to switch between different user-interfaces, performing different steps in there throughout the whole model development phase? I would not call this a unified workflow for model development. The paper title also states that it is an automated workflow. So is there a master script (written in what language?) that calls the different packages? This could make sense for GRASS-GIS and maybe QGIS, but not for RStudio which is "just" (but yet a powerful) IDE for R.C2D-Rain vs. C2D-Discharge: Are these two completely separate programs with corresponding substeps/ subscripts in the workflow?
Line 158: Is the FILINO model a part of C2D and can be called from there?Line 173-199: Here different steps for processing the topography/ meshes are described but it remains unclear which software components are responsible for the different steps e.g. build-in functions of Gmesh?
Line 205: "...using a home made mesher...". What is this "home made" mesher exactly doing? Is it a separate option in C2D?
Sections 3.1.1/3.1.2: Are the mentioned buffers/ mesh sizes always prescribed or is the user allowed to choose different values for his/her specific modelling case?
Line 248: So that means that C2D only works with this development branch version of Telemac-2D?
Line 250-259: It is mentioned that C2D works with a variety of precipitation input data, but only two French precipitation products are exemplified. What would a user need to do, to utilize other precipitation products, e.g. from other meteorological/ hydrological services? Is there a specific format required to allow processing with C2D? Or would the user even need to modify the source code of C2D?
Line 310-320: Can C2D handle all these data products out-of-the-box? If not, what are the required input files, e.g. ESRI-shapefiles? How are model parameters mapped to the land-use classes, e.g. by providing a lookup-table to C2D?
Section 3.5: So these hydraulic structures need to be defined in an (external) GIS software, and can then be handed over to C2D? What is C2D then actually doing with it? Does it prepare additional input files for Telemac-2D?
Section 3.7: Is this a general recommendation for modelling or an active feature of C2D? Are the values for coarse and fine resolution (25 and 5m) preset or just examples? As this section states it is about "automated domain sectioning": Is the result of this "option" an optimized domain sectioning?
C2D has dependencies on various third-party software. Please provide a table that lists all these dependencies (including plugins, packages therein) and also make statements on the version numbers (version combinations) that are needed for working with C2D.
One feature of C2D that is highlighted in the abstract and the title is the automatization of workflows. However, when reading through the paper, many steps of model building still seem to be a manual step-by-step procedure, e.g. preparing GIS databases, then doing some processing steps, etc. So I think a discussion on the limitations on automatization with respect to model building with C2D should be added at some point in the paper.
Does C2D also provide functionality for running Telemac-2D and for post-processing the model output data?
Minor comments:
Line 101: "...as illustrated in figure,..." Which figure? Number is missing
Line 287,325,etc.: "Optinnal" -> "optional"
Line 329: "...a GIS database is needed...". How should a potential user know what to do/ how to use it? How should this database look like?Citation: https://doi.org/10.5194/egusphere-2025-3333-RC2 -
AC2: 'Reply on RC2', Frédéric Pons, 08 Nov 2026
Dear Reviewer
We sincerely thank the reviewer for the careful reading of our manuscript and for the constructive comments. We particularly appreciate the positive assessment of the efforts made to develop Cartino2D and its potential to facilitate the development of complex, high-resolution flood-inundation models.
We agree that the technical architecture of Cartino2D, the respective roles of the different software components, and the specific contributions of Cartino2D itself were not sufficiently described in the initial manuscript. We also acknowledge that the presentation of the test cases could better highlight the added value of Cartino2D, rather than focusing primarily on the hydraulic modelling results.
Cartino2D is a dedicated, modular pre-processing software framework for the end-to-end preparation of high-resolution 2D hydraulic models. Rather than being a mere collection of scripts or a wrapper around existing software, it orchestrates established third-party tools (e.g., GRASS-GIS, Gmsh, Telemac) through integrated processing workflows, while providing its own functionalities for geospatial data handling, terrain and bathymetry preparation, computational domain construction, mesh generation and hydraulic model parameterization, Telemac computation and post-processing.
In the revised manuscript, we will therefore:
- Add a dedicated annex describing the technical architecture of Cartino2D, its main components, their interactions, and the overall workflow.
- Clarify the respective roles of Cartino2D and the third-party software packages it uses, distinguishing between external software functionalities and processes specifically developed within Cartino2D.
- Provide more practical information on configuration files, input data requirements, and user interface.
- Clarify the degree of automation achieved by Cartino2D and identify the steps that still require user intervention.
- Improve the case studies to better demonstrate how Cartino2D facilitates model development, particularly in terms of scalability, reproducibility, and processing time.
We address the individual comments below.
In detail
RC: General comments
RC: One of my major concerns with the paper is that details on the technical architecture of the software package are completely missing. Cartino2D heavily relies on a variety of well-established software packages (e.g. GRASS-GIS, GMSH, R), but it is never clear which software component is doing what and what is the exact role of C2D. Is it just a collection of scripts, one master script that performs all the processing steps, or does it have a GUI?
AR: Cartino2D is organised around a main script named C2D_RUN, which acts as the central entry point to the software. This script is developed in R and provides a menu-based interface through which users can access and run the different processing steps. It orchestrates the various scripts and external software packages involved in the workflow. The script is run from RStudio. RStudio is therefore not a specific graphical interface developed by Cartino2D.
QGIS is used as a GIS visualisation environment. Dedicated QGIS project files (.qgz) and associated symbology files (.qml) are provided to visualise the different processing stages and the corresponding spatial datasets. QGIS is therefore primarily used to inspect and validate the spatial data generated throughout the workflow, rather than to control the overall execution of Cartino2D.
The interaction with Cartino2D itself is mainly provided through the menus implemented in C2D_RUN.
Step0 initialises the work with a polygon layer defining the working areas, referred to as sectors.
The PreC2D menu allows users to prepare databases and files in the formats required by Cartino2D, to download databases, define CN or Manning-Strickler parameters, and create Rainfall or discharge inputs, manage the way between 25m simulations and 5 m simulations… These operations are guided by Cartino2D but are not fully automated.
The main Cartino2D workflow consists of Steps 1 to 9.
Steps 1 to 4 correspond to the pre-processing stage, Step 5 is the launch of Telemac with Local computation or remote computation on a cloud or high-performance computing cluster. Steps 6 to 8 correspond to post-processing for each sector and each scenario and Step 9 merges the results from all sectors into a single raster dataset for each output variable (water depth, velocity, etc.).
Steps 1 to 9 can be run together as an automated workflow. In operational mode, we prefer to have a view after step 4, step 5 and step 8.
We will better describe this processing sequence in the revised manuscript.
R is the main orchestration language and controls the execution of the other software packages, notably through calls to the R system() function. The main external components and their respective roles are as described in supplement pdf file “TableDEPENDENCIES.pdf” done by AI. These dependencies will be better described in the revised manuscript,
Importantly, Cartino2D is not simply a collection of calls to external software. A substantial part of the processing is implemented directly in R using dedicated packages and functions. These include, among others, doParallel, dplyr, foreach, ggplot2, htmlwidgets, mapview, plotly, raster, RCurl, readxl, rvest, sf, sfheaders, ssh, tidyverse, utils, and tools. Cartino2D is designed to work with recent versions of its software dependencies, although compatibility with QGIS is currently limited to versions earlier than 4. We will explicitly mention these functionalities in the revised manuscript.
The added value of Cartino2D therefore lies in the integration and orchestration of these different tools within a consistent workflow, together with the specific data-processing procedures, model-configuration routines, and automation functionalities developed for flood-inundation modelling.
RC: Main comments:
RC: Line 80-82: It is stated that C2D builds upon several open-source packages, e.g. GDAL, R etc., but it never becomes obvious throuhout the paper how they interact, how they are connected and which package is doing what. In addition, three software packages with graphical-user interfaces are mentioned (RStudio, QGIS, GRASS-GIS). So that means that (potential) users need to switch between different user-interfaces, performing different steps in there throughout the whole model development phase? I would not call this a unified workflow for model development. The paper title also states that it is an automated workflow. So is there a master script (written in what language?) that calls the different packages? This could make sense for GRASS-GIS and maybe QGIS, but not for RStudio which is "just" (but yet a powerful) IDE for R.
Please refer to our detailed response to the general comment on the technical architecture of Cartino2D above.
RC: C2D-Rain vs. C2D-Discharge: Are these two completely separate programs with corresponding substeps/ subscripts in the workflow?
AR: No. C2D-Rain and C2D-Discharge are not separate software packages. Both functionalities are directly available within the same Cartino2D workflow and are selected through the configuration parameters.
RC: Line 158: Is the FILINO model a part of C2D and can be called from there?
AR: FILINO and Cartino2D are two independent software tools with some shared functionalities and complementary applications.
FILINO is specifically dedicated to topographic data processing, whereas Cartino2D focuses on the preparation, configuration, and implementation of hydraulic models. FILINO is therefore not a component of Cartino2D, nor is it an integrated module that is systematically called by Cartino2D.
RC: Line 173-199: Here different steps for processing the topography/ meshes are described but it remains unclear which software components are responsible for the different steps e.g. build-in functions of Gmesh?
AR: This processing is performed during Step 1, before mesh generation, it is the preparation of the topography for the management of boundary conditions.
RC: Line 205: "...using a home made mesher...". What is this "home made" mesher exactly doing? Is it a separate option in C2D?
AR: Cartino2D offers two mesh-generation approaches, which can be selected by the user depending on the modelling requirements:
- For unstructured meshes, Cartino2D uses GMSH.
- For regular meshes, Cartino2D uses an in-house meshing procedure specifically developed for the software.
The latter is what is referred to as the "home-made mesher" in the manuscript. It is not an external software package but a meshing procedure developed and implemented by the Cartino2D team.
RC: Sections 3.1.1/3.1.2: Are the mentioned buffers/ mesh sizes always prescribed or is the user allowed to choose different values for his/her specific modelling case?
AR: The buffer distances and mesh sizes are user-defined parameters and can be adapted to the specific requirements of each modelling case.
However, their selection must remain consistent with the physical characteristics of the study area and the intended modelling objectives.
RC: Line 248: So that means that C2D only works with this development branch version of Telemac-2D?
AR: No. Cartino2D is not restricted to a specific development branch of TELEMAC-2D.
It can be used with different TELEMAC-2D versions. Specific modifications to some TELEMAC-2D source files (.f files) are required for our applications. These modifications are integrated through the USER_FORTRAN directory, which allows users to incorporate the required developments without modifying the main TELEMAC-2D source code.
RC: Line 250-259: It is mentioned that C2D works with a variety of precipitation input data, but only two French precipitation products are exemplified. What would a user need to do, to utilize other precipitation products, e.g. from other meteorological/ hydrological services? Is there a specific format required to allow processing with C2D? Or would the user even need to modify the source code of C2D?
AR: Cartino2D can handle a wide variety of precipitation datasets, particularly spatially distributed raster rainfall products.
The integration of a raster precipitation product is mainly based on a dedicated Excel configuration file, which provides the information required to interpret and process the data. This includes, for example, the coordinate reference system (EPSG code), temporal resolution, rainfall units, and the rules used to identify or extract the corresponding dates from the input data.
Using this approach, we currently support more than 20 different types of raster precipitation products, including datasets provided by Météo-France and local authorities.
However, we cannot guarantee that all possible precipitation formats can be integrated directly without adaptation.
RC: Line 310-320: Can C2D handle all these data products out-of-the-box? If not, what are the required input files, e.g. ESRI-shapefiles? How are model parameters mapped to the land-use classes, e.g. by providing a lookup-table to C2D?
AR: Cartino2D can use all these data products out-of-the box.
Input data must be provided in a compatible vector GIS format and use the same coordinate reference system (CRS). A predefined (apriori) correspondence table is used to assign model parameters to the different input classes.
For the estimation of Curve Number and Manning–Strickler coefficients, Cartino2D relies on an Excel configuration file in which the user specifies the parameter values associated with each input data class, as already described in Section 3.3 (line 295 in the original manuscript).
For example, when vector datasets describing buildings, roads, or other land-use features are available, specific CN values can be assigned to these classes. A CN value of 98 can, for instance, be assigned to building polygons.
This approach provides flexibility in the integration of different spatial datasets and allows users to adapt parameter assignments to their own data sources and modelling requirements.
RC: Section 3.5: So these hydraulic structures need to be defined in an (external) GIS software, and can then be handed over to C2D? What is C2D then actually doing with it? Does it prepare additional input files for Telemac-2D?
AR: Yes. Hydraulic structures are initially defined in a GIS environment, typically using QGIS, and stored in a spatial database.
Cartino2D then identifies and selects the hydraulic structures located within each modelling sector. Based on these data, it automatically generates the corresponding CULVERTS DATA FILE required by TELEMAC-2D.
For each hydraulic structure, the inlet and outlet are defined as mesh nodes. To improve the numerical stability of the hydraulic calculations, the local topography around these nodes is temporarily lowered during the simulation setup.
RC: Section 3.7: Is this a general recommendation for modelling or an active feature of C2D? Are the values for coarse and fine resolution (25 and 5m) preset or just examples? As this section states it is about "automated domain sectioning": Is the result of this "option" an optimized domain sectioning?
AR: Cartino2D supports simulations at different spatial resolutions, including regular meshes with 25 m or 5 m resolution and unstructured meshes with variable resolution, typically ranging from approximately 3 to 25 m in our applications.
These values correspond to configurations commonly used in our operational applications. They are not mandatory or fixed settings, and other resolutions can be selected depending on the characteristics of the study area and the modelling objectives.
The purpose of the automated domain-sectioning procedure is to facilitate the preparation of consistent modelling sectors, which is itself a particularly time-consuming and labour-intensive task.
The procedure relies on a multi-resolution approach:
- A first simulation is performed using a regular mesh with a resolution of 25 m.
- The resulting hydraulic information is combined with hydrological catchment delineation to identify relevant flow pathways and define coherent sectors for subsequent simulations at 5 m resolution (potential significant human intervention).
- The resulting 5 m simulations are used to assess the consistency of the sectorisation and to identify the flood-prone areas that can subsequently support the generation of variable-resolution unstructured meshes (minimal human intervention).
The transition from 25 m to 5 m resolution therefore involves several processing steps that help reduce the time required to define the modelling domains and prepare the subsequent high-resolution models.
Importantly, although the procedure automates a substantial part of the sector preparation, human intervention is still required. In particular, the resulting sector boundaries must be inspected in a GIS environment and may need to be adjusted to ensure that they are hydraulically consistent.
The resulting sectorisation should therefore be considered an automated proposal that supports the modelling process, rather than a fully automatic and systematically optimal domain partitioning.
Regarding the choice of resolutions, the 25 m, 5 m and approximately 3–25 m unstructured mesh configurations are those most frequently used in our applications. Experiments with an initial resolution of 100 m have not provided satisfactory results for this purpose. However, resolutions close to those presented in the manuscript may also be appropriate, depending on the study area.
RC: C2D has dependencies on various third-party software. Please provide a table that lists all these dependencies (including plugins, packages therein) and also make statements on the version numbers (version combinations) that are needed for working with C2D.
AR: Please refer to our response to the general comment on the technical architecture of Cartino2D and the supplement pdf file “TableDEPENDENCIES.pdf” done by AI. These dependencies will be better described in the revised manuscript,
RC: One feature of C2D that is highlighted in the abstract and the title is the automatization of workflows. However, when reading through the paper, many steps of model building still seem to be a manual step-by-step procedure, e.g. preparing GIS databases, then doing some processing steps, etc. So I think a discussion on the limitations on automatization with respect to model building with C2D should be added at some point in the paper.
AR: We agree that the distinction between automated and user-dependent operations should be made clearer.
When all the required input databases are available in the appropriate formats and the modelling sectors have already been defined, Cartino2D can automatically perform most of the subsequent model-development stages (C2D Steps 1 to 9). These include:
These operations can be performed through the C2D_RUN interface, with limited user intervention once the configuration files have been prepared.
However, some operations remain dependent on user input and expert assessment:
- Initial input database preparation (C2D_PreC2D): the required spatial and hydrological datasets must be available and properly formatted. Cartino2D nevertheless includes dedicated routines in the Pre_C2D module to assist users in preparing these databases.
- Validation of the modelling sectors: the initial sector delineation must be checked to ensure that it is hydraulically consistent and suitable for the intended modelling objectives.
- Transition between spatial resolutions (C2D_PreC2D): moving from a 25 m regular mesh to a 5 m mesh, or subsequently to an unstructured mesh, involves intermediate processing and validation steps. In particular, the resulting sector boundaries may require manual adjustments in a GIS environment.
We therefore consider Cartino2D to provide a high degree of automation for the technical implementation and execution of hydraulic models, while retaining human intervention for data preparation, quality control, and certain modelling decisions.
RC: Does C2D also provide functionality for running Telemac-2D and for post-processing the model output data?
AR: TELEMAC-2D simulations can be launched directly from the C2D_RUN interface using two main approaches:
- Local computation on the user's workstation;
- Remote computation on a cloud or high-performance computing cluster.
The second option requires some adaptation to the specific configuration of the target computing environment, as cluster architectures and execution procedures differ between infrastructures.
Cartino2D also includes several post-processing routines through C2D_RUN Steps 6 to 9.
RC: Minor comments:
RC: Line 101: "...as illustrated in figure,..." Which figure? Number is missing
AR: The missing reference is Figure 1
RC: Line 287,325,etc.: "Optinnal" -> "optional"
AR: Ok
RC: AR: Line 329: "...a GIS database is needed...". How should a potential user know what to do/ how to use it? How should this database look like?
AR: To facilitate the use of Cartino2D, a Zenodo repository (https://doi.org/10.5281/zenodo.17778609) has been created to provide interested users with example datasets and the input files required to run the software.
This repository includes the databases necessary to become familiar with Cartino2D and to reproduce the example applications presented in the manuscript. It therefore provides users with a practical starting point for understanding the expected input data structure and the different stages of the workflow.
In our current experience, initial use of Cartino2D is generally facilitated through dedicated training sessions. Feedback from participants has indicated that face-to-face training is particularly helpful for understanding the overall workflow and becoming familiar with the different configuration steps.
However, we have also received feedback from users already familiar with R and RStudio who were able to install and use Cartino2D independently, without particular difficulties.
-
AC2: 'Reply on RC2', Frédéric Pons, 08 Nov 2026
Data sets
Dataset for Cartino2D paper Frédéric Pons and Nabil Hocini https://doi.org/10.5281/zenodo.17778609
Model code and software
Cartino2D Frédéric Pons and Nabil Hocini https://github.com/CEREMA/cartino2d
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 1,640 | 2,266 | 161 | 4,067 | 160 | 205 |
- HTML: 1,640
- PDF: 2,266
- XML: 161
- Total: 4,067
- BibTeX: 160
- EndNote: 205
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
Dear authors,
Unfortunately, after checking your manuscript, it has come to our attention that it does not comply with our "Code and Data Policy".
https://www.geoscientific-model-development.net/policies/code_and_data_policy.html
First, you have archived almost all of the assets necessary to replicate your work in sites that are not acceptable according to the policy of the journal. They include GitHub and GitLab sites, and several others such as data.gouv.fr and inrae.fr. In some cases, such as for the ANTILOPE J+1 product you state that access is restricted, and when checking it, the information in the web page linked states that the data are open. The https://shyreg.pluie.recover.inrae.fr/ web page does not even work.
Therefore, the current situation with your manuscript is highly irregular. It should have never been accepted for peer-review or Discussions in the journal given these issues. The GMD review and publication process depends on reviewers and community commentators being able to access, during the discussion phase, the code and data on which a manuscript depends, and on ensuring the provenance of replicability of the published papers for years after their publication. Please, therefore, publish all the code and data necessary to replicate your work in one of the appropriate repositories and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI)) as soon as possible. We cannot have manuscripts under discussion that do not comply with our policy.
The 'Code and Data Availability’ section must also be modified to cite the new repository locations, and corresponding references added to the bibliography.
I must note that if you do not fix this problem, we cannot continue with the peer-review process or accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive Editor