Need help installing Zap Calendar? Click here for a tutorial on installing Zap Calendar, or find out how to add additional functionality to your Zap Calendar site with the dozens of add-ons available for Zap Calendar.

Zap Calendar's location feature provides grouping of events by location (also known as venues). The Location Manager in the Zap Calendar back-end allows locations to be added, updated or deleted.  A location displays information such as address and contact information, and a description. When creating an event, one can choose between entering a location text description or choosing a location from a list.  Front-end editing can be configured from the Zap Calendar global settings to only choose a location from a list, only entering a location description, or allow the user to choose.  Zap Calendar's CSV and ical import options, as well as the ical sync and Google Maps plugins, are location aware.

Importing Locations

Zap Calendar can automatically associate events to locations during the import process.  When importing events from either iCalendar or CSV feeds, locations with the same name will be grouped together if a location with that same name already exists.  For example, if your event location's description is "Yankee Stadium", and there is already a location named "Yankee Stadium" as seen in the location manager, then events with the location "Yankee Stadium" will automatically be linked to this location when imported. You will need to ensure the locations are created prior to import.

Some iCalendar feeds support the venue extension as defined in the internet draft, "Internet Calendaring and Scheduling Venue Component Specification" (see http://tools.ietf.org/html/draft-norris-ical-venue-01).  This extension defines the location details, such as address and contact information, directly in the ical file.  Zap Calendar supports iCalendar feeds using this extension for both importing and syncing using the ical sync plugin.  When a feed with this extension is imported or synced, the location is automatically created if it does not already exist and populated with the location details.  Imported events at that location are also linked to the location document.