Table of Contents

Getting Started With TMS FNC OpenLayers

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.
  • OpenLayers does not require an API key for the default OSM tile source.

OpenLayers is the quickest TMS FNC Maps provider to bring up because the default base layer can render without a provider token. Keep the Core and Maps runtime packages in the project, then confirm that the embedded browser runtime used by your target framework can reach the tile server. If you later switch to a private tile endpoint, apply that endpoint through Options.TileServer before the first map load.

Add The Control

  1. Drop TTMSFNCOpenLayers from the TMS FNC Maps palette page onto a form.
  2. The default tile layer, OpenStreetMap, is active without an API key.

The dropped control starts with the standard OpenLayers base map and the shared TMS FNC Maps interaction model. Set layout properties such as Align or anchoring the same way you would for any visual control, then keep provider-specific setup in the form initialization path. That keeps base-layer changes, version pinning, and overlay setup in one place before users begin panning or zooming the map.

Add A Marker

procedure TForm1.AddNewYorkMarker;
var
  LMarker: TTMSFNCOpenLayersMarker;
begin
  LMarker := TMSFNCOpenLayers1.Markers.Add;
  LMarker.Coordinate.Latitude := 40.7128;
  LMarker.Coordinate.Longitude := -74.0060;
  LMarker.Title := 'New York';
end;

Next Steps

Move to the guides when the map needs custom tile layers, GeoTIFF overlays, marker anchors, styled clusters, heat maps, labels, or context-click handling. The API reference is the right route when you need the exact declaring class, property type, or inherited member details. For applications that support multiple map providers, compare this page with the shared Maps guide so provider-neutral code remains separated from OpenLayers-specific setup.