paulwynter commited on
Commit
f6d1c19
·
verified ·
1 Parent(s): 836e381

Add Build with Outerview links to dataset card

Browse files
Files changed (1) hide show
  1. README.md +194 -193
README.md CHANGED
@@ -1,193 +1,194 @@
1
- ---
2
- pretty_name: "Electrical Permit Dataset - Multi-City Building Systems Records - Outerview"
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 Dataset - Multi-City Building Systems Records - Outerview
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 **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)**, 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 **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)** geographic index.
19
-
20
- Outerview 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 Outerview API, SDK, CLI, and MCP.
23
-
24
- ### Build with Outerview
25
-
26
- * **[Geographic Feature List](https://www.embed.earth/catalog/features)** — browse geographic features available through Outerview
27
- * **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)** — 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/Outerview/electrical-permits/resolve/main/data.parquet)
87
- * [GeoJSON](https://huggingface.co/datasets/Outerview/electrical-permits/resolve/main/data.geojson)
88
- * [CSV](https://huggingface.co/datasets/Outerview/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
- **[Outerview 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 **[Outerview 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 Outerview 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 **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)**.
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
-
159
- ## License
160
-
161
- ### Dataset compilation
162
-
163
- 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.
164
-
165
- Outerview-created organization, normalization, and documentation should be attributed to Outerview. A suggested attribution is:
166
-
167
- > Outerview, “Electrical Permit Records — 2018–2023,” https://huggingface.co/datasets/Outerview/electrical-permits
168
-
169
- ### Third-party records
170
-
171
- 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.
172
-
173
- ## Limitations
174
-
175
- 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.
176
-
177
- 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.
178
-
179
- ---
180
-
181
- ## Access millions more geographic features
182
-
183
- This Hugging Face dataset contains **159,257 electrical permit records**, but it represents only one collection from Outerview's broader geographic infrastructure.
184
-
185
- **Outerview provides access to millions more geographic features and large collections of geolocated images and videos.**
186
-
187
- Search infrastructure, places, roads, buildings, environmental features, community issues, physical conditions, and other real-world observations programmatically through our API, SDK, CLI, and MCP.
188
-
189
- **[Explore Outerview →](https://huggingface.co/datasets/Outerview/electrical-permits)**
190
-
191
- **[Read the developer documentation →](https://www.embed.earth/docs)**
192
-
193
- **[Search geographic features with the SDK →](https://www.embed.earth/docs/sdk/search)**
 
 
1
+ ---
2
+ pretty_name: "Electrical Permit Dataset - Multi-City Building Systems Records - Outerview"
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 Dataset - Multi-City Building Systems Records - Outerview
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 **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)**, 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 **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)** geographic index.
19
+
20
+ <!-- outerview-tools:start -->
21
+ ## Build with Outerview
22
+
23
+ - [Geographic Feature List](https://www.outerview.ai/atlas) — browse geographic features available through Outerview
24
+ - [Outerview](https://www.outerview.ai/) — programmable infrastructure for Earth
25
+ - [Developer Documentation](https://www.outerview.ai/docs) — APIs, tools, guides, and examples
26
+ - [SDK](https://www.outerview.ai/docs/sdk) — build geographic capabilities directly into applications
27
+ - [CLI](https://www.outerview.ai/docs/cli) — work with geographic search and spatial data from the terminal
28
+ - [MCP](https://www.outerview.ai/docs/mcp) — connect geographic search and spatial tools to AI agents
29
+ <!-- outerview-tools:end -->
30
+
31
+ Outerview 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.
32
+
33
+ Developers can search and work with geographic data programmatically through the Outerview API, SDK, CLI, and MCP.
34
+
35
+
36
+ ## Dataset contents
37
+
38
+ 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.
39
+
40
+ 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.
41
+
42
+ ## Use cases
43
+
44
+ * building-system and renovation research
45
+ * electrification and infrastructure planning
46
+ * permit pipeline analysis
47
+ * neighborhood change studies
48
+ * geospatial machine learning
49
+ * urban data applications
50
+
51
+ ## Schema
52
+
53
+ 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.
54
+
55
+ | Column | Type | Description |
56
+ | --- | --- | --- |
57
+ | `id` | string | Stable identifier for the exported record. |
58
+ | `sample` | boolean | Whether this record was selected for an optional image sample. |
59
+ | `latitude` | float64 | Latitude in decimal degrees using WGS 84 when available. |
60
+ | `longitude` | float64 | Longitude in decimal degrees using WGS 84 when available. |
61
+ | `geometry_wkb` | binary | Geometry encoded as Well-Known Binary for spatial workflows. |
62
+ | `media_url` | string | URL for associated image or visual media when available. |
63
+ | `attribution` | string | Attribution information preserved from the contributing source. |
64
+ | `source` | string | Source or provider associated with the permit record. |
65
+ | `properties` | string | JSON-encoded object containing source-specific permit fields and metadata. |
66
+
67
+ ## Source-specific properties
68
+
69
+ The `properties` field preserves additional information associated with each permit record. Exact keys vary by source and record.
70
+
71
+ | Property group | Description |
72
+ | --- | --- |
73
+ | `permit_number / application_number` | Permit or application identifiers when supplied. |
74
+ | `permit_type / permit_class / work_type` | Local classifications and reported type of work. |
75
+ | `project_name / description / property_use` | Description of the project, work, or associated property. |
76
+ | `status / applied_at / issued_at / completed_at` | Lifecycle status and source milestone dates when supplied. |
77
+ | `address / city / state / postal_code` | Location text and administrative geography when supplied. |
78
+ | `applicant / contractor / owner_name` | Parties named by the source when supplied. |
79
+ | `valuation / units / floor_area` | Reported project measures when supplied. |
80
+
81
+ Not every property is populated for every record, and field names can differ between jurisdictions.
82
+
83
+ ## Download
84
+
85
+ The dataset is available in several formats:
86
+
87
+ * [Parquet](https://huggingface.co/datasets/Outerview/electrical-permits/resolve/main/data.parquet)
88
+ * [GeoJSON](https://huggingface.co/datasets/Outerview/electrical-permits/resolve/main/data.geojson)
89
+ * [CSV](https://huggingface.co/datasets/Outerview/electrical-permits/resolve/main/data.csv)
90
+
91
+ **Parquet** is recommended for analytics, data science, and large-scale processing.
92
+
93
+ **GeoJSON** is useful for GIS software, spatial databases, web maps, and geographic visualization.
94
+
95
+ **CSV** provides a simple tabular representation for general analysis.
96
+
97
+ ## Build with the data
98
+
99
+ ### Geographic search
100
+
101
+ **[Outerview Search](https://www.outerview.ai/docs/sdk)** lets developers search geographic features programmatically instead of relying only on pre-generated datasets.
102
+
103
+ Search can be used in maps, AI systems, research pipelines, monitoring tools, spatial applications, and geographic analysis workflows.
104
+
105
+ ### API, SDK, CLI, and MCP
106
+
107
+ Use the **[Outerview developer documentation](https://www.outerview.ai/docs)** to connect permit records with other geographic features, regions, roads, buildings, infrastructure, and physical-world observations.
108
+
109
+ ## Example applications
110
+
111
+ ### Urban development intelligence
112
+
113
+ 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.
114
+
115
+ ### Change over time
116
+
117
+ Use the release years as a historical baseline for studying construction activity, redevelopment, maintenance, property change, and neighborhood evolution.
118
+
119
+ ### Spatial analysis
120
+
121
+ Join records to administrative boundaries, transit, parcels, infrastructure, or other geographic features for planning and research workflows.
122
+
123
+ ### Geographic AI
124
+
125
+ Give AI systems structured, location-aware context about reported permit activity while retaining source-specific details for inspection.
126
+
127
+ ## Methodology
128
+
129
+ 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`.
130
+
131
+ 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 Outerview independently verified the permit or the work described by the record.
132
+
133
+ ## Data sources and attribution
134
+
135
+ This dataset was prepared and distributed by **[Outerview](https://huggingface.co/datasets/Outerview/electrical-permits)**.
136
+
137
+ Original or contributing sources include:
138
+
139
+ * [DOB NOW: Build Approved Permits](https://data.cityofnewyork.us/Housing-Development/DOB-NOW-Build-Approved-Permits/rbx6-tga4)
140
+ * [Building Permits](https://data.cityofchicago.org/Buildings/Building-Permits/ydr8-5enu)
141
+ * [Los Angeles Building Permits 2020-Present](https://data.lacity.org/d/gwh9-jnip)
142
+ * [Building and Safety - Building Permits Issued Between 2010 and 2019 (N)](https://data.lacity.org/d/dyxf-7hc4)
143
+ * [Building and Safety - Building Permits Issued Before 2010 (N)](https://data.lacity.org/d/e67z-kt2n)
144
+ * [Licenses & Inspections Building and Zoning Permits](https://opendataphilly.org/datasets/licenses-and-inspections-building-and-zoning-permits/)
145
+ * [CCS Permits](https://opendata.minneapolismn.gov/datasets/cityoflakes::ccs-permits/about)
146
+ * [Seattle Land Use Permits](https://data.seattle.gov/d/ht3q-kdvx)
147
+ * [Issued Construction Permits](https://data.austintexas.gov/Building-and-Development/Issued-Construction-Permits/3syk-w9eu)
148
+ * Austin Open Data
149
+ * Chicago Data Portal
150
+ * DataLA
151
+ * DataSF
152
+ * NYC Open Data
153
+ * OpenDataPhilly
154
+ * Seattle Open Data
155
+ * Vancouver Open Data
156
+
157
+ 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.
158
+
159
+
160
+ ## License
161
+
162
+ ### Dataset compilation
163
+
164
+ 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.
165
+
166
+ Outerview-created organization, normalization, and documentation should be attributed to Outerview. A suggested attribution is:
167
+
168
+ > Outerview, “Electrical Permit Records — 2018–2023,” https://huggingface.co/datasets/Outerview/electrical-permits
169
+
170
+ ### Third-party records
171
+
172
+ 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.
173
+
174
+ ## Limitations
175
+
176
+ 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.
177
+
178
+ 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.
179
+
180
+ ---
181
+
182
+ ## Access millions more geographic features
183
+
184
+ This Hugging Face dataset contains **159,257 electrical permit records**, but it represents only one collection from Outerview's broader geographic infrastructure.
185
+
186
+ **Outerview provides access to millions more geographic features and large collections of geolocated images and videos.**
187
+
188
+ Search infrastructure, places, roads, buildings, environmental features, community issues, physical conditions, and other real-world observations programmatically through our API, SDK, CLI, and MCP.
189
+
190
+ **[Explore Outerview →](https://huggingface.co/datasets/Outerview/electrical-permits)**
191
+
192
+ **[Read the developer documentation →](https://www.outerview.ai/docs)**
193
+
194
+ **[Search geographic features with the SDK →](https://www.outerview.ai/docs/sdk)**