# Attribution — assets.secondkickmoto.com Everything served from this host is open data. Nothing here is licensed from a commercial vendor, and there is no key, no auth and no rate limit — the files are public objects on Cloudflare R2 and you are welcome to them under the terms below. Files are laid out by what they cover: `states/{state}/` holds everything that belongs to one state — map tiles (`.pmtiles`), the Forest Service's Motor Vehicle Use Map, roads and trails and BLM's designated routes (`.jsonz`, gzip of newline-delimited JSON) and the routing graph (`.pack`) — and `nationwide/` holds the rest. A rebuilt file is published beside the old one under a dated name, `{name}.{YYYYMMDD}.{ext}`, and the old one stays until no supported app version uses it, so most kinds below exist in more than one vintage. From the first **map data set** on, every state file derived from OpenStreetMap or from an agency is rebuilt together, from one OpenStreetMap snapshot and one capture of each agency dataset, and published under the set's id, the day its inputs were frozen: `{name}.{SET}.{ext}`. A set adds two kinds per state — a transportation file (roads, trails, gates, fords and trailheads) and an agency file (the Forest Service's and BLM's lines) — and replaces the `-roads` file. The rows below marked `{SET}` describe a set's files; the rows without it describe the files published before the first set, which stay until no supported app version uses them. The older `v1/` (tiles, MVUM) and `v2/` (routing graphs) prefixes hold the same files under the same names for older app versions, under the same terms, and are removed once no supported version reads them. The root also holds `app-config.json`, the app's own update notice, which is ours. Companion file: [`LICENSE-OSM.txt`](LICENSE-OSM.txt) — the ODbL notice for the OpenStreetMap-derived majority. ## Per file kind | Files | Count (per vintage) | Source | Licence | Attribution required | |---|---|---|---|---| | `states/{state}/{state}.pmtiles` | 50 | OpenStreetMap, via the [Protomaps](https://protomaps.com) daily planet build (basemap 4.14.11, build `20260720`, OSM snapshot 2026-07-13); the `landcover` layer (z0–7) is ESA WorldCover, via Daylight | **ODbL 1.0**; `landcover` layer **CC BY 4.0** | **Yes** — `© OpenStreetMap contributors`, and the land-cover credit below | | `states/{state}/{state}-roads.pmtiles` | 50 | OpenStreetMap, via the [Geofabrik](https://download.geofabrik.de/north-america/us/) per-state extracts | **ODbL 1.0** | **Yes** — `© OpenStreetMap contributors` | | `nationwide/nationwide-overview.pmtiles` | 1 | OpenStreetMap, via the Protomaps daily planet build (basemap 4.15.1, build `20260811`, OSM snapshot 2026-08-02); the `landcover` layer is ESA WorldCover, via Daylight | **ODbL 1.0**; `landcover` layer **CC BY 4.0** | **Yes** — `© OpenStreetMap contributors`, and the land-cover credit below | | `states/{state}/{state}.pack` | 50 | OpenStreetMap, via the Geofabrik per-state extracts; for the fourteen states with BLM routes, merged with BLM's GTLF Public Display (see below) | **ODbL 1.0** (the merged packs are derivative databases of OpenStreetMap and stay ODbL; BLM's part is public domain) | **Yes** — `© OpenStreetMap contributors`, and *Bureau of Land Management* for the merged BLM routes | | `states/{state}/{state}-terrain.pmtiles` | 50 | [AWS Terrain Tiles](https://registry.opendata.aws/terrain-tiles/) — Terrarium-encoded DEM | Public-domain and open sources, aggregated under the AWS Open Data programme | **Yes** — see the list below | | `states/{state}/{state}-contours.pmtiles` | 50 | AWS Terrain Tiles — 80 ft contours derived from the same DEM | as above | **Yes** — see the list below | | `states/{state}/{state}-publicland.pmtiles` | 42 | [BLM National Surface Management Agency (SMA)](https://gis.blm.gov/arcgis/rest/services/lands/BLM_Natl_SMA_LimitedScale/MapServer) | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *Bureau of Land Management* | | `states/{state}/{state}-water.pmtiles` | 50 | USGS [National Hydrography Dataset](https://www.usgs.gov/national-hydrography) (NHD), its final per-state snapshot | US Government work — **public domain**, 17 U.S.C. §105 | No. USGS asks for this acknowledgment, which we give: *Map services and data available from U.S. Geological Survey, National Geospatial Program.* | | `states/{state}/{state}-mvum.{YYYYMMDD}.jsonz` | 44 | USDA Forest Service [EDW Motor Vehicle Use Map](https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_MVUM_01/MapServer) roads and trails | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-fsroads.{YYYYMMDD}.jsonz` | 44 | USDA Forest Service [EDW National Forest System Roads](https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RoadBasic_01/MapServer), including the roads closed to motorized uses | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-fstrails.{YYYYMMDD}.jsonz` | 44 | USDA Forest Service [EDW National Forest System Trails](https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_TrailNFSPublish_01/MapServer) | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-blm.{YYYYMMDD}.jsonz` | 14 | Bureau of Land Management [Ground Transportation Linear Features (GTLF) Public Display](https://gis.blm.gov/arcgis/rest/services/transportation/BLM_Natl_GTLF_Public_Display/MapServer), layers 0–5: roads and motorized trails managed for public motorized use, open and limited, and trails managed for non-motorized and non-mechanized use | US Government work — **public domain**, 17 U.S.C. §105 | No. Credit, as BLM asks: *Bureau of Land Management* — modifications described below | | `states/{state}/{state}.{SET}.pmtiles` | 50 | OpenStreetMap, via the [Geofabrik](https://download.geofabrik.de/) US extract of the set and the same day's extracts of the neighboring countries a state's tiles reach into (Canada, Mexico, the Bahamas, Cuba, the Russian Far East), tiled by us with [planetiler](https://github.com/onthegomap/planetiler) 0.10.2 and the Protomaps basemap profile 4.14.11; at low zoom [Natural Earth](https://www.naturalearthdata.com) and the [osmdata.openstreetmap.de](https://osmdata.openstreetmap.de) land and water polygons; the `landcover` layer (z0–7) is ESA WorldCover, via Daylight | **ODbL 1.0**; `landcover` layer **CC BY 4.0**; Natural Earth public domain | **Yes** — `© OpenStreetMap contributors`, and the land-cover credit below | | `states/{state}/{state}-transportation.{SET}.pmtiles` | 50 | OpenStreetMap, via the Geofabrik US extract of the set | **ODbL 1.0** | **Yes** — `© OpenStreetMap contributors` | | `states/{state}/{state}-agency.{SET}.pmtiles` | 44 (every state with any agency file) | The four agency files of the same set, below: USDA Forest Service Motor Vehicle Use Map, National Forest System roads and trails, and BLM's GTLF Public Display routes | US Government works — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service*; credit, as BLM asks: *Bureau of Land Management* — modifications described below | | `states/{state}/{state}.{SET}.pack` | 50 | OpenStreetMap, via the Geofabrik US extract of the set, with every route of the state's four agency files of the same set as lines of their own (see below) | **ODbL 1.0** (a derivative database of OpenStreetMap, and stays ODbL; the agencies' part is public domain) | **Yes** — `© OpenStreetMap contributors`, and *Bureau of Land Management* and *USDA Forest Service* for their routes | | `states/{state}/{state}-mvum.{SET}.jsonz` | 44 | As the `-mvum` row above, captured for the set | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-fsroads.{SET}.jsonz` | 44 | As the `-fsroads` row above, captured for the set | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-fstrails.{SET}.jsonz` | 44 | As the `-fstrails` row above, captured for the set | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | | `states/{state}/{state}-blm.{SET}.jsonz` | 14 | As the `-blm` row above, captured for the set | US Government work — **public domain**, 17 U.S.C. §105 | No. Credit, as BLM asks: *Bureau of Land Management* — modifications described below | | `states/{state}/{state}-contours.{SET}.pmtiles` | 50 | As the `-contours` row above, cut to the set's footprint | as above | **Yes** — see the list below | | `states/{state}/{state}-terrain.{SET}.pmtiles` | 50 | As the `-terrain` row above, cut to the set's footprint | as above | **Yes** — see the list below | | `states/{state}/{state}-water.{SET}.pmtiles` | 50 | As the `-water` row above, cut to the set's footprint, from the NHD of every state the footprint reaches | US Government work — **public domain**, 17 U.S.C. §105 | No. USGS asks for this acknowledgment, which we give: *Map services and data available from U.S. Geological Survey, National Geospatial Program.* | | `states/{state}/{state}-publicland.{SET}.pmtiles` | 48 | BLM Surface Management Agency, from its national download (`SMA_WM.gdb`), cut to the set's footprint | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *Bureau of Land Management* | | `states/{state}/{state}-easements.{SET}.pmtiles` | 49 (every state but Hawaii) | The public access easements published under the MAPLand Act by five agencies: the [USDA Forest Service](https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_MAPLandEasement_01/MapServer), the [Bureau of Land Management](https://gis.blm.gov/arcgis/rest/services/recreation/BLM_Natl_MAPLand/MapServer) (lines and areas), the [US Army Corps of Engineers](https://geo-essayons.egis.usace.army.mil/server/rest/services/Hosted/USACE_MAPLand_Easements/FeatureServer), the [National Park Service](https://services1.arcgis.com/fBc8EJBxQRMcHlei/arcgis/rest/services/MAPLand_AccessEasement_py_NPS/FeatureServer) and the [US Fish and Wildlife Service](https://services.arcgis.com/QVENGdaPbd4LUkLV/arcgis/rest/services/FWS_MAPLand_Access_Easement/FeatureServer), captured once nationally for the set and cut to its footprint | US Government works — **public domain**, 17 U.S.C. §105; the Forest Service's MAPLand disclaimer (below) | No. Courtesy credit: *USDA Forest Service, Bureau of Land Management, US Army Corps of Engineers, National Park Service, US Fish and Wildlife Service* — modifications described below | | `nationwide/timber-harvest-{YYYYMMDD}.pmtiles` | 1 | USDA Forest Service [EDW activity facts](https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_ActivityFactsCommonAttributes_01/MapServer/0): timber sales awarded and not completed | US Government work — **public domain**, 17 U.S.C. §105 | No. Courtesy credit: *USDA Forest Service* | ## Modifications we have made BLM asks that anyone modifying its data describe the modifications. For the public-land tiles: source polygons are **reprojected** from Web Mercator to WGS 84, **clipped** to the state's bounding box, **simplified** for rendering at each zoom level (tippecanoe, simplification 6 — 8 for Alaska), and **packed** into vector tiles at z4–12 (z3–11 for Alaska). Adjacent polygons sharing a border are coalesced for tile size. **No attribute value is altered**: `ADMIN_AGENCY_CODE` is carried through verbatim and is the only attribute retained. Boundaries are therefore generalised for display and must not be read as survey-accurate — they were never that in the source either, which is neither a legal document nor a land survey. None of this is approved or endorsed by BLM. The MVUM files are the EDW service's own answer to one query per state bounding box, captured on the date in the file's name: geometry is **simplified** by the server to about 6 ft (`maxAllowableOffset` 0.00002°, five decimal places) in files captured on or after 2026-10-13, and to about 11 m (0.0001°) in earlier ones; and only the attributes a rider is shown are kept — names and route numbers, vehicle classes and the dates each is open, seasonal status, surface, trail class, forest and district. **No attribute value is altered.** The Motor Vehicle Use Map is the legal document for where a motor vehicle may go on National Forest land; these files are a dated copy of its data, and the Forest Service's published map and the signs on the ground govern. The Forest Service road and trail files are built the same way, from `EDW_RoadBasic_01` (all National Forest System roads, and those closed to motorized uses) and `EDW_TrailNFSPublish_01`: geometry **simplified** by the server as the MVUM files' is, and only the attributes the app shows or reads kept — for a road its name and number, maintenance level, surface, jurisdiction, functional class and who it is open to; for a trail its name, type, class, surface, grade, tread width, the uses it is open to and its national designation. **No attribute value is altered.** The app uses them to keep a planned route off a road closed to motor vehicles or a trail not open to the vehicle; the Forest Service's published maps and the signs on the ground govern. The BLM route files are built the same way from BLM's GTLF Public Display service, layers 0–5, one query per layer per state bounding box, on the date in the file's name. The modifications: geometry is **simplified** by the server to about 6 ft (`maxAllowableOffset` 0.00002°, five decimal places) in files captured on or after 2026-10-13, and to about 11 m (0.0001°) in earlier ones; each file holds the routes **selected by its state's area** (every route touching the state's bounding box, whole — not cut at the edge), so a route near a border can appear in both neighbours' files; and only the attributes a rider is shown are kept — route name or number, asset class, OHV designation and its limitation and explanation, allowed modes of transport, access restriction, surface, seasonal restriction, special designation and the NEPA decision document. **No attribute value is altered in these files**; the app rewords BLM's codes in plain language when it shows them. Only routes BLM designates for public use are published, so a track that is not in these files is not thereby closed. As BLM says of its own data, these are neither legal documents nor land surveys: the BLM travel map and the signs on the ground govern. None of this is approved or endorsed by BLM. The same BLM routes are **merged into those fourteen states' routing packs published on 2026-10-09** (`{state}.20261009.pack`; a set's packs are built differently, below), with these further modifications: each route is clipped to the state's own boundary; where an OpenStreetMap way already runs along a route (within 40 m and in the same direction), BLM's line is not added and its vehicle designation is attached to the OpenStreetMap way instead, drawn on that way — every BLM row matched to a way combined, the most permissive winning; rows for authorized or permitted users only are not attached, and no designation closes a county road or town street; where none does, BLM's line is added as a routable way, its ends joined to the OpenStreetMap way they meet when within 20 m. BLM's vehicle classes are reduced to the five the router reads (motorcycle, ATV, UTV, full-size vehicle, limited), four kinds of BLM note are read as vehicle limits (vehicle width or ATV class, single track, authorized or permitted users, "Closed to Motorized"), and over-snow routes are left out. The merged packs say nothing about any track BLM does not list. Fourteen states have a BLM route file — the eleven western states BLM manages land in, plus South Dakota, Texas and Washington, whose bounding boxes reach across a border into Montana's, New Mexico's and Oregon's routes. The other thirty-six have none, and a 404 for one of those is the correct answer. The same is true of the OpenStreetMap tiles: geometry is simplified and thinned per zoom, and tags are reduced to the handful the renderer needs. ## A map data set's files **The footprint.** Every file of a set is cut to one polygon per state, its **footprint**: the state's outline grown 25 miles on every side, or 10 miles for Rhode Island, Delaware, Connecticut, Vermont, New Hampshire, Massachusetts, Maryland and New Jersey (the outline is the US Census Bureau's TIGER state boundary). Neighboring states' files therefore overlap along a state line by the sum of their two distances: about 50 miles between two 25-mile states. The OpenStreetMap extract of each state is cut to its footprint with whole ways; the agency captures are asked of each agency by the footprint's bounding box, and a file keeps the rows whose line touches the footprint, each row whole. Roads, trails, agency lines and routing end at the national border; the base map, contours and hillshade draw past it, inside the footprint. **The base map** (`{state}.{SET}.pmtiles`) is built by us, with the same tiler and profile that made the earlier files, from the set's own OpenStreetMap snapshot: geometry simplified and thinned per zoom and tags reduced to what the renderer draws, as above. Its tiles are every tile at each zoom that touches the footprint, whole. Its roads outside the United States (in Canada and Mexico, and beyond 3 nautical miles at sea) are kept in a layer of their own, `roads_abroad`, cut where they cross the border, with every property unaltered. The land cover is modified as below; Wikidata page-view ranks (QRank, CC0) order the labels and none of their data is in the tiles. **The transportation file** (`{state}-transportation.{SET}.pmtiles`) draws every road, trail and walkway of the set's OpenStreetMap snapshot, zoom 7 to 13, and the gates, fords and trailheads, zoom 12 to 13. Each OpenStreetMap tag kept is read into a closed vocabulary: the road or trail class, surface (folded into paved, gravel, dirt, sand, rock, unpaved and other), track grade, smoothness, four-wheel-drive only, access for each mode, which of motorcycle, ATV, side-by-side and full-size vehicle the tags open or close, single or double track, seasonal and conditional restrictions, bridge, tunnel, ford, level, one-way (for motor vehicles), the hiking, mountain-bike and visibility scales, two census road classes (four-wheel drive, private) and whether a census-imported line was reviewed, name and number; every other tag is left out. A line is drawn from its class's lowest zoom up; geometry is simplified at the lower zooms and not at the top one; no line is dropped or merged to fit a tile. **The agency file** (`{state}-agency.{SET}.pmtiles`) draws the four agency files of the same set, one layer each, zoom 9 to 13. Every row is drawn, whole, except the Motor Vehicle Use Map routes the Forest Service lists as decommissioned, planned or converted. Each row's fields are **read into the app's legend**: a drawing class, the vehicles it is open to (motorcycle, ATV, side-by-side, full-size vehicle, or on foot only; nothing where the agency recorded no use), surface (paved, gravel or dirt), maintenance level, name, number, the season it is open and the Forest Service's route key; a Forest Service road or trail row also says whether Motor Vehicle Use Map rows of the same route key cover it. These are our readings of the agencies' fields, by the rules the app's route planner and route cards use; the agencies' own values are in the four `.jsonz` files, unaltered. Geometry is simplified at the lower zooms and not at the top one. **The routing pack** (`{state}.{SET}.pack`) is the set's OpenStreetMap roads and trails, with every route of the four agency files added as a **line of its own**. No agency route is matched to, attached to or laid on an OpenStreetMap way, and none closes one, except that the app keeps a planned route off an OpenStreetMap road the Forest Service's own rows say is closed to motor vehicles where the two lie together. The modifications to the agencies' data: - each route is **clipped to the footprint**, and coordinates are **rounded** to 1/200,000 of a degree (about 2 ft); - each route's vehicles are **reduced to** the classes the router reads: motorcycle, ATV, side-by-side, full-size vehicle, on foot only, seasonal, and not recorded. For BLM's rows: the allowed-mode code is read to those classes; a blank or unknown code is taken as open to every motor vehicle and marked not recorded; four kinds of note are read as limits (a vehicle width or ATV class, single track, authorized or permitted users only, "Closed to Motorized"); a route for authorized or permitted users only, and the trails of layers 4 and 5 (managed for non-motorized and non-mechanized use), are on foot only. For the Forest Service's rows: a Motor Vehicle Use Map route by its designation and its vehicle columns; a National Forest System road in the closed-to-motorized sublayer on foot only and an open one to every motor vehicle; a trail by its allowed uses or its motorized flag; - **left out**: over-snow routes, the Forest Service's snow and water trails, and a Forest Service road or trail row whose whole mile-post range Motor Vehicle Use Map rows of the same route key cover and draw on the same line (the Motor Vehicle Use Map's row is then the line). A Motor Vehicle Use Map route listed as decommissioned, planned or converted is kept, open to no one, for the closure above. BLM's rows are never left out for another's, nor is one agency's for another's. The packs say nothing about any track an agency does not list. **The agency files of a set** (`-mvum`, `-fsroads`, `-fstrails`, `-blm`, `.{SET}.jsonz`) are captured as described above, with two differences: each is asked by the footprint's bounding box and keeps the rows that touch the footprint, whole; and the Forest Service's files also keep each row's route key and begin and end mile posts, which is how the routing pack and the agency file know one road in two datasets. **No attribute value is altered.** The same fourteen and forty-four states have them as above. **Contours, hillshade, water and public land** (`.{SET}.pmtiles`) are built as described above, over the footprint's bounding box rather than the state's, and then cut to the tiles that touch the footprint. Water reads the NHD of every state the footprint reaches; public land reads BLM's national Surface Management Agency download rather than its map service, with the same modifications as above. **Access easements** (`-easements.{SET}.pmtiles`) are built from one national capture of the six MAPLand easement services, taken for the set on the day its files' metadata names (`sk:source_date`). The modifications: each state's file holds the records whose geometry **meets the set's footprint**, whole; polygons under 10 square meters (about 108 square feet, digitizing slivers) are **left out**; geometry is **simplified** below the top zoom only (tippecanoe, simplification 4) and **packed** into vector tiles at z10–13, with nothing dropped or coalesced to fit a tile. **Attribute values are rewritten, and most are not kept.** Each record keeps only an id, its agency, a title, its unit, its recording, what it records it allows, a unit link and its published day: - the **title** is the road or trail named in the record's `FEATURE_NAME` ("Selway River Road 223"), in title case, or nothing. The name of a grantor or landowner, a file or tract number and anything in parentheses are **removed**, and where a Forest Service record names a person or company and then a road ("HOPKINS, WILLIAM J. BANKS-LOWMAN ROAD #24"), only the road is kept ("Banks-Lowman Road 24"). The Corps', Park Service's and Fish and Wildlife's names are tract codes and are not kept; - the **unit** has the Forest Service's region code stripped ("R01 Northern Region" becomes "Northern Region"), the Corps' district code spelled out ("NWS" becomes "Seattle District") and capitals title-cased; - the **recording** keeps the recording type and number, the county and state and the year, each only where it holds a real value: the agencies' "not available at this time" sentences, "Unknown" and empty placeholders are **removed**; - **what it allows** is BLM's restriction text where it says something ("Camping", "Event") and the Park Service's link to its regulations, and nothing for BLM's `NONE` or for the identical "Use restrictions may apply" sentence on every Forest Service, Corps and Fish and Wildlife record. No grantor's name, placeholder sentence or parenthesis is in any published file (`verify_easement_tiles.py` checks every title). The Bureau of Reclamation's easements are not included. In the words of the Forest Service's service, these data "are not legal documents and are not intended to be used as such" and "may not be used to determine title, ownership, legal descriptions or boundaries, legal jurisdiction, or restrictions that may be in place on either public or private land"; the other four agencies' services publish the same MAPLand Act layer. An easement shows that public access is recorded, not which vehicles may use it; the county record, the managing agency and the signs on the ground govern. None of this is approved or endorsed by any of the five agencies. The land cover in the base tiles is modified too: Daylight vectorized ESA's WorldCover rasters into polygons, and planetiler with the Protomaps basemap tools simplified and tiled them for z0–7. Of the files published before the first set, eight states have no `-publicland` object — Connecticut, Delaware, Hawaii, Massachusetts, Nebraska, New Hampshire, Rhode Island, Vermont. A set builds public land wherever the SMA download has a polygon in the state's footprint, so from the first set only Connecticut and Hawaii have none, because the SMA inventory has nothing to show there. A 404 for one of those is the correct answer, not a gap. The same holds for Hawaii's `-easements` file: no MAPLand easement lies inside its footprint. ## Land-cover attribution, verbatim The `landcover` layer of the base tiles (`{state}.pmtiles` and `nationwide-overview.pmtiles`) is derived from ESA WorldCover, licensed under [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/) and published at . It **requires** this credit: > © ESA WorldCover project 2020 / Contains modified Copernicus Sentinel data > (2020) processed by ESA WorldCover consortium The modifications are described above. ## Terrain and contour attribution, verbatim The AWS Terrain Tiles collection **requires** attribution, per line of contributing source. These are the lines that apply to the coverage served here (continental US, Alaska, Hawaii, and the Canadian and Mexican border margins): > United States 3DEP (formerly NED) and global GMTED2010 and SRTM terrain data > courtesy of the U.S. Geological Survey. > > Canada terrain data contains information licensed under the Open Government > Licence – Canada; > > Mexico terrain data source: INEGI, Continental relief, 2016; > > Global ETOPO1 terrain data U.S. National Oceanic and Atmospheric Administration > > ArcticDEM terrain data DEM(s) were created from DigitalGlobe, Inc., imagery and > funded under National Science Foundation awards 1043681, 1559691, and 1542736 The ArcticDEM line covers Alaska north of 60°, where the terrain tiles use ArcticDEM from zoom 10 up — so it applies to Alaska's contour files, which are cut at zoom 10, and not to Alaska's terrain file, which stops at zoom 9. The files on this host cover the US and its border margins only, but the SK Maps app also streams the same terrain tiles live wherever its map is panned, so it carries the lines for the sources used outside North America as well: > Australia terrain data © Commonwealth of Australia (Geoscience Australia) 2017; > > Austria terrain data © offene Daten Österreichs – Digitales Geländemodell (DGM) > Österreich; > > Europe terrain data produced using Copernicus data and information funded by the > European Union - EU-DEM layers; > > New Zealand terrain data Copyright 2011 Crown copyright (c) Land Information New > Zealand and the New Zealand Government (All rights reserved); > > Norway terrain data © Kartverket; > > United Kingdom terrain data © Environment Agency copyright and/or database right > 2015. All rights reserved; The full list is published at . ## Per-object provenance Every object's upstream, version, licence and build pipeline is recorded individually — not just per kind — in the `source` block beside its SHA-256 in the consuming application's compiled-in digest manifest. Nothing here is identified only by its filename. Files are byte-verified on download against those digests, so an object cannot be silently replaced: a mismatch fails closed rather than installing. ## Rebuilding these files The build is reproducible and the recipe is public: `build_state_tiles.sh` in the SK Maps repository takes a state slug and produces all five tile kinds from the upstreams named above, with pinned versions. `--dry-run` prints the plan and every URL without downloading anything. `build_usfs_layers.py` does the same for the MVUM, Forest Service road and trail, and BLM route files. A map data set's files are built together by `build_set.sh`, from inputs it freezes and records by SHA-256; `--dry-run` prints its plan. ## Contact Second Kick Moto LLC — If you are a data publisher and something here misattributes your work, or is served under terms it should not be, say so and it will be fixed or withdrawn.