10 rows where outage = 696810

View and edit SQL

Suggested facets: lastUpdateTime, currentEtor, cause, crewCurrentStatus

id ▼ outage snapshot lastUpdateTime currentEtor autoEtor estCustAffected hazardFlag latitude longitude regionName cause crewCurrentStatus
1572552659:696810 696810 696810 2019-10-31 13:10:59-07:00 4099 October 31, 2019 - 20:03:37 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1572553224:696810 696810 696810 2019-10-31 13:20:24-07:00 4100 October 31, 2019 - 20:03:37 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1572553832:696810 696810 696810 2019-10-31 13:30:32-07:00 4101 October 31, 2019 - 20:03:37 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1572554423:696810 696810 696810 2019-10-31 13:40:23-07:00 4102 October 31, 2019 - 20:03:37 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1572555039:696810 696810 696810 2019-10-31 13:50:39-07:00 4103 October 31, 2019 - 20:03:37 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 Unknown - PG&E will be assessing the cause. 1 PG&E assessment crew is en route to the outage. 5
1572555654:696810 696810 696810 2019-10-31 14:00:54-07:00 4104 October 31, 2019 - 20:51:52 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1572556227:696810 696810 696810 2019-10-31 14:10:27-07:00 4105 October 31, 2019 - 20:51:52 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1572556840:696810 696810 696810 2019-10-31 14:20:40-07:00 4106 October 31, 2019 - 20:51:52 UTC October 31, 2019 - 21:45:00 UTC October 31, 2019 - 21:45:00 UTC 1 1 38.00847 -121.80997 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1572557438:696810 696810 696810 2019-10-31 14:30:38-07:00 4107 October 31, 2019 - 21:21:08 UTC November 01, 2019 - 05:00:00 UTC   1 1 38.00847 -121.80997 Antioch 42 PG&E is investigating the cause of your outage. 6 PG&E is assessing the cause at the outage location. 4
1572558019:696810 696810 696810 2019-10-31 14:40:19-07:00 4108 October 31, 2019 - 21:21:08 UTC November 01, 2019 - 05:00:00 UTC   1 1 38.00847 -121.80997 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]);