The Map View Menu

The map menu gives the possibility to access some additional map tools:

  • access the gps data list
  • access the spatialite data list.
  • toggle the scalebar
  • open the compass
  • toggle automatic centering on the gps position
  • center the view on the current base map (if possible)
  • go to a location
  • share the current position
  • view the data visible in the viewport in Mixare
  • import data from the underlying mapsforge map
_images/13_map_menu.png

The upper part of the map menu.

Gps data list

The gps data list shows the data surveyed, both points and tracks.

_images/14_gpsdatalist.png

The gps data view. In the upper part the notes button, in the lower part the gps logs list.

The notes are all kept inside a single layer and therefore have a dedicated panel in the upper part.

From there the user can change the visibility.

Notes can be visualized as icons or as circular shapes. The size, color and opacity can be customized by the user. This can be usefull in those cases in which many notes have to coexist in a small space for better readability.

It is also possible to show the label for the note and customize its size and halo.

_images/15_notes_properties.png

The notes properties panel.

Below the notes panel, a checkbox can be used to toggled visibility of image notes.

The list of gps logs gives the possibility to customize the logs. It is possible to change the visibility of the single track using the checkbox, but also to tap on it and enter its properties panel.

_images/16_log_properties.png

The gps log properties panel.

From the properties panel it is possible to:

  • change the name of the track
  • check the start and end date and time
  • update and read the track length
  • change the track stroke width
  • change the track stroke color
  • zoom to the first point of the track in the map view
  • chart the track. The chart has two axes, speed [m/s] on the left and elevation [m.s.l.] on the right.
_images/17_chart_log.png
  • remove the track

Spatialite data list

To be done...

_images/18_spatialite_data_list.png

The list of spatialite based data.

Spatialite Dash pattern: Dash patterns can be specified as dashWidth, dashGap, dashWidth2, dashGap2, dashWidth3, dashGap3, etc. The most basic case would be dashWidth, dashGap i.e. 10, 20.

Go to

The go to function has two possibilities:

  • go to coordinate
  • use geocoding and/or routing
_images/19_goto1.png

In the go to coordinate panel it is possible to insert lat/long coordinates and navigate to the inserted point on the map view:

_images/20_goto_coord.png

Through geocoding it is possible to insert some address and find its location (uses google maps geocoding).

_images/21_goto_point.png

From the same panel it is possible to create a route from the current position to the inserted location.

The services that can be used are OSRM, MapQuest and Graphhopper.

_images/23_goto_route_api.png

The routing service selection dialog with all supported services.

For both MapQuest and Graphhopper the user will need to register to their website and ask for an API-KEY. That key can be inserted in the Geopaparazzi settings. If no key is available, those two routing services will not appear in the available services choice list.

_images/22_goto_route_noapi.png

If no API-KEY is supplied, only OSRM is proposed.

Once the OK button is tapped, the route is calculated by the service starting from the current map center to the destination point. The route is then downloaded and placed in the gps logs tracks.

_images/24_route_rome.png

The fresh downloaded route from Bolzano to Rome.

Share position

The share position entry opens the usual sharing dialog of Android:

_images/25_share1.png

If for example telegram is chosen, the sent link will look like:

_images/26_telegram.png

Import mapsforge data

The mapsforge tiles are generated on the device from a particular vector format. This means that there are information available in the database. Problem is that, very very simply put, the information contained is extracted differently at different zoom levels, because in fact the library and the format have been done that way to allow best rendering performance.

But still it is possible to extract almost everything we see, which is nice.

Let’s see how this works. For this to work it is mandatory that the loaded background map is of type “map”. Assume you have a job to do, are out in the field and want view information overlayed on the ortofoto pictures from the local WMS service.

Well, the map file you get from mapsforge looks like the following:

_images/27_mapsforge1.png

Once the import mapsforge data has been chosen, its panel appears:

_images/27_mapsforge2.png

From the view you can see that 2 types of data can be imported: points and ways.

Points

Since the points are often visible on a different zoomlevel then the current, also 3 zoomlevels below the current are investigated to extract data and double points are not considered. So if you start this at zoomlevel 16, you will also get 17, 18, 19. Since the same are at a different zoomlevel will have many more tiles, about 10000 tiles are read to import the data.

You can add a filter text to import only tags containing a given text or exclude all those containing the text.

Points are imported in the current projectdatabase and saved as forms notes containing all the values Openstreetmap has. As such they can also be edited.

All imported notes have a (MF) in their name. That is done so one can quickly select and remove them. Believe us, that is a feature you want to have since such imports can generate very crowded notes lists.

_images/27_mapsforge10.png

The notes list after a mapsforge import.

Ways

Many types of ways are stored in the mapsforge map files and many of them are actually related to areas.

The user can choose to import:

  • ways: roads, railways, cableways and similar
  • waterways: lines that represent water
  • contours: contour lines if they are available

Since these data are heavy, the data are imported into a dedicated spatialite database. A database for mapsforge extracted data is automatically created if there is none present. You will find a database named mapsforge_extracted.sqlite always present in your maps folder. And you will find 3 layers always present in the spatialite data layers: osm_waterlines, osm_roads and osm_contours.

_images/27_mapsforge3.png

The mapsforge database and layer that host imported data.

Just select the data you want to import and push the start button. In the case you selected all data types, you should see first an import dialog like this:

_images/27_mapsforge4.png

and then something like this:

_images/27_mapsforge5.png

Depending on what has been imported first, the labels might not be coming from the right osm field. In that case it can be simply changed in the spatialite layer settings. Refer to the spatialite data list section.

What happens in the case we use a map that also shows contour lines? To do so, we want to clear those layers. The fastest way to do so is to simply delete the mapsforge database and let Geopaparazzi recreate it on restart.

After doing so and loading a map with contours the same region will import:

_images/27_mapsforge7.png

To have a better idea, change the background map to something different. Here I also changed the contours color to white:

_images/27_mapsforge8.png

Label support is not very advanced, so they get readable only once you zoom in:

_images/27_mapsforge9.png