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

Location Details

The Locations Details sub-tab is located in the Locations tab. The image below shows the table with location data loaded. Each column in the table is sortable; Administrators can click on a column header to sort data. A black arrow indicates which column the data is sorted by and by what direction. Descriptions of the data in the table are below the image.


Calendar

Description automatically generated


Name:

  • 3-letter airport code, e.g. JFK or SYD

 

Latitude and Longitude:

  • Negative latitude means South, positive means North
  • Negative longitude means East, positive means West
    1. A number like 40.384 means 40 degrees, 38.4 minutes.  Therefore it is not a strict decimal number (since 40 degrees 38.4 minutes is equal to 40.64 degrees).  For example:
    2. JFK:   40.384 Latitude, 73.467 Longitude
    3. Means:        40 degrees 38.4 minutes North, 73 degrees 46.7 minutes West
    4. SYD:   -33.568 Latitude, -151.106 Longitude
    5. Means:        33 degrees 56.8 minutes South, 151 degrees 10.6 minutes East
    6. Latitude can range from -90.000 to 90.000
    7. Longitude can range from -180.000 to 180.000

UTC Offset:

  • This is the offset from UTC (GMT) when the location is not in daylight savings.
  • Negative means behind (West), e.g. JFK is -5, SYD is 10
  • NAVBLUE N-PBS only supports whole hour or half hour offsets (e.g. 10, or 10.5 or 10:30)
  • NAVBLUE N-PBS supports values ranging from -12 to 14 (because there are some locations officially between 12 and 14).

 

DST Changes:

DST changes occur at a specific date and time (e.g. 2012-03-11 02:00) and can be either ON (switching DST on) or OFF (switching DST off). DST information is contained in the last 3 columns. The middle column is the current year, the first DST column shows the DST changes before the current year and the last column shows future DST changes.

 

Location Details

Each location shows on a single row:

  • Latitude and Longitude shown in the format described in the Latitude and Longitude section above.
  • UTC Offset shown as either a whole number or a number with .5 for locations with half hour offsets.  Negative means behind (West).
  • DST Information – last 3 columns
  • DST switch ON is represented by white sun icon left to the date time
  • DST switch OFF is represented by black sun icon left to the date time
  • DST date/times show in the format as above (e.g. 2013-03-10 02:00).
  • The table has space for up to 2 DST changes before the current ­year, up to 2 changes in the current year, and up to 2 changes in the following year.
  • The DST fields (within the 6 DST columns) must adhere to DST field validation

 

DST Field Validation

NAVBLUE N-PBS will validate information when entered into the system, validation occurs when editing through the interface using Add or Edit or when importing a locations file:

For the current year and the year after the current year (2011 and 2012 in the above example), and for each year within the exported CSV file, the values in the 2 columns FIRST and SECOND must adhere to the following rules:

  • Each of the columns (FIRST and SECOND, under the given year) must contain either a valid date within that year, or must be blank.
  • If a location has 2 DST changes in the year, the date in the column FIRST must be chronologically earlier than the date in the column SECOND.  Therefore southern hemisphere locations will show the spring switch OFF in column FIRST, and the fall switch ON in column SECOND.
  • If a location has just 1 DST change in this year, it must show in the column FIRST, regardless of the actual date within the year, and the column SECOND must be blank.
  • If a location has zero DST changes in this year, both columns must be blank.


For the 2 columns BEFORE the current year on the UI (e.g. PRE-2011 in the above example), the columns SECOND LAST and LAST must adhere to the following rules:

  • Each of the columns (SECOND LAST and LAST) must contain either a valid date before the current year (e.g. 2011 or before in the above image), or must be blank.
  • Note that these 2 DST changes will usually be in the year immediately before the current year (e.g. 2011 in the above image), but they do not have to be.  (Locations which have 0 or 1 DST changes in 2011 would instead show the most recent 2 DST changes, which may come from earlier years).
  • If a location has more than 2 DST changes present in the database before the current year, then only the most recent 2 will be shown.
  • If a location has at least 2 DST changes before the current year, the date in the column SECOND LAST must be chronologically earlier than the date in the column LAST.
  • If a location has just 1 DST change (in the database) before the current year, it must show in the column called LAST (with the column called SECOND LAST being blank).

 

Did you find it helpful? Yes No

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