outage_snapshots

11 rows where outage = 642385

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: lastUpdateTime, currentEtor, cause, crewCurrentStatus

id ▼ outage snapshot lastUpdateTime currentEtor autoEtor estCustAffected hazardFlag latitude longitude regionName cause crewCurrentStatus
1570203627:642385 642385 642385 2019-10-04 08:40:27-07:00 470 October 04, 2019 - 15:31:04 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E has assigned a crew to assess the outage. 1
1570204220:642385 642385 642385 2019-10-04 08:50:20-07:00 471 October 04, 2019 - 15:40:01 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E has assigned a crew to assess the outage. 1
1570204853:642385 642385 642385 2019-10-04 09:00:53-07:00 472 October 04, 2019 - 15:40:01 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E has assigned a crew to assess the outage. 1
1570205420:642385 642385 642385 2019-10-04 09:10:20-07:00 473 October 04, 2019 - 15:40:01 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E has assigned a crew to assess the outage. 1
1570206026:642385 642385 642385 2019-10-04 09:20:26-07:00 474 October 04, 2019 - 15:40:01 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1570206627:642385 642385 642385 2019-10-04 09:30:27-07:00 475 October 04, 2019 - 15:40:01 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1570207232:642385 642385 642385 2019-10-04 09:40:32-07:00 476 October 04, 2019 - 16:30:51 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1570207812:642385 642385 642385 2019-10-04 09:50:12-07:00 477 October 04, 2019 - 16:30:51 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1570208451:642385 642385 642385 2019-10-04 10:00:51-07:00 478 October 04, 2019 - 16:30:51 UTC October 04, 2019 - 17:15:00 UTC October 04, 2019 - 17:15:00 UTC 1 1 38.00239 -121.79165 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1570209023:642385 642385 642385 2019-10-04 10:10:23-07:00 479 October 04, 2019 - 16:59:26 UTC October 04, 2019 - 22:00:00 UTC   1 1 38.00239 -121.79165 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1570209627:642385 642385 642385 2019-10-04 10:20:27-07:00 480 October 04, 2019 - 16:59:26 UTC October 04, 2019 - 22:00:00 UTC   1 1 38.00239 -121.79165 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [outage_snapshots] (
   [id] TEXT PRIMARY KEY,
   [outage] INTEGER REFERENCES [outages]([id]),
   [snapshot] INTEGER REFERENCES [snapshots]([id]),
   [lastUpdateTime] INTEGER,
   [currentEtor] INTEGER,
   [autoEtor] INTEGER,
   [estCustAffected] INTEGER,
   [hazardFlag] INTEGER,
   [latitude] TEXT,
   [longitude] TEXT,
   [regionName] INTEGER REFERENCES [regionName]([id]),
   [cause] INTEGER REFERENCES [cause]([id]),
   [crewCurrentStatus] INTEGER REFERENCES [crewCurrentStatus]([id])
);
CREATE INDEX [idx_outage_snapshots_outage]
    ON [outage_snapshots] ([outage]);