WSO2 Data Analytics Server is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

All docs This doc
Skip to end of metadata
Go to start of metadata

The Geo Dashboard of WSO2 DAS is a Jaggery application that provides realtime information about geo spatial objects. It processes spatial data from an external source of events and analyzes/manipulates this data to produce meaningful information to end users using the geo dashboard. You can interact with it to generate a variety of alerts and warnings as follows.

Alert type
Speed alertYou can specify a maximum speed limit to all spatial objects. If an object exceeds the specified speed, an alert will be generated.
Proximity alert You can specify a radius and a time. Thereby, a warning will be populated if two spatial objects arrive near each other within the specified limits.
Within alertYou can specify a geo area and if any spatial object comes in to the specified area an alert will be generated.
Stationery alert You can specify a geo area and a fluctuation radius and a time, which will generate an alert if any spatial object is located in that area during the specified time. Fluctuation radius is used to minimize the fluctuation effect of a spatial object.
Congestion AlertYou can define a geo area. An alert is generated when the congestion level in that area changes.

You can use the Geo Dashboard of WSO2 DAS as described below.


Set up the following prerequisites before starting the configurations.

  1. Install the GPL - Siddhi Geo Extension feature. For detailed instructions to install GPL features, see Installing WSO2 GPL Features.
  2. Copy the two extension JAR files in the directory <DAS _HOME>/samples/cep/utils/geo-dashboard-extensions/ to the <DAS _HOME> /repository/components/lib/ directory.
  3. Add <Role>GeoDashboard</Role> to /repository/conf/carbon.xml under <ServerRoles> parent tag
  4. Add the following configuration in <DAS_HOME>/repository/conf/datasources/master-datasources.xml file under <datasources> parent element and restart the server.

        <description>The datasource used for geo dashboard</description>
        <definition type="RDBMS">
                <validationQuery>SELECT 1</validationQuery>

Running the Geo Dashboard

To deploy the required artifacts to run the Geo dashboard, follow the steps below:

  1. Navigate to the <DAS_HOME>/repository/deployment/server directory and check whether it contains the carbonapps directory. If it does not exist, create it.

    The carbonapps directory may not be available by default if your DAS installation is a fresh installation.

  2. Copy the file from the <DAS_HOME>/samples/capp/ directory and place it in the <DAS_HOME>/repository/deployment/server/carbonapps directory.

Executing the producer

Follow the steps below to run the tfl-feed producer client from the command line.

  1. Download GeoTools GIS toolkit
  2. Copy the following client JAR files from downloaded <GeoTools_HOME> directory to both <DAS_HOME>/repository/components/lib/ directory and <DAS_HOME>/samples/cep/lib directory.
    • gt-geojson-13.1.jar
    • gt-main-13.1.jar
    • gt-metadata-13.1.jar
    • jai_core-1.1.3.jar
    • jai_imageio-1.1.jar
  3. Download JTS Topology Suite.
  4. Copy jts-1.8.jar from <JTS_HOME>/lib directory to both <DAS_HOME>/repository/components/lib directory and <DAS_HOME>/samples/cep/lib directory.
  5. Navigate to <DAS_HOME>/samples/cep/producers/tfl-feed/ directory, and execute the ant  command in a new tab of your DAS console, to execute the producer of the Geo  Dashboard application.

Accessing the Geo Dashboard

Follow the steps below to start and access the Geo Dashboard.

  1. Start the WSO2 DAS server. For instructions, see Running the Product
  2. Access the Geo Dashboard application in your Web browser using the following URL: https://localhost:9443/portal/dashboards/geo-dashboard    
    geo dashboard
    This dashboard can be used to define alerts, define geo fences, click on spatial objects to view information relating to them etc. 
  • No labels