Locations & Geocoding
How GlobalEventBase handles global locations.
GlobalEventBase uses a robust geocoding system to normalize locations and enable accurate filtering.
Supported Locations
We currently support event filtering at the Country level using ISO 3166-1 alpha-2 codes.
Common ISO2 Codes
Here are some common codes you might use:
| Country | Code |
|---|---|
| United States | US |
| United Kingdom | GB |
| Canada | CA |
| Australia | AU |
| Germany | DE |
| France | FR |
| Japan | JP |
| China | CN |
| India | IN |
| Brazil | BR |
You can find a full list of ISO 3166-1 alpha-2 codes here.
Retrieving Locations
You can retrieve a list of supported locations programmatically using our API. This is useful for populating dropdowns or validating inputs.
List All Locations
curl "https://globaleventbase.com/api/locations"Filter by Type
You can filter locations by type, such as Country or City.
curl "https://globaleventbase.com/api/locations?type=Country"For full details, check the Location API Reference.
Location Normalization
When we ingest events, we process the raw location string (e.g., "NYC", "London, UK") and resolve it to a structured Location entity in our database.
- Ingestion: Raw location data is received.
- Geocoding: We attempt to match the location to a known city and country.
- Linking: The event is linked to the resolved Location entity.
This process ensures that even if an event lists its location as "The Big Apple", it will correctly appear in searches for "New York" or "US".