Prev (GPS Devices) | Home | Manual | (Commit Code) Next
(inspired by and partially copied from QMS newsgroup)
In the following data item means waypoint, track, route, or area.
There are 3 physical storage types used in QMS for saving data items:
GPX
files (common data format)QMS
files (proprietary efficient binary data format)SQLite
or MySQL
databasesIf selected in the menu Projects - Setup Workspace
data is saved automatically at the end of a QMS run and
regularly after some user-defined time interval.
A backup of databases is recommended from time to time.
All QMS data items belong to a project.
In the case of a GPX
or QMS
file all data in the file belong to one project
which can be loaded into the QMS workspace and saved from here to the file.
QMS allows the use of one or more databases.
Each database consists of a tree. Each node of the tree is either a folder or a data item. Nodes on the highest level must be folders.
There are 3 types of folders:
In addition to this there is a special Lost & Found folder. Deleted data items are kept in this folder. Data can be restored from this folder or deleted. No recovery is possible anymore in the last case.
Group folders can not contain data items. Only folders can be child nodes of a group folder. Thus, group folders can be used to group projects.
Project and other folders can have folders and data items as child nodes.
Folders of type other have the same features like those of type project. Their main purpose is to distinguish visibly between basic data of a project and secondary data in it.
If in the following discussion the term project is used, then this includes also the term other.
The described database structure can be seen in the QMS database view. Here projects and data items can be selected with the help of a checkbox for display in the QMS workspace.
With this database organisation several projects can be saved in one database.
Data items are saved only once in database. They can be referenced in various projects within a given database.
Example of data organisation:
A group folder (blue) with each hike track and its waypoints in a project folder (green).
Additionally, a green summary folder
that contains again all tracks from the other green folders. As the tracks are just referenced by the
folders they are not stored several times as would have done with GPX
or QMS
files.
Other advantages of the use of databases are the possibility
GPX
file everything in the file is completely loaded into the workspace,Search database
of the database (starting with QMS version 1.6.3.post).When creating a new reference to a data item QMS offers the choice either to create simply a reference or a clone (a copy) of the data item.
Source: gmane.comp.gis.qlandkartegt
With QMapShack version 1.6.1 or later:
If you use a database you do not have to load all data of a project. You can load only the items needed. Additionally, if you store a newly created project into the database you do not need to clone (duplicate) the data.
Move the mouse pointer on the database name in the main window. A bubble box appears and shows the physical name of the database file.
Source: www.naviboard.de
This problem appears with a vector map like Freizeitkarte where smaller roads/tracks are only visible at a zoom level where the overview gets lost.
There is no such possibility in QMapShack. The detail levels for vector map data are defined by the map author and can’t be changed within QMapShack.
Users reported about the following ways to improve the visibility of small roads:
View - Setup Map View - Projections&Datum
+lat_ts=60
This sets the latitude of true scale for a Mercator projection. The closer you get to the polar regions the more the map will be skewed horizontally in comparison to the vertical scale. At the latitude of true scale (usually 0 for the equator) the scales are equal.+k_0=0.3
(Source: gmane.comp.gis.qlandkartegt) This is an additional scale factor on the normal scale. A value of 1.0 will have no effect. Try to increase or decrease the given value to get the wanted resultSource: * www.naviboard.de * gmane.comp.gis.qlandkartegt.user
Routing in QMapShack depends on the Routino package and this package does not offer an option to select a preferred road type.
Routing profiles are saved in an XML-file (/usr/share/routino/profiles.xml). Here the preferences/weights of different road types can be modified by the user.
On Routino’s homepage there is an online version where fine
tuning of all parameters can be tried. Once done there one can take over the values into the local profiles.xml
file.
As a general rule don’t do this. QMS saves workspace information in the file workspace.db
. There is only one such
file for all QMS instances. If this file is used by several QMS instances at the same time then the
QMS workspace data behaviour is unpredictable.
qmapshack.exe
:.\translations
: language files.\routino-xml
: routino configuration files including profiles.xml
c:\Users\yor_user_name\AppData\Local\Temp\org.qlandkarte.QMapShack.log
: logfile written if command line option
-f
is usedc:\Users\your_user_name\.QMapShack
: tile caches for online mapsc:\Users\your_user_name\.config\QLandkarte\workspace.db
: backup of last used workspace - used when QMapShack is restartedDue to limitations in the Windows POSIX API Routino can’t handle files larger than 4GB.
Source: Newsgroup thread sourceforge.net/p/qlandkartegt
Calibrated Russian military and other raster maps can be downloaded from various locations.
One of the well known servers is loadmap.net. When downloading a map tile 2 files are created:
a GIF file with the raster map and an OZIExplorer
MAP file with calibration data.
QMapShack supports the use of raster maps via VRT-files. These files can be created with the GDALBuildVRT
tool
which can also be accessed from within QMapShack.
Doing so leads for the above mentioned maps to an error message indicating that
georeference data can’t be found within the MAP files.
To make the raster map usable for QMapShack the following procedure (described for a Windows installation) can be used:
GDAL
toolset and the proj.dll
are in the QMapShack installation directory.data
subdirectory of the QMapShack installation directory is properly installedgdalwarp -of VRT full_path_to_your_raster_map.map full_path_to_your_raster_map.vrt
GDALBuildVRT
does not find the georeference information. Hint for Ubuntu users: Raster maps may have borders. There is an Ubuntu tool to crop semi-automatically the map or a whole series of maps in such a way that the borders are not visible when loaded into QMapShack. Link to the tool: github.com/h4tr3d/geocrop. Description of usage:
Source: http://permalink.gmane.org/gmane.comp.gis.qlandkartegt.user/2624
Consider the following hints:
Use gdalinfo
to verify if the required vrt file provides proper information. Keep in mind that the vrt file
is just an XML wrapper around your
real raster map file. It stores a path to that file. If the path changes
the vrt has to be created again.
If the map is loaded correctly but drawing is suppressed because it
would take too long, the map boundary is still visible as a black frame.
* If you have a layer of raster maps reading the files and scaling the content to an upper zoomlevel is
getting more and more resource intensive the more you zoom out. To avoid endless map loading, QMS will
skip the map if the effort to display it is getting too large.
However if QMS detects overview levels attached to the map it will use them. gdaladdo
is the tool to do so.
Things are getting a bit more difficult for insane large map collections. gdaladdo
will create an overview
file over all maps combined in the vrt file. That might get too large. In this case you have to create single
overview files and combine them in a vrt.