Actual trees, not b-trees...
summary
A public database is built on PostgreSQL + PostGIS import pipeline to map trees across Germany, ingesting CSV exports from five different collection systems and cleaning issues like buildings labeled as trees and inconsistent Latin names and abbreviations. Wrong coordinate projections once put points in Somalia (wrong projection landed trees in Somalia), fixed via pgAdmin’s geometry viewer. A web front end uses GeoServer and OpenLayers, shows vitality in five colors, stores about around 3,000 trees now with 100 attributes each, and expects far larger scale and history tracking.
AI-written summary · about
chapters (14)
- 0:00Introduction and motivation
- 3:18Project goals and challenges
- 7:20Data cleaning and projections
- 9:27Database structure and normalization
- 11:38Visualization and user interaction
- 12:46Additional data layers
- 14:16Q&A: Database size and updates
- 16:30Q&A: Public accessibility
- 17:12Q&A: OpenStreetMap integration
- 18:58Q&A: Data export and tools
- 20:53Q&A: Indexing and future plans
- 21:37Q&A: Geographic expansion
- 22:40Q&A: PostGIS features used
- 23:01Q&A: Related projects and summary
related talks
21mActual trees, not b-trees: or how I found PostgreSQL through PostGIS
37mProcessing Open Street Map Data with Python and PostgreSQL
43mLocate all the things
40mGIS capability of PostgreSql using POSTGIS & OSM DATA
21mThe Open Source Geospatial Community, PostGIS, & Postgres
18mA journey in geospatial timeseries
02h 44mBuilding Geographical APIs with Open Data, PostgreSQL & PostGIS
11mA journey in geospatial timeseries