INSPIRE / data.gov cadastral (US NationalMap): Intelligence Source Guide

The National Map is the USGS base-layer service for United States territory – elevation, hydrography, boundaries, structures, transportation and names – served through the TNM Access API without a key. It is the authoritative geographic frame you hang everything else on, and it is not a parcel register.

At a glance

Source	INSPIRE / data.gov cadastral (US NationalMap)
Category	Corporate, Ownership & Legal Records › Land & Property Registries
Homepage	https://www.usgs.gov/programs/national-geospatial-program/national-map
Machine interface	`https://apps.nationalmap.gov/tnmaccess/`
Format	`REST`
Access	Open — no account required
Disciplines	Government Intelligence
Mission domains	Maritime Security, Border Security & Migration

USGS National Map access API for boundaries, structures and geospatial base layers of US territory. — as catalogued in the platform’s own source registry.

The National Map is the United States Geological Survey's programme for producing and distributing the national topographic base data of the United States and its territories. It is not a single dataset. It is a family of themes maintained on different schedules by different USGS science centres and partners: 3D Elevation Program (3DEP) lidar and derived digital elevation models; the National Hydrography Dataset and Watershed Boundary Dataset for streams, waterbodies and drainage basins; the National Boundary Dataset for federal, state, county, municipal and federally recognised tribal boundaries; the National Structures Dataset for schools, hospitals, fire stations, prisons, post offices and similar built features; transportation networks; land cover; orthoimagery; and the Geographic Names Information System, which is the federal authority for place names. Access is through several routes that share the same underlying holdings: the TNM Access API at apps.nationalmap.gov, which is a product-discovery and download service returning JSON descriptions of downloadable files; the National Map Downloader web application; OGC-compliant map and feature services for live rendering and query; and bulk staged downloads. The catalogue entry for this source bundles The National Map with data.gov, the US federal open-data catalogue, and with INSPIRE, the European Union spatial data infrastructure directive. Those are three separate things and the guide treats them as such: The National Map is the substance, data.gov is a metadata index that points at it, and INSPIRE is the European legal framework that does the analogous job on the other side of the Atlantic through national portals rather than one service.

The analytical job here is georeferencing, not ownership. Almost every other source in an investigation gives you a place name, a coordinate pair, an address or an administrative label, and almost none of them tell you what that place actually is on the ground. The National Map does. It converts a coordinate into a terrain profile, a watershed, a distance to the nearest structure, a jurisdiction and a canonical place name that other federal datasets also use. That matters in three specific ways. First, for boundary work: when you need to know whether an incident occurred inside a county, a tribal land, a national forest or a state, the National Boundary Dataset is the reference the rest of the US federal apparatus uses, so aligning to it removes an entire class of disagreement. Second, for terrain reasoning: 3DEP lidar at one-metre resolution over much of the country lets you test whether a line of sight, a helicopter approach, a flood extent or a claimed vantage point is physically possible – which is a verification technique, not a mapping technique. Third, for name resolution: GNIS gives you the official feature name and its variants, which is how you disambiguate the fourteen places in the United States called Springfield without guessing. What it does not do is tell you who owns anything. There is no national parcel or cadastral layer in The National Map. Property ownership in the United States is recorded at county level by roughly three thousand independent recorders, and it is not federalised. Treating this source as a cadastre is the single most common error made with it.

Who publishes it, and why that matters

The USGS is a scientific bureau of the Department of the Interior with a statutory mapping mission going back to 1879, and the National Geospatial Program that runs The National Map is a long-standing federal line item rather than a project. That gives the source unusual longevity by the standards of this catalogue: the data will still be there in ten years and the licence will still be public domain. The incentive structure is scientific and infrastructural – USGS is measured on coverage, currency and partner adoption, not on traffic or revenue – which means the data is honest about its own gaps and carries real metadata, but also that it is optimised for the geospatial community rather than for investigators. Two practical consequences follow. Delivery mechanisms change on a federal IT cadence: applications get retired and replaced, service URLs migrate, and the download infrastructure has been reorganised more than once. Anything you hard-code against a specific endpoint should be treated as a maintenance liability, and the programme's own documentation page is the authoritative statement of what currently exists, not your cached notes. Second, much of the content is contributed by state, tribal and local partners under cooperative agreements, so quality and currency vary by contributing jurisdiction in ways that are visible only in the metadata. A well-funded state has current lidar and maintained structures data; a poorly funded one has neither, and the national coverage map will not shout about it.

Provenance is the first question to ask of any dataset and the one most often skipped. Who collects it, what their incentive is, whether they publish a methodology, and whether they correct the record when they get something wrong all bear directly on how much weight a finding drawn from it can carry.

What a record actually contains

The fields you will be working with, what each one means, and whether it is something you can pivot on. Read the meanings carefully — more analysis is wrecked by misreading a field than by failing to find one, and a field that looks like an observation is often an inference.

Field	Type	What it means	Pivot value
`title`	string	Human-readable name of a downloadable product, typically encoding the dataset, the geographic tile or area, and the publication date. It is a label, not a stable identifier – do not key your database on it.	The tile or area designator inside it usually maps to a named grid cell you can reuse across USGS products.
`sourceId`	string	Identifier of the product record within the USGS holdings. This is the closest thing to a stable key the discovery API gives you and it is what you store to re-fetch the same product later.	The metadata record for that product, and through it the originating project and contributor.
`datasets`	array	Which National Map theme or themes the product belongs to – elevation products, hydrography, boundaries, structures, imagery and so on. This is the field you filter on when you want one theme and not the whole catalogue.	Sibling products in the same theme covering adjacent areas or earlier dates.
`format`	enum	Physical file format of the download: GeoTIFF, IMG, LAZ or LAS for point clouds, Shapefile, FileGDB, GeoPackage, GeoJSON and others depending on theme. Determines what tooling you need before the data is usable.	none
`downloadURL`	string	Direct link to the product file. These are large – a single lidar tile is routinely hundreds of megabytes – and they are the actual payload, not a landing page.	none
`metaUrl`	string	Link to the formal metadata record describing lineage, accuracy, collection date, contributing organisation and processing history. This is where the truth about a product's reliability lives.	The contributing agency or contractor, the acquisition project, and the accuracy statement you must quote in any finding.
`publicationDate`	timestamp	When USGS published the product. It is not when the underlying imagery or lidar was flown, and the gap between the two is routinely one to three years.	none
`dateCreated / lastUpdated`	timestamp	Record-level timestamps for creation and most recent modification of the catalogue entry. They track the metadata record, not necessarily a resurvey of the ground.	none
`boundingBox / extent`	object	Geographic envelope of the product in decimal degrees, and the named extent class such as a 1×1 degree block, a 7.5-minute quadrangle or a state. Products are tiled, so an area of interest spanning a tile edge needs several downloads.	Adjacent tiles, and the standard USGS quadrangle naming used across a century of paper and digital maps.
`sizeInBytes`	int	File size. Worth reading before you request a hundred lidar tiles over a slow link, and worth using to sanity-check that a download completed.	none
`GNIS feature_id`	string	In the names theme, the permanent numeric identifier of a named geographic feature. It is the federal standard identifier for a place name and it survives name changes, which variant name strings do not.	Other federal datasets that carry GNIS identifiers, and historic map sheets naming the same feature.
`feature class / FCode`	enum	Typed classification of a feature – in hydrography, whether a line is a perennial stream, an intermittent stream, a canal or a pipeline; in structures, whether a point is a school, a hospital or a correctional facility. The class carries most of the analytical meaning.	Filtering to a facility category for proximity and vulnerability analysis.
`HUC code`	string	Hydrologic Unit Code from the Watershed Boundary Dataset, a nested numeric identifier for drainage basins from region down to subwatershed. It is the standard geography for anything involving water.	EPA, USDA and state water datasets, almost all of which are keyed on HUC.
`vertical accuracy statement`	string	In elevation metadata, the tested or estimated vertical accuracy and the quality level of the lidar acquisition. Without it an elevation-derived claim has no error bars and should not be asserted in a report.	The acquisition project report, which usually states flight dates, sensor and ground control.

Coverage — and what is not in it

Geographic coverage is the United States, its territories and possessions – the fifty states, the District of Columbia, Puerto Rico, the US Virgin Islands, Guam, American Samoa, the Northern Mariana Islands and the freely associated states in some themes. It stops at the border. Canada and Mexico appear only as edge-matched context, and there is no international content. Within that footprint, coverage varies sharply by theme. Boundaries, hydrography and geographic names are national and complete. Elevation under 3DEP has been driven toward complete national lidar coverage over more than a decade, but individual states reached full coverage at very different times, and Alaska is largely interferometric synthetic aperture radar rather than lidar because of terrain and weather – a materially different product with different accuracy. Structures coverage is uneven and depends on partner contributions; some counties are richly populated and others carry only the federal facilities. Orthoimagery is a patchwork of acquisitions with different dates, resolutions and leaf conditions. Update rhythm is equally uneven: hydrography and names are edited continuously as corrections arrive, boundaries change when jurisdictions change, elevation updates when a new acquisition is flown and processed, and imagery updates on state or federal acquisition cycles measured in years. The correct mental model is a mosaic of independently maintained layers, not a single map with a publication date.

Known blind spots

Absence of evidence here is not evidence of absence. These are the conditions under which INSPIRE / data.gov cadastral (US NationalMap) will not show you something that is nevertheless real:

There is no parcel, deed, title or ownership layer. If your question is who owns this land, The National Map cannot answer it and no amount of digging will change that – ownership records sit with county recorders and assessors, and federal surface management status sits with the Bureau of Land Management, not USGS.
Coverage ends at the international border, so any cross-border analysis – a smuggling corridor, a river shared with Mexico, a maritime approach – is half-blind and must be completed from the other country's national mapping agency or from a global dataset with consistent treatment on both sides.
Structures data is contributed rather than surveyed, so absence of a building in the structures theme is not evidence that no building exists. Whole categories of facility are missing in jurisdictions that never contributed, and privately held critical infrastructure is systematically underrepresented.
Imagery and elevation are historical the moment they are published. A lidar surface flown four years ago will not show a structure built three years ago, and an analyst who reads absence as demolition or non-existence has made a dating error, not a spatial one.
Sensitive federal facilities are handled inconsistently. Some are generalised, some are omitted, and some appear with a bland classification. You cannot infer the absence of a military or intelligence installation from the absence of a point in the structures theme.
Alaska, the Pacific territories and remote tribal lands are consistently the least current and least accurate parts of every theme, which is exactly where an analyst is most likely to need help and least able to check the result against local knowledge.
The names theme records official and variant names but is not a gazetteer of vernacular, indigenous-language or historical usage in any complete sense. Names removed or changed by policy decisions may leave the current record without the historical string an old document uses.
Nothing in the source is timestamped to an event. It describes durable geography. If your question involves what happened at a place on a date, this source frames the question and cannot answer it.
Tiling and edge effects are real analytical blindspots: a feature that crosses a tile boundary can appear twice, appear clipped, or be inconsistently attributed on either side, and analysts who work a single tile never see it.

Write the blind spot into the product. A statement that something “was not observed in INSPIRE / data.gov cadastral (US NationalMap)” is defensible; a statement that it “did not happen” is not, and the difference is what survives cross-examination.

Access, licensing and what you may do with it

Access model: Open — no account required

Nothing here requires registration, a key or a licence agreement. The TNM Access API accepts unauthenticated HTTP requests and returns JSON describing matching products, including direct download URLs. The National Map Downloader is the same holdings behind a map interface and is the fastest way to understand what exists over an area before you automate anything. OGC-conformant web map and feature services expose the vector themes for live query and rendering, which is the right route when you need to ask a spatial question rather than acquire files. For anything at national scale, use the staged bulk downloads rather than iterating the API – pulling a state's worth of lidar tile by tile is antisocial and slow. In practice the working pattern is: explore in the Downloader, script discovery through TNM Access, fetch the products you actually need, and keep the metadata record alongside every file you keep. The last step is the one people skip and the one that determines whether a finding is defensible six months later.

Licence

Data produced by the USGS as a work of the United States Government is in the public domain in the United States and carries no copyright. In practice this is as permissive as it gets: you may redistribute, modify, incorporate into commercial products and publish derivatives without permission or fee. Two qualifications matter. Some products incorporate contributions from state, tribal, local or commercial partners, and a minority of those carry their own terms or attribution expectations recorded in the product metadata – read the metadata record before redistributing a specific tile rather than assuming blanket public domain. And public domain status in the United States does not automatically translate to every foreign jurisdiction's treatment of foreign government works, which occasionally matters for publication in Europe. USGS asks for citation as a courtesy and because it is good practice; cite the specific product and its publication date, not the programme, because a reader cannot reproduce your result from a programme name.

Rate limits and fair use

There is no published hard quota, which is not the same as no limit. The discovery API is a small service in front of a very large file store, and the file store is where the cost is. Treat the etiquette as: sequential or lightly parallel requests, a pause between them, a descriptive user agent identifying you, and no retry storms on failure. Discovery calls are cheap and you can afford to be thorough with them. Downloads are not – a single lidar tile can exceed a gigabyte, and a county-scale point cloud pull is a multi-terabyte operation that belongs on a bulk route, not on the API. Cache aggressively: this data changes on a scale of months to years, so re-fetching the same tile weekly is pure waste. If you need continuous national coverage in a production system, mirror what you use once and refresh on a schedule tied to publication dates rather than polling.

Licensing changes, and it changes without warning. A dataset that was free for research this year may not be free for commercial or evidential use next year. Confirm the current terms before you build a dependency on it, and record the terms you relied on alongside the data — the licence in force at the time of collection is part of the provenance.

Collecting it

How INSPIRE / data.gov cadastral (US NationalMap) is actually pulled, in the order you would set it up. Prefer the bulk or export interface over per-item lookups wherever one exists: it is kinder to the publisher, faster for you, and gives a reproducible snapshot rather than a series of point-in-time answers you cannot reconstruct later.

Method	Format	Cadence	Notes
TNM Access product discovery	JSON	Query on demand; re-run monthly for a watched area	Programmatic search for downloadable products by dataset theme, bounding box, format and date. Returns metadata plus direct download URLs. This is the route to automate, and the results should be diffed rather than re-downloaded.
OGC map and feature services	XML	Live	WMS, WFS and related services for the vector themes. The right choice when you want to ask a spatial question – what boundary contains this point, what structures lie within two kilometres – without acquiring and hosting the data yourself.
Staged bulk download	bulk	Per publication cycle	Pre-packaged national and state extracts of the vector themes and derived elevation products. Use this for anything above county scale. It is the difference between an afternoon and a fortnight.
The National Map Downloader	HTML	Ad hoc	Interactive discovery over a map. Not an automation route, but the correct first step for any new area of interest because it shows you coverage gaps that an API response will not make obvious.
GNIS names extract	CSV	Periodic	Downloadable gazetteer of official geographic names with feature identifiers, classes and coordinates. Small enough to load whole and the fastest way to build a name-resolution table for US place names.

Ingesting it into the platform

Every step below is idempotent and cursor-based: interrupt one and it resumes from where it stopped rather than duplicating rows or losing progress. Collection is recorded per source, so a feed that quietly stops publishing shows up as a stale timestamp instead of silently thinning your coverage.

Register the themes you actually use as separate sources — In sources.php, treat elevation, hydrography, boundaries, structures and names as distinct registrations with their own last-collected state. They update on different cadences and folding them into one entry destroys your ability to reason about currency.
Collect discovery metadata before payloads — collect.php pulls the product listing for each watched area first and stores the full metadata record. This is what lets you decide whether a new product is worth downloading rather than downloading to find out.
Normalise geometry and identifiers on import — import.php projects everything to a single working coordinate reference system, retains the native one, and carries GNIS feature identifiers and HUC codes through unchanged so they remain joinable to external datasets.
Attach the accuracy statement to every derived value — ingest.php stores the vertical or horizontal accuracy from the metadata record alongside the data itself, so any elevation or distance the platform later computes can be reported with its error term rather than as a bare number.
Build the reverse-geocoding frame — Boundaries, names and structures are indexed so that any coordinate arriving from any other source can be resolved to a jurisdiction, a watershed, a named feature and a nearest-facility list. This is the join that makes the source pay for itself.
Wire it into entity dashboards — country.php and theater.php consume the boundary and terrain layers as the geographic frame for US-territory analysis, and the resolved jurisdiction becomes a facet on any record with a coordinate.
Refresh on publication, not on a timer — cron.php compares publication dates in the discovery response against what is already held and only fetches changed products. Polling a source that changes annually on a daily schedule is a self-inflicted problem.
Preserve superseded products — Old elevation and imagery products are not obsolete, they are a time series. The pipeline retains prior versions with their dates so that change detection between acquisitions remains possible.

Registered sources and their last-collected state are listed in sources.php, and the scheduled chain that keeps them current is in automation.php.

How it is wrong, and how to tell

Every dataset is wrong in characteristic ways. Knowing which ways is the difference between using a source and being used by one, and it is the part of source evaluation most often skipped because it is the part that takes work.

This is among the most reliable sources in the catalogue, and the reason is process rather than reputation. Products carry formal metadata stating lineage, acquisition date, processing steps, contributing organisation and tested accuracy, and the 3DEP acquisitions are specified against a published lidar base specification with quality levels that define point density and vertical accuracy. That means you can quantify how wrong a given product is allowed to be, which is a property almost nothing else in this catalogue has. Where quality degrades, it degrades legibly: a structures layer with sparse coverage in a county is visibly sparse, and an old imagery acquisition states its own date. The real quality risk is not error in the data but error in the analyst's reading of it – using a four-year-old surface as current, treating a contributed layer as a survey, or asserting an elevation difference smaller than the stated vertical accuracy. Judge a specific product by its metadata record, never by the programme's overall reputation, and be especially careful with derived products where the derivation may have been done at a coarser resolution than the source.

Characteristic false positives

Currency mistaken for authority: the product is authoritative for the date it was collected, and analysts routinely read a well-made map as a current one. A structure absent from a 2019 lidar surface may have been built in 2021.
Boundary vintage mismatch: municipal annexations, tribal land determinations and special district changes propagate into the boundary dataset with a lag, so a point can be correctly plotted and assigned to the wrong jurisdiction because the boundary is a year behind the legal change.
Name collision in the gazetteer: many US place names repeat within and across states, and matching on name string alone silently attaches records to the wrong Springfield, Fairview or Riverside. The feature identifier exists precisely to prevent this and is routinely discarded.
Elevation artefacts read as features: lidar-derived surfaces contain vegetation returns, water surface anomalies, building edges and processing artefacts that look like real micro-topography. Bare-earth and first-return products answer different questions and are frequently confused.
Structure classification drift: a point classed as a school may be a closed school, a school administrative office or a building that was a school when the contribution was made. The class describes the contributor's understanding at contribution time.
Hydrography as hydrology: the National Hydrography Dataset shows where channels are, not where water currently is. Intermittent streams appear as lines year-round and analysts infer permanent water from cartography.
Tile-edge duplication: features spanning tile boundaries can be counted twice in a naive aggregation, inflating counts of roads, streams or structures in exactly the areas where several tiles meet.
Coordinate reference confusion: products are delivered in several horizontal and vertical datums, and mixing NAVD 88 with an ellipsoidal height or an older datum introduces metre-scale errors that look plausible and are not flagged.

None of these make the source unusable. They make it a source that requires corroboration before an assertion built on it goes into a product, which is true of every source and admitted by few.

Ageing

Ageing is per theme and per product, not per source. Geographic names and hydrography age slowly and gracefully – a stream is where it was, and a stale record looks almost exactly like a fresh one, which is the danger. Boundaries age in steps: they are correct until a jurisdiction changes and then wrong until the next edit cycle, with no visible signal in between. Structures age badly and invisibly, because the layer never claims completeness and a missing new building is indistinguishable from a building the contributor never recorded. Elevation and imagery age on the calendar and state their own age honestly in metadata, which makes them the easiest to handle correctly: a 2018 acquisition is a 2018 acquisition and should be cited as such. The practical rule is to carry the acquisition date, not the publication date, into every finding, and to state it in the finding itself. A stale record in this source does not look broken. It looks authoritative and describes a landscape that has changed.

What this source feeds

A source is only worth what it lets you conclude. These are the disciplines that collect through it, the mission domains it serves and the data points it yields — every one is a tag, so you can follow any thread from here into the rest of the library.

Collected by these intelligence disciplines

Government Intelligence

Serves these mission domains

Yields these data points

Real Property / Parcel

How each sector uses INSPIRE / data.gov cadastral (US NationalMap)

The same dataset is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The records are shared — the constraints, thresholds and outputs are not.

🎖 Military and defence

This is terrain and infrastructure framing for homeland, National Guard and installation contexts, and for exercise or domestic support planning where commercial terrain products are not licensed for the use. The 3DEP surfaces support line-of-sight, defilade, helicopter landing zone and flood-inundation reasoning at a resolution that supports tactical questions, and the boundary layers resolve the jurisdictional questions that dominate domestic operations – which sheriff, which state, which tribal authority, which federal land manager. Two cautions apply with force: the data is public and so is your reliance on it, and sensitive installations are handled inconsistently enough that absence proves nothing. Use it as the unclassified geographic frame that a mixed-clearance team can all work from, and expect it to be superseded by controlled sources for anything requiring current imagery.

🕵 National intelligence

The value for national intelligence work is as a reference frame rather than as reporting. When a collection product, a partner submission or an open-source claim references a US location, this is the source that turns the reference into a defensible geographic assertion with a stated accuracy. It also supports negative analysis: the terrain either permits a claimed observation or it does not, and lidar-derived line-of-sight is a cheap way to test a human-source claim about what could be seen from where. For GOVINT more broadly, the boundary and names layers are the join key between federal datasets, and adopting them early prevents the slow accumulation of place-name mismatches that eventually makes a corpus unqueryable. It is domestic-only, so it belongs in the frame, never in the substance, of any foreign-focused product.

👮 Law enforcement

Two operational uses dominate. The first is jurisdiction: establishing which agency owns an incident location, whether an offence occurred on federal, tribal, state or municipal land, and therefore which court and which statute apply – a determination that decides cases and is made from boundary data. The second is scene and search work: terrain and hydrography drive search-and-rescue planning, body-recovery probability areas, drainage reasoning for evidence movement, and route analysis around a location. Structures and names support warrant drafting where an address must be tied to a described place. What it will not do is tell you who owns the land, who lives at an address, or who was present – those come from county records, commercial data and process, and the geographic layer only frames them. Treat every measurement you take from it as carrying the product's stated accuracy, because opposing counsel will ask.

🔍 Private investigation and corporate security

For private investigation and corporate security this is free, unrestricted and defensible – three properties rarely found together. It answers whether a claimed property location is where the client says, what the terrain around a site actually looks like, whether a fence line or access road is plausible, and which county's recorder you need to visit next. In due diligence on a physical asset, the elevation and hydrography layers let you check flood exposure and access independently of the seller's representations. The discipline to keep is separating what you established from the map from what you inferred: the map shows a structure of a given footprint at given coordinates on a given date, and everything about who uses it is inference until sourced elsewhere. Because the data is public domain, findings built on it can be shown to a client without licence complications.

📰 Journalism and OSINT media

Investigative journalism uses this mainly for verification and for graphics. Verification: a photograph or video claiming a location can be tested against terrain, waterways, structures and named features, and lidar-derived profiles settle arguments about what is visible from where more decisively than satellite imagery does. Graphics: the data is public domain, so a newsroom can build maps for publication without licensing, attribution negotiations or take-down exposure. The reporting caution is the same one that catches everyone – the imagery or elevation you are using has a date, that date belongs in the caption, and a story that says a facility does not exist because it is absent from a federal layer will be corrected. Where the story is about federal land management or a dispute over boundaries, get the boundary vintage explicitly and say which edition you used.

🌍 NGO, humanitarian and human rights

Humanitarian and environmental organisations use the elevation, hydrography and watershed layers for flood, wildfire and drought exposure analysis, and the structures and boundary layers to identify which communities and facilities sit inside an exposure zone. For work on vulnerable populations in the United States, the combination of watershed boundaries, terrain and facility locations supports the kind of exposure mapping that grant applications and advocacy require, at no cost and with no licence encumbrance on published outputs. The limitation to hold on to is that the structures layer under-represents exactly the informal, marginal and rapidly changing built environment that this work cares about, so it should frame a field assessment rather than substitute for one. Tribal boundary representations should be checked with the relevant nation rather than asserted from the federal layer alone.

🎓 University and research

For research this is a well-documented, citable, reproducible and free base layer with formal metadata and stated accuracy – which is why it appears in the methods sections of a very large body of published work. It supports reproducibility better than most alternatives because products carry identifiers and publication dates you can cite precisely, and superseded versions remain retrievable. The methodological warnings worth passing to students are the ones this guide keeps repeating: publication date is not acquisition date, contributed layers are not surveys, derived products inherit the resolution of their inputs, and any elevation difference smaller than the stated vertical accuracy is noise. For comparative international work, note that the analogous European infrastructure under INSPIRE is a legal harmonisation framework over national portals rather than a single service, so cross-Atlantic comparisons need care about what is actually equivalent.

Playbook: working INSPIRE / data.gov cadastral (US NationalMap) end to end

A repeatable sequence from first pull to finished product. Each phase states what you are trying to establish, not merely what to click — the objective is a defensible chain of reasoning, not a completed checklist.

Phase 1 — Decide whether you need geography or ownership

These are different investigations with different sources. If the question is who holds title, who pays the tax, or who is on the deed, this source cannot help and you should be at the county recorder or a commercial aggregation of county records. Come here when the question is where something is, what is around it, what the ground looks like, or which jurisdiction governs it. Getting this wrong costs a day.

Phase 2 — Establish the area of interest and its coverage before collecting

Open the Downloader over your area and look at what exists per theme and with what dates before writing any code. You are looking for the specific combination of themes and vintages available here, which is rarely the same as the national picture. Write down the acquisition dates you find, because they will constrain every later claim and you will not remember them.

Phase 3 — Pull the boundary frame first

Acquire the federal, state, county, municipal and tribal boundaries covering the area and resolve your incident or entity locations against them immediately. Jurisdiction determines who has authority, which records exist, and often whether an act is an offence at all. Doing this first prevents the common failure of an investigation that develops for a week against the wrong county.

Phase 4 — Resolve place names to identifiers

Take every place name in your material and resolve it to a GNIS feature identifier with coordinates, recording variants and near-matches rather than picking one. Where a name resolves to several features, keep all candidates open and let later evidence eliminate them. Name-string matching without identifiers is the most reliable way to build a confidently wrong corpus.

Phase 5 — Acquire terrain at the resolution the question needs

Match the elevation product to the claim you are testing. A watershed-scale question is answered by a ten-metre model; a line-of-sight or structure-height question needs lidar-derived one-metre data and needs you to know whether you are on a bare-earth or first-return surface. Downloading the highest resolution available by reflex wastes storage and time, and downloading the coarsest produces confident nonsense.

Phase 6 — Test physical claims against terrain

This is the highest-value analytical move the source supports. Compute whether the vantage point in a photograph can see what the photograph shows, whether a described route is passable, whether a claimed flood extent is consistent with the surface, whether a structure's shadow matches its modelled height. Record the accuracy statement with the result, because a line-of-sight conclusion at the edge of the error budget is not a conclusion.

Phase 7 — Characterise the built environment around the location

Pull structures within a defined radius and classify them – schools, hospitals, correctional facilities, emergency services, government buildings. This drives proximity reasoning for risk, for notification obligations and for understanding who would have observed an event. Treat the result as a floor on what exists, never a complete inventory, and say so in the finding.

Phase 8 — Bring in hydrography and watersheds where water is relevant

Drainage explains movement of material, contamination pathways, seasonal access and a great deal of evidence transport. Resolve the location to its hydrologic unit code and you gain access to the whole family of federal water and agricultural datasets that key on the same code. Remember that the dataset shows channels, not current water.

Phase 9 — Build the change-detection stack

Where several imagery or elevation acquisitions exist over the area, order them by acquisition date and compare. Construction, excavation, demolition, road building and vegetation change all appear, and the dated pair gives you a bounded window rather than a guess. This is the only way this source answers a temporal question, and it answers it well when the acquisitions happen to bracket your event.

Phase 10 — Cross the border deliberately or not at all

If your area touches Canada or Mexico, stop and decide how you will handle the other side. Mixing this source with a foreign national mapping product introduces datum, classification and currency discontinuities right at the boundary, which is exactly where your analysis is most sensitive. Either use a consistent global dataset across the whole area or document the seam explicitly.

Phase 11 — Carry accuracy and date into the product

Every measurement in the finished report should be accompanied by the acquisition date and stated accuracy of the product it came from, and every map should carry a source and edition note. This is not bureaucratic ornament: it is what allows a reviewer to distinguish a two-metre difference that is real from one that is inside the error term, and it is what protects the finding when the geography changes.

Phase 12 — Preserve the exact products you used

Archive the product files, their metadata records and their identifiers, not just your derived outputs. Endpoints migrate, products get superseded, and an analysis you cannot re-run against the same inputs is an assertion rather than a result. This costs storage and saves cases.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

What to pair it with

No single source carries a finding. These are the datasets that corroborate, extend or contradict this one — and a source that contradicts is worth more than one that agrees, because it is the only thing that will tell you when you are wrong.

Source	Relationship	What it adds
PLSS / BLM Cadastral (US)	extends	Adds the Public Land Survey System framework and federal surface management status, which is the closest thing to a national land-status layer and the natural next step when the National Map's silence on ownership becomes the obstacle.
County recorder and assessor records	prerequisite	The actual source of US property ownership, deeds, mortgages and assessed values. Held by roughly three thousand independent county offices with no federal aggregation, and unavoidable for any ownership question.
US Census Bureau TIGER/Line	corroborates	The Census Bureau's own geographic framework, with address ranges, statistical geographies and its own boundary representations. Where TIGER and the National Boundary Dataset disagree, the disagreement itself is informative about vintage.
data.gov catalogue	extends	The federal open-data index. It does not hold the data but it is the fastest way to discover which other agency dataset covers a theme The National Map does not, including state and local contributions.
INSPIRE Geoportal	corroborates	The European Union's discovery layer over member state spatial data infrastructures, and the correct analogue when the same analysis has to be done in Europe. It is a metadata index over national services, not a single dataset.
Federal Register API	extends	Land withdrawals, boundary changes, national monument designations and federal land management decisions are enacted through published notices and rules. When a boundary changes, the legal instrument appears here before the map does.
USASpending.gov	extends	Federal construction, remediation and infrastructure awards carry places of performance that resolve against this geographic frame, turning a spending record into a physical site with terrain and neighbours.
USGS ScienceBase	corroborates	The wider USGS data catalogue, which holds the scientific datasets, project reports and acquisition documentation that sit behind National Map products and explain how a given product was made.

Legal, ethical and operational constraints

Use of this source is legally straightforward, which is unusual enough to be worth stating plainly: the data is a work of the United States Government, it is in the public domain domestically, and there is no access agreement to breach. The constraints that do apply are downstream. Deriving precise information about the vicinity of sensitive facilities and publishing it can raise issues under other legal regimes even when the underlying data is free, and analysts working around military, nuclear, correctional or critical energy infrastructure should think about the output, not the input. Combining the geographic frame with personal data – resolving an individual's residence, mapping their movements, or building a pattern-of-life around a home address – moves the work into privacy and data protection territory in most jurisdictions regardless of the base layer's licence, and the proportionality test applies to the combination even though it does not apply to the map. For court use, be prepared to state the product, its acquisition date and its tested accuracy; a measurement offered without those is vulnerable. Where the work is European, note that the equivalent INSPIRE data is subject to member state licensing that is frequently not public domain, so a workflow built on US assumptions will not transplant.

Operational security

Requests to USGS infrastructure are ordinary HTTP requests to a federal government service and are logged like any other. What they reveal is your area of interest with considerable precision: a bounding box in a discovery query is a statement about where you are looking, and a sequence of them over days sketches the shape of an investigation. The download side is worse in one respect, because a request for a specific lidar tile is a much narrower disclosure than a browse of a state. For most work this is an acceptable exposure – the traffic is indistinguishable from the very large volume of academic, engineering and commercial use the service receives – but for sensitive work it is not nothing. Fetch a wider area than you need so the query is not a pointer, use bulk or mirrored copies where the pattern of access matters, and separate collection infrastructure from attributable networks in the usual way. There is no account, so there is no identity beyond the network path, which is both the mitigation and the limit of it.

Two rules that hold regardless of jurisdiction. Collection that is lawful is not automatically proportionate, and a dataset assembled for one purpose does not carry consent for another. Where the records concern identifiable people, the question is not only whether you may hold the data but whether holding it serves the purpose you are accountable for.

Is it earning its place?

Sources accumulate. Feeds get added during an incident and are never reviewed again, and a decade later the pipeline is carrying dead weight that nobody dares remove. These are the measures that show whether INSPIRE / data.gov cadastral (US NationalMap) is contributing anything, and they are worth baselining now so the answer is available later.

Proportion of locations in your working set that resolve cleanly to a jurisdiction, a named feature and a watershed on first pass, which measures whether the geographic frame is actually installed or merely available.
Median age of the elevation and imagery products you are relying on, tracked as a distribution rather than an average, because a single stale tile over the critical area matters more than a good national mean.
Number of findings in which a terrain or line-of-sight test changed the analytical conclusion rather than confirming it – a source that only ever confirms is not being used at its edge.
Rate of place-name ambiguity caught by identifier resolution versus ambiguity discovered later by a reviewer, which is a direct measure of whether the name-resolution step is being skipped.
Count of jurisdiction determinations subsequently corrected, which surfaces boundary-vintage problems before a case relies on one.
Storage and bandwidth consumed per useful finding, because uncontrolled lidar acquisition is the classic way this source quietly becomes expensive.
Share of published outputs that carry acquisition date and accuracy statements, tracked as a compliance measure because it is the single practice that determines whether a finding survives challenge.

Beware of volume. Indicator counts rise easily and say almost nothing. Unique contribution — findings this source produced that no other source in your stack would have — is the measure that matters, and it is usually far lower than anyone expects.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

Publication date and acquisition date are different fields and the second is the one that matters. A product published last year from imagery flown four years ago is a four-year-old observation, and every finding derived from it inherits that age.
Never match place names as strings. Resolve to the feature identifier, keep the alternates, and record which candidate you eliminated and why – because a reviewer will ask why you chose one Fairview over another.
Know whether your elevation product is bare earth or first return before you compute anything. The difference is the vegetation and building canopy, which is metres, and it silently reverses line-of-sight conclusions.
Absence in the structures theme means the contributor did not record it. It never means the building is not there. Write the finding as what is present, not as what is missing.
Check the datum. Horizontal and vertical reference systems vary across products and across the other datasets you will join to, and a datum mismatch produces errors that are large enough to matter and small enough to look plausible.
Treat a boundary as legally current only after you have checked whether the jurisdiction changed. Annexations and tribal land determinations are exactly the situations where the map lags the law and where the answer decides authority.
Use the bulk routes for anything above a county. Tile-by-tile acquisition of a state is slow, fragile, and rude to a shared federal service that has a better route available.
When your area of interest touches the border, decide in advance how you will handle the other side, and put the seam in the product. An analysis that quietly stops at the forty-ninth parallel misleads by omission.
Archive the products, not just the answers. A conclusion you cannot reproduce because the endpoint changed is a conclusion you cannot defend, and this source's delivery mechanisms have changed more than once.

Questions analysts actually ask

Can I get parcel boundaries or property ownership from The National Map?

No. There is no national cadastral or parcel layer in the United States within this source. Parcel geometry and ownership are maintained by individual counties, with wildly varying availability and format, and the federal government does not aggregate them into The National Map. The nearest federal products are the BLM's Public Land Survey System framework and surface management agency layers, which describe survey grid and federal land status rather than private ownership.

Why does the catalogue entry mention INSPIRE if this is a US source?

The catalogue groups analogous national spatial data infrastructures under one heading. INSPIRE is a European Union directive requiring member states to publish harmonised spatial data through their own national portals, discoverable through the INSPIRE Geoportal. It is a legal harmonisation framework, not a dataset, and it is not operated by USGS. If your area of interest is in Europe you should be working through the relevant member state's portal, and you should expect licensing that is often less permissive than US public domain.

How current is the elevation data over a given area?

It varies by acquisition project, not by state or by the programme. The metadata record for each product states the acquisition period and the tested vertical accuracy, and that record is the only reliable answer. In practice much of the contiguous United States has lidar acquired within the last decade, Alaska is largely radar-derived with different characteristics, and some areas have several acquisitions that can be differenced for change detection.

Is the API stable enough to build a production pipeline on?

The data is stable; the delivery mechanisms are less so. USGS has reorganised its download and discovery infrastructure more than once, and applications have been retired and replaced. Build with the endpoint isolated behind one adapter, check the programme documentation rather than your notes when something breaks, and mirror the products you depend on so that an endpoint change is an inconvenience rather than an outage.

Can I rely on the structures layer for critical infrastructure analysis?

Only as a starting point. It is contributed rather than surveyed, coverage varies by jurisdiction, private infrastructure is systematically under-represented, and sensitive federal facilities are handled inconsistently. It is useful for establishing what is known to be present near a location and for building proximity context, and it is not an inventory. Any conclusion that depends on completeness needs another source.

What licence applies if I publish a map built from this data?

USGS-produced content is public domain in the United States and can be published, modified and used commercially without permission. Check the metadata for products incorporating partner contributions, a minority of which carry their own terms. Cite the specific product and its date – not for legal reasons but because a reader cannot evaluate or reproduce your map without knowing which edition you used.

How do I handle an incident location on tribal land?

Resolve it against the federal boundary layer to get an initial determination, then verify with the tribal nation and the relevant federal and state authorities before relying on it. Jurisdictional questions on tribal lands are legally intricate, depend on the status of the land and the parties involved as well as the geography, and have been reshaped by litigation. The map tells you where the line is drawn in the federal dataset; it does not tell you which sovereign has authority over a particular act.

What is the fastest way to check whether a photograph was taken where someone claims?

Resolve the claimed location, pull a high-resolution elevation product and the structures and hydrography layers around it, and test the geometry: what should be visible on the horizon, where the terrain rises, where water and named features sit relative to the camera. Terrain does not change quickly, which makes it a stronger verification substrate than imagery. State the product and accuracy in the conclusion, and treat a marginal result as unresolved rather than confirmed.

Should I use the OGC services or download the files?

Use the services when you have a bounded spatial question and do not want to host data – which jurisdiction contains this point, what structures are within a radius. Download files when you need repeated analysis, offline work, reproducibility or anything at volume. The services are convenient and rate-sensitive; the files are large and permanent. Most serious investigations end up doing both.

Standards, formats and interoperability

What this source speaks natively, and what it has to be translated into before a partner can consume it. Work that arrives in a recognised format is easier to defend, easier to hand over and easier to automate against:

OGC web service standards – WMS, WFS and related interfaces – which is how the vector themes are exposed for live query and how they interoperate with standard GIS tooling.
The USGS Lidar Base Specification, which defines the quality levels, point densities and accuracy classes that 3DEP acquisitions are procured against and that appear in product metadata.
Federal Geographic Data Committee metadata standards, which govern the lineage, accuracy and contact information carried in every product's metadata record.
GNIS feature identifiers, the federal standard identifier for named geographic features, used as a join key across many US federal datasets.
Hydrologic Unit Codes from the Watershed Boundary Dataset, the standard nested geography for water-related datasets across USGS, EPA and USDA.
Standard geospatial file formats – GeoTIFF, LAS and LAZ for point clouds, Shapefile, File Geodatabase and GeoPackage – which determine what tooling is required downstream.
North American horizontal and vertical datums, principally NAD 83 and NAVD 88, which must be reconciled against whatever reference system your other sources use.

References

Primary documentation and authoritative references for this source. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

The National Map — US Geological Survey, National Geospatial Program. The programme page and the authoritative statement of which themes exist, how they are maintained and which access routes are current. Check here first when an endpoint stops working.
TNM Access API — US Geological Survey. The product discovery and download service, with the current parameter documentation. This is the interface to automate against and the place to confirm field names before writing a parser.
The National Map Downloader — US Geological Survey. Interactive discovery over a map interface. The fastest honest answer to what exists over my area of interest and with what dates, and the correct first step before any automation.
3D Elevation Program — US Geological Survey. The elevation programme, including the quality levels and accuracy specifications that govern lidar acquisitions. Read this before asserting anything derived from a terrain surface.
National Hydrography Dataset — US Geological Survey. The surface water dataset and the watershed boundary framework, including the hydrologic unit coding that joins to most federal water and agriculture data.
US Board on Geographic Names — US Geological Survey. The authority for official US geographic names and the home of the Geographic Names Information System. The reference for name disambiguation and for understanding how and why official names change.
USGS ScienceBase — US Geological Survey. The wider USGS data catalogue holding project documentation, acquisition reports and scientific datasets behind National Map products. Where you go when a metadata record raises a question it cannot answer.
Data.gov catalogue — US General Services Administration. The federal open data index. Use it to find the state, local or other-agency dataset that covers what The National Map does not – which for property, permits and local infrastructure is most of it.
Federal Geographic Data Committee — FGDC. The coordinating body for US federal geospatial data and the source of the metadata and content standards that make products from different agencies comparable.
INSPIRE Geoportal — European Commission. The European discovery layer over member state spatial data infrastructures. The correct starting point when the same analysis has to be performed in Europe, and a useful illustration of how differently the two systems are built.
Directive 2007/2/EC (INSPIRE) — EUR-Lex, European Union. The INSPIRE directive itself, which defines the themes, metadata and service obligations placed on member states. Worth reading if you need to know what a European national portal is legally required to publish.
Open Geospatial Consortium — OGC. The standards body behind the web service interfaces used by both The National Map and INSPIRE-compliant national services, and therefore the reason the two can be consumed by the same tooling.

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this source: it registers each National Map theme as a separately versioned source, resolves every incoming coordinate to a jurisdiction, named feature and watershed, and carries the acquisition date and accuracy statement of each product through to the finished report.. Browse the full source catalogue, or follow any tag above into the rest of the library.