Update Here Geocode and Reverse Geocode Provider to GS7 (v7)

Open
#1,230 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
api

Research direction

Start with the Here provider that currently uses here-provider 0.6.0 and compare its geocode and reverse-geocode handling with the linked migration, endpoint, and API reference documentation. Update the integration for GS7 endpoints and its changed response shapes; done means both operations use the new API without relying on the v6.2 response structure.

Written by the indexing model from the issue text.

Description

Here.com has released their GS7 (v7) API.

We are currently using here-provider 0.6.0 that is using v6.2 endpoints. We are updating to use Here's GS7 endpoints per a conversation with our Here.com rep. Our rep let us know that Here.com intends to drop support for our current endpoints (v6.2) and that we should switch to the new GS7 endpoints.

Note: with the change to GS7 the shape of the responses from here has completely changed
Update was made using the following Here.com Documentation.

Here Migration Docs
https://www.here.com/docs/bundle/geocoding-and-search-api-migration-guide/page/migration-geocoder/README.html

Geo-code Endpoint Docs
https://www.here.com/docs/bundle/geocoding-and-search-api-developer-guide/page/topics/endpoint-geocode-brief.html

Reverse Geo-code Endpoint Docs
https://www.here.com/docs/bundle/geocoding-and-search-api-developer-guide/page/topics/endpoint-reverse-geocode-brief.html

Here API Reference
https://www.here.com/docs/bundle/geocoding-and-search-api-v7-api-reference/page/index.html

Dominant language
PHP
Stars
4k
Forks
525
Avg merge
8m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from geocoder-php/Geocoder

All issues in geocoder-php/Geocoder

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.