GitLab

- Visualization
- Refactored Route-Sensor

- unified routing via RealWorldMovementPoints
- reduced overhead due to PositionVector calculations

and corresponding necessities.

~ Settings of the world size were not employed correctly. Furthermore, setting a different zoom for the visualisation / map would fuck up the positioning.
Now the specified world size is used correctly. Zoom is used to specify the zoom level (detail) on the map. Positioning now works with different zoom levels, however, when visualising positions they now need to be scaled to be drawn correctly.

 Minor changes in RealWorldStreetMovement to support new GraphHopper version.

~ Restructured some of the components
+ Debug Monitor to get information about the specific nodes.

- graph hopper needs a temp-folder with a file lock. The new setting
MOVEMENT_GRAPH_UNIQUE_FOLDERS can be used to force unique folders for
the temporary data. Remember to purge the osm folder manually every now
and then, as this will lead to large amounts of temp data in batched
runs.

Movement:
+ Added a multi-type movement model which allows changes of the movement-type mid-simulation per host

Spot Positioning:
+ (Car)Positions of the actors can now be recorded and written to a CSV File which can then be used for the placement of the spots

Spot Assignment:
+Actors don't get a DummyLocation as SpotAssignment anymore, now actual Spots are assigned
+First assignment strategy: Shortest distance assignment

Visualisation:
+ Visualisation Layer
+ OnClick now displays the destination, the assigned Spot and the searchThreshold.

- Attraction Points with weights and radii
- Local movement with correct speed in scaled scenarios
- New weighted transition strategy for local movement

- deprecated MovementSupported
- used LocationSensor and LocationActuator
- decoupled nested listener structures used within the old models

fix transition strategy to only fire once an Attraction Point is reached
remove POI limitation for Json-based Attraction Points

- Prior, moving at a certain speed towards a target position could lead
to overshooting and, thus, to oscillations.

and max for one component. 
Models MAY set a new speed as they wish (api of MovementSupported
changed to allow this behavior). Can be used, e.g., to update speed once
a target waypoint has been reached.

Martin Hellwig authored Jul 16, 2015 and Björn Richerzhagen committed Oct 27, 2015

Added two classes to visualize images as background. One loads background-images at runtime; Also runtime-loading of POIs are now possible