nedflanders
Registered user
Got the Quest with European City Select V6 installed, now whats the difference between City select and Navigator? as V8 of navigator is out will this go onto the quest, just a little confused now 
software update?
- Thread starter nedflanders
- Start date
All is revealed at http://www.pocketgpsworld.com/modules.php?name=Forums&file=viewforum&f=99 or traipse through the GPS section on this forum
nedflanders
Registered user
cheers for the reply, alot of info about the quest on that site, although still not sure if Navigator will cause problems on the quest 1 as it seems to have slowed the quest 2 down from what I can gather and if it's a case of making do with select v7 or crap redraw rates I'll be sticking with v7.
Deleted account W
Guest
Found this:
There are essentially three Garmin products that use the same visible map detail:
Metroguide
City Select
City Navigator
When you ask Garmin Europe about the diffrences, this is the answer you get:
The differences between City Navigator Europe (CNE) and City Select Europe
(CSE) are fairly technical. It all comes down to the number of database
attributes that we are allowed to use in CSE compared to all of the ones
used in CNE.
While in CNE we use all of the possible delivered attributes for all of the
roads, in CSE, per agreement with NAVTEQ, we can only use a limited number
of attributes. The lower number of attributes correspond to lower royalties
to the data vendor for the CSE, however it will also correspond to a change
in the route calculation or address search. The calculated route by CSE
might be the same than CNE in most instances, but in some cases, the CNE
route will be more effective than the CSE.
Example 1: CSE does not include time limitation (closed to traffic
within some hours of the day) for the road links and will consider CLOSED to
traffic any link with a time limitation attached to it. As a consequence
the route calculated using CSE will avoid such roads. The route calculated
with CNE will not avoid such road in the hours when the road is open.
Example 2: CSE does not include mid-road barriers awareness. In these
terms, if the user starts his route from the "wrong" side of the road, the
route calculation will tell him to turn left (or right - if in the UK), even
though it will be impossible for the customer because there is indeed a
barrier in the middle of the road which will not allow the user to go across
the road.
Example 3: CNE address search works on 3 different administration
levels at the same time, CSE address search only works on 2 different
administration levels.
Again the differences will not be extremely evident, but if you notice
discrepancies in route calculation, the above examples should be the key
causing factors.
Similar situation you will find when you compare the MetroGuide Europe (MGE)
route calculation to CNE.
Furthermore, while CNE will continue on evolving in functionality for the
higher end units, CSE has pretty much reached the top of the functionality
at the current stage and no major improvements should become available.
There are essentially three Garmin products that use the same visible map detail:
Metroguide
City Select
City Navigator
When you ask Garmin Europe about the diffrences, this is the answer you get:
The differences between City Navigator Europe (CNE) and City Select Europe
(CSE) are fairly technical. It all comes down to the number of database
attributes that we are allowed to use in CSE compared to all of the ones
used in CNE.
While in CNE we use all of the possible delivered attributes for all of the
roads, in CSE, per agreement with NAVTEQ, we can only use a limited number
of attributes. The lower number of attributes correspond to lower royalties
to the data vendor for the CSE, however it will also correspond to a change
in the route calculation or address search. The calculated route by CSE
might be the same than CNE in most instances, but in some cases, the CNE
route will be more effective than the CSE.
Example 1: CSE does not include time limitation (closed to traffic
within some hours of the day) for the road links and will consider CLOSED to
traffic any link with a time limitation attached to it. As a consequence
the route calculated using CSE will avoid such roads. The route calculated
with CNE will not avoid such road in the hours when the road is open.
Example 2: CSE does not include mid-road barriers awareness. In these
terms, if the user starts his route from the "wrong" side of the road, the
route calculation will tell him to turn left (or right - if in the UK), even
though it will be impossible for the customer because there is indeed a
barrier in the middle of the road which will not allow the user to go across
the road.
Example 3: CNE address search works on 3 different administration
levels at the same time, CSE address search only works on 2 different
administration levels.
Again the differences will not be extremely evident, but if you notice
discrepancies in route calculation, the above examples should be the key
causing factors.
Similar situation you will find when you compare the MetroGuide Europe (MGE)
route calculation to CNE.
Furthermore, while CNE will continue on evolving in functionality for the
higher end units, CSE has pretty much reached the top of the functionality
at the current stage and no major improvements should become available.
Quest 2 uses CNv8NT which, as Pan European reminded us, is esentially the addition of Traffic Messaging (TMC) but using some compression. The Quest uses plain CN so does not have to decompress the files on the fly - which is what is causing problems for the Q2 processor, along with POI handling
nedflanders
Registered user
So Navigator V8 should be ok on the Quest 1 then by the sounds of it, anyone using V7 navigator notice any perforamnce differences?
Similar threads
