mobility-service-interface module code review

SummerMentorshipProgram 2014 RoutesMobilityModel - Mobility trace generation using the Google Maps API.

Mobility trace generation in ns-3 is done either by using the Mobility module included in NS-3 or by importing mobility traces generated by third party programs in a compatible format. The Mobility module included in ns-3 gives programmers the building blocks to create simple or complex traces, but is hindered by the fact that creating complex traces using the current module alone takes too long, even for simulations with just a couple of mobility capable nodes. As for mobility traces generated by third party programs, such as SUMO, they can involve too much work for their generation, especially when the researcher's interest - and expertise - is more on the data communication than on the traffic simulation. Using the Google Maps API it is possible to generate complex mobility traces, simply by providing a start and end point. Since the API is robust, well documented and supported, it can be assumed it will be available in the future.

This patch covers my development from the beginning of the project.
This module supports the following features:

 * Mobility trace generation for nodes
 * Mobility traces with dynamic redirection
 * Automatic creation of mobility for a node container
 * Create mobility traces for nodes using local XML files

One test was developed, to test for the conversion of the WSG84 coordinates to Cartesian coordinates, the time placement of the |ns3::Waypoints| and the polyline conversion algorithm.

Three examples illustrate typical uses for this module
 * routes-mobility-example.cc
 * routes-mobility-automatic-example.cc
 * routes-mobility-offline-example.cc


A Google Maps API key must be created in order to use this module. Information on how to create a Google Maps API key is on the module sphinx documentation.
The API key must be placed in the file src/mobility-service-interface/conf/api-key.txt

More information on this module can be found in the file src/mobility-service-interface/doc/mobility-service-interface.rst and on the project wiki [1].

[1] - http://www.nsnam.org/wiki/RoutesMobilityModel

[tiago.cerqueira, 2014-12-07 01:23:40]

SummerMentorshipProgram 2014 RoutesMobilityModel - Mobility trace generation
using the Google Maps API.

Mobility trace generation in ns-3 is done either by using the Mobility module
included in NS-3 or by importing mobility traces generated by third party
programs in a compatible format. The Mobility module included in ns-3 gives
programmers the building blocks to create simple or complex traces, but is
hindered by the fact that creating complex traces using the current module alone
takes too long, even for simulations with just a couple of mobility capable
nodes. As for mobility traces generated by third party programs, such as SUMO,
they can involve too much work for their generation, especially when the
researcher's interest - and expertise - is more on the data communication than
on the traffic simulation. Using the Google Maps API it is possible to generate
complex mobility traces, simply by providing a start and end point. Since the
API is robust, well documented and supported, it can be assumed it will be
available in the future.

This patch covers my development from the beginning of the project.
This module supports the following features:

 * Mobility trace generation for nodes
 * Mobility traces with dynamic redirection
 * Automatic creation of mobility for a node container
 * Create mobility traces for nodes using local XML files

One test was developed, to test for the conversion of the WSG84 coordinates to
Cartesian coordinates, the time placement of the |ns3::Waypoints| and the
polyline conversion algorithm.

Three examples illustrate typical uses for this module
 * routes-mobility-example.cc
 * routes-mobility-automatic-example.cc
 * routes-mobility-offline-example.cc

A Google Maps API key must be created in order to use this module. Information
on how to create a Google Maps API key is on the module sphinx documentation.
The API key must be placed in the file
src/mobility-service-interface/conf/api-key.txt

More information on this module can be found in the file
src/mobility-service-interface/doc/mobility-service-interface.rst and on the
project wiki [1].

[1] - http://www.nsnam.org/wiki/RoutesMobilityModel