when you set departureTime param for your isoline calculations, the departure time is the local time, but which local time ? The local time of the location departure point, the local time of my web server location ? Is it possible to be more accurate ? Thanks in advance
what is local time for the here api routing calculations
143 Views Asked by info olaf At
1
There are 1 best solutions below
Related Questions in HERE-API
- Error in if (!is.na(hroute$duration_base)) { : argument is of length zero
- Signature mismatch. Authorization signature or client credential is wrong with Android
- Is the Barometric Pressure from the Here Destination Weather API MSLP corrected?
- Road info like curvature, speed limit, slope in HERE SDK for Flutter
- Curvature and traffic light data from a polyline in heremaps
- Here API sdk for flutter
- Here Maps It looks white in React
- Here Maps - route overlaps clusters
- Converting Here API WKTShapeType Multipolygon To GeoJSON?
- Missing address fileds in Here-API auto suggest end-point
- HERE Routing API V8: ignore route restrictions near place or waypoint
- Extracting latitude and longitude from HERE map linkid
- HERE maps - Move map position
- HERE Maps CSP error on Safari browser: blobs can't be loaded
- Geocode Shape not working on H.service.Platform#getSearchService
Related Questions in LOCALTIME
- How to fix the non-updating clock on a tkinter weather app?
- Parse a datetime string that has no 'T' separator using java.time
- Converting UTC to Local Time with daylight saving in Java
- How to save time (Localtime) from WheelTimePicker on API 24?
- Convert Date to UTC DateTime
- LocalTime truncating trailing 00 values
- Is there any date/time function that handles tomorrow's date including carry over into next month?
- Can't get right time in C with localtime()?
- localtime() giving the wrong date in C
- Is there a way to set alarm in android with local date and local time?
- How to convert timestamp, depends on user timezone?
- How to get the current time in a different city in C?
- Why is Java LocalTime 01:32:13.283256 stored as time 00:32:13 in database? 1 hour behind
- Java int formating?
- HQL query: filtering LocalDateTime property by LocalTime
Related Questions in HERE-ROUTING
- Problem of 1 NA result using here.com with Rstudio for routing in Canada
- HERE Routing API v8: How to add waypoint labels?
- HERE Maps Route Matching v8 Can't Set Preferred Route
- Why is Here Routing API v8's response Polyline size 4 times larger than API v7's (deprecated)?
- Bug: Here routing isolines API returning same polygon for all distances
- HERE-Routing API - "These credentials do not authorize access"
- Turn-by-turn latitude and longitude on HERE Routing API
- Retrieve travel times from HERE without reoptimizing waypoint order
- How to request for new traffic information using Route Handle (Here Routing API V8)
- what is local time for the here api routing calculations
- Getting speed limit Advanced Datasets API(aka PDE) is not working well
- Vehicle's height or width does not work in here/com rest api v8
- Here API getting speed limit got PermissionError
- How can I find the middle of a HERE Routing API route?
- HERE Maps Routing: HTTP 429 Too many requests error
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
The following statement in your original question is not accurate:
The Isoline Routing API v8 uses RFC 3339 for the departureTime parameter, so the departure time can be any time and any timezone you want, it doesn't have to be "local".
According to the API documentation, the requested time is converted to the local time at destination. In your case, this means that no matter what time and timezone you use, the service will always adjust it to the time of the city where your coordinates are (origin or destination parameter). Let me give you a few examples:
Example 1: Different timezones
Consider the following request where the coordinates in the origin parameter are in Berlin, Germany:
The timezone offset in the request is -06:00, and it's +01:00 at the origin coordinates (Berlin), so the service converts the input time and uses 2022-01-05T17:00:00+01:00 for the isoline calculation.
Example 2: Same timezone
Since the timezone offset in the request (+01:00) is the same as the timezome at our coordinates location, the service will use the same timestamp for the isoline calculation: 2022-01-05T10:00:00+01:00.
Example 3: Unspecified timezone offset
According to the API documentation, when the timezone offset is not specified, the time is assumed to be local. Since we're still using those coordinates located in Berlin, "local" here means UTC +01:00, so the service uses 2022-01-05T10:00:00+01:00 for the isoline calculation.
Example 4: The "Z" suffix
In RFC 3339, the "Z" suffix denotes denotes a UTC offset of 00:00. In this scenario, the service uses 2022-01-05T11:00:00+01:00 for the isoline calculation.