Navigator
This article explains how the
navigator
on this site works, why you need it when you already have an
AutoPilot and offers examples of its use to illustrate the possibilities.
On this page:
Why the navigator, when there is an autopilot?
The ingame autopilot offers a few options to customize its planning, but is fairly limited beyond them. For one, it always plans a route starting at the system you are currently in. This makes it hard to answer questions like "
How far is it from Jita to Rens?
" when you are somewhere in 0.0.
The autopilot also allows you to avoid low security systems. But what if your
security status doesn't allow travel in systems over 0.8, so you want to get
from Osoggur to Bar in 0.7 and lower
? The autopilot lets you avoid podkill zones, but what if you just want to avoid that gatecamp at Assah? The navigator allows you to
run the same query, avoiding Assah specifically
.
You can combine as many factors as you like. For example, in the above situation, you could
also avoid 0.0 and not travel through Vard
. And because the navigator puts its query in the URL, you can link to specific routes like this article does
1.
What options are there?
Partial names
You can enter full systemnames, but you don't have to. The navigator requires at least three letters from the
start of the systemname. And if you want to use spaces, use an
underscore instead. For example, the result for the
shortest route from Bar to Du Annes
tells you it has selected Bar as the closest match for "Bar" and uses "Du_" to match Du Annes.
Multiple waypoints
Similar to the ingame autopilot, you can plot a route with multiple waypoint. The navigator ignores the order in which you enter system names and always generates a shortest route through all of the systems, starting in one of them and ending in another. For example, "
Jita Rens Osmeden
" yields the same result as "
Jita Osmeden Rens
", both ending in Osmeden.
You can tell the navigator you want a specific system to be the starting system by placing a question mark (?) in front of it. Similarly, put an exclamation mark (!) in front of a system you want to be the endpoint of the route. For example, "
!Jita Osmeden Rens
" and "
http://eve.grismar.net/navigator/index.php?query=%21Jita+%3FOsmeden+Rens&form_id=nav_form
!Jita ?Osmeden Rens]]"
Limit by security status
You can tell the navigator to stay above or below a specific system security level. You can combine limits to further narrow it down. Note that providing a security level with a single decimal indicates ingame security levels and providing more decimals implies
TrueSecurity. For example, compare "
Alsottobier Jolia <0.6
" and "
Alsottobier Jolia <0.60
". Fluekele has an ingame security of 0.6, so it does not satisfy the "<0.6" part. But that 0.6 is rounded; its true security is 0.5617, which does satisfy the "<0.60" part.
Avoid systems
You can avoid a specific system by putting it in your query with a minus (-) in front of it. Compare "
Dital Assah -G-5
" and "
Dital Assah
".
1 Note: the route will generally be the same every time you run the same query; but if the database gets updated or rebuilt, the actual resulting route may slightly vary. It will still satisfy all the conditions and give you one of the fastest alternatives, but sometimes two alternatives have the same number of jumps.
Current EVE version: 5.10.58188 (Empyrean Age 1.0.1)
There are no comments on this page. [Add comment]