Azure Maps byCoordinates api call GMT issue

Question

Azure Maps byCoordinates api call GMT issue

Murphy, Ciaran 5

Hi there,

I'm leveraging the timezone/byCoordinates api call to convert lat and long coordinates to a time zone.

I've ran across an issue when hitting the api call with coordinates located in Ireland 53.3498,-6.2603. GMT is returned with a daylight saving time of -1:00:00 and IST is returned with daylightSavingTime of 00:00:00. My expectation was that GMT was going to be a daylightSavings of 00:00:00.

When hitting the api with coordinates of London (51.507351,-0.12775) the api returns as I expected. GMT has a daylight of 00:00:00 and BST has a daylightSavings of 01:00:00

Is this the expected behavior of the api call byCoordinates?

Thanks

Ciaran

Manas Mohanty 3,110 Microsoft External Staff

Hi Murphy, Ciaran

Currently, both UK and Ireland are 1 hour ahead of GMT.

(UTC+1)

Assuming UTC was 13:18:52 at time of testing, here was my output for both co-ordinates given.

Time Zone Name: GMT Standard Time (GMT) Standard UTC Offset: -0:00 Daylight Saving Offset: 1:00 Local Time: 2025-04-04T14:18:52 Time Zone Display Name: GMT Daylight Time



bing_maps_key = "<bingmapskey>"
datetime_utc = "2025-04-04T12:14:57Z"  # Example UTC datetime

import requests

# Define API endpoint and parameters
latitude = 51.507351  # Example latitude (Dublin, Ireland) 51.507351
longitude = -0.12775 # Example longitude

datetime_utc = "2025-04-04T13:18:52Z"  # Example UTC datetime

# Construct URL with parameters
point = f"{latitude},{longitude}"
url = f"https://dev.virtualearth.net/REST/v1/TimeZone/{point}?datetime={datetime_utc}&key={bing_maps_key}"

# Send request
response = requests.get(url)

# Process response if successful
if response.status_code == 200:
    data = response.json()
    resources = data.get("resourceSets", [])[0].get("resources", [])

    if resources:
        time_zone_info = resources[0].get("timeZone", {})
        generic_name = time_zone_info.get("genericName", "N/A")
        abbreviation = time_zone_info.get("abbreviation", "N/A")
        utc_offset = time_zone_info.get("utcOffset", "N/A")
        converted_time = time_zone_info.get("convertedTime", {})
        local_time = converted_time.get("localTime", "N/A")
        utc_offset_with_dst = converted_time.get("utcOffsetWithDst", "N/A")
        time_zone_display = converted_time.get("timeZoneDisplayName", "N/A")

        print(f"Time Zone Name: {generic_name} ({abbreviation})")
        print(f"Standard UTC Offset: {utc_offset}")
        print(f"Daylight Saving Offset: {utc_offset_with_dst}")
        print(f"Local Time: {local_time}")
        print(f"Time Zone Display Name: {time_zone_display}")

    else:
        print("No time zone data available.")
else:
    print(f"Error: {response.status_code}, {response.text}")

Please let us know if we are on same page on this issue (1hr is standard offset not daylight saving) and share your code as well to replicate the issue at our side.

Note

The Bing maps Find Time Zone - Bing Maps | Microsoft Learn is set to be deprecated by June 30. So,Please use Azure Maps instead.

Attached sample code in Azure Maps for reference.

import requests

# Define API endpoint and parameters
latitude = 51.507351  # Example latitude (Dublin, Ireland) (51.507351,-0.12775
longitude = -0.12775  # Example longitude
api_key = "<azure map key>"

url = f"https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&query={latitude},{longitude}&subscription-key={api_key}"

# Send request
response = requests.get(url)

# Check response status and print result
if response.status_code == 200:
    print(response.json())  # Parsed JSON response
else:
    print(f"Error: {response.status_code}, {response.text}")

Please let us know if it helps or convey any feedback.

Thank you

Murphy, Ciaran 5

Apologies im using azure maps.

The azure maps for dublin Ireland return the following TimeTransitions

{

      "Tag": "IST",

      "StandardOffset": "01:00:00",

      "DaylightSavings": "00:00:00",

      "UtcStart": "2025-03-30T01:00:00Z",

      "UtcEnd": "2025-10-26T01:00:00Z"

    },

    {

      "Tag": "GMT",

      "StandardOffset": "01:00:00",

      "DaylightSavings": "-01:00:00",

      "UtcStart": "2025-10-26T01:00:00Z",

      "UtcEnd": "2026-03-29T01:00:00Z"

    },

compared to for london

{

      "Tag": "BST",

      "StandardOffset": "00:00:00",

      "DaylightSavings": "01:00:00",

      "UtcStart": "2025-03-30T01:00:00Z",

      "UtcEnd": "2025-10-26T01:00:00Z"

    },

    {

      "Tag": "GMT",

      "StandardOffset": "00:00:00",

      "DaylightSavings": "00:00:00",

      "UtcStart": "2025-10-26T01:00:00Z",

      "UtcEnd": "2026-03-29T01:00:00Z"

    }

As you see from above when querying the azure maps api for a location in dublin GMT comes back with a StandardOffset of 1 and DaylightSavings of -1. Where as for London GMT StandardOffset and DaylightSavings are both 0

GMT does not have any offsets or daylight saving so it looks like the response form the api using a latitude and longitude for a location in dublin Ireland is incorrect.

Manas Mohanty 3,110 Reputation points Microsoft External Staff

2025-04-07T03:59:19.7533333+00:00

Hi Murphy, Ciaran

Could you share the azure maps code for replicating the above results.

Thank you.
Murphy, Ciaran 5 Reputation points

2025-04-07T08:15:59.5033333+00:00

Yeah sure thing.

For dublin - https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&subscription-key={APIKEY}&options=all&query=53.3498,-6.2603&language=en

For london - https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&subscription-key={APIKEY}&options=all&query=51.507351,-0.127758&language=en
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-07T11:29:06.32+00:00
Hello Murphy, Ciaran,

StandardOffset refers to the UTC offset in effect at the ReferenceUTCTimestamp.

DaylightSavings represents the time adjustment (in minutes) in effect at the ReferenceUTCTimestamp.

I tried using your coordinates (53.3498, -6.2603) but received incorrect data for both StandardOffset and DaylightSavings, showing GMT incorrectly.

Sample expected results:

"TimeTransitions": [ { "Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-03-30T01:00:00Z", "UtcEnd": "2025-10-26T01:00:00Z" }, { "Tag": "GMT", "StandardOffset": "00:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-10-26T01:00:00Z", "UtcEnd": "2026-03-29T01:00:00Z" }, { "Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2026-03-29T01:00:00Z", "UtcEnd": "2026-10-25T01:00:00Z" } ]

I believe this is a bug. Please report the issue through the Azure Maps feedback channels.

Kindly review the documented process for submitting comments on map data here:

Azure Maps Feedback Tool.
Murphy, Ciaran 5 Reputation points

2025-04-07T13:13:52.9833333+00:00

Hi Sampath,

I have submitted feedback via the feedback tool. Do you know roughly how long it would be before a fix is in place
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-08T04:20:12.68+00:00

@Hello Murphy, Ciaran, there is no ETA. Once feedback is provided, you will get updates .
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-09T02:12:12.8933333+00:00

Hello @Murphy, Ciaran, However, once the data team reviews and processes the feedback, you should see updates in the platform within the next couple of weeks. Thanks for the feedback.
AshokPeddakotla-MSFT 35,951 Reputation points

2025-04-09T03:41:44.1466667+00:00

Do we have any ETA? Can you please take a look at this issue?

Manas Mohanty 3,110 Microsoft External Staff

Hello Murphy, Ciaran

Good day. Thank your patience and time.

The response format for Azure Maps code have changed now. They seems to have omitted the irrelevant information with respect to GMT now.

I am getting below output.

{
  "Version": "2025b",
  "ReferenceUtcTimestamp": "2025-04-18T10:24:40.2195606Z",
  "TimeZones": [
    {
      "Id": "Europe/Dublin",
      "Names": {
        "ISO6391LanguageCode": "en",
        "Generic": "Ireland Time",
        "Standard": "Greenwich Mean Time",
        "Daylight": "Irish Standard Time"
      },
      "ReferenceTime": {
        "Tag": "IST",
        "StandardOffset": "01:00:00",
        "DaylightSavings": "00:00:00",
        "WallTime": "2025-04-18T11:24:40.2195606+01:00",
        "PosixTzValidYear": 2025,
        "PosixTz": "GMT-1IST,M3.5.0/1,M10.4.0",
        "Sunrise": "2025-04-18T06:18:57.7336067+01:00",
        "Sunset": "2025-04-18T20:29:55.0545424+01:00"
      }
    }
  ]
}

Could you verify from your side too.

import requests
 
# Define API endpoint and parameters
latitude = 53.3498 # Example latitude (Dublin, Ireland) (51.507351,-0.12775
longitude = -6.2603  # Example longitude
api_key = "<Azuremapskey>"
 
url = f"https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&query={latitude},{longitude}&subscription-key={api_key}"
 
# Send request
response = requests.get(url)
 
# Check response status and print result
if response.status_code == 200:
    print(response.json())  # Parsed JSON response
else:
    print(f"Error: {response.status_code}, {response.text}")

Thank you.

1 answer

Your answer

Murphy, Ciaran 5 Reputation points

2025-04-04T14:46:47.4266667+00:00

Apologies im using azure maps.

The azure maps for dublin Ireland return the following TimeTransitions

{

"Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-03-30T01:00:00Z", "UtcEnd": "2025-10-26T01:00:00Z" }, { "Tag": "GMT", "StandardOffset": "01:00:00", "DaylightSavings": "-01:00:00", "UtcStart": "2025-10-26T01:00:00Z", "UtcEnd": "2026-03-29T01:00:00Z" },

compared to for london

{

"Tag": "BST", "StandardOffset": "00:00:00", "DaylightSavings": "01:00:00", "UtcStart": "2025-03-30T01:00:00Z", "UtcEnd": "2025-10-26T01:00:00Z" }, { "Tag": "GMT", "StandardOffset": "00:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-10-26T01:00:00Z", "UtcEnd": "2026-03-29T01:00:00Z" }

As you see from above when querying the azure maps api for a location in dublin GMT comes back with a StandardOffset of 1 and DaylightSavings of -1. Where as for London GMT StandardOffset and DaylightSavings are both 0

GMT does not have any offsets or daylight saving so it looks like the response form the api using a latitude and longitude for a location in dublin Ireland is incorrect.
Manas Mohanty 3,110 Reputation points Microsoft External Staff

2025-04-07T03:59:19.7533333+00:00

Hi Murphy, Ciaran

Could you share the azure maps code for replicating the above results.

Thank you.
Murphy, Ciaran 5 Reputation points

2025-04-07T08:15:59.5033333+00:00

Yeah sure thing.

For dublin - https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&subscription-key={APIKEY}&options=all&query=53.3498,-6.2603&language=en

For london - https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&subscription-key={APIKEY}&options=all&query=51.507351,-0.127758&language=en
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-07T11:29:06.32+00:00

Hello Murphy, Ciaran,

StandardOffset refers to the UTC offset in effect at the ReferenceUTCTimestamp.

DaylightSavings represents the time adjustment (in minutes) in effect at the ReferenceUTCTimestamp.

I tried using your coordinates (53.3498, -6.2603) but received incorrect data for both StandardOffset and DaylightSavings, showing GMT incorrectly.

Sample expected results:

"TimeTransitions": [ { "Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-03-30T01:00:00Z", "UtcEnd": "2025-10-26T01:00:00Z" }, { "Tag": "GMT", "StandardOffset": "00:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2025-10-26T01:00:00Z", "UtcEnd": "2026-03-29T01:00:00Z" }, { "Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "UtcStart": "2026-03-29T01:00:00Z", "UtcEnd": "2026-10-25T01:00:00Z" } ]

I believe this is a bug. Please report the issue through the Azure Maps feedback channels.

Kindly review the documented process for submitting comments on map data here:

Azure Maps Feedback Tool.
Murphy, Ciaran 5 Reputation points

2025-04-07T13:13:52.9833333+00:00

Hi Sampath,

I have submitted feedback via the feedback tool. Do you know roughly how long it would be before a fix is in place
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-08T04:20:12.68+00:00

@Hello Murphy, Ciaran, there is no ETA. Once feedback is provided, you will get updates .
Sampath 2,250 Reputation points Microsoft External Staff

2025-04-09T02:12:12.8933333+00:00

Hello @Murphy, Ciaran, However, once the data team reviews and processes the feedback, you should see updates in the platform within the next couple of weeks. Thanks for the feedback.
AshokPeddakotla-MSFT 35,951 Reputation points

2025-04-09T03:41:44.1466667+00:00

Do we have any ETA? Can you please take a look at this issue?
Manas Mohanty 3,110 Reputation points Microsoft External Staff

2025-04-18T10:31:01.2066667+00:00

Hello Murphy, Ciaran

Good day. Thank your patience and time.

The response format for Azure Maps code have changed now. They seems to have omitted the irrelevant information with respect to GMT now.

I am getting below output.

{ "Version": "2025b", "ReferenceUtcTimestamp": "2025-04-18T10:24:40.2195606Z", "TimeZones": [ { "Id": "Europe/Dublin", "Names": { "ISO6391LanguageCode": "en", "Generic": "Ireland Time", "Standard": "Greenwich Mean Time", "Daylight": "Irish Standard Time" }, "ReferenceTime": { "Tag": "IST", "StandardOffset": "01:00:00", "DaylightSavings": "00:00:00", "WallTime": "2025-04-18T11:24:40.2195606+01:00", "PosixTzValidYear": 2025, "PosixTz": "GMT-1IST,M3.5.0/1,M10.4.0", "Sunrise": "2025-04-18T06:18:57.7336067+01:00", "Sunset": "2025-04-18T20:29:55.0545424+01:00" } } ] }

Could you verify from your side too.

import requests # Define API endpoint and parameters latitude = 53.3498 # Example latitude (Dublin, Ireland) (51.507351,-0.12775 longitude = -6.2603 # Example longitude api_key = "<Azuremapskey>" url = f"https://atlas.microsoft.com/timezone/byCoordinates/json?api-version=1.0&query={latitude},{longitude}&subscription-key={api_key}" # Send request response = requests.get(url) # Check response status and print result if response.status_code == 200: print(response.json()) # Parsed JSON response else: print(f"Error: {response.status_code}, {response.text}")

Thank you.

Answer 1

Hi @Murphy, Ciaran

I have spoken with the PM Owner and there is agreement that while it looks odd, it is not wrong. They will review the back-end data around this, but these values do work correctly in the calculation in relation to UTC. Let me use another distant time zone, mine, to illustrate. Let's focus on the "Time Transitions" section for PDT & PST

User's image

You can see that for ANY Time zone calculation you need BOTH "StandardOffset" and "DaylightSavings" modifiers to calculate the correct difference to UTC. You can think of the "DaylightSavings" as the modifier needed to the "StandardOffset" and in all cases both will apply making consuming these very simple. As our data has the Standard Offset for IST that is not Zero, then the Relative Time zone will need that taken into account.

We do agree with you that this looks odd to add 1 then subtract 1 to get the GMT value but it equates to zero and should work. As I said above, they are going to look at the back end data to see if there is a change we can make to the IST definition to have it look more like you would expect but the numbers will work for proper UTC to local time calculations as is, so should you write your code to use these and we do change the data, your code will still work.

Sincerely,

IoTGirl

Share via

Azure Maps byCoordinates api call GMT issue

1 answer

Your answer