Time zone and UTC offset at a point

GET

/geo/timezone

request.sh

curl -X GET https://api.astroway.info/v1/geo/timezone?lat=49.8397&lon=24.0297 \
  -H "X-Api-Key: aw_live_..." \
  -H "Content-Type: application/json"

▸ Try it GET /geo/timezone

• Production

The IANA zone at a point and the UTC offset its clocks kept at that local date and time, from the tz database, never a fixed offset: Kyiv answers +2 in January, +3 in July and +4 on 15 May 1990, when it kept Moscow summer time. time defaults to 12:00 and matters on the day clocks change; a skipped hour resolves to the offset from before the change, a repeated one to its first occurrence. standardOffset is the smaller of the year’s offsets and isDst is true when the clock is ahead of it. Before 1970 the tz database is not reliable everywhere: if you know the local clock, send timezoneOffset to the chart instead.

Authorizations

• ApiKeyAuth

Parameters

Query Parameters

lat required

number

>= -90 <= 90

Example

49.8397

Latitude in decimal degrees, north positive.

lon required

number

>= -180 <= 180

Example

24.0297

Longitude in decimal degrees, east positive.

date

string format: date

Example

1990-05-15

Local calendar date YYYY-MM-DD at the point. Defaults to today (UTC).

time

string

default: 12:00 /^\d{2}:\d{2}(:\d{2})?$/

Example

15:30

Local clock time HH:MM or HH:MM:SS. Matters only on the day clocks change.

fields

string

Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.

Example

planets.name,planets.longitude

precision

integer

<= 15

Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.

Example

4

Responses

200

Successful calculation

Media type application/json

object

ok

boolean

data

object

latitude

number

nullable

longitude

number

nullable

timezone

string

nullable

nautical

boolean

nullable

date

string

nullable

time

string

nullable

utcOffset

number

nullable

utcOffsetText

string

nullable

standardOffset

number

nullable

isDst

boolean

nullable

Example

{
  "ok": true,
  "data": {
    "latitude": 50.45,
    "longitude": 30.52,
    "timezone": "Europe/Kyiv",
    "nautical": false,
    "date": "1990-05-15",
    "time": "15:30",
    "utcOffset": 4,
    "utcOffsetText": "+04:00",
    "standardOffset": 3,
    "isDst": true
  }
}

400

Validation error

Media type application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_INPUT",
    "message": "Validation failed: date: Date must be YYYY-MM-DD",
    "details": [
      {
        "path": "date",
        "message": "Date must be YYYY-MM-DD"
      }
    ]
  }
}

401

Missing or invalid API key

Media type application/json

Example

{
  "ok": false,
  "error": {
    "code": "INVALID_API_KEY",
    "message": "Invalid API key"
  }
}