Nunavut Infrastructure Insight
Understand what’s there. Know what to trust. Prepare the next action.
Prepare an Iqaluit community visit
Start with the sample facility and understand what information supports the planned work.
Illustrative workflow, not an actual GN visit. Review the content below, then continue at the bottom of the step. Your selections stay with you.
Geographic context: © OpenStreetMap contributors · ODbL · Snapshot 6 October 2026 · Drag to pan; use + / − to zoom.
Sample visit scenario overlay: numbered markers are fictional locations, not identified government assets. Turning off the overlay leaves only the real geographic context.
What supports this record?
A mapped location is only part of the picture. Review the source, its age, and what still needs verification.
Actionable evidence checklist
Illustrative priorities based on the sample records. Confidence is a review status, not a calculated probability.
Verify the missing connection endpoint
Responsible role: network lead with local technical support.
Required evidence: confirmed endpoint identifier, location and supporting drawing.
Next action: review records; if necessary, arrange a site verification before the documentation update.
Resolve the equipment discrepancy
Responsible role: facilities record owner and IT support.
Required evidence: reconciled inventory and dated inspection note.
Next action: compare the drawing with the observed equipment and record the correction.
Use the register to prepare the inspection
Responsible role: facilities coordinator.
Available evidence: sample location and register; inspection discrepancy remains open.
Next action: confirm access and include the facility inspection in the proposed visit.
Prepare each task in isolation
Teams search separate drawings, inventory lists and work requests. A missing endpoint may emerge only when the cabling task is being prepared. Potential overlap between visits is harder to see.
Prepare the work together
Review sources in context, flag the prerequisite early, and consider compatible tasks in one visit brief. Teams still validate travel, capacity and access before committing.
No measured time or cost savings are claimed.Prepare a coordinated community visit
Select compatible sample tasks. The planner groups work by community and flags prerequisites; it does not estimate real travel savings.
Your visit preparation brief
Preparation aid only. Sample durations and dependencies require operational validation.
Public context, connected information
This prototype includes a snapshot of real OpenStreetMap roads and building footprints for central Iqaluit. It is not connected to GN systems. Fictional operational examples are kept separate from geographic source data.
Potential building, infrastructure, contour, hydrology and parcel layers. These GN datasets are not included in this version; their specific licence terms and suitability require review.
Explore community GIS downloads ↗460 building outlines and 103 road/trail segments in the downloaded extract. Community-maintained mapping may be incomplete or outdated. Coordinates use WGS84 and a local display projection; not a survey or engineering map.
Download geographic extract (GeoJSON) ↓ · Open Database LicencePotential foundational geographic context and additional official datasets.
Natural Resources Canada ↗Public context for the transfer of responsibilities scheduled for April 1, 2027.
Read the GN explanation ↗What a connected version could enable
Find the record behind the map
Link approved asset registers, drawings, inspection records and document repositories through a shared asset identifier.
Know what needs verification
Preserve source dates, ownership and review history so teams can distinguish verified information from assumptions.
Coordinate the next action
Connect approved work orders and project schedules to help teams prepare compatible work in each community.
Extend across services
The pattern could support facilities, housing and other infrastructure portfolios, with department-specific permissions and workflows.
A production version would be designed with GN teams, existing GIS capabilities and community users, including connectivity and language needs.