Prev (GPS Devices) | Home | Manual | (Commit Code) Next


Frequently Asked Questions


How are QMS data items organised?

(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:

If 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

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.

Is there an easy way to “select all” the contents of one project to drag them into another?

Is there a way to merge projects together?

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.

How to find location of database file used in QMapShack?

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.

Is there a possibility to display small roads/tracks in a vector map without zooming in too much?

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:

Is there a possibility to choose the preferred road class when routing?

Source: * 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.

Can I run several QMS instances at the same time?

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.

User-relevant QMapShack directories (Windows version)

What is the maximum Routino databases file size that can be handled by the QMapShack Windows version?

Due to limitations in the Windows POSIX API Routino can’t handle files larger than 4GB.

How to use Russian military and similar raster maps with QMapShack?

Source: Newsgroup thread sourceforge.net/p/qlandkartegt

Why is a raster map not displayed?

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.

How to edit the elevation of a track point manually?


Prev (GPS Devices) | Home | Manual | (Commit Code) Next