V 5.0.1
| Features | Menus | Appendix |
Note : Files in these formats may contain geodetic information, but it is not always the case.
| Format | Description | Georeferencing | Notes |
| TIFF | TIFF Format | complete | GeoVisu can read TIFF formats non-compressed, CCITT T6 (or Group 4),
Packbits and LZW
(1, 8, 24 bits), but not TIFF JPEG, CCITT 1D, CCITT T4 (or Group 3).
GeoVisu doesn't read "User defined" geodetic information. |
| ECW | On Windows, GeoVisu displays ECW format using ECW-SDK v2.46 provided by ER-Mapper. | complete | |
| MrSID | GeoVisu displays MrSID format using GeoExpress SDK v6.0.7.1407 provided by par LizardTech. | These images don't contain geodetic system information and you have to choose it when loading. If the selected geodetic system is wrong (especially regarding to geographic or projected (cartographic) coordinates), file is loaded but it is not displayed correctly. | |
| GTM 211 | GPS TrackMaker files may contain one or several georeferenced images. | complete | |
| OziExplorer MAP | These files contain transformation points for a given image file. | GeoVisu calculates an affine transformation to process the bitmap. |
| Format | Description | Georeferencing | Notes |
| JPEG | JPEG Exif format, Baseline or Progressive Huffman, containing Exif GPS tag. | Position in WGS84 |
Graphics all have coordinates, but may or may not contain geodetic information.
| Format | Description | Georeferencing | Notes |
| OSM | OpenStreetMap XML format | WGS84 | As OSM has a moving "Map features" data model,
user can modify feature display attributes. GeoVisu reads versions 0.5 and 0.6. |
| MIF | Mapinfo Interchange Format | complete | Associated MID file is not loaded. |
| KML, KMZ | Google Earth (Keyhole Markup Language) | WGS84 | |
| MP | Polish map format, text format from cGPSmapper | WGS84 | |
| SHP | Esri Shapefile format | These graphics don't contain geodetic system information and you have to choose it when loading. If the selected geodetic system is wrong (especially regarding to geographic or projected (cartographic) coordinates), file is loaded but it is not displayed correctly. | Associated DBF file is not loaded. |
| WinAPRS | WinAPRS MAP | These graphics never contain geodetic system information, but they always are in geographic coordinates. Therefore the system expects geographic system. | |
| OVL | Geogrid ASCII Overlay | WGS84 | |
| geonames.org | XML files from geonames.org | WGS84 |
| Format | Description | Notes |
| GPX | GPS eXchange Format | |
| NMEA | Raw NMEA log | |
| MapSend | Magellan MapSend | |
| GTM 211 | GPS TrackMaker (binary) | |
| GTM 212 | GPS TrackMaker text | |
| OziExplorer | Waypoint, tracklog, route, event and point files | |
| Magellan | Raw Magellan log (NMEA format) | |
| USR | Lowrance USR | |
| TK1, TK2, TK3 | Wintec | GeoVisu does not read TK4 waypoint format from WGS1000/GTender. |
| Garmin XML | Garmin Training Center and Forerunner Logbook (HST, CRS) | |
| PCX5 | Garmin PCX5 | |
| MapShow | Alan Map, Holux | Tracklogs and waypoints (WPO, WPR, TRL) |
| Emtac Trine | Raw Emtac Trine log (NMEA format) | |
| GVT GVW GVR |
GeoVisu Tracklogs GeoVisu Waypoints GeoVisu Routes |
GeoVisu uses its own data format to store data downloaded from Garmin et Navilink GPS receivers. These are ASCII files. They can be easily altered. See format in Appendix C. Coordinate system is WGS84. |
| GVN | GeoVisu Navigation | GeoVisu uses its own data format to store data downloaded from Globalsat, Wintec, Skytraq, Navilink GPS dataloggers. These are ASCII files. They can be easily altered. See format in Appendix C. Coordinate system is WGS84. |
| RTKT | Binary Royaltek log prefixed by NMEA sentences. | |
| MTKT | Binary Mediatek (MTK) log prefixed by NMEA sentences. |
GeoVisu reads compressed files in format Gzip (gz) and ZIP. If these files contain georeferenced images or graphics, these will be displayed, except formats ECW and MrSID.
GeoVisu can access Web files by HTTP protocol.
You can tell GeoVisu which file names to displayed either
filelist format (see below).Three configurations can be specified using configuration file :
HTTP followed by something
else than PROXY,
GeoVisu does not connect to the Web.
GeoVisu can access Web files by ECWP protocol using ECW-SDK v2.46 delivered by ER-Mapper.
Loading is done according to the following conditions :
HTTP followed by something
else than PROXY, GeoVisu does not connect to the Web.
A file in .filelist format> is a list of files to be displayed by GeoVisu.
This is especially useful to tell the software wich files to
load from the Web.
File syntax :
The first line of the file is the header :
FileList V1.0
Then, there is one file name per line.
The extension of this format is .filelist
Example :
FileList V1.0 http://geovisu.free.fr/photos/7DPICT3309.jpg c:\images\map.tif c:\graphics\world.shp
A geodetic system is a coordinate system used to express coordinates of positions on Earth.
A geodetic system is described mainly by its spheroid and its origin. The two of them depend on the region to
which the system apply.
Several organizations index geodetic systems.
GeoVisu integrates geodetic systems indexed by
EPSG v6.11, Mapinfo v7.8, and ERMapper.
Moreover, GeoVisu indexes some additional systems ;
for a total of 437 "datum", 82 spheroids, 14 meridians and 817 geocentric transformations.
Finally, GeoVisu supports system codifications used in formats GeoTiff, Garmin,
OziExplorer, GPS TrackMaker.
Cartographic projection systems are used to display an image of a region of the Earth on a plane surface.
GeoVisu supports following projection methods :
Projection method Application regions (non exhaustive) Lambert conic tangent (1 parallel)
Lambert conic secant (2 parallels)France, Belgium, Estonia, some states of Canada and the USA Mercator tangent (1 parallel)
Mercator secant (2 parallels)World, marine charts Transverse Mercator
(including Gauss-Krüger and UTM)World regions, Eastern Europe, Russia, French DOM-TOM, some states of the USA Oblique Mercator
Rosenmund
HotineBorneo
Swiss, Hungary
Alaska, Malaysia, MichiganGauss-Laborde Réunion Polar Stereographic Polar regions (Double) Oblique Stereographic Netherlands, New-Brunswick, Prince Edward Krovak Czech Republic Equirectangular World
GeoVisu uses formats GVW and GVR version 2 when downloading
waypoints and routes from Garmin and Navilink GPS receivers.
Format GVT version 2 is used when downloading
tracklogs from Garmin GPS receivers.
Since GeoVisu version 2.2.0, earlier GVW and GVT formats
are still supported for reading, but are no more written.
Waypoint file (.gvw) stores records containing some fields among these :
identifier;longitude;latitude;comment;geovisu_symbol;gps_symbol;display;red;green;blue;altitude;depth;temperature;time;class;subclass;country;state;city;facility;
Field Description identifier Identifier is a variable length string, between string delimiters. longitude
latitudeLongitude and latitude are in WGS 84 and in decimal degrees. comment Comment is a variable length string between string delimiters. geovisu_symbol GeoVisu symbol is a numerical code. gps_symbol The numerical code as it is stored in GPS receiver ; this information is conserved since GeoVisu does not own so many symbols as some GPS receivers. display A code meaning display mode :
0 = identifier + symbol, 1 = symbol only, 2 = comment + symbol.red
green
blueColor is stored in three numerical values for red, green, blue respectively. altitude Altitude is in meters. depth Depth is in meters. temperature Temperature is in degrees Celcius. time Time is a string in format ISO-8601, between string delimiters. Next fields are not used by GeoVisu.
File starts with line
GVW-V2_GeoVisu_Waypoint
followed by a comment line (giving product number of GPS receiver).
Third line mentions which data fields are present in the file records, with respect to the following order :
identifier;longitude;latitude;comment;geovisu_symbol;gps_symbol;display;red;green;blue;altitude;depth;temperature;time;class;subclass;country;state;city;facility;
If a field value is 0 in this line, then corresponding field is not present in the records.
Possible values for fields in this line are 0 or 1 ; except for
gps_symbol which is the symbol format used by GPS receiver : 0, 1 or 2 (if this value is 1,
the value of field gps_symbol in records will be identical to the one of field
geovisu_symbol ; 2 is Garmin format, 4 is Navilink format).
This is followed by the data records, one per line, each containing the fields identified by a non-zero value in the header line.
Example :
GVW-V2_GeoVisu_Waypoint Garmin 97 D103 1;1;1;1;1;1;1;0;0;0;0;0;0;0;0;0;0;0;0;0; "HTRCNG";3.160774111747742;50.720095038414001;"HOTEL";0;0;2; "ILE";-4.567093933001161;48.638287782669067;"";0;0;0; "KRFPUR";1.393713355064392;43.608947396278381;"CARREFOUR";0;0;2; "MARSLE";5.385017395019531;43.284587860107422;"MARSEILLE";0;0;1;
Tracklog file (.gvt) starts with line
GVT-V2_GeoVisu_Tracklog
followed by a comment line (giving product number of GPS receiver).
Third line mentions which data fields are present in track headers, with respect to the following order :
identifier;number;red;green;blue;thickness;display;point_number;
Field Description identifier Identifier is a variable length string, between string delimiters. number Number replaces identifier on some GPS receivers (in theory, both are not present simultaneously). red
green
blueColor is stored in three numerical values for red, green, blue respectively. thickness Thickness is currently not provided by any GPS receiver, this field will therefore nether be present. display Display field is not used by GeoVisu. point_number The number of points in tracklog must always be present.
In the same way, fourth line tells which data fields are present in trackpoints, in the following order :
longitude;latitude;time;starttrack;altitude;depth;temperature;
Field Description longitude
latitudeLongitude and latitude are in WGS 84 and in decimal degrees. time Time is a string in format ISO-8601, between string delimiters. starttrack Flag of beginning of tracksegment (value = 1) or not (value = 0).
A tracklog may consist of several tracksegments.altitude Altitude is in meters. depth Depth is in meters. temperature Temperature is in degrees Celcius.
Then follow records : for each tracklog, a header line (even if GPS receiver does not use tracklog headers, it will contain at least field Number of points) ; then, one per line, tracklog points.
Example :
GVT-V2_GeoVisu_Tracklog Garmin 97 A300 0;0;0;0;0;0;0;1; 1;1;1;1;0;0;0; 5; 12.571514534950256;8.231505274772644;"2005-05-15T16:25:21Z";1; 12.571535992622376;8.231601834297180;"2005-05-15T17:25:34Z";0; 12.571595001220703;8.231773495674133;"2005-05-15T16:26:01Z";0; 12.571557450294495;8.232057809829712;"2005-05-15T17:26:17Z";0; 12.571396517753601;8.232846379280090;"2005-05-15T16:26:26Z";0;
Route file (.gvr) starts with line
GVR-V2_GeoVisu_Route
followed by a comment line (giving product number of GPS receiver).
Third line mentions which data fields are present in route headers, with respect to the following order :
number;name;comment;red;green;blue;point_number;
Field Description number Route number replaces name on some GPS receivers (in general, both are not simultaneouly present). name Name is a variable length string, between string delimiters. comment Comment is a variable length string between string delimiters. red
green
blueColor is stored in three numerical values for red, green, blue respectively. point_number The number of waypoints in route must be always present.
In the same way, fourth line tells presence or not of fields in waypoints, in the same order as format GVW.
Then follow records : for each route, a header line ; then, one per line, route waypoints.
Example :
GVR-V2_GeoVisu_Route Garmin Quest SYS Software Version 3.50 231 D202 0;1;0;0;0;0;1; 1;1;1;1;1;2;1;1;1;1;1;1;1;1;1;1;1;1;1;1; "ORIGINEde";97; "Autoroute Du Soleil(NW)";3.105568885803223;48.051495552062988;"";0;36;0;000;000;000;9.999999562024e+024;9.999999562024e+024;9.999999562024e+024;"1989-12-30T23:59:59Z";128;"";" ";" ";"";""; " A6(NW)";3.048963546752930;48.082952499389648;"";0;36;0;000;000;000;9.999999562024e+024;9.999999562024e+024;9.999999562024e+024;"1989-12-30T23:59:59Z";128;"";" ";" ";"";""; " A6(M)";2.999997138977051;48.111577033996582;"";0;36;0;000;000;000;9.999999562024e+024;9.999999562024e+024;9.999999562024e+024;"1989-12-30T23:59:59Z";128;"";" ";" ";"";"";
GeoVisu uses format GVN version 3 when downloading
logs from GPS dataloggers whose protocol is wholly binary :
GlobalSat (DG-100, BT-338), Wintec (WBT2001/GRays2, WPL1000, WGS1000/GTender),
Skytraq and Navilink.
This format exists since version 4.0.0 of GeoVisu.
In the case of Navilink, this format is used for both
tracklog and datalog. So, tracklog file is suffixed with .track
and datalog file is suffixed with .datalog .
Navigation file (.gvn) starts with line
GVN-V3_GeoVisu_Navigation
followed by a comment line (giving product number of GPS receiver).
This is followed by data records, one per line, each containing the fields at format below :
longitude;latitude;time;trackflag;altitude;height;depth;temperature;speed;direction;nbsatsinvue;nbsatsused;dgps;fix;hdop;pdop;
Champ Description longitude
latitudeLongitude and latitude are in WGS 84 and in decimal degrees. time Time is a string in format ISO-8601, between string delimiters. trackflag Flag is made of 2 bits (first and second) : start of tracksegment (bit 1) and push-to-log point (bit 2).
- If flag value is 1 or 3 : it is the start of a tracksegment.
- If flag value is 2 or 3 : it is a push-to-log point.altitude Altitude is above the geoid.
It is in meters.height Height est is above the ellipsoid.
It is in meters.depth Depth is in meters. temperature Temperature is in degrees Celcius. speed Speed is in km/h. direction Direction is angle in degrees. nbsatsinvue Number of satellites in vue. nbsatsused Number of satellites actually used to calculate position. dgps Flag of using or not of DGPS or WAAS/EGNOS. fix Fix quality of position :
0 = no fix (invalid position)
1 : fix obtained with unknown quality
2 : 2D
3 : 3D
> 3 = use of DGPS or WAAS/EGNOS.hdop Horizontal dilution of precision. pdop (Position) 3D dilution of precision.
All field are always present, maybe empty.
You can write comment lines at any place in the file : lines beginning with # are comments.
Example :
GVN-V3_GeoVisu_Navigation #GlobalSat DG-100 ID 0000000000000000 #longitude;latitude;time;starttrack;altitude;geoidh;depth;temperature;speed;direction;nbsatsinvue;nbsatsused;dgps;fix;hdop;pdop; 12.571514534950256;8.231505274772644;"2005-05-15T16:25:21Z";;4.100000000000e+001;;;;52.20000;;;;;;;; 12.571535992622376;8.231601834297180;"2005-05-15T17:25:34Z";;3.900000000000e+001;;;;58.30000;;;;;;;; 12.571595001220703;8.231773495674133;"2005-05-15T16:26:01Z";;3.800000000000e+001;;;;63.20000;;;;;;;; 12.571557450294495;8.232057809829712;"2005-05-15T17:26:17Z";;4.000000000000e+001;;;;86.90000;;;;;;;; 12.571396517753601;8.232846379280090;"2005-05-15T16:26:26Z";;3.600000000000e+001;;;;118.50000;;;;;;;;
Rules for the file to be valid :
When the protocol used to download data from GPS receiver is proprietary NMEA,
GeoVisu stores these data as raw data (without any transformation).
It is the case for Magellan (extensions : .mglw for waypoints,
.mglt for tracklogs, .mglr for routes)
and Emtac Trine (datalog, extension .emt).
Other GPS receivers use proprietary NMEA protocol to intiate the communication,
then send their data using a binary format.
That's the case for Royaltek (RGM-3800, RBT-2300, RCD-1000)
and Mediatek / MTK.
In that case, GeoVisu also stores raw data received from GPS (without any transformation) ;
the file (whose extension is respectively : .rtkt
for Royaltek and .mtkt for MTK) therefore contains some binary data.
| Features | Menus | Appendix |