Some high security routes that must pass through low sec still showing as "safe"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Standard steps to produce trade route

What is the expected output? What do you see instead?
Expected output for "safe" routes do not pass through low security at any
point.  Some routes that begin and end in high security, but must pass
through low security, are still being shown as "safe".

What version of the product are you using? On what operating system?
NavBot J, Win XP most recent SP

Please provide any additional information below.
High sec systems in adjacent Pietanan and Malariya constellations in
Lonetrek region are only accessible via low sec.  Navbot shows all routes
leading to these systems as "safe".

Original issue reported on code.google.com by u-t...@mad.scientist.com on 16 Feb 2010 at 10:31

[GoogleCodeExporter]

Original comment by terry...@gmail.com on 17 Feb 2010 at 11:19

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by terry...@gmail.com on 18 Feb 2010 at 11:32

• Added labels: Priority-Low

[GoogleCodeExporter]

Was this possibly a trade with a lowsec shortcut?  I believe J broke this
notification but should be reported properly now in K.

Original comment by terry...@gmail.com on 20 Feb 2010 at 4:09

[GoogleCodeExporter]

I originally thought it might have been a low sec shortcut, but no.  Manually
plotting the routes revealed that all points of access were through low sec.

Original comment by u-t...@mad.scientist.com on 22 Feb 2010 at 3:04