Kerr County Geojson Collection
This collection includes geographic boundary files in geojson format for Kerr County. There is a complete Kerr County polygon plus fifteen 20 km tiles to be used with geospatial analyses. Additionally there are two jupyter notebooks that can be used to split other polygons and reassemble output results. A description (from Claude.ai) describing what the notebooks do is posted below:
Architecting a fishnet grid with UTM alignment for consistent tiling
The notebook is done and tested against a Kerr County boundary file. The notebook is a clean notebook that can be run by a user; the second is the executed version with Kerr County data so users can see the outputs and maps without running anything; the zip contains the 15 Kerr County tiles the notebook produced at 20 km, ready to feed into the Risk Analyzer or other analytical workflows one at a time.
The key design choice is that the grid is snapped to a fixed global origin in an equal-area CRS (EPSG:5070), not to the county's bounding box. Tile edges always land on exact multiples of the tile size, which gives you three things: any AOI you cut later (a neighboring county, a watershed) falls on the same grid; the clipped tiles union back to the original polygon with zero gaps or overlaps (the notebook verifies this — Kerr County passes at 0.000000 km² symmetric difference); and if a particular tile still chokes on the NASA download or other input file downloads, users can re-cut just that tile at half the size and the sub-tiles nest exactly inside it. Tile IDs like kerr_county_c-0016_r+0038 encode the global grid column/row, so the same ID always refers to the same square of ground.
The reassembly section (Section 7) watches a results folder — as a user runs tiles through the Risk Analyzer, drop each output GeoJSON in there named with its tile ID, and the notebook stitches them into one combined map and merged GeoJSON. Until you have real results it runs in a demo mode with synthetic risk scores so you can see what the reassembled choropleth will look like. Once you know the Risk Analyzer's output schema, set RESULT_VALUE_FIELD to the risk attribute name and it becomes a real choropleth. There's also a MIN_AREA_FRAC knob if the tool rejects tiny edge slivers, and a one-line change noted at the bottom if it turns out the Analyzer prefers full rectangles over county-clipped shapes.
About the BOUNDING BOX for KERR COUNTY:
Here are two paste-ready options for the CKAN spatial extra. Both are bare GeoJSON geometry objects (not Features or FeatureCollections), which is what ckanext-spatial expects, in WGS84 with lon/lat ordering.
Option 1 — simplified county boundary (recommended). The original file has 482 vertices; I simplified it to 11 with ~500 m tolerance (99.7% shape fidelity, validity checked), so it's compact enough for a metadata field but still renders as recognizably Kerr County on the dataset page map:
json {"type":"Polygon","coordinates":[[[-99.301,30.1359],[-98.9201,30.1383],[-98.9177,29.7814],[-99.1763,29.895],[-99.2796,29.9042],[-99.6912,29.9086],[-99.6899,30.0739],[-99.7576,30.0741],[-99.7541,30.2907],[-99.3017,30.2866],[-99.301,30.1359]]]}
Option 2 — bounding box, if you'd rather keep it minimal (spatial search results are identical either way, since CKAN's default spatial backend indexes the bounding box anyway):
json {"type":"Polygon","coordinates":[[[-99.7576,29.7814],[-98.9177,29.7814],[-98.9177,30.2907],[-99.7576,30.2907],[-99.7576,29.7814]]]}
In the dataset form this goes into a custom field/extra with key spatial and one of the above as the value; via the API it's "extras": [{"key": "spatial", "value": ""}]. The only visible difference between the two is what draws on the dataset's map preview — the simplified boundary looks better for a county-level dataset on DataX.
Dataset extent
Data and Resources
-
Kerr_County.geojsonGeoJSON
Kerr County Line Boundaries as a geojson polygon
-
KerrCounty20kmTiles.zipZIP
-
Geojson Tiler Notebookipynb
GeoJSON Tiler for Risk Analyzer Workflows is a Python Jupyter notebook that...
-
Geojson Tiler Notebook with Kerr County exampleipynb
This is the geojson tiler notebook executed with an example from Kerr county...
-
tile_index.geojsonJSON
Resulting geojson index from Kerr County Texas Tiler app.
-
tile_index.csvCSV
Generic geojson index spreadsheet for use with the Tiler app.
-
kerr_county_c-0019_r+0040.geojsonJSON
-
kerr_county_c-0019_r+0039.geojsonJSON
-
kerr_county_c-0018_r+0040.geojsonJSON
-
kerr_county_c-0018_r+0039.geojsonJSON
-
kerr_county_c-0018_r+0038.geojsonJSON
-
kerr_county_c-0017_r+0040.geojsonJSON
-
kerr_county_c-0017_r+0039.geojsonJSON
-
kerr_county_c-0017_r+0038.geojsonJSON
-
kerr_county_c-0016_r+0040.geojsonJSON
-
kerr_county_c-0016_r+0039.geojsonJSON
-
kerr_county_c-0016_r+0038.geojsonJSON
-
kerr_county_c-0016_r+0037.geojsonJSON
-
kerr_county_c-0015_r+0039.geojsonJSON
-
kerr_county_c-0015_r+0038.geojsonJSON
-
kerr_county_c-0015_r+0037.geojsonJSON
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Choose Analysis Type:
Problem Statement:
Existing Problem Statements:
Create New Problem Statement:
Analysis Configuration:
Initializing analysis...
Additional Info
| Field | Value |
|---|---|
| Source | |
| Version | |
| Author | Suzanne A Pierce |
| Author Email | Suzanne A Pierce |
| Maintainer | Suzanne A Pierce |
| Maintainer Email | Suzanne A Pierce |
| Temporal Coverage Start | 2025-07-01 |
| Temporal Coverage End | |
| Spatial Coverage | {"type":"Polygon","coordinates":[[[-99.7576,29.7814],[-98.9177,29.7814],[-98.9177,30.2907],[-99.7576,30.2907],[-99.7576,29.7814]]]} |