Covering posts from 0800 ET Saturday May 16 to 0800 ET Sunday May 17, 2026. Sources: 161 geospatial feeds.
Quiet day across the feeds — three posts worth your time.
1. QGIS Grant Programme 2026 Results — QGIS.org blog
The QGIS project announced nine funded proposals from its 2026 grant cycle — and in a notable departure from prior years, all proposals that cleared the discussion phase were funded without a community vote, because the budget situation allowed it. The nine QEPs read as a blueprint for QGIS 4 readiness and architectural modernization: async refactoring (QEP 422), removal of the QgsProject::instance() singleton (QEP 423), a move away from geometry shaders in the 3D renderer (QEP 424), restored print layout HTML support for QGIS 4 (QEP 420), and improved Wayland compatibility (QEP 419). The absence of a voting round is the real signal here — a healthier project treasury means fewer tradeoffs between competing proposals, which tends to accelerate technical debt paydown.
→ QGIS Grant Programme 2026 Results
2. MapAction's 'support on-demand' model — MapAction
MapAction published a piece in the RICS Land Journal on its "support on-demand" deployment model — providing flexible humanitarian mapping capacity in DRC and Myanmar at a moment when the humanitarian sector is navigating unprecedented funding cuts. The framing is explicitly about filling data gaps under resource pressure, not scaling up. The choice of the RICS Land Journal as publication venue is notable: MapAction is making the case to a property and built-environment professional audience, not a geo-sector insider one. That's either outreach or fundraising, and probably both. The DRC and Myanmar focus also puts the piece squarely in two of the most data-scarce conflict environments currently active.
→ MapAction's 'support on-demand' model
3. We now publish an Accessibility Conformance Report — OpenCage Blog
OpenCage published its first Accessibility Conformance Report after a prospective customer requested one during a sales process — prompting a round of accessibility review and remediation across the geocoding platform and docs. Worth a quick read not for the report itself but for what it reveals about enterprise procurement: accessibility compliance is now a checkbox on vendor evaluation forms, even for API services. OpenCage's transparency about the trigger (customer demand, not internal initiative) is refreshingly candid, and their framing around "usable by everyone" connects accessibility explicitly to their core service philosophy.
Powered by Neptune