Urban Noise Sensor Reliability Log

This dataset provides detailed reliability logs for urban noise pollution sensors, including operational uptime, incident records, location data, and maintenance actions. It enables smart city managers and IoT teams to monitor sensor health, optimize maintenance schedules, and ensure continuous environmental monitoring for urban planning and public health initiatives.

  • last updated 18 Dec 2025
  • by GoMask
The brief that made it

Proactive maintenance scheduling for urban noise sensors

Sample rows

preview · 8 of 75 rows · all 19 columns
log_idstringmaintenance_actionstringincident_countintegerresolvedbooleanincident_typestringsensor_idstringinstallation_datedatelast_maintenance_datedatelocation_street_addressstringlocation_citystringlocation_statestringlocation_postal_codestringlocation_countrystringuptime_hoursfloatincident_severitystringincident_datetimedatetimeresolution_datetimedatetimemaintenance_notesstringincident_descriptionstring
A3K9J7L2firmware_update2truesensor_errorSN-1001A2023-06-152024-05-10125 Market StSan FranciscoCA94105USA712.5medium2024-05-08T14:20:002024-05-09T10:30:00Updated firmware to latest version.Sensor intermittently failing to record data.
B7Q2D1F8cleaned_device0blankblankSN-1002B2022-10-212024-04-29967 Canal AveChicagoIL60607USA1052.7blankblankblankRoutine cleaning and calibration.blank
L8Z3T6R1rebooted1trueconnectivity_issueSN-1003C2023-03-042024-03-16240 Queen StTorontoONM5V 2B6Canada1307.8low2024-03-12T16:45:002024-03-12T17:30:00Rebooted gateway, connection restored.Brief loss of wireless connection during rain.
P2W8U3F4blank0blankblankSN-1004D2024-01-08blank44 BroadwayNew YorkNY10007USA1891.6blankblankblankblankblank
V6C2N7H9other3falseenvironmental_damageSN-1005E2022-11-192024-05-05390 Pacific AveSeattleWA98104USA548.2high2024-05-03T09:10:00blankTemporary repairs performed; needs replacement.Sensor casing cracked due to fallen branch.
T4E1B9K5rebooted1truepower_failureSN-1006F2023-07-122024-02-0612 King St ETorontoONM5C 1C3Canada1560.3critical2024-02-05T21:10:002024-02-06T08:20:00Power restored, system rebooted.Complete power outage for 2 hours.
M3R9Q1V8cleaned_device0blankblankSN-1007G2022-09-272024-04-01201 Main StVancouverBCV6A 2S5Canada1238.4blankblankblankDevice cleaned and humidity checked.blank
X2V7O1A4blank0blankblankSN-1008H2023-12-03blank11 E Madison StChicagoIL60602USA987.3blankblankblankblankblank

What the 75 rows show

from the 75-row sample

Cleaned_device (maintenance action) stands out: mean incident_count is 0.23, against 1.4 for the rest.

  • 82%resolved = true
  • 1median incident_count
  • 4location countries
  • 4incident severities
  • 13location states
  • 14location cities
Mean incident_count by maintenance_action59 rows
0242.4replac…5 rows0.83firmwa…12 rows0.23cleane…22 rows1.5reboot…15 rows1.8other5 rows
incident_count75 rows, in bands of 0.5
0204037022011041024incident_count →

Median 1, from 0 to 4.

incident_type38 rows with a value · 37 left blank
  1. sensor_error11
  2. connectivity_issue9
  3. environmental_damage8
  4. power_failure8
  5. other2
19 columns by typefrom the column list below
  • string 12
  • integer 1
  • float 1
  • date 2
  • datetime 2
  • boolean 1

Columns

19 columns in four groups
blueprint · 19 columns
columntypedescriptionexample
Text 12 columns
log_idstringUnique identifier for each reliability log entryuniqueA3K9J7L2
sensor_idstringUnique identifier for the noise sensor deviceSN-1001A
location_street_addressstringStreet address where the sensor is installed125 Market St
location_citystringCity where the sensor is installedSan Francisco
location_statestringState or province where the sensor is installedCA
location_postal_codestringPostal code of the sensor's location94105
location_countrystringCountry where the sensor is installed4 countriesUSA
incident_typestringType of incident encountered (e.g., power failure, sensor error, connectivity issue)5 values · optionalsensor_error
incident_severitystringSeverity level of the incidentlow · medium · high · critical · optionalmedium
incident_descriptionstringDetailed description of the incidentoptionalMinor data upload delay.
maintenance_actionstringType of maintenance action taken (e.g., replaced sensor, firmware update, cleaned device)5 values · optionalfirmware_update
maintenance_notesstringAdditional notes or comments about maintenance actionsoptionalFirmware module patched.
Numbers 2 columns
uptime_hoursfloatTotal operational hours recorded for the sensor since last maintenance0 or more712.5
incident_countintegerNumber of reliability incidents recorded for the sensor during the log period0 or more2
Dates and times 4 columns
installation_datedateDate when the sensor was installed at its current location2023-06-15
last_maintenance_datedateDate of the most recent maintenance performed on the sensoroptional2024-05-10
incident_datetimedatetimeDate and time when the incident occurredoptional2024-05-08T14:20:00
resolution_datetimedatetimeDate and time when the incident was resolvedoptional2024-05-09T10:30:00
True or false 1 column
resolvedbooleanIndicates whether the incident has been resolvedoptionaltrue

Use it for

  • resolved82%31 of 38 rowsmean incident count b…2.4repl…0.83firm…0.23clea…1.5rebo…

    A technology dashboard

    The resolved rate, incident_count by maintenance_action and a breakdown of incident_type. Excel, Power BI or Tableau.

  • Why do the 22 cleaned_device rows have a mean incident_count of 0.23?

    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 logs with sensor_id, installation_date and last_maintenance_date to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 19 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 dataset75 rows19 columns
Yours1,000 rows19 columnslocation_street_address: UK only

blueprint · urban-noise-sensor-reliability-log

Behind this dataset

Same schema. As many rows as you need.

These 75 rows came out of a blueprint — 19 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
  • Each record represents a unique sensor for a specific day.
  • Device status must be one of: Operational, Partial Outage, Full Outage.
  • Incident field logs noise threshold breaches or sensor malfunctions.
  • Maintenance response time (in hours) is recorded when incidents occur.
  • Includes sensor location type: School Zone, Residential, Commercial, Park, or Industrial.
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
urban-noise-sensor-reliability-log

More in Technology

Browse all
Also in TechnologyIoT Device Network EventsCustomer Support Case EscalationsMeeting SchedulesAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.