Data & verification policy
তথ্য ও যাচাই নীতি
The rules below decide which information Elaka360 shows and which it does not. The key point: next to every piece of information it says which source it came from and whether it has been verified.
The four evidence levels
From a primary government source (gazette, LGD, BBS, or a government register or portal).
From a reliable secondary source (e.g. Wikipedia, newspapers, census compilations); not officially verified.
From a community dataset or a user submission; not yet verified.
Not yet checked against any source.
The word “verified” is used only for officially verified information. So far, no information has reached this level.
Sourced versus not-yet-verified information
A piece of information counts as “Sourced” (publishable) only when:
- its evidence level is “Officially verified” or “Secondary source”, and
- the name of the source it was taken from (and a link where possible) is recorded.
The rest of the information is shown too, so that you can find your own area and point out errors. But every such page carries a “Not verified” warning at the top, and search engines are not allowed to index it. Emergency hotlines are never shown without a source, and any future Open Data export will contain only sourced information. These rules are enforced at the database level.
Why most upazilas and unions are “Not verified”
The lists of divisions, districts and city corporations were checked against secondary sources and published. But the full list of the levels below the district (upazilas, unions) came from a community dataset, in which some new upazilas and unions are missing or in the wrong place. Until they have been checked against the official list, they are shown as “Not verified”.
Exceptions: as part of the Rajshahi pilot, the upazilas of Rajshahi District, and a few areas for which a separate source was found, are sourced.
About the population figures
Population figures are taken from the BBS Census 2022 (via the citypopulation.de compilation), but not on the same basis at every level: adjusted figures are used for divisions and districts, and enumerated figures for the upazilas of Rajshahi District. So the upazila figures may not add up exactly to the district total.
How corrections work
- If you see an error, tell us through the contact form, or sign in and send a correction — with a source for the correct information.
- A reviewer on the Elaka360 team looks at the source and approves the suggestion, asks for changes or rejects it.
- If approved, the information is updated and the new source is shown with it. A record of changes is kept.
See the detailed rules in the contribution guidelines.
Sources of published information
This list is generated from the dataset of this version of the site.
Sources of information awaiting verification
Known gaps
Gaps in the dataset that we know about, and the plans to fill them (from the project’s quality-check list):
~33–40 unions missing vs the official 4,571–4,578 (seed has 4,538 after removing 3 duplicates). All unions are community data and not published.
Planned fix: Import the LGD/BBS union list and reconcile by geocode.
No record has official (Tier 1) evidence yet; published areas and places rest on secondary sources.
Planned fix: Verify against LGD/BBS/gazette sources in the admin verification centre.
Seed and Consolidated Master v3.0 differ in Sirajganj (82 vs 83), Bogura (Gabtali/Sonatala), Rajshahi Bagha (Chakrajapur) and Chapainawabganj (5 names each way).
Planned fix: See docs/data/UNRESOLVED_CONFLICTS.md; resolve with primary evidence.
New upazilas Eidgaon, Madhyanagar, Dasar and Guimara have 0 unions; their unions still sit under the parent upazilas (Naldanga fixed Nov 2026 from the Natore district portal).
Planned fix: Re-parent unions per the creation gazettes.
Shayestaganj union and Nurpur were moved to Shayestaganj Upazila; Brahmandura was added without a source id.
Planned fix: Confirm against LGD.
No coordinates or boundaries for upazilas/unions.
Planned fix: Use the BBS/HDX admin boundary sets (ADM3/ADM4).
BBS geocodes are filled for divisions only.
Planned fix: Add district/upazila/union geocodes from BBS.
Only Rajshahi District's 14 pourashavas are listed, and that list is unverified.
Planned fix: Import the LGD pourashava list (330).
No wards, mouzas or villages.
Planned fix: BBS mouza/village lists.
District areas are computed from boundary polygons (approximate).
Planned fix: Replace with BBS official areas.
District/division population uses the 2022 adjusted figures; Rajshahi upazilas use enumerated figures.
Planned fix: Choose one basis app-wide.
Only 8 pilot places; 3 are unverified and have no coordinates.
Planned fix: Field verification + OSM import.