search

3drepo / 3drepo.io

3D Repo web server
http://www.3drepo.io
GNU Affero General Public License v3.0
95 stars 38 forks source link

HERE Maps location services update #3124

Closed Charence closed 5 months ago

Charence commented 2 years ago

Description

We have received notification from HERE that the Map Tile API we currently use will be retired by September 30, 2022. We should consider migrating to their newer offerings and also consider if some of the new APIs will be useful to us.

Goals

TBD

Tasks

TBD

Related Resources

Their e-mail:

=======

Thank you for being a HERE Location Services customer.


The predecessor HERE hosted version of HERE Location Services your company is using is being retired as of September 30th, 2022.

The HERE Premium SDK (3.x) will be maintained until December 31st, 2022, with only critical bug fixes being addressed.

But do not worry, the new versions of our HERE Location Services are even more powerful and easy to use.

They have been redesigned from scratch and now have:

 

Self-hosting

If you are self-hosting applications that are based on HERE Location Services, then you may continue to do so for the term of your present contract, but you are hereby notified that as of December 31st, 2022 HERE will not be providing technical support and bug fixes for these legacy HERE Location Services anymore. The last map releases will be in November 2022, based on 2022 Q4 data. Select HERE Location Services of the new generation will also be commercially available for self-hosting, currently planned for March 31, 2022.

 

What’s next? 

The next step is to start planning your migration to the new versions.


In case of any questions please reach out to your HERE Account Executive or our technical support team who are always available to help. 


Yours faithfully,

The HERE Location Services Product Team


                                                                                                                          

                                                    APPENDIX

                                                                                                                          


If you are using any of the HERE Location Services based on the following versions, we ask that you migrate your application to the latest versions of HERE Location Services prior to September 30th, 2022:


The HERE Premium SDK (3.x) will be maintained until December 31st, 2022, with only critical bug fixes being addressed.


We encourage you and your development teams to explore and evaluate our new HERE Location Services and getting yourselves familiarized with the new features and functions they have to offer.

With the new service framework in place, we are also on our way to delivering new functionalities that will only become available through the newly released HERE Location Services. Check below the exciting new service releases already available or planned to become available soon for you:

Vector Tile API v2:  enabling client-side map rendering and customization of map look and feel in conjunction with Maps API for Java Script v3.1.


Routing API v8: providing new modes and features such as


Matrix routing API v8: offered as a unified routing service for all matrix sizes


Isoline routing API v8: offered as a unified routing service for all Isoline options Supporting new routing modes:


Route Matching API v8:


Waypoints Sequencing API v8:


Map Attributes API v8:


Geofencing API v8:


Geocoding & Search v7: aligning former Geocoding and Places/Search APIs into one simplified API that integrates the features of both


Public Transit API v8: enabling improved functionality of Transit Routing and Next Departures features


Intermodal Routing API v8: bringing several additional benefits.


Network Positioning API v2:


Maps API for JavaScript v3.1:


HERE SDK 4.x (Lite, Explore and Navigate variants):



All developer guides include a Migration Guide section that explains the changes to the previous versions.

All our customers today can benefit from these new features and capabilities when accessing the newest versions of the HERE Location Services. If you are already using token or API key authentication, then no change regarding access credentials is needed. If however, you’re still using app_id and app_code, please check out the documentation posted at https://developer.here.com/documentation/authentication  where you will find information on how to create and use new credentials.

Charence commented 2 years ago

This page looks useful: https://developer.here.com/documentation/maps/3.1.30.7/dev_guide/topics/migration.html

carmenfan commented 2 years ago

Raster maps are not yet available https://stackoverflow.com/questions/72408680/here-api-upgrade-map-tiles-v2-1-to-raster-tiles-v3-giving-credentials-error

Charence commented 11 months ago

@carmenfan Bump from HERE Maps:

Dear Customer,

Thank you for being a valued and loyal customer with HERE Technologies!

Following our announcement from February 2023 related to the end-of-life of our predecessor versions of Location Services and the requested upgrade to our new versions of HERE Location Services, we wanted to reach out to you, today, and remind and notify you of the previously shared end-of-life date.

The end-of-life of our old, predecessor versions of HERE Location Services remains unchanged as December 31st, 2023, for both our cloud location services and the Premium SDK (3.x).

We want to reiterate that all customers are asked to upgrade to the latest versions of HERE Location Services on platform. This means that you will have to onboard to the platform, request subscription of according plans and change the APIs you use until December 31st, 2023.

While we ask you to please try everything possible and ensure that you have upgraded your applications by this date we understand that there are scenarios where you might not be able to meet this deadline for reasons beyond your control. For this we would like to provide additional guidance on how to handle it.

The upgrade process can only begin after the migration to the HERE platform has been completed. This is the case if you need to upgrade to a service that is only offered on the platform (Raster Tile v3, Map Image v3, Traffic v7, Traffic Raster Tile v2, Traffic Vector Tile v2, Batch Geocoding v7, Multi-Reverse Geocoding V7 and SDK 4.x Navigate). In this case, please work with your HERE representative on the migration.

If you or your customer has already migrated to the platform, or the new version of the service you need to upgrade to is available on the Developer Portal (Vector Tile v2, Geocoding & Search v7, Routing v8, Isoline Routing v8, Matrix Routing v8, Route Matching v8, Map Attributes v8, Waypoints Sequencing v8) and there is no need to upgrade to any of the services only available on platform. Then, migrating to platform is not a dependency, but due to other HERE’s driven reasons (e.g. commercial, legal constraints) or reasons of your own (Q4 code freeze, Q4 priorities, extended implementation timelines, capacity, etc.) you are prevented from meeting the deadline, please share with your HERE representative your needed extension time.

You or your customer cannot proceed with the upgrade due to critical feature/functionality or service availability blockers that prevent you to upgrade. Please work with your HERE representative on documenting blockers and validating that no alternative path exists, and we will try and work on finding a suitable solution.

We kindly request you to make reasonable efforts to upgrade by these deadlines. We will ensure your upgrade experience and support with HERE is as smooth and good as possible. We will carefully monitor the progress.

Please reach out to your HERE Account Executive if you would appreciate technical assistance on upgrading to the latest Location Service releases.

Do you need further help?

For technical inquiries regarding the upgrade, please contact your HERE representative. We are more than happy to jointly look into the best upgrade options for you.

If you do not have an assigned Account Executive, please reach out to us via StackOverflow.

If you have a paid support plan with access to the HERE Support Portal https://support.here.com/csm, please raise a support ticket. Our team will be happy to assist you.

Your HERE Account Executive will be available for you to discuss your upgrade and any needs for support from our Professional & Technical Support team to facilitate your upgrade. For more information on the latest version of HERE Location Services, please refer to www.developer.here.com and work with your Account Executive to get registered for our platform portal, on platform.here.com, today. They will be more than happy to support.

We hope you are as excited as we are about the next generation of HERE Location Services. If you have further questions regarding your existing contract, pricing or your upgrade and migration options, please do not hesitate to contact your HERE Account Executive.

Yours faithfully,

The HERE Location Services Product Team

carmenfan commented 9 months ago

@AsiteZane I completely forgot about this... tagging you for attention

We need to look into prioritising this work if we want to maintain the feature

zaneulhaq commented 9 months ago

@carmenfan - thank you, this was for 5.12.0, i've put it as "To Discuss" so we can see what we can do about this with whatever else we have planned for 5.10.0 and whether the urgency on this has changed.

zaneulhaq commented 9 months ago

@carmenfan - to find out what needs to be done to address this.

Charence commented 9 months ago

Here Maps v2.1

randomApiServer = number from 1 to 4
hereBaseDomain = ".base.maps.ls.hereapi.com"
uri = "/maptile/2.1/maptile/newest/normal.day/" + req.params.zoomLevel + "/" + req.params.gridx + "/" + req.params.gridy + "/" + size + "/png8"
apiKey = "?apiKey=" + config.here.apiKey

request = randomApiServer + hereBaseDomain + uri + apiKey

Example: 1.base.maps.ls.hereapi.com/maptile/2.1/maptile/newest/normal.day/19/259056/170116/256/png8?apiKey=xxx Code; https://github.com/3drepo/3drepo.io/blob/master/backend/src/v4/routes/maps.js

Here Maps v3.0.3

hereBaseDomain = "https://image.maps.hereapi.com/mia/v3"
resource = "base"
projection = "mc"
view = "center:${latitude},${longitude};zoom=${zoomLevel}
size = "256x256"
format = "png"
uri = "/${resource}/${projection}/${view}/${size}/${format}"
apiKey = "?apiKey=" + config.here.apiKey

request = hereBaseDomain + uri + apiKey

Example: https://image.maps.hereapi.com/mia/v3/base/mc/center:51.50662758216181,-0.14987087094778326;zoom=15/256x256/png?apiKey=newXXX

Docs: https://platform.here.com/services/details/hrn:here:service::olp-here:rendering-map-image-3/api-ref

API Key authentication is still supported but the old key won't work. A new one needs to be generated through app registration in platform.here.com.

zaneulhaq commented 9 months ago

This will require work on transposing x y z to long/lat and may also include some graphics work - not just api url changes unfortunately. putting in 5.12.0 so that we can see what capacity is but likely to be in 5.14 unless it becomes a critical client issue when HERE MAPS is no longer supported.

carmenfan commented 9 months ago

Just putting a note here so we don't forget: @Charence is currently investigating if we can pass lat/long to maptiler as well - so don't have to have different logic for different service providers.

Charence commented 9 months ago

Good news @carmenfan @AsiteZane

I had another look and there's a Here v3 API I missed, which takes the col/row for a map tile.

uri = "https://maps.hereapi.com/v3/{resource}/{projection}/{zoom}/{column}/{row}/{format}"
apiKey = "?apiKey=" + config.here.apiKey

request = uri + apiKey

Example: https://maps.hereapi.com/v3/base/mc/19/259056/170116/png?style=explore.day&apiKey=newXXX Docs: https://platform.here.com/services/details/hrn:here:service::olp-here:rendering-raster-tiles-3/api-ref

The default style looks a bit different.

v2.1 (normal.day): here-v2

v3.0.3 (explore.day): here-v3

EDIT:

There's also a Traffic Tile

Example: https://traffic.maps.hereapi.com/v3/flow/mc/19/259056/170116/png?apiKey=newXXX Docs: https://platform.here.com/services/details/hrn:here:service::olp-here:traffic-raster-tile-service-3/api-ref

carmenfan commented 9 months ago

@AsiteZane in which case it's a pretty simple fix, just need to adjust URLs on the backend.

Charence commented 7 months ago