Looking into this;
- I don't believe the service uses the convention you mentioned.
- There is no option to customize the rules of how the service works.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Using the Azure Map service and more specifically the GetTimezoneByCoordinates
Using that API with coordinate points in North Sea for example { Latitude : 59.58907, Longitude : 1.057123}
would result in a summarized response indicating timezoneId to be Etc/UTC { "id": "Etc/UTC", "standardOffset": "00:00:00" }
First question : Does the Azure Map service determine the timezoneId using the UN (United Nation) convention of 14 miles after which the time zone revert back to the natural time zone ?
If yes, is there a way to customized that rule so that the distance before reverting can be modified to a different value ? (in my present case the expected result would be timezoneId = "Europe/London" so that Day Light Saving can be taken into account)
Thanks
Pascal.
Looking into this;
There is no specific convention used by the Time Zone API. The ID’s are based on IANA ID’s. This is also the source of most of the Time Zone API data. The land boundaries are based on Microsoft determined geopolitical boundaries. International waters have their own time zone standard different from land time zones and these maritime standards are not covered by IANA. For areas outside of the land boundaries (i.e.: international waters), the Azure Maps Time Zone API is just using standard time zones of the world.