paulwynter commited on
Commit
fba9e58
·
verified ·
1 Parent(s): f078483

Publish Electrical Permit — 2018,2019,2020,2021,2022,2023 (v1)

Browse files
Files changed (2) hide show
  1. README.md +78 -1
  2. manifest.json +1 -1
README.md CHANGED
@@ -1,9 +1,86 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  # Electrical Permit — 2018,2019,2020,2021,2022,2023
2
 
3
- Open permits dataset from electrical_permit_permits; generated for 2018,2019,2020,2021,2022,2023.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
4
 
5
  ## Files
6
 
7
  - [Parquet](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.parquet)
8
  - [GeoJSON](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.geojson)
9
  - [CSV](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.csv)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ tags:
3
+ - geospatial
4
+ - open-data
5
+ - tabular
6
+ - parquet
7
+ - geojson
8
+ - csv
9
+ - electrical-permit
10
+ - permits
11
+ - year-2018
12
+ - year-2019
13
+ - year-2020
14
+ - year-2021
15
+ - year-2022
16
+ - year-2023
17
+ libraries:
18
+ - datasets
19
+ size_categories:
20
+ - 100K<n<1M
21
+ ---
22
+
23
  # Electrical Permit — 2018,2019,2020,2021,2022,2023
24
 
25
+ This release contains 159,257 public permit records from 2018, 2019, 2020, 2021, 2022, 2023. It focuses on electrical permit. Electrical permit records capture reported work on electrical systems and related building improvements. They are useful for studying renovations, upgrades, electrification activity, and the geography of permitted electrical projects.
26
+
27
+ EmbedEarth publishes the records in a consistent geospatial format while preserving source-specific fields in the `properties` column. The release is useful for exploratory mapping, time-series analysis, urban development research, infrastructure planning, and reproducible open-data workflows. A record describes what a contributing source reported; it is not, by itself, proof that work was completed or that a project reached a particular construction milestone.
28
+
29
+ ## Dataset contents
30
+
31
+ The downloadable files contain the same normalized records in Parquet, GeoJSON, and CSV. Records include coordinates or geometry when available. Source-specific permit numbers, work descriptions, statuses, dates, parties, addresses, valuations, and classifications remain inside the JSON-encoded `properties` field so the source detail is retained without forcing different municipal schemas into one misleading set of columns.
32
+
33
+ ## Columns
34
+
35
+ | Column | Type | Description |
36
+ | --- | --- | --- |
37
+ | `id` | string | Stable identifier for the exported record. |
38
+ | `sample` | boolean | Whether the record was selected for an optional image sample. |
39
+ | `latitude` | float64 | Latitude in decimal degrees (WGS 84) when a valid location is available. |
40
+ | `longitude` | float64 | Longitude in decimal degrees (WGS 84) when a valid location is available. |
41
+ | `geometry_wkb` | binary | Record geometry encoded as Well-Known Binary for spatial workflows. |
42
+ | `media_url` | string | URL for associated visual media when available. |
43
+ | `attribution` | string | Attribution text carried into the exported record. |
44
+ | `source` | string | Source or provider label carried into the exported record. |
45
+ | `properties` | string | JSON-encoded source-specific permit attributes; parse this field to access the original fields. |
46
+
47
+ ### What to look for in `properties`
48
+
49
+ Depending on the contributing source, `properties` may include a permit or application number, permit type or class, work description, project or property use, lifecycle status, application or issue dates, completion dates, address, city, state, postal code, applicant, contractor, owner, valuation, and other local fields. Field names and meanings can differ between jurisdictions, so keep the source label and original values with any analysis.
50
 
51
  ## Files
52
 
53
  - [Parquet](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.parquet)
54
  - [GeoJSON](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.geojson)
55
  - [CSV](https://huggingface.co/datasets/EmbedEarth/electrical-permit/resolve/main/data.csv)
56
+
57
+ ## Geographic Feature List
58
+
59
+ Explore the [EmbedEarth Geographic Feature List](https://www.embed.earth/catalog/features) for related geographic datasets and feature categories.
60
+
61
+ ## Data source and attribution
62
+
63
+ Prepared and distributed by [EmbedEarth](https://embed.earth). Contributing public sources represented in this release include:
64
+
65
+ - [DOB NOW: Build Approved Permits](https://data.cityofnewyork.us/Housing-Development/DOB-NOW-Build-Approved-Permits/rbx6-tga4)
66
+ - [Building Permits](https://data.cityofchicago.org/Buildings/Building-Permits/ydr8-5enu)
67
+ - [Los Angeles Building Permits 2020-Present](https://data.lacity.org/d/gwh9-jnip)
68
+ - [Building and Safety - Building Permits Issued Between 2010 and 2019 (N)](https://data.lacity.org/d/dyxf-7hc4)
69
+ - [Building and Safety - Building Permits Issued Before 2010 (N)](https://data.lacity.org/d/e67z-kt2n)
70
+ - [Licenses & Inspections Building and Zoning Permits](https://opendataphilly.org/datasets/licenses-and-inspections-building-and-zoning-permits/)
71
+ - [CCS Permits](https://opendata.minneapolismn.gov/datasets/cityoflakes::ccs-permits/about)
72
+ - [Seattle Land Use Permits](https://data.seattle.gov/d/ht3q-kdvx)
73
+ - [Issued Construction Permits](https://data.austintexas.gov/Building-and-Development/Issued-Construction-Permits/3syk-w9eu)
74
+ - Austin Open Data
75
+ - Chicago Data Portal
76
+ - DataLA
77
+ - DataSF
78
+ - NYC Open Data
79
+ - OpenDataPhilly
80
+ - Seattle Open Data
81
+
82
+ The source organizations publish their own records, definitions, update schedules, and terms. Review the linked source pages for source-specific attribution and licensing requirements before redistribution or commercial use. This dataset card does not replace those original terms.
83
+
84
+ ## Limitations
85
+
86
+ Coverage, field definitions, geocoding quality, status values, and update timing vary by contributing jurisdiction. Missing coordinates and missing attributes are expected. Permit issuance, approval, or record publication should not be interpreted as proof that the reported work actually occurred. Compare records over time only after accounting for jurisdictional and source-definition differences.
manifest.json CHANGED
@@ -1,6 +1,6 @@
1
  {
2
  "title": "Electrical Permit — 2018,2019,2020,2021,2022,2023",
3
- "description": "Open permits dataset from electrical_permit_permits; generated for 2018,2019,2020,2021,2022,2023.",
4
  "version": "v1",
5
  "row_count": 159257,
6
  "files": {
 
1
  {
2
  "title": "Electrical Permit — 2018,2019,2020,2021,2022,2023",
3
+ "description": "This release contains 159,257 public electrical permit records from 2018, 2019, 2020, 2021, 2022, 2023. Records preserve source-specific fields in the JSON-encoded properties column and include geospatial coordinates or geometry when available. Use it to study permit activity, development patterns, and changes over time and place.",
4
  "version": "v1",
5
  "row_count": 159257,
6
  "files": {