Overview
The Temane map-folio example under /home/aaron/framework/map-folio_temane/ is especially useful here because it separates infrastructure into practical families:
- roads
- buildings
- power lines and power sites
- amenities and other built features
That separation is better than one generic “infrastructure” layer because the analytical role of each family is different.
Why it matters
- Roads shape access and logistics.
- Power layers shape transmission, interconnection, and industrial context.
- Buildings and amenities help reveal settlement intensity and local service geography.
- Combined infrastructure context often explains why a route was chosen or why an area became sensitive.
When to use
Use infrastructure layers when:
- reviewing route alternatives
- planning site access
- assessing proximity to grid or transport assets
- explaining project feasibility to mixed technical audiences
Inputs
Common inputs:
- OSM transport and power layers
- government road or grid datasets where available
- industrial and port footprints
- building and land-use context
The archived Temane OSM-derived example is a useful reminder that even an imperfect local extract can still show valuable patterns, including major highways, unpaved roads, power lines, generators, and substations.
Recommended layer families
| Layer family | Typical use | Common caution |
|---|---|---|
| Roads and tracks | Access, logistics, route comparison | Surface and passability are often incomplete |
| Power lines | Grid context, crossings, network adjacency | Voltage and operator are unevenly populated |
| Power facilities | Generation, substations, switching points | Polygon versus point representation can vary |
| Buildings | Settlement intensity and built footprint | Building coverage can be dense but semantically shallow |
| Amenities | Community and service context | High thematic value, low completeness in some regions |
Workflow and method
- Separate transport, power, and social-service context into different layers.
- Preserve source attributes like
highway,power,voltage, andsurface. - Normalize a smaller project schema for analysis.
- Simplify geometry for web display if needed.
- Keep a richer analytical copy for desktop review.
Live infrastructure sample
Outputs
Useful outputs include:
- access-route maps
- crossing and adjacency review layers
- infrastructure context maps for stakeholder briefings
- cleaned transport and power packages for downstream analysis
Limitations
- Open infrastructure data can be biased toward visible networks and major assets.
- Small service roads, private facilities, or newer assets may be absent.
- Power layers may carry geometry with weak operational metadata.
- Buildings show built presence, not necessarily occupancy or sensitivity.