{//% unless portal.user.is_agent %} Tickets
Login Submit a Ticket News {//% endunless %}

Import / Export Location Details

The Import/Export subtab in the Locations tab allows you to import and export the Locations Details file. You can edit or add new locations and change times associated with pairings according to daylight saving times.

Graphical user interface, text, application, email 
Description automatically generated

The Location DST - Import/Export sub tab, inside the Locations tab, contains buttons for Choose File (browse), Import and Export.


CSV File Format  

The CSV file format is similar to the table seen on the Locations Details sub tab, with 1 line per location, but includes all DST records in the database, with 2 columns per year (with no concept of a current year).

A Locations CSV file always includes a header row, and can contain any number of years (including zero years).

The following is an example of a header row (with years 2010 to 2014) together with a corresponding location row:

Name,Lat,Long,UTC Offset,2010 FIRST,2010 SECOND,2011 FIRST,2011 SECOND,2012 FIRST,2012 SECOND,2013 FIRST,2013 SECOND,2014 FIRST,2014 SECOND

ERT,-14.254,23.169,-10,,,,,2012-03-10-0200-ON,2012-11-03-0200-OFF, 2013-03-09-0200-ON,2013-11-09-0200-OFF,,

The header row must contain a continuous range of years.  For example, if some locations in the database have DST records for 2010, and some have DST records for 2014, but none have DST records for 2011, then the columns 2011 FIRST and 2011 SECOND must still appear in the CSV file, even though they will be blank for every location.

The DST fields within each subsequent row must be within the same year as the corresponding field in the header row. The DST field values use the format 2012-03-10-0200-ON:

  • Either ON or OFF is appended to distinguish between DST switching ON and OFF


Import Functionality

When a Location file is imported, the import will fail (with an appropriate error message) in the following cases:

  • if the header row is not present in the valid format (described above)

  • if any record has any field which is not in the expected format (3 letters for Name, 11.345 for Lat/Long (after zero-padding, see below), -10.5 for UTC Offset, 2012-03-10-0200-ON for DST fields)

  • if any DST field is not in the correct year corresponding to the header row

  • if any DST fields do not conform exactly to the DST Field Rules.

Latitude and Longitude will be zero-padded to be in the required format.  For example, if the import file contains 5.4, this will be changed to 5.400 before being imported. This actually means 5 degrees and 40.0 minutes. 

Any Location not present in the file will be deleted from the system if it is not an active location. If it is an active location, then it will not be deleted, and an error message will show in the import report stating that it could not be deleted. Any new Location in the file will be added to the system, with the specified details.

Other Locations will be updated with any changes made to Latitude, Longitude, UTC Offset and DST. For each location being updated, all pre-existing DST records are removed, and the new set of DST records are created to match the values in the file.


When an import has completed:

Before the changes are made to the database, the import report shows on the screen, and the user is given the option to Continue or Cancel.

If they choose to Cancel, no changes are made. If they choose to Continue:

  • Changes are then made to the database

  • The user is presented with a Confirm button, which must be clicked.

  • Changes will then be immediately reflected within the table on the main Locations tab.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.