Drop a parcels Shapefile on the canvas, pull the zoning polygons live from PostGIS, reproject both to one CRS, and spatially join them — 80,000 parcels tagged with their zone in seconds. Parcels that straddle two zones flag themselves on the map. Export styled layers and a clean table for the planning team, then re-run the whole thing when the zoning database changes.
Ask who owns the parcels-to-zoning join and everyone points at someone else. It usually lives in a geopandas notebook a contractor wrote, half a dozen reprojection calls deep, that breaks the moment the zoning table grows a new column. Meanwhile the planning team just wants a spreadsheet that says which parcels sit in which zone and which ones straddle a zone line. On the canvas that's a handful of live nodes, and the answer is always current.
A parcels Shapefile from your county's cadastre — ours is about 80,000 lots — and read access to the PostGIS instance holding the zoning polygons. That's all: no geopandas, no shapely, no SQL beyond picking a table from a dropdown. If you don't have a PostGIS box handy, the bundled sample connection serves the same zoning layer so you can follow along.
Councils rezone. When the zoning table gets updated in PostGIS, you don't rebuild anything — the @load node reads it live, the reproject and spatial join recompute from cache, and the conflict flags shift on their own. Re-export and the planning team gets a fresh table the same afternoon, without a single line of code changing hands.
Drag the county parcels Shapefile — all 80,000 polygons — onto the canvas. The @load node reads the geometry and the full attribute table without choking, and the preview draws every lot colored by its current land-use code. The inspector shows the file's CRS so you know exactly what you're reprojecting from.
Add a second @load node pointed at your PostGIS connection and pick the zoning table from the dropdown. LSD pulls the polygons live with their geometry and SRID intact, so you're joining against the planning database of record, not a stale export. The two layers preview together, already stacked in map space.
The parcels arrive in a state-plane CRS and the zoning table in web mercator, so add a @shape reproject node and set both to a shared EPSG code. The preview snaps the layers into exact alignment, and every downstream step inherits the new projection automatically. The reprojected layers cache, so the join never warps geometry twice.
Chain a spatial-join node and set the predicate to intersects, matching each parcel to the zoning polygon it falls in. LSD tags all 80,000 parcels with their zone code in one pass, and the preview recolors the map by zone as the join completes. The joined layer is a cached intermediate the rest of the canvas reuses.
Add a filter node that flags any parcel intersecting more than one zone — the boundary straddlers the planning team actually cares about. The map lights those lots up in red while clean matches fade back, and the live count tells you exactly how many need review. Drag the overlap tolerance to ignore slivers from imperfect edges.
Style the joined layer with a zone-color palette, then wire a @deliver node that writes styled Shapefile layers plus a clean parcel-to-zone table. Export drops the layers for GIS and a flat CSV the planning team can open in a spreadsheet — parcel ID, zone, and conflict flag, no geometry. When the zoning table updates in PostGIS, re-run and both exports refresh.
Read an 80k-parcel Shapefile and pull the zoning polygons live from the PostGIS planning database.
Reproject both layers to one CRS, spatially join parcels to zones, and flag boundary conflicts.
Export zone-styled map layers and a flat parcel-to-zone table for the planning team.
Turn LiDAR terrain, rainfall GeoTIFFs, and a drainage Shapefile into a flood-risk raster, a 3D flyover, and a district report — live sliders, no scripts.
Model post-closure pit-lake rebound in LSD — krige borehole heads against a NetCDF recharge grid and deliver a live 3D drawdown model plus report.
Validate 63 LAS drillhole logs against collar surveys, krige a lithology block model, and export one glTF the whole team can open.
Build churn features from Postgres events and Parquet snapshots, catch a leaky window visually, and score the holdout with ONNX — on one canvas.
Score a million-row Parquet batch with an ONNX model — training-identical normalization, live previews, scored Parquet and metrics out.
Turn raw LAS/LAZ sweeps from a mobile robot into a nav-ready occupancy grid and 3D map — registration to export with zero scripts.
Sync CSV sensor logs with live REST telemetry, flag outliers and dropouts, and score every robot pass/fail before the field trial.
Turn folders of line-scan images and a label CSV into an ONNX defect-segmentation pipeline with overlay QA and a per-coil defect report.
Turn GeoTIFF orthomosaics into a stitched land-cover raster with per-class area stats, using tiled ONNX segmentation you can preview at every step.
Align CMM measurement points to a nominal CAD mesh, compute point-to-surface deviation, and export a color-mapped glTF model with a pass/fail report.
Resample a week of machine sensor logs, baseline each tag, and flag drift and step changes on a live dashboard with a ranked maintenance shortlist.
Join a live meter feed to 85 campus building meshes, aggregate it hourly, and paint a 3D heat-map that repaints as energy use shifts, plus a weekly report.
Drag the county parcels Shapefile — all 80,000 polygons — onto the canvas. The @load node reads the geometry and the full attribute table without choking, and the preview draws every lot colored by its current land-use code. The inspector shows the file's CRS so you know exactly what you're reprojecting from.
Chain a spatial-join node and set the predicate to intersects, matching each parcel to the zoning polygon it falls in. LSD tags all 80,000 parcels with their zone code in one pass, and the preview recolors the map by zone as the join completes. The joined layer is a cached intermediate the rest of the canvas reuses.
Add a filter node that flags any parcel intersecting more than one zone — the boundary straddlers the planning team actually cares about. The map lights those lots up in red while clean matches fade back, and the live count tells you exactly how many need review. Drag the overlap tolerance to ignore slivers from imperfect edges.
Style the joined layer with a zone-color palette, then wire a @deliver node that writes styled Shapefile layers plus a clean parcel-to-zone table. Export drops the layers for GIS and a flat CSV the planning team can open in a spreadsheet — parcel ID, zone, and conflict flag, no geometry. When the zoning table updates in PostGIS, re-run and both exports refresh.