Case study
ExtentPad
Open KML, KMZ, Shapefile, GeoJSON, CSV and DXF files in the browser, with nothing to install. Style, edit, measure and compare them on a map, then save the result.
More detail
The problem
Most GIS work still starts in a heavy desktop app. Someone sends you a KML, a Shapefile or a DXF, and you cannot see it properly until that software is installed, licensed and set up. I wanted a workspace that opens in the browser, keeps the file on the device, and stays usable when the file is large.
ExtentPad is that workspace. You drop a file and see it on the map, with layers, styles, measurements and editing in one screen. There are no accounts, no API keys and no backend in this build. Nothing is uploaded.
Who it's for
Anyone who needs to open, inspect and tidy spatial files without firing up a desktop GIS. That includes GIS users, surveyors, land and property teams, and site scouts. The core is a general-purpose workspace I can reuse for other work later. Surveyor-specific tools can sit on top as optional add-ons, rather than defining the whole product.
What I built
A full-screen map with a docked sidebar and an inspector. No modal dialogs in the way.
- Open GeoJSON, KML, KMZ, GML, Shapefile, CSV and DXF, including several files at once.
- A virtualised Features tree that stays usable at 10,000 entities, grouped by folder or collection.
- Style and labels: file colours, colour-by-field (categories or a numeric ramp), and on-map labels.
- Edit on the map: drag a feature or its vertices, snap to nearby edges, undo and redo. Multi-select for geometry tools: buffer, merge, clip, cut out and split.
- 3D terrain, an elevation profile along a line or polygon boundary, and a street/satellite swipe compare.
- Save as GeoJSON, KML or KMZ, with styles and folders kept, plus a PNG or PDF of the current view.
Stack
Next.js 16, React 19 and TypeScript, Tailwind CSS 4 and shadcn/ui. A WebGL vector map engine in the browser, with OpenFreeMap streets, Esri World Imagery and Mapterhorn terrain. Turf.js for measurements and geometry operations, plus parsers for KML/KMZ, GML, Shapefile, CSV and DXF. Everything runs client-side.
Key decisions and why
Keep the core generic. ExtentPad started as a parcel viewer, but the useful part is a reusable GIS workspace. Parcel- and surveyor-specific ideas stay optional, so the same app can carry other kinds of work later.
Make 10,000 entities feel ordinary. The Features list is virtualised, and each row subscribes to its own store entry instead of rerendering the whole tree when one item changes. Selection highlighting uses GPU feature-state on the map, so picking a shape does not rebuild the layer data.
Commit a drag once, on release. Edit handles are custom. While you drag a vertex or a feature, the map does not pan underneath it, and the geometry is written back once when you let go, not on every pointer move.
Round-trip the file the user already has. KML and KMZ keep folder hierarchy, placemark styles and custom point icons. "Save as" writes a new dated file. The original on disk is never overwritten.
No server required. Parsing, styling, editing, 3D and export all run in the browser. That keeps files private and the deployment simple: a static front end, no database and no keys to manage.
The system
The Next.js app runs entirely in the browser. Parsers, the WebGL vector map, style, edit, 3D and export all stay on the device. There is no API and no database in this build.
How it holds up
The app is live at extentpad.vercel.app. Source is available on request.
I timed a synthetic 10,000-polygon dataset (20 collections) on the live site, in headless Chromium on a cloud VM with software graphics. A desktop GPU may paint faster; these are the numbers I actually measured, median of five runs, after the app and basemap were already loaded:
- 10,000 parcels listed in the sidebar in 0.21 s (range 0.13 to 0.28 s).
- Drawn on the map in 2.35 s (range 2.29 to 2.48 s). That includes the camera flight to the layer.
- The view settled in 3.13 s (range 2.91 to 3.20 s).
- Opening the Features tab showed the first row in 71 ms. Clicking a feature opened the inspector in a median 134 ms (five clicks, range 79 to 596 ms).
What I'd do next
- Shareable links, so a cleaned file can be sent without emailing the original.
- An "ask your parcels" assistant on top of the open layers.
- An attribute table with filters and select-by-attributes, joins, geometry check and repair, georeferencing, and GeoTIFF / WMS overlays, then Shapefile and FlatGeobuf export.
01 / Results
- 10,000 parcels listed in the sidebar in 0.21 s.
- Drawn on the map in 2.35 s, including the camera flight.
- Live at extentpad.vercel.app. Source is available on request.
Next project
One More Turn