Opening an existing project

1. Click Open and select an .inp file.
2. The network loads onto the map.
3. Some features from older EPANET models may not be fully supported, and warnings will indicate any missing elements.

You can import your existing EPANET models into epanet-js using the standard INP file format. This lets you view, edit, and run simulations right in your browser - no extra software needed. Just keep in mind that not all EPANET features are supported yet. We’re actively improving the importer and aiming for full compatibility over time.

Key requirements & limitations

1. Steady-state simulations only:

   Currently, epanet-js primarily supports steady-state hydraulic simulations. This means that while many elements of your INP file will be imported, features related to Extended Period Simulation (EPS) or water quality modeling are generally not supported for simulation purposes.

   • Time patterns for demands or reservoir heads will use their first value for the steady-state calculation.
   • Complex tank dynamics, operational controls, rules, and water quality parameters (sources, reactions, etc.) are not processed or simulated.
   • If your INP file contains settings like a DURATION greater than zero, epanet-js will flag this as an EPS model, but will still attempt to run a steady-state simulation based on the initial conditions.

2. Nodes must have coordinates:

   All nodes (junctions, reservoirs, tanks) defined in your INP file must have corresponding entries in the [COORDINATES] section to be properly imported and visualized. If coordinates are missing for some nodes, you will receive a warning, and those nodes will not be included in the imported model.

3. WGS84 projection (latitude/longitude) required:

   For epanet-js to correctly display your network on the map, all geographic coordinates in your INP file (for junctions, reservoirs, tanks, and pipe vertices) must be in the WGS84 (EPSG:4326) geographic coordinate system (latitude and longitude).

   • If your INP file uses a different projection system (e.g., a local state plane or UTM coordinates), you will encounter an error message during import:

     "Your INP includes coordinates or vertices that use a projection system that is not supported yet. Please ensure all assets are geocoded using the WGS84 standard."

<aside> <img src="/icons/globe_blue.svg" alt="/icons/globe_blue.svg" width="40px" />

EPANET Projection Converter Utility

You can convert your INP file to the WGS84 system using our EPANET Projection Converter utility: https://utils.epanetjs.com/projection-converter

</aside>

Import issues & warnings

When you import an INP file, epanet-js checks its contents. If it finds sections that aren't supported, options that differ from the default settings, or features related to EPS or water quality, it will list them as issues.

• These issues appear in a dialog after the import finishes.
• They're there to help you understand which parts of your model might not be fully supported or used in epanet-js.
• It's a good idea to review them so you’re aware of any differences between your original EPANET model and what’s shown in epanet-js.

When you save the model, epanet-js will ask you to save a copy so your original file stays unchanged.

Tips for a successful import

1. Use WGS84 coordinates: Make sure your model uses WGS84 (latitude/longitude) for all node and pipe coordinates. You can convert them using the EPANET Projection Converter.
2. Check for missing coordinates: Each node (junction, tank, reservoir) needs coordinate data to be imported and shown on the map. Double-check that this info is included.
3. Look over any issues: After import, epanet-js will list any issues or warnings. Reviewing them helps you understand what parts of the model might not carry over fully.
4. Simplify for steady-state: epanet-js currently only supports steady-state simulations. We’ll try to simulate the network using the initial conditions in your INP file, but you might want to adjust the model to reflect a specific point in time, like peak hour.

We're always working to improve INP file support and add more features. You can follow progress in our changelog.

INP section support details

Here's a breakdown of how epanet-js currently handles different sections commonly found in an EPANET INP file: