Exporting results

The results page has an export bar with buttons for each format. Every export reflects the current state of the run, including any per-well edits you have made in the details table.

Exported files are written to the outputs\ folder inside the install directory and are also offered as a browser download.

CSV

Each table on the results page has its own Export CSV button. The CSV reflects the table’s current sort and filter state.

The per-well CSV reflects any per-well edits you have made — the exported values are the post-override numbers (NPL, finished depth, stickup, top of fracture / aquifer / screen) and any recomputed SAD, impact, and status that follow from them. A rightmost Edited column lists, for each row, the field names you adjusted (for example NPL, Stickup), so a reviewer can see at a glance which inputs are yours rather than BCGW’s. Rows with no edits leave this column blank.

The per-well CSV also carries a derived Outside Validity Yes/No column, so the Cooper-Jacob validity advisory (shown on screen as a purple row tint) survives the export.

KML

A KML file for Google Earth. It contains one placemark for the pumping well plus one for each observation well, colour-coded by status and sized by predicted impact. The full per-well result row travels with each placemark as attached data.

PDF

A landscape PDF report, one section per page: input parameters and a summary-card row; the method and assumptions; the results map; the distance-drawdown and impact charts; the at-risk summary table; and the full per-well details table. Every page carries a screening-tool banner, and the footer records the run timestamp, run ID, tool version, and signed-in user.

The results map page shows the whole search buffer around the pumping well, with every well coloured by status and sized by predicted impact, a dark ring on each licensed well, well tag numbers, a scale bar and a north arrow. It always shows the full buffer, however you last panned or zoomed the map on screen. The background follows the basemap you picked on the results map; OpenStreetMap, the default, prints as Esri Streets, which looks much the same. The background is downloaded when the PDF is made. If that fails, the map is drawn on a plain background and the page says so.

Interactive HTML map

A single self-contained HTML file with an interactive map — the pumping well, the search buffer, and every observation well with clickable popups. It opens in any browser with no software to install and stays interactive (pan, zoom, switch basemap).

The basemaps in the file are Esri Streets (shown first), Topographic and Satellite. OpenStreetMap is not offered: its servers refuse map tiles to a page opened from a file on your computer. The file needs an internet connection to draw its basemap.