You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Root cause: the branch briefly restored the retired HERE app_id/app_code path even though this major-version line is meant to standardize on the current API-key-based Geocoding and Search API.
Remove the legacy HERE constructor, parsing models, sample/test config, and docs so the public surface matches the intended breaking-change direction.
Copy file name to clipboardExpand all lines: README.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
# Generic C# Geocoding API [](https://github.com/exceptionless/Geocoding.net/actions/workflows/build.yml)[](https://github.com/exceptionless/Geocoding.net/actions/workflows/codeql-analysis.yml)
2
2
3
-
Includes a model and interface for communicating with current geocoding providers while preserving selected legacy compatibility surfaces.
3
+
Includes a model and interface for communicating with current geocoding providers.
4
4
5
5
| Provider | Package | Status | Auth | Notes |
6
6
| --- | --- | --- | --- | --- |
7
7
| Google Maps |`Geocoding.Google`| Supported | API key or signed client credentials |`BusinessKey` supports signed Google Maps client-based requests when your deployment requires them. |
| Bing Maps |`Geocoding.Microsoft`| Deprecated compatibility | Bing Maps enterprise key |`BingMapsGeocoder` remains available for existing consumers and is marked obsolete for new development. |
10
-
| HERE Geocoding and Search |`Geocoding.Here`| Supported | HERE API key or legacy app_id/app_code | Uses the current HERE Geocoding and Search API when an API key is configured and retains the legacy credential flow for compatibility. |
10
+
| HERE Geocoding and Search |`Geocoding.Here`| Supported | HERE API key | Uses the current HERE Geocoding and Search API. |
11
11
| MapQuest |`Geocoding.MapQuest`| Supported | API key | Commercial API only. OpenStreetMap mode is no longer supported. |
12
12
| Yahoo PlaceFinder/BOSS |`Geocoding.Yahoo`| Deprecated | OAuth consumer key + secret | Legacy package retained for compatibility, but the service remains deprecated and unverified. |
13
13
@@ -76,7 +76,9 @@ Bing Maps requires an existing Bing Maps enterprise key. The provider is depreca
76
76
77
77
MapQuest requires a [developer API key](https://developer.mapquest.com/user/me/apps).
78
78
79
-
HERE supports a [HERE API key](https://www.here.com/docs/category/identity-and-access-management) for the current Geocoding and Search API. Existing consumers can also continue using the legacy `app_id`/`app_code` constructor for compatibility.
79
+
HERE supports a [HERE API key](https://www.here.com/docs/category/identity-and-access-management) for the current Geocoding and Search API.
80
+
81
+
The current major-version line no longer supports HERE `app_id`/`app_code` credentials. Migrate existing HERE integrations to API keys before upgrading.
80
82
81
83
Yahoo still uses the legacy OAuth consumer key and consumer secret flow, but onboarding remains unverified and the package is deprecated.
82
84
@@ -93,7 +95,7 @@ Alternatively, if you are on Windows, you can open the solution in [Visual Studi
93
95
94
96
### Service Tests
95
97
96
-
You will need credentials for each respective service to run the service tests. Make a `settings-override.json` as a copy of `settings.json` in the test project and put in your provider credentials there. For HERE, that can be either `Providers:Here:ApiKey` or the legacy `Providers:Here:AppId` plus `Providers:Here:AppCode` pair. Then you should be able to run the tests.
98
+
You will need credentials for each respective service to run the service tests. Make a `settings-override.json` as a copy of `settings.json` in the test project and put in your provider credentials there. Then you should be able to run the tests.
97
99
98
100
Most provider-backed integration tests skip with a message indicating which setting is required when credentials are missing. The Yahoo suite now follows the same credential gating, but the provider remains deprecated and unverified.
99
101
@@ -105,4 +107,4 @@ The sample app in `samples/Example.Web` is an ASP.NET Core 10 minimal API that c
105
107
dotnet run --project samples/Example.Web/Example.Web.csproj
106
108
```
107
109
108
-
Configure a provider in `samples/Example.Web/appsettings.json` or via environment variables such as `Providers__Azure__ApiKey`, `Providers__Bing__ApiKey`, `Providers__Google__ApiKey`, `Providers__Here__ApiKey`, `Providers__Here__AppId`, `Providers__Here__AppCode`, or `Providers__MapQuest__ApiKey`. Once the app is running, use `samples/Example.Web/sample.http` to call `/providers`, `/geocode`, and `/reverse`.
110
+
Configure a provider in `samples/Example.Web/appsettings.json` or via environment variables such as `Providers__Azure__ApiKey`, `Providers__Bing__ApiKey`, `Providers__Google__ApiKey`, `Providers__Here__ApiKey`, or `Providers__MapQuest__ApiKey`. Once the app is running, use `samples/Example.Web/sample.http` to call `/providers`, `/geocode`, and `/reverse`.
0 commit comments