Public Infrastructure Edge Deployment Log

This dataset tracks edge computing device deployments across public infrastructure, capturing detailed location, operational uptime, software compliance, and anomaly events. It enables urban planners and government teams to monitor IoT assets, ensure regulatory adherence, and respond quickly to incidents, supporting smart city digital transformation and efficient infrastructure management.

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

Monitoring and managing edge device deployments for smart city initiatives

Sample rows

preview · 8 of 75 rows · all 22 columns
deployment_idstringregulatory_compliance_statusstringuptime_hoursfloatsoftware_compliantbooleanlocation_countrystringdevice_idstringdevice_typestringdeployment_datedatelocation_latitudefloatlocation_longitudefloatlocation_street_addressstringlocation_citystringlocation_statestringlocation_postal_codestringlast_maintenance_datedatesoftware_versionstringanomaly_detectedbooleananomaly_event_typestringcontact_person_namestringcontact_person_emailstringnotesstringanomaly_event_descriptionstring
DEP0001compliant1456.3trueUSADEV-001sensor2024-04-0340.7128-74.006123 BroadwayNew YorkNY100072024-05-27v2.3.1falsenoneLaura Chenlaura.chen@nyc.govInitial deployment in park areablank
DEP0002compliant2200.8trueUSADEV-002camera2023-11-1434.0522-118.2437456 Main StLos AngelesCA900122024-04-30v3.0.0falsenoneMiguel Santosm.santos@la.govblankblank
DEP0003compliant14.2trueUSADEV-001sensor2024-06-0140.7134-74.0075125 BroadwayNew YorkNY10007blankv2.3.2falsenoneLaura Chenlaura.chen@nyc.govRedeployment after scheduled upgradeblank
DEP0004compliant893trueUKDEV-003gateway2024-02-1551.5074-0.1278789 King StLondonLondonWC2N 5DU2024-05-02v1.8.5falsenoneAmir Patelamir.patel@london.gov.ukUpgraded to latest firmware last maintenanceblank
DEP0005compliant312.4trueJapanDEV-004router2024-05-1035.6895139.6917100 ShibuyaTokyoTokyo150-0002blankv2.1.9falsenoneKeiko Tanakakeiko.tanaka@tokyo.jpblankblank
DEP0006non-compliant59falseFranceDEV-005camera2024-05-2748.85662.352250 Rue de RivoliParisÎle-de-France75001blankv3.0.0truenetwork_issueLuc Moreauluc.moreau@paris.frNon-compliance due to outdated security patchIntermittent connectivity observed during peak hours.
DEP0007compliant8.6trueNetherlandsDEV-006sensor2024-06-0252.37024.895275 DamrakAmsterdamNorth Holland1012blankv2.2.3falsenoneSven de Vriessven.devries@amsterdam.nlNew sensor for air quality monitoringblank
DEP0008pending415.7falseUSADEV-007gateway2024-04-2241.8781-87.6298200 W Adams StChicagoIL606062024-05-28v1.9.1truehardware_failureJanet Leejanet.lee@chicago.govUnit pending compliance reviewGateway lost power unexpectedly; replaced unit.

What the 75 rows show

from the 75-row sample

Compliant (regulatory compliance status) stands out: 63 of its 63 rows have software_compliant = true, against 3 of 12 for the rest.

  • 88%software_compliant = true
  • 241.2median uptime_hours
  • 5device types
  • 5anomaly event types
Software compliant rate by regulatory_compliance_statussoftware_compliant = true
0%50%100%100%compliant63 of 630%non-compliant0 of 760%pending3 of 5
uptime_hours75 rows, in bands of 500
02550499933100102,5004,500uptime_hours →

Median 241.2, from 1.9 to 4,189.

location_country75 rows · top 10 of 22 values
  1. USA23
  2. Canada21
  3. Japan3
  4. Germany3
  5. China3
  6. UK2
  7. France2
  8. India2
  9. Spain2
  10. Italy2
22 columns by typefrom the column list below
  • string 15
  • float 3
  • date 2
  • boolean 2

Columns

22 columns in four groups
blueprint · 22 columns
columntypedescriptionexample
Text 15 columns
deployment_idstringUnique identifier for each edge device deployment eventuniqueDEP0001
device_idstringUnique identifier for the edge computing deviceDEV-001
device_typestringType or model of the edge device (e.g., sensor, gateway, camera)sensor · gateway · camera · router · othersensor
location_street_addressstringStreet address of the deployment locationoptional123 Broadway
location_citystringCity of the deployment locationNew York
location_statestringState or province of the deployment locationNY
location_postal_codestringPostal code of the deployment locationoptional10007
location_countrystringCountry of the deployment locationUSA
software_versionstringCurrent software version running on the devicev2.3.1
anomaly_event_typestringType of anomaly event detected (if any)6 values · optionalnone
anomaly_event_descriptionstringDetailed description of the anomaly eventoptionalIntermittent connectivity…
regulatory_compliance_statusstringOverall regulatory compliance status for the deploymentcompliant · non-compliant · pending · unknowncompliant
contact_person_namestringName of the responsible contact person for the deploymentoptionalLaura Chen
contact_person_emailstringEmail address of the responsible contact personoptionallaura.chen@nyc.gov
notesstringAdditional notes or comments about the deploymentoptionalSensor for pilot test
Numbers 3 columns
location_latitudefloatLatitude coordinate of the deployment location-90 to 9040.7128
location_longitudefloatLongitude coordinate of the deployment location-180 to 180-74.006
uptime_hoursfloatTotal hours the device has been operational since deployment0 or more1456.3
Dates and times 2 columns
deployment_datedateDate when the device was deployed2024-04-03
last_maintenance_datedateDate of the most recent maintenance performed on the deviceoptional2024-05-27
True or false 2 columns
software_compliantbooleanIndicates if the device software is compliant with regulatory standardstrue
anomaly_detectedbooleanIndicates if any anomaly event has been detected for this deploymentfalse

Use it for

  • software compl…88%66 of 75 rowsmean uptime hours by …573.3compli…603.4non-co…701.8pending

    A government dashboard

    The software_compliant rate, uptime_hours by regulatory_compliance_status and a breakdown of location_country. Excel, Power BI or Tableau.

  • Why do 66 of 75 rows have software_compliant = 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 deployments with device_id, device_type and deployment_date to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 22 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 rows22 columns
Yours1,000 rows22 columnslocation_latitude: UK only

blueprint · public-infrastructure-edge-deployment-log

Behind this dataset

Same schema. As many rows as you need.

These 75 rows came out of a blueprint — 22 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 row represents a unique edge device deployment event.
  • Device type must be one of: traffic sensor, environmental monitor, energy meter, surveillance camera.
  • Status must be 'active', 'inactive', or 'maintenance'.
  • Compliance field denotes adherence to current municipal IT regulations.
  • Anomaly flag is set when unexpected downtime exceeds 1 hour.
  • Software version must match approved city standards.
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
public-infrastructure-edge-deployment-log

More in Government

Browse all
Also in GovernmentSmart Park Device Uptime LogCivic Participation Event AttendanceUrban Noise Pollution Sensor DataAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.