Table of Contents

Getting Started With TMS FNC Google Maps

Prerequisites

  • TMS FNC Core installed and the runtime package added to the project.
  • TMS FNC Maps installed and the runtime package added to the project.
  • A Google Maps JavaScript API key with the Maps JavaScript API enabled.

Google Maps features such as KML layers, Street View, heat maps, directions, geocoding, and places may require additional Google Cloud APIs or billing configuration. Start by validating a plain map with the Maps JavaScript API key, then enable the feature-specific Google services your application uses. Keep the API key assignment in the form initialization path so the component can load Google Maps before markers, overlays, or Street View settings are applied.

Add The Control

  1. Drop TTMSFNCGoogleMaps from the TMS FNC Maps palette page onto a form.
  2. Set the APIKey property to your Google Maps API key.

The dropped control uses the shared TMS FNC Maps collections for markers, labels, polylines, polygons, circles, rectangles, and heat maps, then adds Google-specific options such as Street View, KML layers, overlay views, map IDs, keyboard shortcuts, and marker clustering. Put provider setup before data setup: assign APIKey, configure Options, then add markers and overlays.

Add A Marker

procedure TForm1.AddLondonMarker;
var
  LMarker: TTMSFNCGoogleMapsMarker;
begin
  TMSFNCGoogleMaps1.APIKey := '<your Google Maps JavaScript API key>';

  LMarker := TMSFNCGoogleMaps1.Markers.Add;
  LMarker.Coordinate.Latitude := 51.5074;
  LMarker.Coordinate.Longitude := -0.1278;
  LMarker.Title := 'London';
end;

Next Steps

  • Guides - clustering, KML layers, Street View, heat maps, labels, complex polygons, and overlay views.
  • API reference - full class reference.

Move to the guides when the map needs Google-specific layers or interaction behavior. The Google Maps guide covers the feature areas that usually require more than one property assignment, including KML click handling, Street View state, cluster setup, heat-map weighting, and complex polygon holes. The API reference is the right route for exact property types, event signatures, inherited members, and related option classes when you are wiring these workflows into an existing application.