This doc is Work In Progress

Starting

The generation is run via map-generator action (Actions and Admin teams have necessary permissions)

We create separate branches for each maps generation which is meant to get public, e.g. generate-260122 for a release or generate-260201-test for a public test build:

• easy to look up which commits had been in the generation
• easy to add temp / experimental changes especially for test generations

(all mapgen needed PRs should be either merged or cherry-picked to generate maps for a particular release milestone)

Monitoring

• number of generated maps https://mapgen-fi-1.comaps.app/cgi-bin/status.pl
• mapgen server resource usage https://mapgen-fi-1.comaps.app/munin/system-day.html
• mapgen output directory (including logs and ready map files) is available via https://mapgen-fi-1.comaps.app/osm-maps

Smoke testing

World*.mwm and 1-2 regional map files should be smoke tested before publishing/distributing:

• its possible to download them even before the whole generation is complete from https://mapgen-fi-1.comaps.app/osm-maps
• test search, routing, cross-mwm routing, check that isolines are present
• check the world map looks normal at a glance
• there should be no sudden big changes in files sizes

CDN upload

Run via action after maps generation is finished and smoke tests are passed.

Merging

Download the new data/countries.txt file and raise a [planet] Update map data to xxxxxx PR with it.

Raise a meta-php PR with new maps data version.