GIS Country Databases: Current Version Update
GIS Country Databases: Current Version Update
A location project begins with a simple question: which places are in scope? A single country may be enough for one map, delivery region, research project or business workflow. Another project may span several countries and need a set of data products that can be compared carefully. Oddity's GIS collection is organized country by country so you can begin with the location that matters, review its actual fields and coverage, and choose the database that fits the work.
This coordinated update brings 117 country geocode products together in one announcement. Turkey is outside this update and will be handled separately. The index below links directly to every product page. Each page remains the authority for its own current version, build, coverage, fields, samples, license and delivery details. The products share a release program, but they are not interchangeable. Population, available attributes, geographic detail, source vintage and practical limitations can vary by country. Read the page for the country you need rather than assuming one product's profile describes the entire collection.
Start with the country, then check the detail
The index is the quickest route to a product, but the product page is where the decision happens. Check its coverage description and full field profile. Look at the sample values and the stated limitations. Consider the geographic level your workflow expects: a country label alone does not tell you whether the available records match the streets, settlements, administrative areas or other location concepts you have in mind. Where you need a particular field, confirm that field on the exact current page before purchasing.
A project that combines countries deserves an extra pass. The field names, null rates, formats and record counts can differ. Even when two products express similar ideas, their available detail may vary. Build a small mapping of the attributes your application actually uses, then check each chosen country against it. This avoids treating a convenient column name as a promise of identical coverage. If a necessary attribute is missing from a product's current profile, plan for that difference rather than filling it by assumption.
The same care applies to freshness. Country product pages describe their own data and limitations. A coordinated release date does not mean every fact in every source was observed on that day. Use the stated vintages and product notes for decisions that depend on recency. Historical information can still be useful, but it should not be mistaken for a current observation simply because it ships in a new package.
Find the current version and the right access
Oddity offers only the most current version of each database for sale. Each updated product page identifies its own current version and build. Review those exact details on the country page before choosing a package. The announcement is a guide to the collection; it is not a substitute for the details or terms attached to a specific product.
If you purchased an earlier version, sign in to review the current offer available to your account. Prior ownership may matter for eligibility to obtain the current release. It does not itself mean a new version has been purchased or downloaded, and it does not turn an older version into another active storefront option. The offer and access shown for your account are the relevant next steps. If something looks inconsistent, use the exact product name and version when contacting support.
Before placing an order, check the live license, price, tier, package contents and delivery information for each product in your cart. The products are distinct, even when purchased together. A single order may contain several products, but each should appear as its own item with its own rights and delivered files. The same principle applies if you already have an account entitlement: confirm the country and version associated with each download.
Work with the exact delivered package
Once you have access, use the product's current Help guide for the format and field descriptions of that exact release. Keep the protected download you save, and compare it with the package description. A shared update article can explain how to navigate a collection, but it cannot replace the signed guide, release notes and field profile for each country.
If you are importing more than one database, start with a small sample of the fields your workflow needs. Verify data types, text encoding and join keys for each package. Decide how your application will handle empty values and country-specific fields. A combined map or table can be useful, but a good cross-country view is built from checked relationships, not from a guess that similarly named columns always mean the same thing. Keep the original downloaded archives so you can return to the exact release if a transformation needs review.
For visual work, test a small region before rendering the full project. Check labels, boundaries, scales and any location matching that your application performs. A geocode database supplies data; your map, search or reporting logic still determines how that data is interpreted and displayed. If your use case depends on a specific precision or coverage threshold, compare it with the current product's documented limits.
Compare coverage across borders
When a project crosses borders, start with the smallest set of countries you actually need. Open each product's current field profile and write down the columns your application requires, including the data type and examples of nonempty values. A field that exists in one country may be absent or sparsely populated in another. Check the published Distinct and Missing figures where they are provided; a column name by itself says little about how many usable values you will receive. This is especially useful for search, geocoding, address matching, territory analysis and map labeling, where a missing locality or administrative level can change the result.
Then decide where your application needs a common shape and where it should preserve country-specific detail. A shared import table can make reporting easier, but forcing every source into the same columns may discard useful information. Keep the original column names and source notes alongside your mapping. Test a few records from each country before processing the full set, and check how your workflow treats empty strings, nulls, accents and alternate place names. That small comparison is faster than discovering a mismatch after a map or search index has been built.
Keep each release traceable
If you obtain several country packages, record which current product page and version supplied each file. Keep the downloaded archives separate even if you combine their records for an application. This lets you revisit the exact field definitions, replace one country's data without rebuilding everything, and explain why two similar locations may have different attributes. For work where recency matters, compare the product's stated source dates and coverage notes instead of treating the shared announcement date as the observation date for every record. The country pages and their signed guides remain the source for those details.
One announcement, many exact products
This is one update announcement for the collection, not 117 nearly identical articles. The directory below is meant to save you time while keeping the country pages distinct. Open the countries you need, compare the actual current profiles, and follow the product-specific Help links for details. The shared GIS Help article explains the navigation and current-version approach in shorter form.
This index links to the live product routes. If a page shows a version or offer that differs from what you expected, treat the product page and your account as the place to verify access before ordering. For questions about a specific file, send support the database name and version. Do not include account passwords or private project data in a support request.






Start a useful discussion below. Your contribution will appear after staff review.