External service requirements
TMS FNC Maps wraps hosted mapping providers, so most applications need a provider account, service key, and terms review before they can display maps or call geocoding, routing, places, timezone, elevation, or static map services.
API keys
OpenLayers and Leaflet can use open tile sources, but most commercial providers require an API key. Use the TMS service key guide to find the current registration route for each supported provider:
Assign the key to the relevant component's APIKey property, or to the service-specific connection settings documented by that component. A key issued by one provider is not interchangeable with another provider.
Deprecated providers
The Bing Maps and TomTom integrations remain documented because existing applications may still use them, but the underlying provider APIs are deprecated by their vendors.
| Provider | Affected Maps components | Vendor information |
|---|---|---|
| Bing Maps | TTMSFNCBingMaps, Bing backends for geocoding, directions, static maps, timezone, and places |
Bing Maps V8 Web Control |
| TomTom | TTMSFNCTomTom, TomTom backends for geocoding, directions, and static maps |
TomTom Maps SDK for Web release notes |
For new projects, prefer a provider whose API and commercial terms are active for your target platforms. When maintaining existing applications, test provider availability and quota behavior before each release.
Terms of use
With TMS FNC Maps you receive source code and support for integrating the supported services in Delphi applications. The use of hosted map services is still governed by each provider's terms, quotas, service availability, and billing rules.
| Provider | Terms |
|---|---|
| Google Maps | Google APIs terms |
| Microsoft Bing Maps | Microsoft Maps product terms |
| Microsoft Azure Maps | Azure legal information |
| OpenLayers | OpenLayers project |
| TomTom | TomTom terms and conditions |
| HERE Maps | HERE terms and conditions |
| MapBox | Mapbox service terms |
| Apple MapKit | Apple developer terms |
| Airmap | Airmap terms |
| MapQuest | MapQuest developer legal |
The application owner is responsible for complying with the selected provider's terms and for paying any provider fees that apply to the application's usage.
Limited warranty
TMS Software cannot guarantee the current or future operation, approval, availability, terms, quotas, or uptime of third-party map services. If a provider changes its conditions, service availability, or API behavior, TMS Software will make reasonable efforts to accommodate the change where technically possible, but provider changes remain outside TMS Software's control.