GPXSee opens GPX, TCX, FIT, KML, IGC, NMEA and Garmin CSV files, however not all format features are supported for all formats. Generally, GPXSee supports three kinds of data objects:
Naturally, if a format supports only a subset of the objects, GPXSee also supports only this subset. Some formats - especially KML - have support for a plenty of other data objects like surfaces or even 3D structures. Those are not supported by GPXSee.
In addition to GPS data, data from the following sensors is supported by GPXSee:
- Heart rate
Two kinds of maps are supported by GPXSee - online maps and offline maps. You may either load them "ad hoc" from the GUI or they can be loaded automatically at program startup from the following directory:
User specific map directories that - when present - override the global map directory are also supported. The paths are as follows:
|OS X, Linux:||$HOME/.gpxsee/maps|
The map directory is recursively searched when loading the maps, so it may contain an arbitrary directory structure.
The mapsource definition file format is based on XML and is fairly simple. For the formal map source file syntax see the mapsource XSD file. The paragraphs below are a "human-readable" summary of the XSD syntax/semantics divided by map type.
The root map element contains two mandatory elements - name
and url, and two optional elements - zoom and bounds.
The tile X and Y coordinates are replaced with
$y in the URL and the zoom level is replaced with
$z. An example map source definition file can look like:
<?xml version="1.0" encoding="UTF-8"?> <map xmlns="http://www.gpxsee.org/map/1" type="OSM"> <name>USGS Imagery</name> <url>https://navigator.er.usgs.gov/tiles/aerial_Imagery.cgi/$z/$x/$y</url> <zoom min="2" max="15"/> <bounds bottom="0" top="74"/> </map>
The bounds are WGS84 latitude/longitude values in degrees. If omitted, the default zoom range is <0, 19> and the default bounds are <-85.0511, 85.0511> and <-180, 180>.
WMTS maps are distinguished by setting the type attribute of the
map element to
WMTS. Both the KVP and REST access methods
For KVP, the url element represents the WMTS base URL and two
additional elements are required - layer and set
(TileMatrixSet in WMTS). Optional format and style elements may
be specified defining the desired image format and layer style. If not set,
image/png is used for format and the default style for
<?xml version="1.0" encoding="UTF-8"?> <map xmlns="http://www.gpxsee.org/map/1" type="WMTS"> <name>CUZK</name> <url>http://geoportal.cuzk.cz/WMTS_ZM_900913/WMTService.aspx</url> <layer>zm</layer> <set axis="yx">ogc:1.0:globalcrs84pixel</set> </map>
For REST access, the url element's type attribute must be set
REST. The URL then represents the URL of the capabilities XML
document. Defining the format has no relevance for the REST access method.
<?xml version="1.0" encoding="UTF-8"?> <map xmlns="http://www.gpxsee.org/map/1" type="WMTS"> <name>Wien - Ortho</name> <url type="REST">http://maps1.wien.gv.at/wmts/1.0.0/WMTSCapabilities.xml</url> <layer>lb</layer> <style>farbe</style> <set>google3857</set> </map>
There is one more important attribute - the axis attribute of the
set element. It specifies the axis order of the CRS used for the
tile matrix set. The default order is obtained from the CRS definition like
specified in the standard, but in praxis many servers use a wrong order. This
is why GPXSee enables overriding the default axis order using the axis
attribute. Possible values are
Finally, one can define additional dimensions like
the dimension element. Use a separate entry for every additional dimension.
WMS maps are distinguished by setting the type attribute of the
map element to
WMS. WMS map definitions are very similar to
WMTS map definitions, the main difference is that you must specify the map
CRS using the crs element instead of specifying the tile set. Like in the
case of the set element, you may specify the axis attribute to
override the default axis order.
It is possible to combine multiple WMS layers together in one map. To do so, use a comma separated list of WMS layers as the layer element content and a corresponding comma separated list as the style element content (can be omitted if all styles are the default style).
<?xml version="1.0" encoding="UTF-8"?> <map xmlns="http://www.gpxsee.org/map/1" type="WMS"> <name>Katastr nemovitostí</name> <url>http://services.cuzk.cz/wms/wms.asp</url> <layer>polygony_parcel,polygony_budov,polygony_k_u</layer> <crs axis="yx">EPSG:3034</crs> </map>
OziExplorer maps, TrekBuddy maps/atlases, Garmin JNX maps and GeoTIFF images are supported by GPXSee. Supported map projections are Mercator (including Web Mercator), Transverse Mercator (including UTM), Lambert Conformal Conic, Albers Equal Area, Lambert Azimuthal Equal Area, Křovák's and Latitude/Longitude (2D geographic). Additionally, the Swiss and Hungarian Oblique Mercator projections are aupported using LCC1 approximation. For list of supported datums and projected coordinate systems see the GCS.csv and PCS.csv configuration files (can be modified or overridden by user files like the map directory).
You may easily create offline atlases from online map services by using Mobile Atlas Creator (MOBAC).
All of the supported formats with waypoints capability - GPX, KML, TCX, NMEA and Garmin CSV - can be loaded either as data files or as POI files. When a file is opened as a POI file, only waypoints reasonable near the tracks/waypoints of the loaded data files are displayed.
To make GPXSee load a POI file automatically on startup, add the file to the
POI directory in one of the configuration paths.