Concepts
Data Model
Understanding the Event and Location entities.
The GlobalEventBase API revolves around two main entities: Event and Location.
Event Object
An Event represents a specific occurrence, such as a concert, conference, or festival.
| Field | Type | Description |
|---|---|---|
id | Integer | The unique internal identifier for the event. |
ts | DateTime | The timestamp when the event was indexed. |
raw_payload | JSON | The rich data payload containing event details. |
Raw Payload Structure
The raw_payload is a flexible JSON object that typically contains:
{
"title": "Event Title",
"description": "Full description of the event...",
"start_date": "2023-12-01T18:00:00Z",
"end_date": "2023-12-01T22:00:00Z",
"location": {
"venue": "Convention Center",
"city": "New York",
"country": "US",
"coordinates": {
"lat": 40.7128,
"lng": -74.0060
}
},
"categories": ["Conference", "Tech"]
}Location Object
Locations are normalized entities that events are linked to. This allows for efficient geospatial querying.
| Field | Type | Description |
|---|---|---|
id | Integer | Unique identifier. |
type | String | The type of location (e.g., Country, City). |
identifier | String | A unique string identifier (e.g., US, US/NY/New York). |
iso2 | String | The ISO 3166-1 alpha-2 country code (e.g., US). |
Relationships
- Events are associated with Locations (e.g., an event happens in a City, which is in a Country).
- This hierarchical structure enables queries like "Find all events in the US".