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

Improve permit dataset card and use plural repository URL

Browse files
Files changed (1) hide show
  1. README.md +166 -60
README.md CHANGED
@@ -1,86 +1,192 @@
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.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
+ pretty_name: "Electrical Permit Records — 2018–2023"
3
+ license: other
4
+ size_categories: ["100K<n<1M"]
5
+ tags: ["geospatial", "tabular", "open-data", "urban-planning", "public-records", "semantic-search", "spatial-analysis", "parquet", "geojson", "csv", "datasets", "electrical", "building-systems", "electrification", "maintenance", "utilities", "urban", "mapping", "year-2018", "year-2019", "year-2020", "year-2021", "year-2022", "year-2023"]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
6
  ---
7
 
8
+ # Electrical Permit Records — 2018–2023
9
 
10
+ A geospatial open-data release of **159,257 electrical permit records** from 2018, 2019, 2020, 2021, 2022, 2023.
11
 
12
+ This dataset was created and distributed by **[EmbedEarth](https://embed.earth)**, programmable geographic infrastructure for searching, retrieving, and computing across the physical world.
13
+
14
+ The release contains records of permitted electrical work and related building improvements. Electrical permits provide a location-aware view of renovation, building-system upgrades, electrification activity, and reported electrical projects. Records were normalized for consistent geospatial analysis while source-specific attributes remain available for inspection.
15
+
16
+ ## Search millions more geographic features
17
+
18
+ This Hugging Face release is a downloadable dataset from the broader **[EmbedEarth](https://embed.earth)** geographic index.
19
+
20
+ EmbedEarth provides developers and AI systems access to **millions of geographic features and large collections of geolocated images and videos** spanning infrastructure, places, roads, buildings, nature, community issues, and other physical-world observations.
21
+
22
+ Developers can search and work with geographic data programmatically through the EmbedEarth API, SDK, CLI, and MCP.
23
+
24
+ ### Build with EmbedEarth
25
+
26
+ * **[Geographic Feature List](https://www.embed.earth/catalog/features)** — browse geographic features available through EmbedEarth
27
+ * **[EmbedEarth](https://embed.earth)** — programmable infrastructure for Earth
28
+ * **[Developer Documentation](https://www.embed.earth/docs)** — APIs, tools, guides, and examples
29
+ * **[Geographic Search SDK](https://www.embed.earth/docs/sdk/search)** — search geographic features and regions programmatically
30
+ * **API** — integrate geographic search and spatial data into applications
31
+ * **SDK** — build geographic capabilities directly into applications
32
+ * **CLI** — work with geographic search and spatial data from the terminal
33
+ * **MCP** — connect geographic search and spatial tools to AI agents
34
 
35
  ## Dataset contents
36
 
37
+ This release contains **159,257 geolocated permit records** from 2018, 2019, 2020, 2021, 2022, 2023. Each record represents a permit-related record reported by one of the contributing public sources. Where available, records include coordinates, geometry, permit dates, lifecycle status, project or work descriptions, source attribution, and source-specific properties.
38
 
39
+ This is a **compiled public-records dataset**, not a complete administrative inventory for every city or jurisdiction. Coverage reflects the contributing sources and their reporting practices.
40
+
41
+ ## Use cases
42
+
43
+ * building-system and renovation research
44
+ * electrification and infrastructure planning
45
+ * permit pipeline analysis
46
+ * neighborhood change studies
47
+ * geospatial machine learning
48
+ * urban data applications
49
+
50
+ ## Schema
51
+
52
+ The downloadable Parquet and CSV files use a normalized schema. Source-specific permit attributes are stored as JSON inside `properties` rather than expanded into separate top-level columns. GeoJSON exposes the same record attributes alongside each record's geometry.
53
 
54
  | Column | Type | Description |
55
  | --- | --- | --- |
56
  | `id` | string | Stable identifier for the exported record. |
57
+ | `sample` | boolean | Whether this record was selected for an optional image sample. |
58
+ | `latitude` | float64 | Latitude in decimal degrees using WGS 84 when available. |
59
+ | `longitude` | float64 | Longitude in decimal degrees using WGS 84 when available. |
60
+ | `geometry_wkb` | binary | Geometry encoded as Well-Known Binary for spatial workflows. |
61
+ | `media_url` | string | URL for associated image or visual media when available. |
62
+ | `attribution` | string | Attribution information preserved from the contributing source. |
63
+ | `source` | string | Source or provider associated with the permit record. |
64
+ | `properties` | string | JSON-encoded object containing source-specific permit fields and metadata. |
65
+
66
+ ## Source-specific properties
67
+
68
+ The `properties` field preserves additional information associated with each permit record. Exact keys vary by source and record.
69
+
70
+ | Property group | Description |
71
+ | --- | --- |
72
+ | `permit_number / application_number` | Permit or application identifiers when supplied. |
73
+ | `permit_type / permit_class / work_type` | Local classifications and reported type of work. |
74
+ | `project_name / description / property_use` | Description of the project, work, or associated property. |
75
+ | `status / applied_at / issued_at / completed_at` | Lifecycle status and source milestone dates when supplied. |
76
+ | `address / city / state / postal_code` | Location text and administrative geography when supplied. |
77
+ | `applicant / contractor / owner_name` | Parties named by the source when supplied. |
78
+ | `valuation / units / floor_area` | Reported project measures when supplied. |
79
+
80
+ Not every property is populated for every record, and field names can differ between jurisdictions.
81
+
82
+ ## Download
83
+
84
+ The dataset is available in several formats:
85
+
86
+ * [Parquet](https://huggingface.co/datasets/EmbedEarth/electrical-permits/resolve/main/data.parquet)
87
+ * [GeoJSON](https://huggingface.co/datasets/EmbedEarth/electrical-permits/resolve/main/data.geojson)
88
+ * [CSV](https://huggingface.co/datasets/EmbedEarth/electrical-permits/resolve/main/data.csv)
89
+
90
+ **Parquet** is recommended for analytics, data science, and large-scale processing.
91
+
92
+ **GeoJSON** is useful for GIS software, spatial databases, web maps, and geographic visualization.
93
+
94
+ **CSV** provides a simple tabular representation for general analysis.
95
+
96
+ ## Build with the data
97
+
98
+ ### Geographic search
99
+
100
+ **[EmbedEarth Search](https://www.embed.earth/docs/sdk/search)** lets developers search geographic features programmatically instead of relying only on pre-generated datasets.
101
+
102
+ Search can be used in maps, AI systems, research pipelines, monitoring tools, spatial applications, and geographic analysis workflows.
103
+
104
+ ### API, SDK, CLI, and MCP
105
 
106
+ Use the **[EmbedEarth developer documentation](https://www.embed.earth/docs)** to connect permit records with other geographic features, regions, roads, buildings, infrastructure, and physical-world observations.
107
 
108
+ ## Example applications
109
 
110
+ ### Urban development intelligence
111
 
112
+ Map permit activity by place and time, compare reported work across jurisdictions, and combine permit records with buildings, roads, land use, neighborhoods, and other geographic context.
 
 
113
 
114
+ ### Change over time
115
 
116
+ Use the release years as a historical baseline for studying construction activity, redevelopment, maintenance, property change, and neighborhood evolution.
117
 
118
+ ### Spatial analysis
119
 
120
+ Join records to administrative boundaries, transit, parcels, infrastructure, or other geographic features for planning and research workflows.
121
 
122
+ ### Geographic AI
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
123
 
124
+ Give AI systems structured, location-aware context about reported permit activity while retaining source-specific details for inspection.
125
+
126
+ ## Methodology
127
+
128
+ The release combines public permit records from contributing municipal and regional open-data sources for 2018, 2019, 2020, 2021, 2022, 2023. Records are normalized into a common geospatial structure while source-specific values remain in `properties`.
129
+
130
+ Matching, classification, date interpretation, geocoding, and field availability can differ by source. Inclusion means that a record was present in a contributing public dataset; it does not mean that EmbedEarth independently verified the permit or the work described by the record.
131
+
132
+ ## Data sources and attribution
133
+
134
+ This dataset was prepared and distributed by **[EmbedEarth](https://embed.earth)**.
135
+
136
+ Original or contributing sources include:
137
+
138
+ * [DOB NOW: Build Approved Permits](https://data.cityofnewyork.us/Housing-Development/DOB-NOW-Build-Approved-Permits/rbx6-tga4)
139
+ * [Building Permits](https://data.cityofchicago.org/Buildings/Building-Permits/ydr8-5enu)
140
+ * [Los Angeles Building Permits 2020-Present](https://data.lacity.org/d/gwh9-jnip)
141
+ * [Building and Safety - Building Permits Issued Between 2010 and 2019 (N)](https://data.lacity.org/d/dyxf-7hc4)
142
+ * [Building and Safety - Building Permits Issued Before 2010 (N)](https://data.lacity.org/d/e67z-kt2n)
143
+ * [Licenses & Inspections Building and Zoning Permits](https://opendataphilly.org/datasets/licenses-and-inspections-building-and-zoning-permits/)
144
+ * [CCS Permits](https://opendata.minneapolismn.gov/datasets/cityoflakes::ccs-permits/about)
145
+ * [Seattle Land Use Permits](https://data.seattle.gov/d/ht3q-kdvx)
146
+ * [Issued Construction Permits](https://data.austintexas.gov/Building-and-Development/Issued-Construction-Permits/3syk-w9eu)
147
+ * Austin Open Data
148
+ * Chicago Data Portal
149
+ * DataLA
150
+ * DataSF
151
+ * NYC Open Data
152
+ * OpenDataPhilly
153
+ * Seattle Open Data
154
+ * Vancouver Open Data
155
+
156
+ Where available, record-level attribution, source information, and source URLs are preserved in the exported records. Users should retain applicable attribution and comply with the terms established by each original source.
157
+
158
+ ## License
159
+
160
+ ### Dataset compilation
161
+
162
+ This release is a compiled and normalized collection of public records. The source metadata does not provide one uniform machine-readable license covering every contributing jurisdiction, so the front matter uses `other` rather than asserting a single license for all underlying records.
163
+
164
+ EmbedEarth-created organization, normalization, and documentation should be attributed to EmbedEarth. A suggested attribution is:
165
+
166
+ > EmbedEarth, “Electrical Permit Records — 2018–2023,” https://embed.earth.
167
+
168
+ ### Third-party records
169
+
170
+ The compilation attribution above does not replace, expand, or override licenses, terms, attribution requirements, or access conditions attached to third-party records. Users are responsible for reviewing the linked source pages before redistribution or commercial use.
171
 
172
  ## Limitations
173
 
174
+ Coverage depends on the contributing jurisdictions, their publication policies, their geographic coverage, and their update schedules. Field definitions, status values, date semantics, geocoding quality, and completeness vary across sources.
175
+
176
+ A permit record describes what a source reported. Permit issuance, approval, or publication should not be interpreted as proof that construction, demolition, installation, occupancy, or other work actually occurred. Applications requiring authoritative project or compliance decisions should independently verify the relevant record with the responsible jurisdiction.
177
+
178
+ ---
179
+
180
+ ## Access millions more geographic features
181
+
182
+ This Hugging Face dataset contains **159,257 electrical permit records**, but it represents only one collection from EmbedEarth's broader geographic infrastructure.
183
+
184
+ **EmbedEarth provides access to millions more geographic features and large collections of geolocated images and videos.**
185
+
186
+ Search infrastructure, places, roads, buildings, environmental features, community issues, physical conditions, and other real-world observations programmatically through our API, SDK, CLI, and MCP.
187
+
188
+ **[Explore EmbedEarth →](https://embed.earth)**
189
+
190
+ **[Read the developer documentation →](https://www.embed.earth/docs)**
191
+
192
+ **[Search geographic features with the SDK →](https://www.embed.earth/docs/sdk/search)**