Telecom Tower REITs · Data.gov / US GSA
Data.gov Antenna Tower Datasets Catalog
Datadory delivers data gov antenna tower datasets catalog data covering the eight federal, state, county and city wireless-facility inventories one narrow query surfaces from roughly 552,000 cataloged records - San Francisco commercial wireless facility sets, Los Angeles small-cell nodes, Connecticut Siting Council towers and antennas, Loudoun County telecom towers - each arriving as a nine-field row carrying the publishing organization, its government-level badge, the underlying modification date, offered formats and the catalog's own verification stamp. Delivered through API, files, or your warehouse.
API, files, or your warehouse. Daily, weekly, or hourly.
What is the Data.gov Antenna Tower Datasets Catalog?
It is one query against the United States government's catalog of catalogs, read as a table. The phrase antenna tower returns eight matching datasets from roughly 552,271 indexed as of the August 2026 research pass - and because the catalog harvests agency and municipal metadata feeds directly, the eight skew local rather than federal: San Francisco's existing and proposed commercial wireless telecommunication services facility sets, Los Angeles small-cell nodes on streetlight poles, the Connecticut Siting Council's telecommunications towers and antennas, Loudoun County's telecom tower points.
That skew is the value. A federal registration ledger holds structures filed with the regulator; these are permitting authorities publishing their own registers, including facility types - rooftops, pole attachments, small cells - that never enter a federal filing. Within Datadory's catalog this record scores 7/10 against a mean of 7.81 across 1,744 datasets and sits seventh on the best telecom tower REITs datasets board precisely because its narrower query surfaces county and city lists the wider result set buries. Get a sample of this dataset scoped to named states, counties or publishers and judge the rows first.
What do sample rows look like?
One typed row per cataloged result, identical in shape whether the publisher is a city permitting office or a national laboratory:
title : Telecommunications Towers and Antennas
organization : State of Connecticut
org_type : State
dataset_last_updated: 2026-07-17
formats : json xml csvRead the five rows above as the spread the query actually returns. The San Francisco set documents commercial wireless facilities in a dense urban market - with the honesty flag that the existing-facility layer is explicitly marked upstream as no longer maintained. Los Angeles small cells ride streetlight poles, the segment of the network that lives closest to the ground and furthest from any federal filing. Connecticut runs its inventory on a quarterly statutory cycle, so the July 17, 2026 stamp reflects a maintenance rhythm, not a one-off upload. Loudoun County arrives with six renditions including GIS and archive formats. And the NIST spectrum-sharing study proves the query is a keyword match, not a curated shelf - two of the eight entries are tangential, and we leave them visible rather than pruning them silently.
View counts, relevance scores and the catalog's link-check stamps complete each delivered row; the sample states its walked scope instead of inheriting the headline.
What fields does each result card carry?
Nine fields, verified against live cards during the August 2026 research pass rather than reconstructed from documentation. Three do the structural work:
- organization / org_type - who publishes it and at what level of government. The badge column is what lets a single pull separate a city permitting register from a federal research report without reading either.
- dataset_last_updated - the publisher's own modification date, carried up onto the index row. Freshness reads off the row itself.
- catalog_last_checked - when the harvester last confirmed the links behind the record. Read against the modification date, the pair tells you whether you are looking at a maintained inventory or a frozen one.
Then the ranking plumbing: search_relevance scoring each hit against the phrase, views_last_month recording demand, formats stating the renditions on offer, title and description_snippet for triage. Deeper payloads - full abstracts, resource-level listings, origin-portal resolution - fold under additional fields on request rather than being promised blind. Provenance for the whole family of government slices is profiled on the US Federal Open Data (data.gov) source profile.
Where does coverage run, and at what grain?
Geography - the United States, reached wherever the catalog harvests a publisher; the current result set concentrates where local governments maintain tower GIS layers: California, Connecticut, Virginia.
Temporal - the index refreshes daily over continuously harvested metadata, while constituent inventories carry their own rhythms: Los Angeles current to August 2026, Connecticut refreshed quarterly by statute, Loudoun last modified September 2023, San Francisco's existing layer frozen and flagged. The two timestamps per row are what make that mix navigable instead of treacherous.
Granularity - one row per cataloged dataset record, each pointing down at a point-level facility inventory. The index row is not the structure; the extracts beneath it are, and they arrive joined through the origin-portal crosswalk on request.
Set against the wider catalog - 1,744 datasets averaging 7.81 - this record scores 7/10: a fully verified card schema and honest provenance stamps, held back by a thin eight-row result set that carries two off-topic entries. Where that lands in the slice: best telecom tower REITs datasets.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Your cadence is yours alone. Take the discovery layer alone as a monitored map of which governments publish tower inventories and when they last touched them, or take it joined to the underlying facility extracts where a question needs the points themselves. Deliveries arrive normalized to the field dictionary above with both timestamps intact, so consecutive pulls diff cleanly and a newly published county layer surfaces the morning it appears.
Two postures work well in practice. Monitoring-first: watch the result set for additions and modifications - the change log is the product when the question is who published what lately. Join-first: resolve each record to its origin portal and land the facility points in your own tables alongside the registry and commercial layers. Most teams start with the first and grow into the second; get a sample cut to your jurisdictions and both postures arrive populated.
Who uses this data, and for what?
Six jobs the record earns its keep on:
- Sub-federal siting intelligence - city and county layers reach the rooftop and pole-attachment builds the national registration regime never holds; the same instinct behind competitor tracking applied to permits instead of press releases.
- Jurisdiction-by-jurisdiction mapping - filter by level and publisher to count who maintains what, where; the discipline behind market sizing pointed at government record-keeping itself.
- Regulatory and permitting monitoring - diff modification stamps between pulls and catch inventory refreshes the week they happen.
- Due-diligence corroboration - set permit-grade records beside commercial consolidated inventories before trusting either alone.
- Citation-grade research - named publishers and verification stamps behind every quoted count; see the wider citation-grade research shelf.
- Feature engineering - facility points join onto coordinate-keyed network and structure-stock models.
Each job maps to a persona below, and the sample validates whichever one you came for.
Which personas get the most value?
Competitive Intelligence & Product Teams lead fit - permitting authorities publish footprint evidence no vendor deck matches; see competitive intel x telecom tower REITs. Market Researchers & Consultants (relevance 2) get jurisdiction denominators that make coverage claims citable - market researchers x telecom tower REITs. Developers & Data-Product Builders (2) prototype monitoring products against a uniform nine-field index that behaves identically across heterogeneous portals - developers builders x telecom tower REITs. Journalists, Academics & Students (2) cite named offices and verification stamps rather than anonymous aggregations. Data Scientists & ML Engineers (1) and Investors & Quant Researchers (1) consume the extracted points and the permitting tempo respectively - investors quants x telecom tower REITs. Persona-by-persona detail lives on the telecom tower REITs data hub.
How does it compare within telecom tower REITs data?
This record owns the sub-federal permitting register territory, and the neighbours own territories beside it. Its closest sibling, the Data.gov Cell Tower Datasets Catalog, runs a broader query against the same index and returns 46 harvested inventories - the overlap is deliberate, and this narrower slice stays on the board because it surfaces county and city lists the larger result set buries deeper in the ranking. The FCC Data Hub Licensing and Tower Data registry owns federal filings at national scale with owning entities attached; TowerMaps US Cell Tower Database owns the commercial consolidation with owners and sales contacts; OpenCellID Bulk Downloads observes what is actually on air worldwide.
Only this slice answers which local governments maintain tower registers and how current each one runs - because only a harvesting catalog sees every publisher at once. The breadth-versus-signal trade against the observed-cell layer is worked through in OpenCellID Bulk Downloads vs Data.gov Antenna Tower Datasets Catalog.
Why route it through Datadory at all?
Because the artifact is a search-results page over more than half a million records - server-rendered cards, per-publisher portals underneath, two timestamps and a handful of ranking signals per card - and most questions want one normalized table. Datadory flattens the slice to the nine-field spine, resolves each record to its origin portal on request, diffs consecutive pulls so additions and retirements announce themselves, and schedules the whole thing on your cadence.
Browse the rest of the industry on the telecom tower REITs data hub, the best telecom tower REITs datasets ranking, or the full catalog; the publisher side of the family is profiled at the US Federal Open Data (data.gov) source profile.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| Field | Type | Definition | Example |
|---|---|---|---|
title | string | Dataset title as published by the originating agency - the primary human-readable key for triage. | Existing Commercial Wireless Telecommunication Services Facilities in San Francisco |
organization | string | Publishing organization named on the result card - the authority whose process produced and maintains the inventory. | City of Los Angeles |
org_type | enum | Government-level badge: Federal, State, County or City - the column that turns a mixed result list into a filtered jurisdiction cut. | City |
description_snippet | text | Truncated notes text harvested from the underlying metadata record. | Small cell locations attached to streetlight poles citywide |
dataset_last_updated | date | The underlying dataset's own last-modified date, carried from the harvested metadata - publisher-side freshness, distinct from the catalog's check below. | 2026-08-11 |
formats | string | Renditions the underlying inventory offers - JSON, XML and CSV on most cards, KML, HTML, ZIP and API renditions on some county layers. | csv json kml zip html api |
search_relevance | number | Query relevance score the catalog engine assigns against the searched phrase. | 55.53 |
views_last_month | integer | Monthly view count the catalog tracks per record - a thin but honest demand signal across government publishers. | - |
catalog_last_checked | datetime | Timestamp of the harvester's last successful link check - the second of the two timestamps that make freshness readable per row. | 2026-08-11 23:36 |
Additional fields on request | - | Detail-page payloads (fuller abstracts, resource-level listings, identifiers), origin-portal crosswalks, change detection between pulls, and joins onto the registry, commercial and observed-cell layers. | - |
Data.gov Antenna Tower Datasets Catalog - product specification
| Attribute | Value |
|---|---|
| Industry | Telecom Tower REITs |
| Publishing body | Data.gov, operated by the US General Services Administration |
| Query shape | Phrase search against the full catalog index: antenna tower |
| Result count | 8 matching datasets from roughly 552,271 indexed (August 2026 research pass) |
| Observed publishers | San Francisco, Los Angeles, Connecticut Siting Council, Loudoun County VA, NIST, Department of the Interior |
| Recorded renditions | JSON, XML, CSV on most cards; KML, HTML, ZIP and API links on some county layers |
| Fields | 9-field verified card schema; detail-page payloads fold out on request |
| Geographic coverage | United States; current results concentrate in California, Connecticut and Virginia |
| Temporal coverage | Constituent inventories modified April 2019 through August 2026; index refreshed daily |
| Delivery cadence | Daily, weekly, or hourly |
What teams do with it
- Sub-federal siting intelligence City and county permitting layers reach rooftop and small-cell installs the national registration regime never captures - the tier where densification actually happens.
- Jurisdiction-by-jurisdiction market mapping Filter by government level and publisher to count who maintains what, where - a census of local wireless-facility record-keeping rather than an estimate.
- Regulatory and permitting monitoring Diff modification stamps between pulls to catch the morning a Siting Council refreshes its tower inventory or a city publishes a new facility layer.
- Due-diligence corroboration Set permit-grade municipal records beside commercial consolidated inventories before leaning on either alone for footprint claims.
- Citation-grade research and journalism Named publishers, government-level badges and verification stamps let quoted counts survive editorial scrutiny without a chain of screenshots.
- Feature engineering for network models Point-level facility extracts join onto coordinate-keyed models of coverage, densification and structure stock once the origin-portal crosswalk resolves them.
Questions buyers ask
What does one delivered row of data gov antenna tower datasets catalog data contain?
Nine fields: the dataset title, the publishing organization, its Federal, State, County or City badge, a description snippet, the underlying dataset's last-modified date, the renditions on offer, the query relevance score, a trailing-month view count and the catalog's own link-check timestamp. Detail-page payloads and origin-portal resolution fold out on request.
Why does the query return only eight results?
The phrase is narrow and the catalog matches titles and abstracts literally, so eight of roughly 552,271 indexed records qualify as of the August 2026 research pass. Thin does not mean shallow: each match is an entire maintained inventory - a city's facility points, a state council's tower register - most offering several file renditions apiece. The broader sibling query returns 46, with the relevant county and city hits buried deeper in the ranking.
Which publishers appear in the result set?
State and local permitting authorities dominate: San Francisco's existing and proposed commercial wireless facility sets, Los Angeles small-cell nodes on streetlight poles, the Connecticut Siting Council's telecommunications towers and antennas refreshed quarterly by statute, and Loudoun County, Virginia telecom tower points. Two of the eight are tangential federal entries - a NIST spectrum-sharing simulation and a solar-tower radar imagery set - kept visible rather than silently pruned.
How can you tell a living inventory from a frozen one?
Read the two timestamps together. The publisher's modification date says when the contents last changed; the catalog's link-check stamp says when the record was last verified. San Francisco's existing-facility set is explicitly flagged upstream as no longer maintained - the candour is part of the schema, so staleness reads off the row instead of surfacing mid-project.
How is this different from the sibling Data.gov Cell Tower Datasets Catalog?
Same index, different query. The sibling searches a broader phrase and harvests 46 inventories; this record searches the narrower phrase and returns 8, trading breadth for rank quality on exactly the county and city lists the larger set buries. Running both ledgers and diffing them is the honest play, which is why both records remain in the slice.
Can a sample be scoped to specific states, counties or publishers?
Yes. Name the geographies, the government levels or the individual inventories you care about and the sample arrives in exactly the schema shown above, extended across whichever cut you need - with the underlying facility points joined through the origin-portal crosswalk where you want them. Delivery runs through API, files, or your warehouse on a daily, weekly, or hourly cadence.
Notes on this record
- Local by construction Permitting authorities publish registers here that the federal filing regime never holds - rooftops, pole attachments and small cells included.
- Two timestamps per row The publisher's modification date and the catalog's link-check stamp travel together, so living and frozen inventories separate by reading the pair.
- Frozen sets, flagged San Francisco's existing-facility layer is explicitly marked upstream as no longer maintained - candour about staleness is part of the schema, not a defect found later.
- Scored honestly 7/10 against a catalog mean of 7.81 across 1,744 datasets - a fully verified card schema and provenance stamps, held back by a thin result set carrying two off-topic entries.
Datasets that pair with this one
- Data.gov Cell Tower Datasets Catalog The sibling query returns 46 broader hits; this narrower slice stays on the board because it surfaces county and city lists the larger set buries.
- telecom tower REITs data hub The pooled slice view - property layers, regulatory files and market data for the tower complex in one place.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.