Modelling the holiday-based redistribution of South Africans in December


Over the coming months, I’m planning on developing a map series to showcase often overlooked aspects of Cartography and GIS. The idea is to explore topical subject matter to create insightful and (hopefully) beautiful maps.

This is the first in the series.


Every December hundreds of thousands of South African holiday-makers push pause on their lives and scatter across the country; making time to explore, relax and unwind.

I got to wondering if there would be a simple way of modelling this behaviour. Surely there must be some universal underlying factors that could be used to help explain where people go in December? I also knew I wanted to represent my data in a non-traditional way.

For the sake of simplicity, I limited my sights on South Africans moving within South Africa for the holiday season and eventually settled on four broad factors to consider:

  • F1 [-] Distribution of population during the rest of the year
  • F2 [+] Accessibility (using major roads as a proxy)
  • F3 [+] Distribution of holiday accommodation
  • F4 [+] Distribution of National Parks

There are obviously many more factors at play however these four seemed to interact spatially in a dynamic enough way across the country that I was happy to move forward with my investigation.

The density per factor was calculated per municipality, normalised across the country and combined into an equation that attempts to model the interaction between these factors as a linear function.


In the formula, population density acts as a push factor – people will be moving away from areas of high population density towards areas with low population density. The availability of accommodation, how accessible the area is and the distribution of national parks all act as pull factors.

The amount that each factor contributes towards the final index is controlled with weights and the global difference within each variable is exaggerated by squaring it’s normalised value to highlight the most favourable areas more clearly.

The final index can be used to rank order each municipality based on the likelihood that it will be visited in December by people who do not live in that region.

These values were then used to generate the following cartogram:


  • You can explore the map right down to the municipal level
  • The shades of blue represent the percentage change in surface area relative to the region’s usual size. This is affected by the rank as well as the relative difference in the ranks surrounding the area.
  • National parks are included as well as major cities as you zoom in for context
  • The top 20 sites are highlighted with the concentrically banded points
  • Clicking anywhere on the map will return the overall rank for that region

Cartograms have been around since the 1800s. They provide us with a new perspective to our world by taking a thematic variable and typically substituting it for the area of the land that it represents.

The creation of cartograms comes with several challenges as regions must be scaled and still fit together. A recent (2004) and popular method of generating contiguous cartograms is the Gastner-Newman Method. This method is faster, conceptually simpler to understand and produces easily readable cartograms. The algorithm guarantees topology and general shape preservation (albeit with some distortion). This method allows its users to choose their own balance between good density equalization and low distortion of map regions, making it flexible for a wide variety of applications.

Now I need YOUR help.

Taking this one step further, I’ve configured a crowd sourcing web application which will allow users to post about their holiday destinations in a collaborative manner.

You will be able to access this from anywhere on any device and see information contributed by all users of the application. My hope with this is that this information will further support the outcome of the formula and cartogram produced in this exercise.


Please share far and wide and happy holidays!

Insights for ArcGIS – A new spatial Business Intelligence (BI) tool in ArcGIS 10.5

ArcGIS 10.5 is on its way, with the planned release scheduled for mid-December 2016. One of the big changes coming is a new product being unveiled called Insights for ArcGIS.

So, what exactly is Insights for ArcGIS? I would like to look at it as a map centric BI tool. It allows you to perform analytics which helps you uncover secrets about your data. The data in this app is displayed on “cards”. On each card a user can display a map, chart or table with data.

I have played around with the app at pre–release stage and thought it would be nice to give you a preview before the app is released officially. I summarised some important things to know about insights as well as of my favourite things about the app.

The important things about Insights for ArcGIS:

  • It is only available with ArcGIS Enterprise 10.5.
  • It is a premium extension to Portal for ArcGIS with an additional cost.
  • It is a web application and can be accessed through a web browser.
  • You need to have an identity (Username and password) to use it.

Now for some of my favourite features about the app

1. Location is key

In most BI systems, the map card is there just to visualise data. With Insights, you have similar “mapping & visualisation” power as you would in your ArcGIS Online map viewer. This means you can create heatmaps, change symbology, set transparency etc.

In the example below I have added a card that has carjacking data collected at police stations in Gauteng over 10 years. You will note that smart mapping options included in Insights.


Within the card, I could change several things. The attribute field I choose to style my data by, the symbol type as well as the symbol style. With points data, you can also easily create a heatmap.

2. Multiple data sources

The real power of Insights for ArcGIS is that it allows you to pull data from multiple data sources into one dashboard view.

Currently supported data sources are:

  • Web maps and feature services from your organisation portal.
  • The Esri living atlas
  • Databases (SAP HANA, MS SQL, Teradata …tbc)
  • Excel spreadsheets

Insights is only available on Portal for ArcGIS. One of the limitations for now is that you cannot pull data from your ArcGIS Online organisational account into a card. This may well be on the future development path of the product. We will have to wait and see.

3. Document, share and re-run workflows

This is one of my favourite features on this app. Insights gives you the ability to document and share your analysis workflow with other users.

Remember model builder from ArcGIS Desktop? Insights has a similar tool. The only difference is that the workflow gets created for you. Below are 4 cards with different visualisations, analysing crime in September 2016 around the Johannesburg area.

As you create your visualisations, all your steps are being recorded in the background. You can switch to workflow view to see your workflows. The workflows can be shared and re-run. There is an update button that gives you the option to update the model. Here you can replace data and click update. When you switch to Page view this will then update the graphs and chart on your cards.


 4. Questions that guide your spatial analysis workflows

As I was doing my analysis, I noticed a button at the bottom of my active card. It’s called an action button, circled in red in the image below this tool makes spatial analysis easy. The tool asks a geographical question, and uses geoprocessing tools to then answer the questions. This puts geoprocessing tools in easy to understand everyday language.

Picture3.png5. Easy to use

What I love the most about Insights is the ease of use. I love the fact that tools and functionality are contextual. It’s very modern and uncluttered and has this drag and drop functionality that makes all analysis easy because it suggests tools as you pick data.

In conclusion, we live in an era where timely business information is critical to success. For a lot of our clients, ArcGIS is the system of record and business critical to their operations. Insights for ArcGIS offers a configurable BI tool specifically adapted to combine Esri’s spatial analysis platform with other record systems in your operation.

How does one get access to Insights for ArcGIS? You will need to have ArcGIS Enterprise licensed and installed on your premises. For more information regarding licensing and prices do not hesitate to contact your account manager.



Mathematically Verifying South African ID Numbers with Survey123

This blog post describes how South African ID numbers can be verified mathematically in Survey123. South African ID numbers have the following format:


YYMMDD : Date of birth.
G  : Gender. 0-4 Female; 5-9 Male.
SSS  : Sequence No. for DOB/G combination.
C  : Citizenship. 0 SA; 1 Other.
A  : Usually 8, or 9
Z  : Control digit

The most challenging part of verifying the ID number is the control digit which is calculated by using the Luhn algorithm – this will be the focus of this blog post.

The best way to tackle complex mathematical functions in Survey123 is to break it up into separate mathematical calculations and using calculated fields:

The check digit is the last digit of the SA ID number so it can be retrieved with the following function: substr(${idnr}, string-length(${idnr}) – 1, string-length(${idnr})) where ${idnr} refers to the captured ID number.

Once you have an understanding of the substr() function the rest of the calculations used to verify the ID number is pretty much straight forward.

The survey’s XLSForm file can be found here (and can be freely used): SA Id number

  1. Copy the file to your downloads folder
  2. Open Survey123 Connect
  3. Create a New Survey and base it on an existing file
  4. Choose the Excel file that you have downloaded
  5. Your survey will be generated


  1. The SA ID Number does not indicate if a user was born in 19yy or 20yy so both options are catered for – with a logic test to see if the birth date is in the future (age not greater than zero)
  2. Race is no longer indicated in the SA ID Number

Esri Field Mobility

Maintaining field assets such as roads or fire hydrants, requires engineers and managers to know what condition these assets are in. After all, prevention is better than cure and fixing problems is much more time consuming and expensive than just keeping all assets serviced and in good working condition.

Many organizations rely on a field workforce to support these daily operations. Having the capability to get information into and out of the field in a timely manner can increase the efficiency and effectiveness of the organization. Information collected in the field using easy-to-use solutions can share information with solutions including the executive operational dashboard in near real-time allowing decision-makers within an organization to make more informed and timely decisions. These mobile solutions can also improve the workflows of field personnel by providing them with on-demand access to actionable and task-relevant information creating a more efficient and effective workforce.

In a scenario where the data already resides in a geodatabase, how can office staff or dispatchers send out staff to the field to inspect and evaluate the condition of an asset easily and quickly and ideally without a paper trail?

Simply put, the workflow can be streamlined with the use of Workforce for ArcGIS in conjunction with Collector for ArcGIS.

Workforce for ArcGIS: Creating an Assignment

With Workforce for ArcGIS, office staff can manage the deployment of all field crews by assigning jobs to each individually and monitoring their progress and position in real time.

Creating an assignment on the Workforce for ArcGIS web app allows for the dispatcher to:

  • Choose the assignment Type
  • Set the location of assignment (Address or   coordinate)
  • Choose the staff member
  • Set Priority of assignment
  • Set the due date/time for completion
  • Description of assignment/task
  • Attach files for use by the field staff such as images or technical drawings.

Assignments are sent to the field worker via an internet connection to their mobile phones or tablets, running on Android, iOS or Windows 10.


Once the assignment has been created, the user in the field can choose to accept or decline the assignment, all of which will notify the dispatcher in the office.

When an assignment has been accepted and “Start” is chosen, the field user will access the details of the job as well as be able to access the applications used to both navigate to the location  or capture the data.


Navigating between Workforce for ArcGIS and Collector for ArcGIS on a mobile device

The user will choose the Collect option at the top-right in order for the hydrants to show on a map. Using Collector for ArcGIS allows for the user to access the existing feature where it’s properties can be altered.

Collector for ArcGIS: Feature attributes
Collector for ArcGIS: Editing feature attributes

Once a hydrant is selected, all it’s relevant data is displayed and ready to be edited, if required.

And when the inspection is complete, the tick at the top-left is selected, which will sync the data from the mobile device with the data source, keeping in mind that an internet connection is required.

Lastly, the applications will switch back to the Workforce for ArcGIS, where the field worker will select the “Finish” option, notifying the dispatcher of the assignments completion.


Collector and Survey123 for ArcGIS are also capable of capturing new features with the same workflow and do not require internet access though the location (GPS) has to be switched ON, on the mobile device.

Capturing data in the field has never been easier!

How to save over 70GB of hard drive space in one click!


Recently I found myself wondering where exactly all the space on my hard drive was going. One day it was there, and the next it was gone.

I did my usual Windows clean-up but still wasn’t happy with the outcome so I did a bit more exploring into the Esri side of things to see what could be done. And the answer, quite simply is, A LOT, with absolute minimal effort!

Today I am going to introduce you to a lesser known tool from the Data Management Toolbox (and definitely finding its way into my Top 10) called Compact.

The tool does what the name implies, specifically for file (and personal) geodatabases which we all characteristically have scattered across our hard drives.

The underlying architecture of these types of geodatabases relies on binary files – as you add, remove and edit data within the geodatabase these files become fragmented which ultimately decreases the performance of your database and takes up wasted space.

What compact does is rearrange how these files are stored on your disk, reducing the overall size and improving overall performance. WIN-WIN!

To explore just how much a difference this could possibly make, I wrote a script that could iterate through all of the directories on my computer, searching for these geodatabases to perform a compact operation on them. If you’re working with a specific feature class or a database is locked for whatever reason, the script will gracefully skip over it and continue on its hunt for free space in your directories. Your overall savings may vary based on the type of work you’re doing with your databases on a day-to-day basis, I personally saw a total of 70 GIGABYTES of data released back into the system. That’s a lot of 0s and 1s.

Geodatabase Compactor

I’ve made the script into a geoprocessing tool which you can download here. If you’re the more inquisitive type, you can right click on the tool in a Catalog window and click Edit to see the nuts and bolts – it’s a very good example of Python’s os.walk function to step through files and directories.

You can choose the nuclear option like I did, and scan an entire drive, or choose a specific directory for it to iterate through.

If you have background geoprocessing enabled, progress messages will be logged to the Results Window.

Depending on the number of geodatabases you have on your PC, the first run of the tool may take some time. Subsequent runs will be faster as your databases will already be optimised.

Happy space saving!

Make your own 3D web app

jsapiWe all know that ArcGIS comes with a very large number of out of the box apps that seemingly do just about everything! Surprisingly though, we often come across the problem of finding an app that “fits just right” with what you need to achieve. The solution to this is to build your own app using an API or Runtime. The beauty of the ArcGIS APIs and Runtimes is that they extend the platform – meaning you can leverage all the power of ArcGIS such as Server, map services, web maps, popups, geoprocessing, etc all in a front-end that suits your workflow, user needs and styling choices. This may seem daunting, but don’t be fooled, anyone can do it!

This post will take you through some basic steps to create your own custom web application using a 3D scene. We will use the ArcGIS JavaScript API 4.0 to make the app.

1. Getting started – setting up your environment

Like I said, this is really simple. There are only two things you need. Firstly, you will need an ArcGIS Online subscription to make a web scene that we will load into our custom app

Secondly, you will need is a JavaScript IDE (editor) such as Notepad++ or WebStorm (link).

And that’s it, we are ready to go!

2. Creating the web scene

Log in to your ArcGIS Online account and click the menu option entitled “Scene”. This is a familiar interface very similar to the “Map” tool that lets you other webmaps. Use this tool to create a web scene with your own data layers, popups and symbology. In my example, I have added the provinces of South Africa as a layer and extruded them to show some 3D.

Creating a web scene in ArcGIS Online

Make sure to save the scene when you are done and take note (copy into notepad) of the item id for the web scene. You can grab this from the address bar in your browser. My id is “0390e2ec01fa488a847d4e413f015cd0”.

Getting the web scene’s ID

Note that to make things easier, you can share your web scene publically. This will avoid your app needing to authenticate you when opening it (i.e. logging in). In future, you can add security to your app as required.

More info on how to create a web scene, go to this link.

3. Creating your web page structure

Open up a new, empty html file in your IDE of choice. We will first put in the basic structure of the HTML page to get us going (TIP: I have created myself a template that I can re-use as a starting point each time I want to create a new app – saving me the time of creating the structure). An HTML page consists of some mandatory sections:

  • HTML doctype declaration – so that a web browser knows that the page is an HTML file (and what version – we are using 5)
  • Head – this includes all necessary ‘meatadata’ for the web page including the styling and logic (javascript)
    • Title – be sure to set a readbale title that you will see on your browser tab
    • CSS – this is the styling file and its easiest to pull in the CDN hosted Esri stylesheet
    • Javascript libraries – this is the ‘core’ JS library that will enable all kinds of web mapping goodness, we will pull in the CDN hosted JSAPI from Esri (link)
    • Javascript – this is the logic of your won app, here will enter our code to load a scene view and any other logic we want from the page
  • Body – this is the HTML which provides the structure of the page using HTML tags (link)

Here is my basic skeleton template including the links to the CDN CSS and JavaScript libraries that make up the ArcGIS JavaScript API (v4.0):

<!DOCTYPE html>

<title>My First 3D Web App</title>

<link rel="stylesheet" href="">
<script src=""></script>

/* section for my custom code */


<!-- page layout will go here --> 


More info on creating HTML pages, go to this link.

4. Building the HTML page structure

Before we can add a map (or other elements) to the UI, we need to create the structure of the page itself. Now, there are many ways to skin this cat which I wont go into in this post, but I am going to use a couple of layers (“DIV”s in HTML parlance) to layout my page. This is where you can really start to have fun – since you are in full control of everything, you can choose layout, colours, fonts, graphics, etc to make you page look great!

Here is the HTML layout code that is inserted into the “body” section:

<div id="wrapper" style="position: absolute; top: 0; bottom: 0; left: 0; right: 0; background-color: rgb(200,200,200)">

  <div id="mapPanel" style="position: relative; float: left; width: 60%; height: 100%">

  <div id="mapDescription" style="position: relative; float: left; width: 40%; height: 100%; background-color: rgb(220,220,220)">
    <p style="margin: 10px; font: normal 10pt verdana;">Welcome to my very first 3D web app! You can click around and navigate the scene.</p>


5. Adding the JavaScript “Scene View”

Since v4.0 of the ArcGIS JavaScript API, Esri now uses a new pattern for adding maps to the view. This is done by first creating the map (which is a container) and then adding a view to that map.

Here is the code for loading my map which is inserted directly into the <script> section:

], function(SceneView, WebScene) {

  var scene = new WebScene({
    portalItem: {
      id: "0390e2ec01fa488a847d4e413f015cd0" // replace with your web scene's ID

  var view = new SceneView({
    container: "mapPanel",
    map: scene


Note that I have entered the Item ID from the web scene I created earlier as the reference. This means that the logic will now create a scene container, find the scene item by its id and load that into the scene as a view. Too easy!

More info on the ArcGIS JavaScript API, go to this link.

6. Revel in your mastery

And that’s it! You have created your first 3D web app. To view it, simply open the HTML page in your favourite browser (JSAPI v4.0 is supported in Chrome, Firefox, and IE 11).

Here is a screenshot of my first app:

My First 3D Web App!

Happy coding!

– Richard

Moving and shaking the mining industry

Esri MUGAnyone who believes that Mining, as an industry and technology consumer, is standing by and doing nothing while it struggles through a major downturn, surely did not attend the Esri Mining User Group (MUG) meeting, recently held at the University of Pretoria’s Virtual Reality Centre for Mine Design (link).

Although it is true that the impacts of new ideas and new technologies may not yet have resuscitated the status quo, there is certainly hope, perhaps due to the current economic climate, that these changes to our thinking and doing within operational mining will bring about true business disruption for the greater good.

The advent of true integrating technologies such as ArcGIS as well as other powerful process, analytical and visualisation tools is showing that things need not be what they have always been.

Providing an industry-wide glimpse of new capabilities, Esri partners spoke about some promising new developments including direct geospatial enablement of governance and risk systems (Isometrix), geotechnical integration and analysis with slope monitoring systems (Aciel Geomatics), the blurring of OT and IT systems (OSIsoft) and the new business outlook for Spatial Dimension (Trimble).

Certainly a highlight of the day was the use of the Virtual Reality Centre’s demo theatre; a 360-degree immersive VR cylinder that showcased some initial R&D underway with key partners, looking at how VR can enhance mine planning, production analysis, above-to-underground visualisation and other high value 3D questions in a truly immersive environment. Breaking down barriers of understanding to achieve better decisions and outcomes is the ultimate goal… Watch this space!

But the day was ultimately focussed on our users.

Esri MUG 2

Miranda Muller from AngloGold Ashanti gave some inspiring insights into how to pilot new technologies in an industry that is typically averse to trying cutting-edge tech including drones, IoT and VR.

Theodor Paetzold spoke about how Rio Tinto is trying to resurrect its global user groups that assist in creating a global GIS community for better support and collaboration.

Pieter Mostert at Anglo American gave some create insight into how GIS technology has been used to improve the business of mineral exploration and the entire mining value chain –by creating a single integrated source of the truth for people to access anywhere around the globe.

Finally, Professor Fred Cawood of the University of Witwatersrand rounded things off seriously by addressing some of the pressing questions and ideas needed for moving the mining industry forward in a decline against the backdrop of our socio-political climate.

Carl Bester, from Esri South Africa, gave a ‘mid-term’ update of ArcGIS for Mining and how it has been received by our current users since it has evolved over the past few years. He also provided some insight for new and emerging users on the possibilities of creating an interconnected geospatial platform within a mining operation to deliver the right information, at the right time, in the right way to the people who need it.

It is an exciting space that is ever expanding, leveraging the new tools and capabilities of ArcGIS, and contributing to the changing face of information and data in the mining industry.

All these talks provided some thought provoking concepts that showed how, by embracing digital technology, we can revive and ultimately disrupt the mining industry. The focus is on us, the technologists, to be the agents of change within our organisations to push through new developments that have been proven to be beneficial to the industry.

The Esri MUG is a collaborative forum that aims to bring users with common challenges and experiences together to learn and share ideas. The meeting at Tuks was just one such initiative and we welcome further ideas on how to improve this teamwork approach. Esri South Africa will be hosting more MUG events in future, do join us next time.

Please drop us a line if you would like to know more about the discussions and presentations offered on the day.

– Richard

Improving underground mine safety

Pillar safety analysis on the map:

Thinking about Lily Mine as reported by Mail & Guardian on February 15,2016, that the central pillar of ore, called a crown pillar, collapsed subsequently leading to the lamp room which was at the entrance swallowed up by the sinkhole burying three mine employees. This made me to think of the underground solutions we have implemented using 1ArcGIS for Mining to visually analyse on the map the safety factor of pillars individually and accumulatively, and be able to overlay on that single map – mine progress, surface infrastructure and all other related mine assets.

Many mine incidents recorded in the past have always been linked with pillar failure. Geotechnical engineers in an effort to predict and minimise such incidents; use proven, yet complex mathematical calculations to determine the safety factor of pillars in the mine. Most of these calculations are time consuming to replicate and difficult to display to relate them with other possible surrounding risks as well as the cumulative effect with surrounding pillars.

Applying Geography using ArcGIS has proven that it can remove technology barriers between different mine technical systems and save time to get to the answer required to making a decision. Using the application in a coal mine to calculate and display the pillar safety factor in historical workings and active areas proved to be highly beneficial. A complex geotechnical method was incorporated into ArcGIS platform with variable parameters taken into consideration including pillar shape, distance between pillars, size, material and other surface irregularities of the hanging wall and foot-wall.  The pillar safety factors were easily displayed and shared to key stakeholders and accessible using any device such as iPad, enabling decision makers to make decisions wherever they were. It became much easier to replicate the model for other mines with flexibility to change parameters. The time to load new data entries and to verified them on accuracy drop from taking months into seconds.

Safety Factor

This did not only improve the method used and data quality. It also flagged risk areas that were never considered before in the underground workings and on surface by enabling visibility of other assets that were at risk of sinkholes should a pillar collapse.

1ArcGIS for Mining is a mining focused solution leveraging ArcGIS Platform technology



Monitor your assets in real time

As part of the ArcGIS Platform, the GeoEvent Extension for Server enables real time data processing and works seamlessly with your other ArcGIS software. Several of our clients have a need to monitor their business data in real time, and need to track their vehicles / assets to ensure all business processes run smoothly. ArcGIS GeoEvent Extension for Server enables an organisation to filter and process their event data in real-time and this allows them to connect and view virtually any type of streaming data from their device or office.

Setting up the GeoEvent Extension for ArcGIS Server can be tricky and in this blog we hope to cover all the necessary steps to make it work. We have implemented GeoEvent Extension for Server mostly at organisations that need to view the near real time location of their vehicles – consuming telematics data. In our example the data we are using has the following records:

  • vehicle id
  • event time
  • ignition on or off
  • speed of vehicle (km/hr)
  • g-force data

One of the requirements is to send out notifications to both the delivery service manager and to the delivery recipient. Three types of notifications are required for this scenario:

  • when vehicle enters a dangerous zone (e.g. a known hijacking zone)
  • when vehicle is driving above the speed limit
  • when driver is within 5 km of the location where the parcel is being delivered

The driver behaviour warnings are sent to the delivery service manager, while the delivery recipient is notified that the driver is close to delivery.

  1. Create an empty feature class in an enterprise database using the schema of the csv file.

You can download the xlsx file and convert it to csv.

Note: use the coordinates in the csv file to create the feature class and delete all the records using the truncate tool.

2. Create a zoning / geofences feature class in the enterprise geodatabase.

Note: create domains in the geodatabase for the type of zone e.g. Dangerous / Buffer; and style the data accordingly.

3. Publish a map service to ArcGIS Server.

Note: feature access must be enabled (both datasets must be from the same enterprise geodatabase).

2 feature access

4. Import the GeoEvent Definitions using the ArcGIS Server feature service.

Note: Make sure the ArcGIS Server or Portal is registered with GeoEvent Server. Use the tracking layer (step 1).

3 register server5. Import the GeoFences and create GeoFence Synchronization Rules using the ArcGIS server feature service.

Note: Use the zoning / geofences layer (step 2).

4 geofence

5 geofence sync


6. Add and configure the csv file as an input service.

Note: use the Receive Text from a TCP Socket for the Input Connector. The Server Port must match the port that will be used in the simulator.

6 tcp text in

7. Add and configure the tracking layer feature service as an output service.

Note: use the Add a Feature for the Output Connector.

7 car fs out

8. Various notifications can be created to inform the delivery service manager or the delivery recipient. In this example Send an Email was used as an Output Connector.

Note: Access to an SMTP server is required – contact your system administrator for help with this, or you can use gmail for testing purposes.

8 email buffer

9. Create and Publish a GeoEvent Service to connect your inputs (step 6) to the various outputs (step 7 & 8).

Note: txt-to-car is a processor; speed, buffer-zones and dangerous-zones are all filters.

9 geoevent service

txt-to-car:10 txt to car

speed:11 speed

buffer-zones:12 buffer zones

dangerous-zones:13 dangerous zones

10. Upload the csv file in GeoEvent Simulator.

14 load from file

11. Connect to the server and port (step 6). Set all the other settings and play the simulator.

15 simulator

The results can be viewed in a web map or application (Portal) or desktop. Notifications will be received as zones are reached or when the vehicle is speeding.

16 web map

Use the 11 steps above to set up your GeoEvent Extension for Server. The data can now be viewed in a web map from virtually any device.