Data Sources

Source transparency matters for developer trust. This page explains where each dataset comes from and how it is maintained.

Postcodes

Source: MHNahib/bangladesh-postcodes-npm (MIT)
Update Cadence: Imported from a community dataset; reviewed before changes are applied.
Notes: 733 entries mapped to district IDs. Community reference data is marked verified: false; confirm delivery details with the postal service.

Geo data

Source: github.com/nuhil/bangladesh-geocode
Update Cadence: Seeded into Supabase; refreshed manually when upstream changes are reviewed.
Notes: Provides divisions, districts, upazilas, unions, and district coordinates.

Prayer times

Source: adhan-js calculation
Update Cadence: Calculated per request and cached for 1 hour.
Notes: Uses district coordinates or supplied coordinates with Asia/Dhaka output.

Holidays

Source: Curated JSON
Update Cadence: Updated annually after public holiday lists are confirmed.
Notes: Current data is intentionally explicit and reviewable.

Exchange rates

Source: Bangladesh Bank
Update Cadence: Imported daily by Vercel Cron at 06:00 Bangladesh time.
Notes: Stored in Supabase and cached for public API requests.

Mobile operators

Source: Maintained static prefix list
Update Cadence: Updated when BTRC/operator prefix allocation changes.
Notes: Covers 013-019 Bangladesh mobile prefixes.

Bangladesh encyclopedia

Source: Wikipedia, Bengali Wikipedia, curated seed data, and admin-reviewed enrichment
Update Cadence: Expanded by import scripts and checked by weekly data-quality cron.
Notes: Records expose source, source_url, verified, and needs_image so developers can decide how strict their app should be.

Verified vs Unverified

BDApi4All is transparent by design. Every encyclopedia record carries review fields so apps can show only verified records, include unverified records with a badge, or build their own moderation workflow.

verified: true: The record has a source-backed URL from an enrichment/import pipeline or admin review. It is still open to correction if a better official source appears.
verified: false: The record is useful as seed/reference data, but it needs manual review before being treated as authoritative.
source: Identifies where the record came from, such as wikipedia, wikipedia_search, google_books, open_library, curated_seed, or ai_generated.
needs_image: True means no confirmed reusable image URL is attached yet. The API does not invent image URLs.