v1.27.0

A guide can now publish its organisation units without their boundary polygons, or without any geometry.

How much geometry a Location carries

[generate.organisation_units] geometry takes one of three values:

• full (the default) publishes each Location with its position and its boundary, as it did before.
• position keeps Location.position (the DHIS2 point, or the centre of the boundary) and leaves out the location-boundary-geojson extension. Boundaries are most of a registry's size on an instance with detailed polygons, so this gives a much smaller guide that still places every organisation unit on a map.
• none publishes neither, and the run leaves geometry out of its DHIS2 read.

[generate.organisation_units]
geometry = "position"

d2w fhir init --geometry position seeds the key in a new project. Under --with-registry it goes to the registry package, which is the project that publishes the Locations. A guide that depends on a registry package is refused any value other than full, with a message pointing at the package's fhir.toml. The registry page and the guide's home page say which setting the organisation units were published under.

The organisation units page

The capture server now tells the organisation units page which setting was used.

• Under position, the map draws the organisation units as points and says the guide publishes no boundaries.
• Under none, the page has no map: the hierarchy and the details share the screen.
• The note shown when a selected organisation unit has no coordinates now blames the source it can be sure of. That is the DHIS2 instance when this project published the units, and the registry when another package did.

The reference is What goes in. A project picks up the new line in its fhir.example.toml with make update.