File: control

package info (click to toggle)
viking 1.7-1
  • links: PTS, VCS
  • area: main
  • in suites: buster, sid
  • size: 14,364 kB
  • sloc: ansic: 64,436; sh: 6,939; xml: 4,565; makefile: 781; python: 356; cpp: 246; perl: 213
file content (61 lines) | stat: -rw-r--r-- 2,200 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
Source: viking
Section: utils
Priority: optional
Maintainer: Bernd Zeimetz <bzed@debian.org>
Uploaders: Guilhem Bonnefille <guilhem.bonnefille@gmail.com>
Build-Depends: debhelper (>= 11),
 libcurl4-gnutls-dev,
 libexpat1-dev,
 libgtk2.0-dev,
 libglib2.0-dev (>= 2.12.0),
 libgps-dev (>= 2.90),
 xsltproc,
 docbook-xsl,
 docbook-xml,
 intltool,
 bc,
 gnome-doc-utils (>= 0.3.2),
 libgexiv2-dev,
 libbz2-dev,
 libmagic-dev,
 gnome-common,
 libsqlite3-dev,
 libmapnik-dev [!mips !mips64el !mipsel !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !powerpcspe !sh4 !x32 !alpha],
 libgeoclue-2-dev,
 liboauth-dev,
 nettle-dev
Standards-Version: 3.8.4
Homepage: http://viking.sf.net
Vcs-Git: https://salsa.debian.org/debian/viking.git
Vcs-Browser: https://salsa.debian.org/debian/viking

Package: viking
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, gpsbabel
Suggests: gpsd
Recommends: expect-dev
Description: GPS data editor, analyzer and viewer
 Viking aims to be easy to use, yet powerful in accomplishing a wide
 variety of GPS related tasks. It uses a hierarchical layering system
 to organize GPS data, maps, and other layer types with spatial data,
 such as coordinate lines.
 .
 Some of the things you can use Viking for are:
 .
  * Uploading and downloading waypoints, tracks to/from GPS.
  * Realtime GPS tracking and track recording.
  * Import and export of gpx files.
  * Preparing tracks and waypoints for trips using maps from services
    such as OpenStreetmap and Terraserver. You only need to upload the data
    to your GPS before you leave. The maps together with your tracks
    and waypoints can also be printed and used during the trip.
  * After trips, tracks and waypoints from GPS can be downloaded,
    stored, managed and reused in later trips.
  * Analyzing OHV and hiking trips, understanding where you went and
    how far you were from something.
  * Making waypoints and tracks to follow to easily get someplace
    you've never been before or don't have GPS data for but Terraserver
    maps exist for it.
  * Making maps with coordinate lines.
  * Analyzing speed at different places, adding waypoints where you forgot
    to mark one but did slow down or stop.