≋
SEARCHMONT RESPONSE AREA WATER SOURCE EVALUATION ATLAS
SCVFD Research
Study boundaries

Loading ORN…

Loading building footprints…

The Searchmont Resort hydrant stays visible.

Uploaded outlines only. The KML uploads contain outlines only. Microsoft footprints are a separate layer; ORN roads and Microsoft footprints are separate layers. Township boundaries are not yet imported.

Searchmont areaExploration workspace
MAP KEY Existing source Drafting location Manual access route ORN road segment Within travel budget Proposed storage Home cluster Detected building
INVENTORY RECORD

Water location

FOUR-TOWNSHIP STORAGE STUDY

Planning record

SOURCE SEGMENT & LOCAL ASSUMPTIONS

Imported road

Source attributes remain unchanged. This local assumption does not verify tanker suitability or current conditions.

ABOUT THIS WORKSPACE

Local knowledge, made visible.

This prototype contains a real Esri topographic background and 21 locations imported from Searchmont FD - Water Sources.kmz: 20 water locations and the fire hall. The resort hydrant is the one existing source identified by the user. Other water locations are recorded as drafting locations; their notes and verification needs are preserved. Fictional sample roads can be shown separately.

Drafting can tie up people and equipment. Each water record therefore keeps people, equipment, setup time, preference and access notes separate. Unknown values stay unknown.

Coverage uses manual road records and, when enabled, imported ORN segments. Imported roads join only at matching original vertices (coordinates rounded to six decimal places); geometric crossings alone are not connected. Source direction fields are respected where recognised. Manual drawing can snap nearby endpoints. It does not route over background map roads. When enabled, the ORN scenario uses imported line geometry with explicit user assumptions. It is not a certified routing network: connectivity, turn restrictions, grade separation, blocked passages, structures, load limits and real-time access have not been validated. Water setup time is stored separately and is not included in the road coverage calculation.

The uploads Buildings in Searchmont.kml and Roads in Searchmont.kml each contain one polygon: Response Area and Searchmont and Area respectively. They are displayed as user-supplied study outlines, not verified response jurisdictions or township boundaries. Neither upload contains individual buildings or road centre lines; building geometry has since been added separately from Microsoft Canadian Building Footprints. The road summary is retained as unverified reference information and is excluded from travel calculations. Separate ORN Composite segment geometry has now been imported from the linked service for a buffered rectangular window around the Response Area. Full intersecting segments are retained. ORN source attributes are kept separate from local planning overrides. The imported snapshot is not a live road-condition service. Contains information licensed under the Open Government Licence – Ontario. No terrain raster has been imported, so road gradients have not been calculated.

The Evaluate tab computes routes from every building centre toward the resort hydrant using projected points on the nearest included road segment. Point-to-road gaps are reported separately and excluded from road distance and time. Results therefore describe road legs rather than complete driveway-to-hydrant journeys. Cluster radius is straight-line distance around a building-centred circle. The evaluator greedily selects the densest remaining circle and assigns each building at most once; it is not a globally optimal grouping. All structures are considered, regardless of verified residential use. The evaluator uses its own visible speed assumptions and the local road exclusions, independently of the Coverage toggle.

Edits remain in this browser, not a shared database. Export GeoJSON to keep a portable copy. Water, facility, home-cluster and proposed-storage records are exported separately. Proposed storage is never counted as available water. Cluster screening compares user-entered home counts and straight-line distance to the existing hydrant. It does not infer homes from imagery or identify engineering-ready sites. Microsoft building footprints are displayed separately as unclassified structures. The extracted subset retains complete footprints whose centres fall inside the Response Area outline. Nearby structure counts use footprint centres and an explicit circular radius, not road distances or household counts. Microsoft reports varying imagery dates and imperfect detection; local completeness has not been validated. The original repository is archived. Building data is available as a separate GeoJSON download with Microsoft attribution and an ODbL notice. Township names are user-assigned; township boundaries have not been imported.

Your NRCan / GEOSCAN reference ↗
The reference is retained here; its layer contents were not verified or imported.

Ontario GeoHub ↗ · Future road and water layers
Basemap tiles © Esri and its data providers, including NRCan and OpenStreetMap contributors. Leaflet mapping library.