Submit feedback / data corrections

Found a boundary drawn wrongly, a year that does not line up, an attribute code problem, or want a new feature? Describe it here and we will work through every report. Data corrections are the most welcome kind of feedback on this site.

Name the entity: country (ISO3 or name) + administrative level (ADM0/1/2) + year — this makes triage 10× faster.
Provide evidence: a link to a national statistics office, government gazette or authoritative dataset speeds things up enormously.
State the expectation in one sentence: what is wrong now, what it should be, and on what basis.

Feedback type

Pick the closest one; if unsure, choose “Other”.

Data correctionBoundary, attributes or code that do not match reality

Missing country or yearAn entity or year has no data

Inaccurate boundaryWrong shape, offset or missing geometry

Attribute or code errorNames, ISO3/HASC codes, source fields

Feature requestNew needs for the website, downloads or map

OtherNone of the above

Entity involvedoptional, but strongly recommended for data reports

Country / territory (ISO3 or name, searchable)

Start typing and choose from the suggestions, e.g. BRA, Brazil. If it is not listed you can type it manually.

Administrative level

ADM0 = country boundary, ADM1 = first-level, ADM2 = second-level (municipality/district).

Data year

The year the geometry or attributes represent, e.g. 2022.

Description of the problem

Please cover three things: current state (what is wrong), what it should be, and evidence. Example: in ADM1, the western boundary of “Mato Grosso do Sul” sits about 15 km east of the official IBGE 2022 boundary; evidence is the municipios layer on the IBGE website (link below).

{n} characters (at least {min} characters)

A link to an official source speeds things up enormously. A page or direct link from a government statistics office, official gazette or authoritative dataset (IBGE, DANE, geoBoundaries …).

This site is purely static and cannot receive file uploads. Upload your screenshot to an image host first (GitHub images, Imgur, SM.MS …), then paste the direct image URL here. You can also drag and drop images straight into the GitHub issue editor.

Leaving an email helps us follow up. Note: if you submit via GitHub issue this email becomes publicly visible; leave it blank if you prefer. We use it only to discuss this feedback.

Anti-spam check

No backend here, so an arithmetic question and hidden fields keep bots out.

3 + 4 = ?

Enter the result as digits.

As you type, your content is saved automatically in your browser’s localStorage, so nothing is lost even if the network fails; you can export JSON from “My previous feedback” at the bottom of the page.

View my previous feedback

The records below are stored in your browser (localStorage); our servers cannot see them and they disappear if you switch browsers or clear the cache. Export JSON if a submission fails or you want an archive.

No records yet.

This page needs JavaScript to submit. You can enable it temporarily in your browser settings, or use one of these routes instead:

Open an issue directly on GitHub: https://github.com/YOUR_GH_USERNAME/gtamap/issues/new (replace YOUR_GH_USERNAME with the repository owner).
Send an email to the site contact address with the subject [GTAmap feedback] country + level + year.

Submit feedback / data corrections

Submission result