Know where the map comes from
Map and place data
NavOSS uses OpenStreetMap-derived map and place data together with The City of Calgary's public Business Licenses and Parcel Address datasets. OpenStreetMap is open data licensed under the Open Data Commons Open Database License. Visible attribution names both OpenStreetMap contributors and The City of Calgary.
Calgary records are mirrored to a private local index every 24 hours; live searches do not go to Calgary Open Data. Home-occupation business records and malformed parcel rows are excluded. No source can guarantee every informal, new, relocated, or unlicensed place, and parcel coordinates may not identify the best vehicle entrance.
Routing
Production routes are calculated by self-hosted Valhalla using the same checksum-verified Alberta and British Columbia OpenStreetMap release as self-hosted Nominatim. Current live certification covers Calgary and Kelowna local routes plus both intercity directions. Route responses remain explicit that live traffic is unavailable.
Safety cameras
Fixed red-light and speed-on-green locations come from The City of Calgary's Intersection Safety Cameras dataset. NavOSS validates and caches the official records without sending user location to Calgary Open Data.
Kelowna regional context
Official Kelowna-area construction, closures, and incidents come from DriveBC Open511. Ordinary highway webcam locations and image links come from the OGL-BC DriveBC HighwayCams catalogue. These webcams are not enforcement cameras. Fixed public police facility markers come from the official Kelowna RCMP contact directory and are not live officer, patrol, incident, or checkpoint locations.
Kelowna search and driving routes use the live, separately certified regional OpenStreetMap import. DriveBC events and webcams are informational overlays and never alter route selection, ETA, rerouting, or speech.
Camera data can be incomplete or outdated. Alerts are supplementary and never replace posted signs or road laws.
What NavOSS does not use
NavOSS does not scrape or copy route, place, traffic, or map data from Apple Maps, Google Maps, Waze, or other proprietary navigation products. Manual comparisons are evidence for testing, not a source database.
An optional Google Places UI Kit component can receive the selected public POI name and coordinate and render Google's photos, rating and rating count, review text, and required attribution in its own visually separated native view. NavOSS checks the returned name and coordinate to prevent a mismatch, but does not add those values to its OpenStreetMap result, read them into shared contracts, or retain them. GooglePlacesSwift 10.15.0's underlying SDK privacy manifest declares location, Device ID, Other Data, performance, product interaction, and search history collection for analytics and/or app functionality, with no tracking. The separate external reviews link opens Google Maps only after the user chooses it. Builds without the restricted Google key make no Google place-details request and do not link that SDK.
Detailed registry
Dataset IDs, update cadence, fields, safeguards, and links are maintained in the repository's data-source documentation.