GIS inspection, import and export
Phasor has two related GIS workflows. GIS inspects and imports existing source data. Network design builds distribution layouts and exports their geometry, quantities and findings.
Keep geographic evidence separate from electrical evidence. A line on a map does not establish its impedance, rating or connection state.
Inspect an existing source
- Open GIS → Inspect source.
- Choose a GeoJSON, GeoPackage, QGS or QGZ file.
- Read the layer inventory: provider, geometry type, coordinate reference system and feature count.
- Read the findings and their remediation. Inspection is read-only and does not add elements to the model.
A QGIS project can reference other files. Keep those sources available and inspect unresolved-layer findings before import.
The separate Topology preview tab in the inspected development build displays a built-in checkpoint fixture. It is not a preview of the file you just selected. For your selected file, use the preview in Import & commit.
Import a reviewed source
- Start with a blank project and open Import & commit.
- Set Source file and Source revision (required). The revision is the issue date or export tag you are attesting to.
- Choose the import mode: geographic-only for geometry and identity, or electrical-reviewed for reviewed electrical parameters as well.
- Load the reviewed Mapping profile file. Check the layer/field interpretation, units, coordinate system and topology tolerances.
- Keep Logical namespace consistent for the same source identity.
- Generate the selected-source preview. Inspect geographic and electrical reconciliation, disconnected components and blockers.
- Approve and commit that exact reviewed preview. If the preview is lost or the source changes, generate and review it again.
Do not select electrical-reviewed mode to bypass missing cable, transformer or source data. Use the preview’s findings to resolve the missing evidence.
Export a designed network
Open a completed Network design. Select Export in its header and choose the format.
| Format | Files and intended use |
|---|---|
| QGIS project | A styled .qgz project, sibling .gpkg data and staking-sheet CSV. Keep the bundle together. |
| GeoPackage | Spatial layers and attribute tables in one .gpkg, with QGIS layer styles. |
| GeoJSON | Layer files, style sidecars and attribute tables for transfer to compatible systems. |
| KML | A styled document with layer folders for Google Earth and compatible viewers. |
Choose the save destination. The saved-export notification links to the written file. A design with no result cannot be exported through this control.
Exports use WGS 84, EPSG:4326, with longitude/latitude geometry. The local design coordinate system is recorded as metadata. Use an appropriate projected coordinate system in your GIS when measuring in metres.
Review the handoff
Check the site boundary, plant source, LV/MV lines, transformers, poles, service drops, served structures and findings. Optional layers appear only when the design contains them. Review the bill of materials and design-summary demand and costing basis.
Exported voltage-drop fields are design estimates; metadata states their authority. Do not label them solved bus voltages unless you are reporting the separate committed load-flow result.
The QGIS bundle references a live OpenStreetMap basemap with attribution. It does not bundle tiles. The GeoPackage alone does not contain that live basemap, and imagery is not exported.
Limits and recovery
An unsupported path, wrong extension or missing result must be corrected before export. A broken QGIS source reference needs its actual file; guessing a replacement can change the design evidence.
Shapefile and CAD/DXF are outside this export workflow. An export is a data handoff, not field verification or construction approval.
These instructions replace the older geographic-view description and follow the September 2026 development build. Use Plant to network for the electrical study boundary.