Parent Directory | Revision Log
Ubuntu compile fixes, removed image loading option
1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | <ossohelpsource> |
3 | <folder> |
4 | <title>GPXView</title> |
5 | <topic> |
6 | <topictitle>License</topictitle> |
7 | <context contextUID="help_gpxview_license" /> |
8 | |
9 | <para>GPXView is free software: you can redistribute it and/or |
10 | modify it under the terms of the GNU General Public License as |
11 | published by the Free Software Foundation, either version 3 of |
12 | the License, or (at your option) any later version.</para> |
13 | |
14 | <para>GPXView is distributed in the hope that it will be useful, |
15 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
16 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
17 | GNU General Public License for more details.</para> |
18 | |
19 | <para>You should have received a copy of the GNU General Public |
20 | License along with GPXView. If not, see |
21 | <display_text>http://www.gnu.org/licenses/</display_text>.</para> |
22 | </topic> |
23 | |
24 | <topic> |
25 | <topictitle>Introduction</topictitle> |
26 | <context contextUID="help_gpxview_intro" /> |
27 | |
28 | <para>GPXView is a geocaching application. You can learn more |
29 | about the geocaching activity at web sites like |
30 | www.geocaching.com and www.geocaching.de.</para> |
31 | |
32 | <para>GPXView is a viewer for GPX files generated by the |
33 | geocaching.com. The geocaching.com service is only available |
34 | to paying customers. GPXView is also capable to process the |
35 | LOC files available from geocaching.com as well as various |
36 | other sites for geocaching.</para> |
37 | |
38 | <para>GPXView is by itself a complete geocaching solution |
39 | allowing you to view information about geocaches, to navigate |
40 | to geocaches and even to interface to the popular mapping |
41 | application Maemo Mapper.</para> |
42 | </topic> |
43 | |
44 | <topic> |
45 | <topictitle>Contribute</topictitle> |
46 | <context contextUID="help_gpxview_contribute" /> |
47 | |
48 | <para>You are invited to contribute to GPXView if you like. There |
49 | are several ways you can contribute. You may ... |
50 | |
51 | <list> |
52 | <listitem>... donate money e.g. via paypal to till@harbaum.org |
53 | </listitem> |
54 | <listitem>... test GPX files from sources yet untested |
55 | </listitem> |
56 | <listitem>... contribute code |
57 | </listitem> |
58 | <listitem>... improve this document |
59 | </listitem> |
60 | <listitem>... do whatever you think helps this project |
61 | </listitem> |
62 | </list> |
63 | </para> |
64 | </topic> |
65 | |
66 | <topic> |
67 | <topictitle>Plattforms</topictitle> |
68 | <context contextUID="help_gpxview_plattforms" /> |
69 | |
70 | <para>GPXView was developed for the Hildon/Maemo framework used |
71 | on the Nokia Internet Tablets like the N800 and N810. Since |
72 | the Hildon framework is based upon the GTK framework, a |
73 | popular user interface framework on Linux systems, GPXView |
74 | can -- with minor limitations -- also be used on standard |
75 | Linux desktop PCs. A ready-to-run binary version is currently |
76 | only distributed for the Nokia Internet Tablets.</para> |
77 | </topic> |
78 | |
79 | <topic> |
80 | <topictitle>Import</topictitle> |
81 | <context contextUID="help_gpxview_import" /> |
82 | |
83 | <para>GPXView will start with a nearly blank screen. In order to |
84 | work with GPXView you need to have at least one GPX or LOC |
85 | file installed on your device in any location (e.g. on a |
86 | memory card). Files from the following sources have been |
87 | tested and should work fine with GPXView: |
88 | |
89 | <list> |
90 | <listitem>http://www.geocaching.com</listitem> |
91 | <listitem>http://www.geocaching.com.au</listitem> |
92 | <listitem>http://www.opencaching.de</listitem> |
93 | </list> |
94 | </para> |
95 | |
96 | <para>GPXView supports the following file types: |
97 | <list> |
98 | <listitem><display_text>*.gpx</display_text> containing one |
99 | or more detailed cache descriptions</listitem> |
100 | <listitem><display_text>*.loc</display_text> containing one |
101 | or more simple cache descriptions</listitem> |
102 | <listitem><display_text>*.zip</display_text> containing a |
103 | *.gpx and *-wpts.gpx file</listitem> |
104 | </list> |
105 | </para> |
106 | |
107 | |
108 | <para>GPX files usable with GPXView can also be generated from |
109 | various other file formats using the Geocaching Swiss Army |
110 | Knife (GSAK) on a Windows PC.</para> |
111 | |
112 | <para>Two kinds of import are supported by GPXView: |
113 | <display_text>Import file</display_text> will import a single |
114 | GPX or LOC file into GPXView. This file will get a seperate |
115 | entry in the main screen and can be processed |
116 | independently. This is supposed to be used with typical GPX |
117 | files containing a significant number of cache |
118 | entries. <display_text>Import dir</display_text> will import |
119 | all files from a directory. These files will be trated like a |
120 | single file in GPXView. This is meant to be used with files |
121 | containing typically only one cache entry.</para> |
122 | </topic> |
123 | |
124 | <topic> |
125 | <topictitle>Export</topictitle> |
126 | <context contextUID="help_gpxview_export" /> |
127 | |
128 | <para>GPXView supports the export of cache locations to Maemo |
129 | Mapper. This works very similar to the geopoi tools for |
130 | Maemo. The export function behaves differently depending on |
131 | the main screen state. If the main screen shows the list of |
132 | GPX files, all caches from all GPX files are exported. If the |
133 | function is called while the list of caches (e.g. the contents |
134 | of a GPX file or some search results) is displayed all caches |
135 | in the cache list will be exported. Finally, if the function |
136 | is being called from a single cache details view then only |
137 | this single cache is being exported.</para> |
138 | |
139 | <para>The cache list and expecially the GPX list typically |
140 | contain a significant number of caches. Exporting more than |
141 | about 150 caches is not recommanded since export as well as |
142 | import in Maemo Mapper will be quite slow. Therefore the |
143 | export tool has an option to specify the radius around the |
144 | current position the caches are exported from. Caches in |
145 | greater distance than specified under |
146 | <display_text>radius</display_text> will not be |
147 | exported.</para> |
148 | |
149 | <para>The caches are exported into a separate sqlite database |
150 | (the default name is |
151 | <display_text>/home/ user/ MyDocs/ .documents/ Maps/ gpxview_poi.db |
152 | </display_text>). Maemo Mapper has to be configured to use |
153 | this database instead of its original one. You can set this in |
154 | Maemo Mappers settings in the POI tab.</para> |
155 | |
156 | <heading>Icons</heading> |
157 | |
158 | <para>Maemo Mapper supports the usage of customized icons for |
159 | POIs. GPXView automatically installs matching icons for all |
160 | supported cache types. These icons are also installed as |
161 | separate files at |
162 | <display_text>/home/ user/ MyDocs/ .documents/ Maps/</display_text> |
163 | by default.</para> |
164 | </topic> |
165 | |
166 | <topic> |
167 | <topictitle>Settings</topictitle> |
168 | <context contextUID="help_gpxview_settings" /> |
169 | |
170 | <para>The <display_text>Settings</display_text> dialog can be |
171 | reached via the main menu. It consists of a number of tabs |
172 | organizing the various settings into logical groups:</para> |
173 | |
174 | <para> |
175 | <list> |
176 | <listitem>The <display_text>GPS</display_text> tab contains |
177 | everything related to setup your current position. This can |
178 | either be entered directly or it can be derived from |
179 | GPS. This position will then be used for everything but the |
180 | caches goto view. The cache goto view will always use the |
181 | GPS. This tab allows you to maintain a list of locations |
182 | besides the current GPS position allowing you to quickly |
183 | check whether e.g. there are caches close to your home |
184 | or work location. At least one location (the Home location) |
185 | needs to be in that list. Thus the "Home" location cannot be |
186 | renamed or removed from the list.</listitem> |
187 | |
188 | <listitem>The <display_text>Misc</display_text> tab contains |
189 | miscellaneous global settings. The default display format for |
190 | distances can here be switched between imperial and metric. |
191 | This only affects values output by GPXView. The user may |
192 | always use any format. E.g. a entry box containg something |
193 | like "100 yd" in imperial mode can be manually changed to "10 |
194 | m" without the need to disable imperial mode.</listitem> |
195 | |
196 | <listitem>The <display_text>GPXList</display_text> tab contains |
197 | settings regarding the main screen when displaying the list |
198 | of loaded GPX files. Here you can specify the elements to be |
199 | displayed in that view.</listitem> |
200 | |
201 | <listitem>The <display_text>Cache list</display_text> tab contains |
202 | settings regarding the main screen when displaying a list of |
203 | caches. You can specify the elements to be displayed in that |
204 | view. Also caches marked "found" in the caches notes view may be |
205 | hidden from this list. Furthermore the screen saver can be disabled |
206 | for this view. This makes sense together with the update option |
207 | also in this tab. This allows you to use GPXView to monitor |
208 | surrounding caches while e.g. driving.</listitem> |
209 | |
210 | <listitem>The <display_text>Cache</display_text> tab contains |
211 | settings regarding the main screen when displaying a single |
212 | cache. Both, the compass damping and the screen saver settings |
213 | available here, affect the goto view in the cache detail view. |
214 | The compass damping enables applies some averaging on the GPS |
215 | signal used to determine the compass direction. Increasing |
216 | the damping increases the stability of the compass display, but |
217 | also reduces its sensivity. As a rule of thumb, bad GPS devices |
218 | need much damping, good ones less. The n810 internal GPS is |
219 | not a good one, new external bluetooth GPS devices are better. |
220 | </listitem> |
221 | </list> |
222 | </para> |
223 | |
224 | </topic> |
225 | |
226 | <topic> |
227 | <topictitle>Location Editor</topictitle> |
228 | <context contextUID="help_gpxview_locedit" /> |
229 | |
230 | <para>The location editor allows you to create or modify a |
231 | location. The coordinates will be displayed in red color |
232 | if they aren't considered to be valid coordinates. The two |
233 | buttons with the Maemo Mapper icons link to the Maemo |
234 | Mapper application. The button with the red arrow is only |
235 | enabled if GPXView has received a valid position from |
236 | a running Maemo Mapper. This position can be imported in |
237 | the location editor using that button. The button with the |
238 | green arrow allows to export the current location to |
239 | Maemo Mapper, allowing to make Maemo Mapper to jump its |
240 | view to that position.</para> |
241 | </topic> |
242 | |
243 | <topic> |
244 | <topictitle>Precise Position</topictitle> |
245 | <context contextUID="help_gpxview_precpos" /> |
246 | |
247 | <para>The <display_text>Precise Position</display_text> dialog |
248 | is being useful whenever position information with increased |
249 | precision is being needed. This dialog captures all position |
250 | events from the enabled GPS and displays a position averaged |
251 | over all information received while the dialog is open. This |
252 | is e.g. useful when placing geocaches. The GPS must not be |
253 | moved during this process.</para> |
254 | |
255 | <para>An additional visual representation of the position |
256 | information received from the GPS gives and impression of |
257 | signal stability and signal precision. In that graphic, the |
258 | blue spot marks the averaged position, the red spot the |
259 | position last received and the green crosses all positions |
260 | received so far. This feature is only working once coordinates |
261 | with sufficient variance (diameter > 3 ft) have been |
262 | received. The visualization wouldn't work below that |
263 | threshold.</para> |
264 | </topic> |
265 | |
266 | </folder> |
267 | </ossohelpsource> |