Skip to Content (Press Enter)
Community › Forge › Assets list › OutSystems Maps
Login to follow
OutSystems Maps

OutSystems Maps (ODC)

Supported
Stable version 2.3.1 (Compatible with ODC)
Uploaded on 6 May (5 days ago) by OutSystems
OutSystems Maps

OutSystems Maps (ODC)

Details
Detailed Description

Maps made easy, from developers to developers.

Use the OutSystems Maps to create visual rich enterprise-grade interfaces that help the user to quickly have map-based insights of the data.

Key features

  • Built for Web and Mobile apps
  • Simple to use and extend
  • Add Markers, and Directions
  • No javascript knowledge required


Developer experience using OutSystems Maps

To access a sample version of OutSystems Maps, you can download the OutSystems Maps Sample from Forge and launch it in Service Studio. These samples also have documentation.

We're continually improving this solution and adding more features. To help us cover more specific and complex scenarios, let us know what you'd like to see in this component's support tab.


Note: Currently, Google Maps and Leaflet are supported.
ODC Asset screenshot_0ODC Asset screenshot_1
Release notes 

What's New

  • ROU-12633 - Added a new HeatmapLayer block using deck.gl as the provider.
    This update introduces a high-performance HeatmapLayer, powered by deck.gl, replacing the native Google Maps HeatmapLayer.
    This ensures continued support and enhanced visualization capabilities ahead of Google's scheduled removal of the legacy library in Maps JavaScript API version 3.65 (May 2026).
  • ROU-12638 - Updated Google Maps Drawing Tools to use TerraDraw as the new default provider.
    This update replaces the native Google Maps Drawing Library with TerraDraw to ensure continued functionality following Google's announcement that the legacy library will be removed starting with Maps JavaScript API version 3.65 (May 2026).

Fixed Issues and Improvements

  • ROU-12504 / RPM-6440 - Fixed an issue that caused the Map component to experience significant performance lag and unresponsiveness.
    This occurred when handling large datasets with multiple markers, specifically when the MarkerCluster feature was enabled.