Quiet Corners

What it does

Quiet Corners Field Maps turns a rectangle you draw, or a named USGS 7.5-minute quadrangle, into a field-ready topographic map of exactly that area, printed on ordinary Letter paper at true scale. The sheets are indexed and aligned so they tape together edge to edge, Forest Service road-use seasons are drawn over the USGS Topo base, and every sheet carries the retrieval date of each source it was built from. The PDF is assembled in your browser: no upload, no account, no server. You build one on the Quiet Corners map itself, under “Print field maps of this area” — the same map you pick a county on, because there is only one. This page is where the sources, the printing instructions and the calibration procedure are written down; the privacy page says what the map services receive.

Starting sets

Above the layer switches are two buttons, each a named set of those same switches for one kind of outing. A button is a shortcut, never a mode: it ticks and unticks the boxes below and moves the two choices above them, you can see exactly which ones it moved, and every one of them is still yours to change afterwards. No layer reaches the map any other way.

• A night under the sky — night light emissions, the aurora outlook and the air-quality category, with the boundary lines out of the way and no base map under them. It answers whether tonight is worth the drive from here, and how far out you would have to go. Precipitation radar is deliberately not in this set: it reports what the beam met aloft in the minutes just past, which is not cloud tonight — the hourly conditions card is what answers the hours ahead — and it is a second full-screen picture over the first, which is the clutter limit below.
• A day out on public land — national parks, forests, wilderness and refuges; Forest Service land ownership parcel by parcel; MVUM road and trail designations; hiking trails; Forest Service and BLM recreation sites; on the topo base. It answers where you may legally go and what is there when you arrive. A boundary still says nothing about access — see the section below.

What these sets are held to. Two of the three things worth measuring here are enforced by a test rather than by good intentions, and a set that exceeded either could not be built at all. The third, task completion, is not mechanical: it is watched rather than asserted, and what the code holds each set to is that it states the question it claims to answer.

• Load size. Each layer switched on is one query of its own against its service, and a query pages up to twenty requests. The public-land set is six layers, a worst case of 120 requests for one settled view; the night set asks the vector services for nothing at all, because its surface is a picture handed straight to the map. Six is the ceiling until a wider set has been measured.
• Clutter. At most one continuous-colour surface at a time, and that is now enforced rather than promised: Land, sky & light context is a choice of one — the steepness of the ground, night lights, radar, aurora, air quality, wildlife records, the Quiet Corners county ranking, or No context surface — exactly like the base map above it. It used to be four independent checkboxes, so a reader could stack four filled surfaces over each other and nothing stopped them; the light-emissions surface is drawn at 80% and the radar at 55%, and those two alone leave under a tenth of whatever is beneath them showing. No context surface is where the panel starts, and it stays a row of its own so turning them all off again is always one click. On the map key, the public-land set draws nineteen distinct marks and the night set draws one. The county ranking is the one surface here with no service behind it at all — it is the dashboard’s own local data, drawn on screen only, and it is never in the printable-vector fetch loop and never on the printed key: a screen-only layer switched on for the screen used to still be listed as a source on the sheet that never carried it, and the credit list is now built from what actually reaches paper rather than from what the reader had switched on.

Highlight

Two buttons above the layer switches, Highlight trails and Highlight boundaries, thicken the lines of one drawn layer and dim everything else on the screen; Clear highlight restores exactly what was on screen before, never an approximation of it. A summary line states in words whatever the screen currently differs from the default view, and the map key dims and brightens its swatches the same way the map itself does, from the same state. None of this is a mode: switching a layer on or off, or drawing a new area, works exactly as it did before a highlight was ever pressed.

Advanced, closed by default under the buttons, exposes the same handful of knobs by hand: how much to dim everything not highlighted, how heavy the drawn lines are, how solid a filled polygon is, and a menu to spotlight any one layer directly rather than only trails or boundaries. Touching any of these releases a Highlight-button press back to a plain setting — there is no state where a highlight and a manual edit disagree about what is on screen.

None of this reaches the printed sheet. The PDF is built from the print recipe alone — area, paper, scale, overlap, grid and the layers you checked — and the emphasis state above is never one of its fields; asking for it is refused outright rather than silently ignored. A screen highlighted for reading is not a page marked up for printing, and the sheet’s credits list is built the same way, from what was actually fetched for it, not from anything a highlight touched.

Three settings your device or browser may already be asking for are honoured here specifically because dimming is designed to reduce contrast for everything but the highlight, which a reader who has turned up contrast is asking never to happen: more contrast and Windows’ forced colors both cancel every dimmed opacity outright rather than trying to draw a softer version of it, and a highlighted button still marks itself without relying on colour alone. Reduced motion costs nothing extra here, because a highlight or a clear takes effect immediately rather than fading in.

What a boundary does not mean

State game lands, parks and other managed areas are drawn as boundaries: a line marks where a designation begins and ends. It is not a statement that the ground inside is open to you, and it is not a statement that the ground outside is closed. Seasons, permits, camping, fires and vehicle access are the managing agency’s to state, not this map’s to infer, and they differ unit by unit. An empty result means the state’s service returned nothing for that area, which is not the same as “no public land here”. Confirm access and current closures with the managing agency before you travel.

Parcel boundaries are drawn from the counties’ own recording and tax maps, at 1:24,000 only. A parcel line is a record, not a survey: it is drawn to locate a property for taxation, not measured to establish where its corners are, and a recorded line and a surveyed line disagree routinely. It is not permission to enter. Coverage differs county by county, so a blank area means the county published nothing there rather than that the ground is unowned. No owner name, mailing address or occupancy field is ever requested — the catalogue records each state’s owner-bearing fields as a refuse-list, and every parcels layer this map offers has had its actual field VALUES audited, not just its field names, because a field named for a category can still hold people: North Dakota’s Ownership is declared with a nine-value domain and one county had filled it with individual landowners.

Mapped wetlands are neither a boundary nor a landholding, and the map draws them in their own colour for that reason. A wetland edge is approximate by construction — it is a line someone drew on an aerial photograph, which is why it is drawn broken rather than solid — and it carries no statement about access, ownership or what any law regulates. Where nothing is drawn, the layer’s own row says whether the ground was mapped and holds none or has never been mapped at all; those are different facts and they look identical on the map.

The same sentence is printed on the map key of every set that draws a boundary, because the sheet in your hand is where it matters.

On the screen each boundary family — National Forest, Wilderness, National Park unit, Wildlife Refuge, state game land, state park, other state-managed area — has its own colour and a light fill, so you can see where one begins and tell it from the next; the key beside the map shows the same colours. On paper they are all one blue, told apart by their line pattern, because a printed sheet is a grayscale halftone and a hue would not survive it.

Status

Proof stage. The engine builds real PDFs; what is outstanding is the physical verification — a ruler-and-tape test on printed sheets — which has to pass before the builder is offered as finished work. Until it does, the builder carries that caveat on its face, wherever it is hosted.

Sources

• USGS Topo basemap — National Map basemap tiles, the base map on every sheet, and the screen’s base unless you choose another.
• USGS Imagery Only basemap — National Map imagery tiles, an optional screen base on the same host as the topo. Measured 2026-09-12: cached through level 16, level 17 answers 404; the service states its data was refreshed June 2024. It shows ground cover as flown, on a multi-year cycle, not access.
• USGS Shaded Relief Only basemap — National Map shaded relief tiles, an optional screen base on the same host. Measured 2026-09-12: cached through level 13, level 14 answers 404, so closer in the same picture is enlarged and the layer row says so. It shows the shape of the ground, not what is on it.
• USGS 7.5-minute map index — National Map map indices, the named quadrangle outlines you can pick from.
• US Forest Service Motor Vehicle Use Map (MVUM) — EDW MVUM service, road and trail designations with seasonal dates. Tap or tab to a route and it says who may drive it and when — “Open to passenger cars Apr 1 – Dec 15”, or “Closed to passenger cars; open to high-clearance vehicles year-round”. A blank field is the inventory not answering, so it is never reported as closed and never as open; a route the source called seasonal without giving a window says the dates are not stated rather than reading as year-round.
• US Forest Service road inventory (Road Basic) — EDW RoadBasic service, the maintenance level and surface type of a forest road. MVUM answers whether you may drive a road; this answers what your vehicle would meet on it. Tap or tab to a road on the map and it says so in the inventory’s own words — “Crushed aggregate or gravel; suitable for passenger cars (level 3)”.
• USGS 3D Elevation Program (3DEP) — 3DEP ImageServer, elevation sampled along a drawn route for the optional summary page.
• Annual NLCD land cover — Annual NLCD Collection 1.1 ImageServer, what the ground was mapped as, as an optional screen surface. It is served from the USDA Forest Service’s imagery platform rather than from MRLC’s own host, which answered none of 33 probes over 19 minutes when this was measured — the product is USGS’s, the door it comes through is the Forest Service’s, and the credit names both. The year is always stated, because the service will not: ask it without one and it quietly answers its newest, which is 2024, and the same square of ground in NW Las Vegas reads Shrub/Scrub for 1985–2005 and Developed for 2006 on. The class numbers are published nowhere — the service’s own attribute table comes back empty — so the fifteen this map labels were recovered by exporting one extent twice, as raw values and as rendered colours, and pairing all 65,536 pixels; the sixteenth, Perennial Ice/Snow, did not occur in that extent and the key says its class number is unverified rather than passing it off as known. Every 30 m square is about a quarter-acre and holds one class, so a road or a creek narrower than that disappears into whichever class won the square. The lower 48 states only. There is no NLCD land-cover service here for Alaska, Hawaii or the territories, and the layer says the view is outside coverage rather than drawing it as bare ground — a distinction the picture itself cannot make, since an out-of-coverage export and an ocean export are byte-identical.
• NLCD percent tree canopy cover — TCC ImageServer, the modelled share of a 30 m square that tree crowns cover, on the same host and as the alternative screen surface — the two are radio buttons in one group, so one is drawn at a time. Its year is stated for the same reason and reaches 2025, one year further than land cover, so a card showing both dates each separately. The service’s own serviceDescription still advertises the older v2023-5 and contradicts its description; the catalogue of rasters settles it in favour of v2025-6, and the catalogue is what this map reads. Two values in the data are not percentages — 254 marks a non-processing area and 255 the background — and they are never averaged into one or shown as canopy. 70% canopy is not 70% shade on a trail: it is a view from above in one year, smoothed across a time series, and says nothing about the season or about what is under the crowns.
• USGS 3DEP terrain slope — the same 3DEP ImageServer, rendered through its Slope Degrees raster function as an optional on-screen surface. Steepness is shown in degrees and the key gives the percent-rise equivalent beside every band, because percent rise is tan(degrees) × 100 — 45° is a 100% rise — and the service labels no unit anywhere. The colours are this site’s own: the service publishes no class breaks for its ramps, so its picture cannot honestly be given a key. The export is asked for as png32 so that ground the elevation model does not reach arrives with a transparent alpha channel and is left undrawn, instead of collapsing onto the same value as level ground. Which way a hillside faces is read only where the slope is above zero — flat ground has no facing direction, and the service reports flat as 0, the same number as due north. It is arithmetic on a bare-earth surface averaged over a cell tens of metres across: not a statement that anywhere is safe to travel, and not a picture of sun or shade at any hour.
• USGS 3DEP shaded relief — the same 3DEP ImageServer, rendered through its named Hillshade Gray raster function, as an optional companion sheet. It shows the shape of the ground; the contour values stay on the topo sheet.
• USGS PAD-US public access — PAD-US Public Access FeatureServer, the access category a land manager filed for each protected unit your area touches, as an optional answer in words rather than as ink on the map. Four categories exist and the layer names all four in the service’s own wording — Open, Restricted, Closed and Unknown. Unknown matters most: the service’s own picture defines colours for only three of them, so a map drawn from its symbology silently drops the 43,047 records that carry Unknown, and here it is a fourth answer rather than a shade of Open. What a category is not, ever, is permission: it describes a management regime at whatever date it was filed, says nothing about camping, fires, hunting, driving or being there after dark, and a boundary still encloses private inholdings. The acreage shown beside a unit is that whole unit’s area and says so — six units touching a 491,877-acre rectangle carry 3,033,604 acres between them, because the polygons run far outside it, so no acreage is ever added up across an area. Outside the conterminous states PAD-US fills what it does not inventory with a single 105,513,892-acre background polygon whose category is Unknown; it is excluded from the request and dropped again on arrival, and the row says the inventory stops there rather than repeating it. The service publishes no version and no date on a record, so the row carries the date it was retrieved.
• EPA Level III ecoregions — the Omernik ecoregion service, read from a copy this site serves rather than from EPA on every visit. It names the kind of country a place is in — “Northern Lakes and Forests”, within “NORTHERN FORESTS” — drawn by analysts from geology, landforms, vegetation, climate, soils, land use, wildlife and hydrology together. It is a classification of the landscape, never a reading of it, and it says nothing about any particular acre. The data has not moved since December 2011, so there is no freshness to gain by asking EPA live, and the national request is refused outright unless it carries a generalization parameter — baking that into a committed file removes the failure rather than guarding it. The copy is 85 regions and 949,718 bytes, fetched only when the switch goes on. Conterminous states only: Alaska and offshore answer with nothing, and the row says the map stops there rather than that the ground has no character.
• USDA National Agriculture Imagery Program (NAIP) — NAIP imagery service, the optional aerial companion sheet.
• USGS National Map government units — govunits MapServer, federal designation boundaries: National Park System units, National Forests, designated Wilderness and National Wildlife Refuges, plus county boundaries from the 2025 TIGER/Line county file. County lines come from this service rather than the generalized outlines the county finder uses: those sit a median of 250 metres from the real boundary and up to 2.4 kilometres at worst, which is most of an inch on a 1:24,000 sheet and in places nearly four. Bureau of Land Management is deliberately not drawn — its polygons are Field Offices, administrative jurisdictions rather than holdings, and the Moab Field Office alone spans 2,907 square miles of mostly non-federal ground.
• FEMA National Flood Hazard Layer — the NFHL map service, the regulatory floodplain, as an optional screen overlay. It is the one context surface here that is not about a moment: an engineering study modelled the 1%-annual-chance floodplain, FEMA adopted it for insurance and floodplain management, and it was drawn on a panel. So it never says where water has been or will be, and it is never drawn in the same breath as a weather alert. Its age belongs to the panel, not to the screen. The zone record carries no date at all — the effective date is a join to the FIRM panel underneath — and one 0.12° × 0.07° view measured panels adopted 2012-11-02 and 2016-12-08, four years apart, so the row gives the range rather than one date that would be false for most of what you can see. Zone X is not one thing: the 0.2%-annual-chance area, minimal hazard and areas behind a levee all arrive as X, and the subtype is what says which, so it is always shown. Where FEMA has published no study the layer draws nothing and says so — that is ground nobody assessed, never ground found to be low risk — and the map service is asked whether a study exists at all before it is asked for any zones, because zero zones over a rectangle means those two different things. A base flood elevation is printed only where the record states the datum it is above; 154 of the 159 zones measured carry -9999 in that field, which is the service declining to say. Dense views are refused rather than drawn: one 0.6° × 1.0° extent holds 29,016 zone polygons, so the layer counts first and asks you to zoom in above 1,500 rather than fetching fifteen pages of shapes nobody can tell apart.
• US Forest Service surface ownership — EDW SurfaceOwnership service, the Forest Service’s own Land Status Record System, parcel by parcel. A National Forest’s proclamation boundary encloses private inholdings; this layer says which ground inside it the Forest Service actually owns and which it does not. Dense by nature — 81 parcels in one quadrangle — so it is drawn as unlettered hairlines at every scale rather than left out. The record’s case name is the person the ground was bought from and is never requested.
• Bureau of Land Management recreation sites — BLM National Recreation Sites and Facilities, the 1,304 places BLM publishes as recreation areas. BLM land is the one federal estate this map drew boundaries for and gave you nowhere to stop; this is the layer that answers it. Each site carries the agency’s own directions and description — reduced to plain text, never rendered as the provider’s HTML — its own page on blm.gov, and the last-updated date that record states, which runs per record rather than per service. Opening a BLM pin — click it, or tab to it and press Enter or Space — shows those lines as a card you can read, scroll and shut with Escape; hovering still gives just the site’s name. Where a record says nothing, the card says the inventory did not say, never that there is no access. It is a list of recreation sites and nothing else: the source’s own night-sky language appears in 3 of the 1,304 records, so the layer makes no claim about what the sky does over any of them.
• US Fish and Wildlife Service National Wetlands Inventory — NWI Wetlands service, the mapped wetlands of an area, as an optional overlay. It is an inventory drawn from aerial imagery, not a survey and not a visit: a photo-interpreter read wetland vegetation, hydrology or geography in a picture taken in a stated year, and FWS says a margin of error is inherent and that inspection on the ground may revise any boundary. The year varies enormously and is read per place from the service’s own source layer — Horicon Marsh in Wisconsin was mapped from 1994 black-and-white photography at 1:20,000, Tonopah in Nevada from 2022 colour infrared — so the layer states the year for the area you drew rather than one national date, and says the scale is not stated where the record does not give a usable one. A polygon says nothing about access, ownership, whether the ground is wet today, or whether any law regulates it: FWS uses a biological definition that need not match Clean Water Act boundaries, and some farmed wetlands, seagrass and submerged aquatic vegetation are excluded from the programme outright. A blank area is two different facts, and the layer says which: ground that was mapped and holds none, or ground the inventory has never mapped — every unmapped area is in Alaska or the Pacific territories. A large area is refused rather than fetched: the service is asked how much it holds first, and past 4,000 wetlands nothing is requested, because asking anyway takes minutes and times out rather than failing.
• NOAA National Weather Service forecast — api.weather.gov, the hourly forecast for a selected place: temperature, precipitation chance, humidity, dew point and wind. Two steps, because a latitude and longitude is not a forecast: /points/{lat},{lon} names the forecast office and grid cell and hands back the forecast URL to ask. Temperature arrives in whichever unit the response states — the same hour answered 86 °F and 30 °C seconds apart depending on the request — so the unit is always read, never assumed. A forecast belongs to a grid cell rather than to a summit, so a valley and the ridge above it can share one. Wind is reported as the direction it comes FROM; an hour rounded to “0 mph” is the product’s rounding floor and is never reported as calm, and an hour with no stated direction says so rather than pointing north. Gusts are not in the hourly product at all — they come from the same office’s forecast grid (/gridpoints/{office}/{x},{y}), where every value covers a span of hours rather than one hour and each field starts and ends its spans in different places, so the spans are spread over an hour grid and matched by time before anything is read; a gust is reported as a peak rather than a sustained speed, and a forecast that states no gust is never read as no gusts. Cloud cover comes from the same grid, as the share of sky the forecast expects to be covered in that hour — stated by the service in percent, and read only when the service says percent, because a count of eighths printed as a percentage would report a covered sky as a clear one. An hour the grid does not state is reported as unknown, which is not the same as a clear sky, while a stated 0% is a real forecast and is shown as one. The hours are the place’s own: the card names the hour in the place’s zone, so on the night the clocks go back the two 1 AMs keep their own cloud values and on the night they go forward the hour that never happens is never printed. Past the end of the forecast’s own stated span the weather is simply not out yet, which the card says while the calculated sun and moon times still stand, and a forecast older than its refresh window says it is out of date rather than showing its numbers as current. Outside the United States and its territories the service answers “no forecast here”, which is a state the card shows rather than an error. The two cards fail apart: the place’s own clock zone arrives with the first response, the sun and moon times are arithmetic on that zone and owe the forecast nothing, so a forecast that fails after the zone has arrived takes only the forecast card with it and leaves tonight’s times standing.
• NOAA National Weather Service alerts — active watches, warnings and advisories, the products in force at the selected place, on a card of their own. It is deliberately not part of the forecast card above: a forecast is a number for an hour, an alert is a product an office issued with a window of its own, and a failure in either leaves the other standing. Each alert shows its own issue and end times, stamped in the selected place’s time zone rather than yours, and links to the Weather Service’s record for that alert — the web field every single alert carries is the agency front page, identical on all of them, so it is never offered as detail about one. Nine alerts in ten carry no drawn outline at all: 342 of the 386 in force when this was measured were zone-based, so an alert names the zones it applies to instead of a shape, and a missing outline is the usual case rather than an empty answer. An alert whose own end time has passed while the page held the response stops being in effect and says so; one the office cancelled is withdrawn whatever expiry it still states; and a service that fails says it could not be reached, which is never rendered as “nothing in force”. Most of all, a quiet card means no National Weather Service product is in force here — not that the ground is free of danger. These are the hazards this one agency issues products for, which is not every hazard that exists.
• GBIF wildlife records — GBIF occurrence search, counts of times somebody saw a living thing inside the area you are looking at and wrote it down, as an optional screen surface. It is asked as a single bounded count per area — limit=0 with facets, about 3.5 KB — never as a list of records, and that is not a performance choice: coordinateUncertaintyInMeters was present on 4,043 of 133,925 records (3.0%) in the cell this was measured against, so the precision of a record is usually unknown and nothing is drawn as a dot. The area is shaded and no location inside it is claimed. Only public-domain (CC0) and Creative Commons Attribution records are asked for; that filter is a complete whitelist over GBIF’s closed five-value licence enum, it is enforced by the server, and the row says how many records in the area it removed. Each contributing dataset is credited by its own published citation, resolved from the record’s dataset key — the dataset name field is absent on the largest publisher, so crediting from it would silently leave that publisher out. The count is an upper bound: two publishers can submit the same sighting and a count of records cannot tell them apart. Records whose location was deliberately widened — to protect a threatened species, or at the recorder’s request — arrive stating about 28 kilometres of uncertainty; they are counted and never placed. Most of all, this is a record of effort: two cells the same size measured 133,925 records and 827, a hundred-and-sixty-fold difference in recording and not in wildlife. An empty area means no records in this selection — not no animals, not poor habitat, and often just that nobody walked there with a phone. Nothing here says a species is present now, says where in the area it was, or says you will see it. No photographs are loaded: media carry their own licences, separately from the record holding them. GBIF data user terms.
• NOAA National Weather Service radar — MRMS base reflectivity, the national radar mosaic, as an optional screen overlay. It answers what is falling now, which the hourly card does not: an hourly number belongs to a grid cell and an hour, and a shower crossing one ridge is neither. What radar sees is what the beam met aloft, not what reached the ground — a beam clears an intervening ridge, and a light return can be dry air or birds. The service keeps a rolling window of about two hours and nothing older, so the layer always states the time the frame it is showing was valid and how long ago that was; past twenty minutes it says the picture is too old to act on rather than drawing it as current, and a service that does not state a time is reported as unknown. It is drawn on screen only and never on a printed sheet, because a two-hour window is out of date before the ink dries.
• NOAA aurora forecast — SWPC’s OVATION model, an optional screen overlay for the chance of aurora overhead. It is a forecast, and the payload says so itself: the observation time and the forecast time it carries measured sixty-six minutes apart, so the layer names the forecast time rather than describing the sky as it is now. It models the chance of aurora overhead and says nothing about cloud, so a high number and a clear night are two separate questions. Over the lower 48 it reads zero on almost every night — all 1,560 cells covering it were zero when the source was measured, with the first non-zero values near 65N — so “nothing forecast here” is the ordinary answer rather than a gap in the data. The whole-globe file is about 900 KB, so it is fetched only when the layer is switched on.
• EPA AirNow air quality — AirNow latest-hour AQI contours, the air quality category EPA published for the most recent hour it had. What the records hold is the whole of what the layer can say: a category from Good to Hazardous, and the hour it belongs to. There is no pollutant field and no index value in them at all, so the layer names the category and stops — it never names a pollutant and never states a number, because either would be invented rather than read. It is an observation of a past hour and never an outlook: every reading carries the hour it covers and how long ago that was, and one older than four hours says it is too old to act on rather than being shown as current. The contour surface is interpolated between monitoring stations, so ground with no monitor near it still takes a colour from what was measured elsewhere, and EPA publishes these hourly figures as preliminary rather than as the verified official record. United States only — 115 contours covered the whole country when it was measured, all sharing one hour, which ran 144 minutes behind the clock.
• NOAA smoke plume analysis — NESDIS Satellite Analysis Branch HMS smoke, an optional screen surface showing where an analyst outlined smoke in that day’s satellite images. It is smoke aloft — a column of air seen from above, not the air at head height — and it is deliberately a separate question from the air quality contours above, which measure a different thing at a different height and disagreed with it over the same ground when both were measured. The three classes are how opaque the smoke looks from orbit; NOAA says they roughly approximate 0–10, 10–21 and 21–32 micrograms per cubic metre through the column, and states plainly that no guarantee is made about the real density, so the layer reports them as approximations and never as a reading. Each plume carries the satellite image window it was drawn from, in UTC, and the row leads with that window rather than with the class. It is a daylight product: nothing is analysed at night, the first plumes of a day appear around local noon, and an empty map before then means the day has not been analysed rather than that the sky is clear — which the layer asks the service directly rather than assuming. North America only, screen only. NOAA publishes the same analysis as a KML file on its own file host, which serves no cross-origin header at all and cannot be read by a browser; this service is the same day’s analysis, feature for feature, and needs no archive opened and no KML parsed.
• NIFC wildfire perimeters — WFIGS current interagency perimeters, an optional screen surface showing boundaries mapped for active incidents. “Current” is the service’s name for itself, not a promise about any shape in it: each boundary was mapped at some earlier moment, and the median measured three weeks old with one in ten past two months — so the row states the age of every perimeter it draws instead of one “as of” for the layer, and a boundary whose mapping date the record does not state says so rather than being drawn as fresh. One record in the national set is dated the year 0926, which naive arithmetic would render as 401,770 days old; anything before 2000 is read as unknown. Prescribed burns are filtered out — planned, deliberate fire is not wildfire, and drawing one as the other would be a factual error — and incidents reported fully contained remain in the service, so a perimeter is not proof of active fire. The national set is 37 MB unsimplified and did not transfer at all when it was measured, so the shapes are always requested simplified to what the screen can resolve. NIFC states these data are dynamic and are not legal documents: nothing here is a closure, an evacuation order, or a statement about any road.
• NASA Black Marble night lights — GIBS WMTS tiles, the optional light-emissions context surface on the screen. It is a picture of light sent UPWARD from the ground, taken from orbit and averaged over a year, and the newest composite this service publishes is 2016 — so the year is part of the layer’s own name rather than a footnote. Two things it deliberately does not do. It never prints a Bortle class, a 1-9 rating or any score: upward radiance measured by a satellite and what a human eye sees standing underneath are different quantities, and mapping one onto the other would not be a unit conversion. And it never claims to describe tonight. Its finest detail is zoom 8, which is where the tile set stops — closer in, Leaflet enlarges the same picture and the layer row says so, because an enlarged tile looks exactly like real detail.
• State land services — game lands, state parks, other state-managed areas and county parcel boundaries, one service per state, measured and recorded in state-sources.json, the one catalogue the map reads. Boundaries only; no owner or occupancy information is ever requested.

Every source a set is built from is credited by name on its printed map key, derived from what the build actually consumed rather than written by hand.

Tap a recreation site and it also says how far the nearest unpaved road is — “0.7 mi from a mapped crushed aggregate or gravel road (straight-line)”. Three things that phrase is careful about: mapped means the roads fetched for the area you are looking at and no others; straight-line means exactly that, because nothing here calculates a route, a legal right of way or a driving time; and a road whose surface the inventory never stated is not counted as unpaved, so a site with nothing to say says nothing rather than promising gravel nobody looked up.

A road’s rating is the Forest Service’s record, not a report of current condition: a road can wash out, gate or be logged over without the inventory changing. Where no record matched the route, the road is drawn at its plain width and says nothing extra — an empty rating would read as “the inventory looked and found it ordinary”. Where two records disagree about the same route, the map says they disagree rather than picking one.

Honesty rules. MVUM is a designation dataset published forest by forest, not a live passability feed, and not every forest is included. Seasonal dates are shown only when the source supplies them: on screen when you select a route, and on the printed key under Seasonal routes, one line per route that reached the sheet. Routes the source called seasonal and gave no dates for are counted there too — listing only the dated ones would read as “these are the seasonal roads here”, and you would drive an unlisted one in February on the strength of it. A source that fails to load never disappears silently: it blocks the PDF, or you remove that layer explicitly. Each source prints its own retrieval or dataset date; there is no single composite “as of” date.

Which states are covered

50 of 51 states publish at least one land layer this map can read, measured 2026-09-06. Federal layers work everywhere, so a state with none here still gets a map.

Limits

Contiguous United States only. Letter paper at 1:24,000 or 1:48,000. PDF creation targets desktop Chromium and Edge first. This is not a navigation or safety authority: confirm current conditions with the managing forest or land office before you go.

Documentation

Source decision record

Printing instructions

Print at Actual size (100%) and turn off any Fit or Shrink option. Each sheet carries its own page ID, and inside each grey overlap band the ID of the sheet that adjoins there with an arrow pointing at it. Lap two sheets so the arrows meet, slide them until the corner crosses in the band sit on top of each other, and tape. Tape each row left to right first, then join the rows.

Names & landmarks

Named places & landmarks is a layer switch like any other, off by default, listed under the same federal group as the base map: summits, gaps, ridges, falls, springs, lakes, populated places and the rest of GNIS’s vocabulary, one point per name from USGS’s Geographic Names Information System. Turning it on asks for whatever area is on screen; panning or zooming asks again for the new area, and an answer for a rectangle you have since left is dropped rather than drawn, so the names on screen always match the area in front of you. A search that genuinely finds nothing prints “No named terrain found in this area” — a real answer, not a failure — and a search that did not finish (too many names for the area, a timeout, an error) says so distinctly and never draws a silently incomplete set; “zoom in or refine the area” is what an over-cap answer asks you to do.

Screen labels declutter automatically as you zoom: only as many names as comfortably fit are lettered, and every one still gets its marker even when its label is crowded out. A name whose label did not fit stays reachable in Names not shown on the map (crowded out) below the layer switch — tab to it, or tap it, and it takes label priority on the map, the same as tabbing to a placed marker and pressing Enter or Space opens that name’s own card (its kind, its state and county, and the note that GNIS gives one published point per name, never an elevation, and not every place the name is used).

A name on the printed USGS Topo base is not the same thing as a name this layer draws, and the base map’s own text cannot be decluttered the way this layer’s labels are: if the topo base already carries a name near a point this layer also names, the two may repeat on paper. See “Named terrain on the sheet” below for exactly how a name reaches a printed sheet.

Named terrain on the sheet

Named summits, gaps, ridges, falls, springs and other GNIS terrain names print as a small shape (one per kind, listed in the key) beside the name in physical type, sized and positioned from the sheet’s own scale — never from how far you have zoomed the screen. A name shares the same on-paper space as the road, trail and site labels already there: when a name’s text would land on top of something else, it is nudged to the next open spot near its point in a fixed, repeatable order, so the same area prints the same way every time. The point marker itself never moves — only its name can be bumped, and if no open spot is found nearby the name is left off and counted in the build record while its marker still prints, so you can see something is there even without a label crowding the sheet. Names print in the same typeface as everything else on the sheet; an accented spelling (Cañón, Étang) prints as GNIS spells it, and only a character that typeface cannot represent at all falls back to ?, the same fallback every other label on the sheet already uses.

Like the base map and MVUM above, an interrupted or over-cap fetch of GNIS names blocks the PDF rather than printing an incomplete set of names with nothing said — see “Named terrain (GNIS) must load completely before export” below.

Printing the key on its own

Print the key, under the map key on the Quiet Corners map, hands you a one- or two-page PDF of every symbol the layers you have switched on can draw, with the notices those symbols oblige. It is the same key a built set carries at its back — the same table, the same strokes — so it can be printed and read before a single map sheet is spent, and kept with the sheets afterwards. It lists what the layers can draw, not what a particular area contains; the on-page key is what narrows after Check sources. The two keys are deliberately not identical: the on-page key describes the map on your screen, so it drops the UTM grid and the sheet-overlap marks (which exist only on paper) and says of anything the current zoom is too coarse to draw that it appears when you zoom in.

Calibrating a printer

Before printing a set on a printer you have not used for these sheets, add ?calibrate=1 to the Quiet Corners map’s address. It hands you a one-page PDF instead of the map builder. Print that one sheet at Actual size (100%) with Fit and Shrink off, and it answers the two questions no test can answer from a file:

• Scale. Lay a ruler along either 10 cm bar. 9.9 cm instead of 10.0 means the printer prints 1% small, and the map’s scale bar will read the same way.
• Unprintable margin. The sheet carries nested rectangles 0.25, 0.20, 0.17 and 0.15 in from the paper edge, each labelled. The smallest labelled inset that printed complete on all four sides is the smallest inset that is safe on that printer; the sheets use 0.25 in today. Four corner marks sit on a real sheet’s frame corners, so a missing mark means the frame itself is being clipped.

Keep the sheet with the printer. It is good for every future job on that machine.

Troubleshooting

The sheets do not measure true to scale. The print dialog scaled them. Choose Actual size (100%) and turn off Fit to page, Shrink oversized pages and any borderless option. A test sheet’s scale bar is the check: measure it against a ruler before printing the whole set.

“Check sources before building.” Nothing has been asked of the map services yet. Check sources first; the page will not build a PDF from sources whose state it does not know.

Layers do not appear when I switch them on. Switch the layer on and stop moving the map: once the view settles the page asks for what is on screen and draws it. Two views ask for nothing, on purpose — zoomed out past the level the topo base appears at, and a view covering more ground than one query can honestly answer. Both say so on the page. Building the PDF always re-asks for the printed box itself, so a sheet never draws features fetched for somewhere else.

Which context surface am I looking at, and when is it from? Whichever one is chosen under Land, sky & light context — only one can be on at a time — and the map itself carries a line naming it and the time its data refers to. That time is the source’s own and never the moment it was fetched: the aurora surface shows the time it is a forecast for, radar and air quality show the time they were observed, and the night lights show their vintage (a 2016 composite, not tonight). The wildlife records are an aggregate over a span of years rather than a moment — a cell holds records from many different days — so that line says the time is unknown and the row beneath it names the year range the count covers. The steepness surface is arithmetic rather than a reading, and the national elevation model states no date for a given piece of ground, so its line says the time is unknown instead of borrowing the clock. The county ranking names no service and so states its own dashboard vintage rather than a fetch time, the same wording an inventory carries. A source that will not state its time says so on that line rather than being shown as current.

Can I turn the base map off, or see the aerial or relief on screen? Yes — under Base map in the Layers panel, choose USGS Topo, aerial imagery, shaded relief or no base map at all; the choice is for the screen only. The PDF still prints the topo base on every sheet, with aerial imagery and shaded relief available as companion sheets under Extra sheets.

“USGS Topo must load completely before export.” At least one base-map tile did not come back. The build refuses rather than printing a sheet with a blank patch. Try again — the tile service rate-limits bursts — and if it persists, reduce the area or use 1:48,000, which needs fewer tiles.

“MVUM: unavailable” or a coverage that will not reach complete. The Forest Service service did not answer, or answered partially. MVUM is published forest by forest and not every forest is in it, so a genuinely empty answer for an area outside any published forest is not an error. If you want the base map regardless, turn the MVUM layer off explicitly and build without it — the page will not quietly drop a layer you asked for.

A layer says “partial” instead of “complete.” The map services answer a large rectangle one page at a time, and say in the answer whether more is waiting. A layer reads “partial” when the service still had more than it handed over, so what the page holds is a piece of that layer, not all of it. The build refuses on a partial layer for the same reason it refuses a missing tile: a truncated set is worse than none, because on paper it looks finished. Draw a smaller box and check sources again. Recreation sites and trails used to report themselves ready in exactly this situation — the sheet printed with trails missing and nothing said so.

“Named terrain (GNIS) must load completely before export.” The named-terrain query for your area came back partial, over the record cap, or timed out. The build refuses rather than print a set of place names with unstated gaps. Try again, draw a smaller box, or switch the names layer off explicitly to build without it.

The build is slow, or the tab runs out of memory. Every tile and every sheet is rendered in your browser, so a large area at 300 dpi is real work. The page shows an estimate before you start. If it is uncomfortable, cut the area, drop to 200 dpi, or use 1:48,000.

Nothing downloads at the end. PDF creation targets desktop Chromium and Edge first. A browser that blocks large blob downloads, or a private window with storage disabled, can stop the file being handed over.

The area came back slightly different after a reload. Recipes saved before September 2026 stored only the projected sheet extent, so restoring one rebuilds the box from the sheet grid and returns a slightly larger area. Redraw the box once and it will save and restore exactly from then on.