dwg7 in 5 Minutes

dwg7 is Domain Working Group 7 of the UN Open GIS Initiative. It works on “Smart Maps”: web maps that stay open, so that anyone can build, test, and reuse them. Its method is a public record. Each piece of work leaves a thread that runs from a question to a result and a correction. This page describes that method as it appears in the dwg7 issues on 2026-11-11. The issues are the source, and this page is a reading aid.

The method

question → experiment → result with conditions → review and correction → reuse

Read one thread, and the chain is visible. #1003 compares two map servers on a Raspberry Pi.

  1. Question. Where does a small, cheap computer reach its limit when it serves map data?
  2. Experiment. A contributor ran both servers on a Raspberry Pi 4B. The load was 4 workers sending 20 map requests each, on 5,000 random points.
  3. Result with conditions. One server in one mode served 16.9–22.5 requests per second. The other served 13.1–13.6. The thread gives versions and settings beside each number.
  4. Review and correction. A second contributor repeated the test on other operating systems and found that the result depended on a default file path. The first contributor confirmed it and corrected two earlier statements in the same thread.
  5. Reuse. A hands-on guide for an older, smaller Raspberry Pi followed. Its measurements are the open item.

Ten habits behind the method

The record shows the same habits across ten themes and about a thousand threads. Each habit has one place where you can see it.

  1. Conditions beside numbers. Hardware, versions, data, and load stand next to every figure (#1003).
  2. Hypothesis before test. A thread says “my hypothesis is” and returns later with the verdict (#567).
  3. Visible correction. A fix appears next to the claim it repairs, often as struck-through text (#642).
  4. Reasons in words. A design choice comes with its reasons, in a short list or a decision record (#642, #936).
  5. Invitation to repeat. Code and steps are public, and readers repeat them and report back (#642).
  6. Open items stay open. A thread names what remains and the condition for resuming (#567).
  7. Care for shared resources. A copy is hosted so that nobody must hit the public source repeatedly (#920).
  8. Decisions that settle. A thread closes when the idea has become part of the work (#936).
  9. Start from others’ work. A thread builds on a published article or on an issue in another project (#361, #920).
  10. Quiet observation. A thread watches a public source over time and compares two dates (#857).

Rhythm

What the work looks like now

Why this guide reads the method this way

This guide’s reading: international and public-sector geospatial work needs claims that others can verify, choices that outlast staff changes, and data that stays open. A thread that keeps its conditions, corrections, and open items gives all three. Open repositories and issues carry all three as a matter of course.

Your path in four steps

  1. Observe. Read one thread from its question to its result.
  2. Choose. Pick a friction from your own work that fits the chain.
  3. Try. Run one experiment from Good First Experiments. State your conditions.
  4. Share. Post your record as a comment or an issue, and link the thread you started from.

Onboarding Paths matches these steps to your background.

Back to index