When data can't be open
summary
Builds an Urban Observatory web client that serves aggregated neighborhood indicators while keeping source survey data protected, using GeoNode + GeoServer + PostGIS for catalog, auth and serving, an existing Leaflet prototype for the UI, and docker compose deployment with an nginx proxy. Authentication uses OAuth via GeoNode to get access tokens and enforce group permissions. Integration requires page-scraping, default credentials are insecure out of the box, containerized backups and scaling need custom work, but the system runs and controls access.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:05Why data can't be open
- 4:03Urban Observatory software stack
- 7:37Integrating GeoNode
- 10:37Deployment with Docker
- 13:30Security setup challenges
- 16:18Scalability limitations
- 17:06Q&A session
related talks
21mOpen Source framework for geospatial data discovery
01h 41mOpenStreetWhat? Mapping The World With Open Data
05mSimplifying access to OpenStreetMap data for urban planning
24mGeo+Django: Geo beyond the Django
28mReal Time GeoJSON APIs
32m"A Developer's Guide to Open Source Web Mapping Libraries"
22mSpatial Analysis and the Geoweb
01h 34mBuild a Web Map with Open Source Tools