Google Deprecation of KML Layers

Today, April 30, Google sent out an email stating that KML Layers will no longer be supported after the May 3.65 update. Do you have any plans to add support for this functionality, or will we need to figure out how to support it on our own moving forward?

Option 1 - Force the API version to 3.65 after it’s released next month. That will be good until May 2027, when Google deprecates that version.

Option 2 - Migrate KML boundaries to other formats, like GeoJSON, and render those on your own.

Option 3 - “Data-driven Styling”. Is this supported via FNC Maps now, or are there plans?

Hi,

At this time we do not plan to add a built‑in KML layer to TTMSFNCGoogleMaps. Current KML support in the component depends entirely on the Google Maps library itself.

  1. You can use the Options.Version property to lock the Google Maps API to a specific version if required.
  2. Importing GeoJSON is supported and can be used as an alternative to KML. You can apply styling manually to imported features.
  3. DDS is not supported at the moment. This is a good suggestion and we will consider adding DDS support in a future release.