01 / PURPOSE

Question and purpose

This record explains how to inspect and reproduce BY Maps: not as a forecast, but as a documented set of sources, transformations, and comparability limits. The research question remains separate from a scenario and from the visual layer.

02 / SOURCES

Source and input registry

The input registry should name the source series, its date and definition, the data version used, and every transformation before a result is published. The repository is the point for independent inspection; licence and current status must be checked at the source.

Before comparison, the record should state which series answers which question, the period and territorial level it covers, and what has been excluded. A visible repository link supports inspection, but by itself does not establish data completeness, reuse rights, or the currency of a branch.

03 / METHOD

Method steps

Sources are normalised while preserving date, definition, and transformation. Packages should include a version, checksums, and reproduction instructions.

The method steps are: define the observation, identify the input version, describe each transformation, check comparability, and separate an observational result from a scenario. Each step should leave a trace that lets a reviewer inspect a change after data or code are updated.

03A / EXAMPLE

Worked verification example

A BY Maps reproduction example begins with one published series and one identified territorial level, not a finished chart. Record the access date, version identifier, population definition, and transformation used. If joining two series requires manually matching boundaries or definitions, show the result as a conditional variant and retain the source values alongside the calculation.

04 / TEST

Validation and negative cases

Validation checks whether territorial units and statistical definitions are comparable, as well as missing data, boundary changes, and partially covered series. A result must not conceal where observation becomes a conditional scenario.

05 / REPRODUCE

Reproduction instructions

To reproduce the material, obtain the identified data and code version, run the described transformations, and compare the outcome with the documented version. A discrepancy should be recorded as a control result, not smoothed away in a final graphic.

06 / VERSION

Version and change record

The record version is tied to data and code versions. A source, definition, or transformation change requires a new entry and a renewed limitations check rather than a silent chart replacement.

07 / LIMITS

Limitations

Comparability changes with administrative boundaries and statistical definitions.

Reproduction does not remove source limitations. Different population definitions, gaps in a series, or boundary changes may limit comparison even when code runs without error. That limitation belongs next to the result rather than in an invisible technical footnote. The record helps inspect the described result within its boundaries; it is not a finished forecast, explanation of a trend’s causes, or substitute for a new source analysis.

08 / CITE

Citation

A citation should include the title, version, update date, and URL. This record does not grant a licence to external data or verify facts that are absent from the registered material.

DOBROVOLA. BY Maps — data and method. Version 1.0, 2026-08-02.

BibTeX

@dataset{dobrovola2026bymapsdataandmethod,
  author = {DOBROVOLA},
  title = {BY Maps — data and method},
  year = {2026},
  version = {1.0},
  url = {https://dobrovola.dev/en/research/by-maps-data-and-method}
}

Open the source artifact