Bug#819486: routino: At parks routino often can not find the route.

2016-03-30 Thread Andrew M. Bishop
>> Package: routino
>> Version: 3.1.1-2
>> Severity: normal
>>
>> Reproduce:
>> 
>> 1. Open http://www.routino.org/uk-leaflet/router.html
>> 2. Set point "1": -0.73458 E / 51.37529 N
>> 3. Set point "2": any. For example: -0.06579 E / 51.47898 N
>> 4. Click "Shortest Route"
>> 5. Get:

>> Loaded Files: nodes, segments, ways & relations
>> Found Closest Point: Waypoint 1
>> Error: Cannot find node close to specified point 1.

This is not a bug in Routino.

The route that has been asked for starts in the middle of an area with
no roads and asks for transport by motorcar.  The nearest road is
more than 1 km from the first waypoint and Routino has a limit of 1 km
when searching for the nearest highway.  To find a route a starting
point closer to the nearest accessible highway should be selected.

It could be argued that Routino should search further but in most
cases it does not make sense to choose a starting point that is so far
from the given waypoint.

-- 
Andrew.
--
Andrew M. Bishop   http://www.routino.org/



Bug#819486: routino: At parks routino often can not find the route.

2016-03-30 Thread Roman V. Nikolaev
Bugreport #819486 I also wrote.
I work with routino a very long time. And how I can tell, these are two
different bugs.

29.03.2016 23:29, Sebastiaan Couwenberg пишет:
> Control: tags -1 upstream
> Control: forwarded -1 a...@gedanken.org.uk
> 
> Hi Andrew,
> 
> Roman reported an issue in the Debian Bug Tracking System for Routino
> 3.1.1 that it often cannot find routes when one of the locations is in a
> park.
> 
> The report is included below and available online:
> https://bugs.debian.org/819486
> 
> Can you confirm this issue, and possibly suggest a fix?
> 
> On 03/29/2016 02:32 PM, Roman V. Nikolaev wrote:
>> Package: routino
>> Version: 3.1.1-2
>> Severity: normal
>>
>> Reproduce:
>>
>> 1. Open http://www.routino.org/uk-leaflet/router.html
>> 2. Set point "1": -0.73458 E / 51.37529 N
>> 3. Set point "2": any. For example: -0.06579 E / 51.47898 N
>> 4. Click "Shortest Route"
>> 5. Get:
>>
>> router --shortest --lon2=-0.06579 --speed-steps=0 --highway-ferry=20 
>> --highway-primary=90 --highway-service=40 --speed-residential=48 
>> --transport=motorcar --property-multilane=60 --speed-secondary=88 
>> --speed-service=32 --highway-unclassified=60 --speed-motorway=112 --height=0 
>> --highway-steps=0 --property-footroute=45 --speed-ferry=10 
>> --highway-cycleway=0 --highway-residential=50 --highway-motorway=100 
>> --highway-secondary=80 --speed-path=0 --width=0 --speed-primary=96 
>> --lat1=51.37529 --oneway=1 --speed-cycleway=0 --length=0 --turns=1 
>> --weight=0 --speed-unclassified=64 --lon1=-0.73458 --property-paved=100 
>> --speed-track=16 --lat2=51.47898 --highway-track=0 --property-bridge=50 
>> --property-bicycleroute=45 --highway-tertiary=70 --property-tunnel=50 
>> --speed-trunk=96 --highway-trunk=100 --speed-tertiary=80 --highway-path=0 
>> --reverse= --loop= --dir=routino-data
>>
>> Loaded Files: nodes, segments, ways & relations
>> Found Closest Point: Waypoint 1
>> Error: Cannot find node close to specified point 1.
>>
>> Time: 0.000 CPU / 0.011 elapsed
>>
>> I see this bug in many parks. I think this may be due to many footways 
>> around.
>>
>> -- System Information:
>> Debian Release: 8.3
>>   APT prefers stable
>>   APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 
>> 'testing-proposed-updates'), (500, 'stable-updates'), (500, 
>> 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 
>> 'oldstable'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
>> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages routino depends on:
>> ii  libbz2-1.01.0.6-7+b3
>> ii  libc6 2.19-18+deb8u3
>> ii  libroutino-slim0  3.1.1-2
>> ii  libroutino0   3.1.1-2
>> ii  routino-common3.1.1-2
>> ii  zlib1g1:1.2.8.dfsg-2+b1
> 
> Kind Regards,
> 
> Bas
> 


-- 
Roman V. Nikolaev



Bug#819486: routino: At parks routino often can not find the route.

2016-03-29 Thread Sebastiaan Couwenberg
Control: tags -1 upstream
Control: forwarded -1 a...@gedanken.org.uk

Hi Andrew,

Roman reported an issue in the Debian Bug Tracking System for Routino
3.1.1 that it often cannot find routes when one of the locations is in a
park.

The report is included below and available online:
https://bugs.debian.org/819486

Can you confirm this issue, and possibly suggest a fix?

On 03/29/2016 02:32 PM, Roman V. Nikolaev wrote:
> Package: routino
> Version: 3.1.1-2
> Severity: normal
>
> Reproduce:
> 
> 1. Open http://www.routino.org/uk-leaflet/router.html
> 2. Set point "1": -0.73458 E / 51.37529 N
> 3. Set point "2": any. For example: -0.06579 E / 51.47898 N
> 4. Click "Shortest Route"
> 5. Get:
> 
> router --shortest --lon2=-0.06579 --speed-steps=0 --highway-ferry=20 
> --highway-primary=90 --highway-service=40 --speed-residential=48 
> --transport=motorcar --property-multilane=60 --speed-secondary=88 
> --speed-service=32 --highway-unclassified=60 --speed-motorway=112 --height=0 
> --highway-steps=0 --property-footroute=45 --speed-ferry=10 
> --highway-cycleway=0 --highway-residential=50 --highway-motorway=100 
> --highway-secondary=80 --speed-path=0 --width=0 --speed-primary=96 
> --lat1=51.37529 --oneway=1 --speed-cycleway=0 --length=0 --turns=1 --weight=0 
> --speed-unclassified=64 --lon1=-0.73458 --property-paved=100 --speed-track=16 
> --lat2=51.47898 --highway-track=0 --property-bridge=50 
> --property-bicycleroute=45 --highway-tertiary=70 --property-tunnel=50 
> --speed-trunk=96 --highway-trunk=100 --speed-tertiary=80 --highway-path=0 
> --reverse= --loop= --dir=routino-data
> 
> Loaded Files: nodes, segments, ways & relations
> Found Closest Point: Waypoint 1
> Error: Cannot find node close to specified point 1.
> 
> Time: 0.000 CPU / 0.011 elapsed
> 
> I see this bug in many parks. I think this may be due to many footways around.
> 
> -- System Information:
> Debian Release: 8.3
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 
> 'testing-proposed-updates'), (500, 'stable-updates'), (500, 
> 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages routino depends on:
> ii  libbz2-1.01.0.6-7+b3
> ii  libc6 2.19-18+deb8u3
> ii  libroutino-slim0  3.1.1-2
> ii  libroutino0   3.1.1-2
> ii  routino-common3.1.1-2
> ii  zlib1g1:1.2.8.dfsg-2+b1

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#819486: routino: At parks routino often can not find the route.

2016-03-29 Thread Roman V. Nikolaev
Package: routino
Version: 3.1.1-2
Severity: normal

Reproduce:

1. Open http://www.routino.org/uk-leaflet/router.html
2. Set point "1": -0.73458 E / 51.37529 N
3. Set point "2": any. For example: -0.06579 E / 51.47898 N
4. Click "Shortest Route"
5. Get:

router --shortest --lon2=-0.06579 --speed-steps=0 --highway-ferry=20 
--highway-primary=90 --highway-service=40 --speed-residential=48 
--transport=motorcar --property-multilane=60 --speed-secondary=88 
--speed-service=32 --highway-unclassified=60 --speed-motorway=112 --height=0 
--highway-steps=0 --property-footroute=45 --speed-ferry=10 --highway-cycleway=0 
--highway-residential=50 --highway-motorway=100 --highway-secondary=80 
--speed-path=0 --width=0 --speed-primary=96 --lat1=51.37529 --oneway=1 
--speed-cycleway=0 --length=0 --turns=1 --weight=0 --speed-unclassified=64 
--lon1=-0.73458 --property-paved=100 --speed-track=16 --lat2=51.47898 
--highway-track=0 --property-bridge=50 --property-bicycleroute=45 
--highway-tertiary=70 --property-tunnel=50 --speed-trunk=96 --highway-trunk=100 
--speed-tertiary=80 --highway-path=0 --reverse= --loop= --dir=routino-data

Loaded Files: nodes, segments, ways & relations
Found Closest Point: Waypoint 1
Error: Cannot find node close to specified point 1.

Time: 0.000 CPU / 0.011 elapsed

I see this bug in many parks. I think this may be due to many footways around.

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 
'testing-proposed-updates'), (500, 'stable-updates'), (500, 
'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages routino depends on:
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18+deb8u3
ii  libroutino-slim0  3.1.1-2
ii  libroutino0   3.1.1-2
ii  routino-common3.1.1-2
ii  zlib1g1:1.2.8.dfsg-2+b1

routino recommends no packages.

routino suggests no packages.

-- debconf-show failed