TV White Space (TVWS) and Unlicensed Spectrum Usage

This dataset provides granular records of unlicensed spectrum usage across TV white space, ISM, and U-NII bands, including device geolocation, power limits, regulatory compliance, and coexistence with licensed services. It is ideal for spectrum management, interference analysis, and regulatory reporting, supporting advanced analytics and network planning.

  • last updated 1 Nov 2025
  • by GoMask
The brief that made it

Spectrum management and regulatory compliance monitoring

Sample rows

preview · 8 of 180 rows · all 20 columns
usage_idstringdevice_typestringfrequency_start_mhzfloatcoexistence_with_licensedbooleanspectrum_bandstringdevice_idstringfrequency_end_mhzfloatpower_limit_dbmfloatdfs_requiredbooleangeolocation_query_timedatetimegeolocation_latitudefloatgeolocation_longitudefloatgeolocation_accuracy_mfloatdatabase_providerstringchannel_numberintegerlicensee_service_presentbooleanusage_start_timedatetimeusage_end_timedatetimeusage_purposestringnotesstring
tvws-1a7kW2zETVWS radio471trueTVWSdev-001-tvws47530false2023-03-01T06:15:00Z35.6895139.691710.5Tokyo TVWS DB23true2023-03-01T06:17:00Z2023-03-01T07:12:00Zbroadband accessEnterprise mesh deployment, regulatory compliance verified.
iot-9v4bXmtPIoT sensor654falseU-NIIiot-0047-polar6608true2023-01-12T19:25:00Z89.9-135500Polar U-NII DB190false2023-01-12T19:26:00Z2023-01-12T19:56:00ZIoTSensor mesh, polar region test.
wifi-OPZk6x3RWi-Fi AP2412falseISM 2.4GHzwifi-121-nyc243720false2023-02-18T14:35:00Z40.7128-74.0065NYC WiFi DB6false2023-02-18T14:36:00Z2023-02-18T16:36:00Zbroadband accessHigh engagement in business district.
tvws-Ew7DkS12TVWS radio698trueTVWSdev-002-tvws69836false2023-01-10T03:00:00Z-23.5505-46.633315SaoPaulo TVWS DB65true2023-01-10T03:02:00Z2023-01-10T04:02:00ZbackhaulEdge frequency usage, licensed service coexistence.
iot-2l_R8ywKIoT sensor470falseISM 2.4GHziot-0082-outbk4725false2023-02-05T11:12:00Z-33.8688151.209325Sydney Outback DB130false2023-02-05T11:16:00Z2023-02-05T11:46:00ZIoTWildlife sensor deployment.
wifi-b6_19XJpWi-Fi AP5745falseISM 5GHzwifi-212-lon580528true2023-03-05T20:30:00Z51.5074-0.12783London WiFi DB36false2023-03-05T20:31:00Z2023-03-05T22:01:00Zbroadband accessDFS enabled, dense urban environment.
tvws-mxN2h3_vTVWS radio474trueTVWSdev-003-tvws48020false2023-01-15T08:45:00Z55.755837.617312Moscow TVWS DB24true2023-01-15T08:49:00Z2023-01-15T09:49:00ZbackhaulBackhaul for metro connectivity.
wifi-4rM2Qb8gWi-Fi AP2422falseISM 2.4GHzwifi-309-par246218false2023-01-22T09:15:00Z48.85662.35226Paris WiFi DB11false2023-01-22T09:16:00Z2023-01-22T10:01:00Zbroadband accessPublic hotspot near tourist attractions.

What the 180 rows show

from the 180-row sample

TVWS radio (device type) stands out: 56 of its 56 rows have coexistence_with_licensed = true, against 18 of 124 for the rest.

  • 41%coexistence_with_licensed = true
  • 590.4median frequency_start_mhz
  • 4usage purposes
  • 596.2median frequency_end_mhz
  • 20.0median power_limit_dbm
  • 12.3median geolocation_accuracy_m
Coexistence with licensed rate by device_typecoexistence_with_licensed = true
0%50%100%100%TVWS rad…56 of 560%Wi-Fi AP0 of 500%IoT sens…0 of 56100%Other18 of 18
frequency_start_mhz180 rows, in bands of 1,000
080160152014001403,0006,000frequency_start_mhz →

Median 590.4, from 470.0 to 5,825.

spectrum_band180 rows · 4 values
  1. TVWS79
  2. U-NII38
  3. ISM 2.4GHz34
  4. ISM 5GHz29
20 columns by typefrom the column list below
  • string 7
  • integer 1
  • float 6
  • datetime 3
  • boolean 3

Columns

20 columns in four groups
blueprint · 20 columns
columntypedescriptionexample
Text 7 columns
usage_idstringUnique identifier for each spectrum usage recorduniquetvws-1a7kW2zE
device_idstringUnique identifier for the device accessing the spectrumdev-001-tvws
device_typestringType of device (e.g., TVWS radio, Wi-Fi AP, IoT sensor)TVWS radio · Wi-Fi AP · IoT sensor · OtherTVWS radio
spectrum_bandstringSpectrum band used (e.g., TVWS, ISM 2.4GHz, ISM 5GHz, U-NII)TVWS · ISM 2.4GHz · ISM 5GHz · U-NIITVWS
database_providerstringName of the geolocation database providerTokyo TVWS DB
usage_purposestringPurpose of usage (e.g., broadband access, IoT, backhaul)broadband access · IoT · backhaul · other · optionalbroadband access
notesstringAdditional notes or comments about the usage eventoptionalUrban TVWS deployment.
Numbers 7 columns
frequency_start_mhzfloatStart frequency in MHz470 to 698471
frequency_end_mhzfloatEnd frequency in MHz470 to 698475
power_limit_dbmfloatMaximum transmit power allowed (in dBm)0 to 3630
geolocation_latitudefloatLatitude of device location (WGS84)-90 to 9035.6895
geolocation_longitudefloatLongitude of device location (WGS84)-180 to 180139.6917
geolocation_accuracy_mfloatAccuracy of geolocation in meters0 or more · optional10.5
channel_numberintegerChannel number used (if applicable)1 to 196 · optional23
Dates and times 3 columns
geolocation_query_timedatetimeTimestamp of the geolocation database query2023-03-01T06:15:00Z
usage_start_timedatetimeTimestamp when spectrum usage started2023-03-01T06:17:00Z
usage_end_timedatetimeTimestamp when spectrum usage endedoptional2023-03-01T07:12:00Z
True or false 3 columns
dfs_requiredbooleanIndicates if Dynamic Frequency Selection (DFS) is requiredfalse
coexistence_with_licensedbooleanIndicates if coexistence measures with licensed services are in placetrue
licensee_service_presentbooleanIndicates if a licensed service is present on the channel/frequencytrue

Use it for

  • coexistence wi…41%74 of 180 rowsmean frequency start …525.6TVWS…2.4kWi-F…668.8IoT …670.7Other

    A telecommunications dashboard

    The coexistence_with_licensed rate, frequency_start_mhz by device_type and a breakdown of spectrum_band. Excel, Power BI or Tableau.

  • Why do 74 of 180 rows have coexistence_with_licensed = true?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable usages with device_id, device_type and spectrum_band to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 20 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset180 rows20 columns
Yours1,000 rows20 columns

blueprint · tv-white-space-tvws-and-unlicensed-spectrum-usage

Behind this dataset

Same schema. As many rows as you need.

These 180 rows came out of a blueprint — 20 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Device ID and operating frequency
  • TVWS spectrum: unused TV broadcast channels (470-698MHz)
  • Geolocation database query for available channels at device location
  • Transmit power limits based on proximity to protected contours
  • ISM bands: 2.4GHz (2400-2483.5MHz), 5GHz (5150-5850MHz)
  • DFS (Dynamic Frequency Selection) for radar detection in 5GHz U-NII bands
  • Channel availability: time duration channel remains available
  • Coexistence: avoiding interference with licensed broadcasters, radar
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
tv-white-space-tvws-and-unlicensed-spectrum-usage

More in Telecommunications

Browse all
Also in TelecommunicationsLicensed Spectrum Inventory and Regulatory AllocationsTelecommunications Equipment Failure LogsMobile Data Usage Pattern DatasetAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.