
What is humanitarian GIS?
The MapScaping Podcast - GIS, Geospatial, Remote Sensing, earth observation and digital geographyShow Notes
Hugo Powell, from immap.org shares his expert insights on how GIS technologies are leveraged to analyze data, visualize scenarios, and facilitate rapid decision-making during emergencies. Here are the key tools mentioned: 1. **Kobo Toolbox**: An open-source tool used for data collection in humanitarian contexts. Kobo Toolbox allows for both quantitative and qualitative data collection and is operational offline, which is crucial in areas with limited internet connectivity. It supports geospatial data collection and can be used for needs assessments in settings like refugee camps. 2. **ODK Collect**: Similar to Kobo Toolbox, ODK Collect is an open-source mobile application used for field data collection. It is widely used in humanitarian efforts for its ease of use and the capability to work offline. 3. **QGIS**: A free and open-source geographic information system used for viewing, editing, and analyzing geospatial data. Hugo notes that QGIS is core for mapping and data analysis in humanitarian operations. 4. **Tableau and Power BI**: Business intelligence tools mentioned for their use in analyzing and visualizing data. These tools help in making data-driven decisions during humanitarian operations. 5. **Humanitarian Data Exchange (HDX)**: An open platform for sharing data across crises and organizations, which helps in avoiding duplication of efforts and enhances coordination among humanitarian actors. 6. **Humanitarian OpenStreetMap Team (HOT)**: Provides crowdsourced geospatial data which is extremely valuable in humanitarian settings for its accuracy and timeliness. 7. **Esri’s Living Atlas and other Esri tools**: While not open-source, Esri’s tools are sometimes used for their comprehensive geospatial data, particularly in natural disaster contexts like earthquakes. 8. **Humanitarian Spatial Data Center**: Managed by IMAP, this tool aggregates and processes data, providing access to data, analytics, and visualization tools all in one place. It has been particularly successful in deployments like Afghanistan.
This episode was sponsored by scribblemaps.com https://youtu.be/CDkG9eS6H2M
Recommended Listening Geospatial Support For Humanitarian Emergencies A Self-Contained Environment For Open-Source Geospatial Tools GGIS Offline And In The Field The Business Of Web Maps Peer to Peer Mapping And Digital Democracy
I am working on a new project over at QuickMapTools.com and any feedback is really appreciated!
More from The MapScaping Podcast - GIS, Geospatial, Remote Sensing, earth observation and digital geography
Point clouds still feel a little bit like magic to me. You walk through a room, a city, or even just your living room with a scanner or your phone, and you can recreate it afterwards. But on their own, point clouds aren't actually that smart. So what would it mean for every single point to know not just where it is, but what it is, and how it relates to everything around it? My guest this week is Dr. Florent Poux, an adjunct professor, director of the 3D GeoData Academy, and author of 3D Data Science with Python. Florent has spent around 15 years on this one problem, and he developed the idea of the smart point cloud. And, as he pointed out just before we hit record, he's also a human, which we can't take for granted these days. In this conversation, we get into:
Cloud-Native Geospatial for Small Teams: How the Utah Geological Survey Did It What happens when a small, technical team at a state agency decides to go cloud native? They don't have terabytes of satellite imagery. They have lots of small datasets, lots of scientists and lots of people who just want to get at the data. In this episode, I talk with Marshall Robinson and Clinton Lunn from the Data Management Program at the Utah Geological Survey. They moved from a traditional ArcGIS Server setup to Postgres and GeoServer, and then to a cloud-native pipeline built on GeoParquet, PMTiles, and a STAC catalog. What I really wanted from this conversation was recipes. Picture a GIS person at a local council (say, here in New Zealand) who's curious about this stuff and needs a proof of concept to take to their manager. Where do they start? We talk about:
We already have a map. Actually, we have lots of maps. So why did Overture build another one? My guest in this episode is Amy Rose, CTO of the Overture Maps Foundation, and she makes a pretty compelling case. Overture isn't trying to replace OpenStreetMap — it sits downstream from it, and from hundreds of other sources, doing the unglamorous work of standardising all of that into something you can actually put into production. A light touch, as Amy puts it. Enough structure to be usable, not so much that the dataset starts trying to be everything for everybody. We spend a good chunk of the conversation on GERS — the Global Entity Reference System. It's a persistent ID stamped on buildings, roads, places, and addresses, which means the same building in OpenStreetMap, Google, Microsoft, and the City of Vancouver all share one identifier. If you've ever wrestled a messy spatial join into submission at 11pm, you'll understand immediately why this matters. And because Overture keeps all the source records, you're not stuck with their choice of polygon. You can go and pick your own. We also get into metadata, which Amy points out has been a dirty word for most of our careers — everybody wants it, nobody wants to write it. Except now it matters more than ever, because the biggest users of geospatial data aren't people anymore. They're machines. Humans are good at filling in missing context. Machines just produce a plausible answer and move on. That's a problem when there's critical infrastructure or human lives involved. Plus: whether "authoritative" still means anything, how signals and evidence might replace traditional contribution models, why there's no best representation of anything — only fit for purpose — and what Amy would add to Overture next if every other problem were magically solved. A really enjoyable conversation, and one that changed how I think about what a map actually is.
Republished Episode - I wanted to resurface this episode because positioning is everything, and it's a great overview of how it works.
Earlier this year I ran a small experiment called the Geospatial Launchpad — six weeks of working closely with a couple of people to help them push their geospatial projects forward. West was one of them. His project is Sentinel Bird (sentinelbird.com): an archive of every Sentinel-2 visit over the Gaza Strip since 2015, with 10-meter resolution imagery for each district, interactive comparison sliders, change-over-time timelapses, and a downloadable press pack — all free, no accounts, no paywall, licensed for anyone to use for anything. In this conversation, we get into what Sentinel Bird is, why West built it, and everything he ran into along the way — the marketing, the SEO, the feedback, all the stuff that has nothing to do with the tech but everything to do with whether a project actually goes anywhere. We talk about: