Contributing to the Leonida Atlas

Evidence contributions

A useful correction includes the proposed place or viewpoint, a stable public source URL, its publisher, what the source visibly establishes and an evidence level that matches the claim. Proximity, memory or repeated community lore alone are not enough.

• Separate an official appearance reference from community-estimated placement.
• Keep missing coordinates unknown; never substitute zero.
• Do not infer roads, boundaries or names from neighboring landmarks.
• Include attribution and rights information for contributed material.
• Retain source identifiers and explain changes to imported records.

Code contributions and forks

Use the contribution instructions and issue tracker in the repository or fork you are working with. Include a focused description, expected behavior and relevant verification. Coordinate transforms, evidence labels and the separation between source data and personal edits must remain intact.

The public application should build and run as a guest without private credentials. Keep credentials and local configuration out of source changes. Optional integrations must remain explicit and independently configurable.

Personal annotations

Local notes and markers are a useful place to collect observations before proposing a source correction. Exporting a backup shares those annotations; it does not submit them to the project or publish a change to the source catalogue.