Where the bloody hell are you? GIS in Go
summary
Description of GIS practicalities and pitfalls with concrete numbers and tools: coordinates often arrive as lon/lat or UTM with mixed datums and Australia shifts about 7 cm per year so older data sits ~30 cm off; projections (Web Mercator vs Lambert/Albers) change area calculations; polygon validity errors routinely break analysis — examples include invalid polygons causing internal fire starts in bushfire models. Toolchain used: PostGIS + GEOS + GDAL, Go libraries (Pol Mach Ob, GoGeom, peterj/simplefeatures) and raster limits like a 24 GB DEM at 30m and rasters with 166+ bands.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 1:04What is GIS and geographic data
- 3:35Geographic data structures
- 7:24Validating polygon rules
- 10:11Go libraries for GIS
- 14:02PostGIS and spatial functions
- 17:35Raster data in GIS
- 21:46Raster challenges and solutions
- 22:27Conclusion and contact
related talks
19mThe Power of GeoDjango
54mGeoDjango
45mMapping the Future: The Intersection of Geospatial, Open Source, and Open Data
30mSpatial data and GeoDjango
22mSpatial Analysis and the Geoweb
46mDiscovering 40 Geo-APIs in 40 Minutes
52mThe Location of Things from A to (X,Y,Z)
26mWhy are coordinate transformations so confusing?