Routino is an application for finding a route between two points using the
dataset of topographical information collected by OpenStreetMap.
This router uses a routing algorithm that takes OSM format data as its input and
calculates either the shortest or quickest route between two points. To optimise
the routing a custom database format is used. This allows the routing to be
performed quickly after a modest one-off pre-processing stage.
A selection is possible for any of the major OSM transport types and for each of
the main OSM highway types a preference can be provided and a speed limit.
Restrictions on one-way streets, weight, height, width and length are also
options. Further preferences about road properties (e.g. paved or not) can also
be selected.
The processing of the input XML file is based on rules in a configuration file
that transform the highway tags into tags that are understood by Routino. The
generation of the output files (HTML and GPX) uses language fragments selected
from another configuration file which allows multi-lingual output from the same
database.
The router takes into account private/public/permissive restrictions on highways
as well as tagged speed limits and barriers (gates, bollards). The simplest and
most common turn restriction relations (those composed of a way, node and way)
are also supported.
===> The following configuration options are available for routino-3.4.4:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
astro: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* ABURAYER Rewsirow <rewsirow@ff.iij4u.or.jp>
* Alexander Leidinger
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Andrew Pantyukhin <infofarmer@FreeBSD.org>
* Andrey Zakhvatov
* Anton Berezin <tobez@FreeBSD.org>
* Anton Berezin <tobez@tobez.org>
* Anton Karpov <toxa@toxahost.ru>
* Brion Moss <brion@queeg.com>
* Bruce M Simpson <bms@FreeBSD.org>
* Chris Piazza <cpiazza@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Fix CONFLICTS entries in archivers, astro, audio
Fix conflicts entries based on a script that searches for duplicate
files installed by several ports.
Some patters seem to make ports conflict with themselves, but this is
actually not the case due to the check-*-conflicts logic implemented
in bsd.port.mk, which excludes self-conflicts.
PHP based ports have been ignored in this commit as requested by the
committers currently working on the php-8.1 import.
Approved by: portmgr (implicit)
astro/routino: revbump to fix astro/qmapshack
The previous commit added two libraries to the package, but failed to
bump the port. The immediate fallout is astro/qmapshack fails at
run-depends stage on incremental bulk builds.
PR: 210062
[NEW] astro/routino: Router for OpenStreetMap Data
Routino is an application for finding a route between two points using the
dataset of topographical information collected by http://www.OpenStreetMap.org.
This router uses a routing algorithm that takes OSM format data as its input and
calculates either the shortest or quickest route between two points. To optimise
the routing a custom database format is used. This allows the routing to be
performed quickly after a modest one-off pre-processing stage.
A selection is possible for any of the major OSM transport types and for each of
the main OSM highway types a preference can be provided and a speed limit.
Restrictions on one-way streets, weight, height, width and length are also
options. Further preferences about road properties (e.g. paved or not) can also
be selected.
(Only the first 15 lines of the commit message are shown above )
