2.1.4. Location Processing Enabler

2.1.4.1. Introduction 

This Enabler was scoped out from the original (Geo)localization Enabler. It’s been decided to split its functionality into two enablers – one concentrating mostly on the hardware part and this one – focusing on localization data processing. Eventually, the Location Processing Enabler will provide flexible geofencing capabilities allowing to:

2.1.4.2. Features 

define “regions” and “points” of interest, and identify them in a unique way
update the geometry of defined regions and points (possibly also in a streaming fashion)
query relationships between a given position and selected region/point(s)
create and subscribe to streams of “geofencing events”.

2.1.4.3. Place in architecture 

For ASSIST-IoT Pilot it will be closely used with Location Trackin EnBLER

2.1.4.4. User guide 

Will be determined after the release of the enabler.

2.1.4.5. Prerequisites 

2.1.4.5.1. Scala

Scala is a language of preference for the SRIPAS group. Scala provides support for functional idioms and static typing. Those two features and familiarity with the language are arguments for Scala in the IoT environment, to support high reliability demand of the business.

2.1.4.5.2. PostGIS

PostGIS is a spatial database extender for PostgreSQL object-relational database.

2.1.4.5.3. REST (Enabler’s API)

Currently it is decided as project-wide standard. REST is overall a web standard.

2.1.4. Location Processing Enabler

2.1.4.1. Introduction 

2.1.4.2. Features 

2.1.4.3. Place in architecture 

2.1.4.4. User guide 

2.1.4.5. Prerequisites 

2.1.4.5.1. Scala

2.1.4.5.2. PostGIS

2.1.4.5.3. REST (Enabler’s API)

2.1.4.6. Installation 

2.1.4.7. Configuration options 

2.1.4.8. Developer guide 

2.1.4.9. Version control and release 

2.1.4.10. License 