strumble
-
Posts
479 -
Joined
-
Last visited
Posts posted by strumble
-
-
Discoverer overwrites the CityNavigator Maps on the units.
Whether you have both enabled you will see only the Discoverer!
To see CityNavigator you have to disable Discoverer.
Discoverer is routable.
Discoverer is unable to see all one-way streets and pedestrian areas, especially as the detail could be years out of date.
-
I found the same as you! The text can be bigger but the icon cannot.
But
You can increase the size of a POI to 24 x 24.
So for some important waypoints I created a POI at the location [POI name and text is not shown] to get a larger personal icon with the waypoint text and icon ontop.
In the UK there are 10,000 speed cameras POIs so the 24 x 24 icons are easier to see!
It is not perfect but it helps me.
-
Do you have CityNavigator active as well as Discoverer.
If you have - turn off one or the other, as both contain CityNavigator.
I had this problem on my Oregon 300 but it corrected with the duplicate maps disabled.
Which Discoverer map are you using and what zoom level are the problems happening at?
I had a National park at 1:25 and the South of England and Wales 1:50 operating at the same time and the unit did not like that! I had turn one off to get the best results.
The duplication of CityNavigator within different mapsets was a problem especially as they were different updates.
Now I have no problems with [provided I disable duplicates] :-
MetroGuide NA
CityNavigator Europe
Discoverer 1:25 Coast Path
Discoverer 1:50 South of England and Wales
-
-
-
In the UK we get:-
-
You get some help here:-
http://forums.Groundspeak.com/GC/index.php...p;hl=discoverer
-
Are your Discoverer maps on both Internal and SD cards?
Are they downloaded or bought on SD cards?
I had problems when the Discoverer maps were listed as #1 as you could not disable individual maps!
.
.
..
However, by putting one Discoverer map on internal and the other on the SD I eliminated the problems as I could disable one Discoverer and use the other!!!!!!
.
.
..
-
I too am reverting to 3.2 - too many hangs, reboots, discoverer maps not showing. Hmmm....
So far there are no problems created with this software for my Discoverer maps, in fact they seem clearer.
However, I only have one Discoverer map active at any one time.
This is because each Discoverer has five different maps within it so to have more Discoverer maps active you are multiplying the active maps by five and then I get problems! In each Discoverer map you are duplicating/triplicating the CityNavigator, 1:25000, 1:2500 and in some cases the 1:50.
If you have identical maps on the internal and SD cards it usually gives problems[ie Discoverer on SD and Internal]!
I THINK.
-
. I have a couple of these maps loaded on an SD card so wonder if it is an issue with multiple maps?
The 3.2 works fine.
Have you all of them activated at the same time?
-
Questions for discoverer users if I may:-
I have the National Parks (but don't live in an area covered by them). Browsing a track on the oregon 300 which is covered by the maps, I find the zoom and pan speed very poor - anything between 3 and 10 seconds.
Is this normal ? Is it worse with bigger maps eg Northern England ? Are there any tricks in minimising the delay ?
I've seen it suggested that when zoomed in on a discoverer map and using it on a bike, it causes the unit to crash because it cannot keep up with the re-draw - is this a common experience ?
Cheers.
In the options remove all other maps especially CityNavigator as it is built into Discoverer!
Zooming out takes longer than zooming in.
I have the south of England and Wales which is bigger than the National Parks, it is slower than CityNavigator to 'pan' but look at the amount of detail included!
Discoverer works well at 70mph in a car with all the UK speed cameras included, so the problem on the bike is not normal!
Beta software 3.01 works well for me whereas the more recent versions caused me problems.
-
Post this type of topic on the Discoverer thread?
http://forums.Groundspeak.com/GC/index.php...p;hl=discoverer
After all Discoverer maps are unique to the UK so with 170 replies and 17,000 views you may jog someone there!
-
Too often we get requests for help from fellow members and after spending considerable amounts of our time we get no thanks or FEEDBACK!
I draw a line under my involvement on this website and will watch without posting.
g-o-cashers thank you for all your postings and help.
.
.
.
-
On the units that have the firmware to support it you can name:-
gmapsupp0
gmapsupp1
gmapsupp2
gmapsupp3
I have loaded and operate:-
MetroGuide NA,
Topo GB,
CityNavigator
Discoverer
as seperate image files - there is no need to combine them with the Oregon.
-
TOPO GB v2
752 maptiles
1664MB with autorouting details.
-
If you make a track with your gps in one hand and the gps is between a highrise/mountain/canyon and your body, then you take the gps in the other hand, where the gps has a better reception because it has a better view to the sat's, you can see a difference.
This is not new, has nothing to do with new beta's or waas.
The 'smooth' track is just software averaged and actually I think it's wrong.
We seemed to have discussed the issue of changing hands at Dec 2008/Feb 2009.
I tried the test in the early part of the year -walked the same route every day for exercise with Oregon in my right hand in both directions.
Result the accuracy of the 2mile route varied depending on whether walking South/West or North/East.
I tried another test on a 'board walk' 3 feet wide on a Nature reserve in both direstions.[with Oregon in my right hand in both directions] Result the accuracy varied depending on whether walking South/West or North/East.
I tried another test along a 4"[inch] wide kerb along my street. [with Oregon in my right hand in both directions] Result the accuracy varied depending on whether walking South/West or North/East.
The best way to test the accuracy was the board walk with a bog on both sides because it had precise boundaries and restricted you to a track 3 feet wide.
So the principle of changing hands and getting different readings was understandable as the view of the satellites change
So if you are walking along a cliff edge in Wales [in fog or darkness] make sure the unit has a clear view of the satellites in the south and west!!
-
Beta Software: Oregon 400t, Ver. 3.15, Beta as of Aug 18, 2009,
http://www8.garmin.com/support/download_details.jsp?id=4573
Oregon 300
-
I'm seriously tempted by an oregon 300 but don't want to potentially carry around half a dozen memory cards with discoverer maps on. Questions:-
- I understand discoverer maps are locked to the card they are bought on ?---Yes
- can this lock be undone ? (if so, how ?)--- Illegally
- I understand it's also possible to download the discoverer maps rather than buy them on a card ?----- Many people have not been successful
- at the point of downloading, the maps cannot be locked to a particular card and presumably bind themselves to the first card they're put on ? --No the are unlocked to the unit. replace your unit and you loose the maps.
- would it be possible to use mapupload to merge discoverer maps into a single image file (before they were transferred to a card), therefore getting around the need to have several memory cards ? --- Not needed you can use the the Oregon and put as many different maps on the Unit and card since the recent firmware.
- does anyone know if 1:25k regions will be released in time ?--How big would the file be for a 1:25 region?????????? 1:25 only work at 500feet and 300feet and below that they blur. 1:50 for the region is 2GB approx.
Cheers.
Post this type of topic on the Discoverer thread? The answers are next to your question.
-
My new Discoverer card arrived.
Southern England and Wales 1:50 is great with v3.01!!!
Note:-
The symbol is a lighthouse not a sexual symbol.
Some of the website members enter UK over this lighthouse - the pilots sometimes call it St. Rumble!!
-
Sorry Splashy I did not know you were HERE!!
At least the original poster and I have experienced the same problem but it was not important to me.
-
I can calulate a 1500 mile route without problems, but all my Map data is on the SD.
Perhaps it has to do with the European Mapping where we have so many roundabouts, tunnels and minor roads?
-
Within Discoverer, CityNavigator, and TOPO are the same maps but up until recently they have worked without crashes.
In emails to Garmin they are interested in the POIs within my unit so I tried OPTION changes and improved 'panning' with Oregon v3.13, so there is problem with POIs and their Zoom level within Discoverer.
However, the 'shutoffs' were happening whatever the mapping software was active.
Last night I re-installed Oregon v3.01 and now the Discoverer and Unit are working again without 'shutoff' or 'crashes'!!!
The problem of the screen/maps 'hanging' or partly loading when zooming in or out [on Discoverer] has been improved and is now acceptable.
-
I'm not an expert but I think:- it has nothing to do with the size of the maps and where they are - it is the ability to calculate one route of 1000 miles with all the automatic via points, changes to roads that gives the message about memory.
-
Purely curious. How does it it deal with ferries / chunnel? What did it decide?
Is that question for me?
If it is - by default it uses the chunnel and adds 50 minutes to the route.
The route to Ireland through Fishguard adds 3:15 time to the route-Correct for Ferry but the CAT does it in 90minutes.
I never use that method I always plan a route to the Ferry or Chunnel and then from the other side.
It will do Rosslare through Fishguard over to Calais but I prefer the split routing.
Oregon 300 in car
in GPS technology and devices
Posted
For serious autorouting in the UK, the CityNavigator is clearer and updates seem to be available far more often.
However, the cost of the updated maps is hard to justify as so little changes over a two year period in the UK but I found when towing in Europe the updated maps are justified as last time I went abroad juctions had been re-numbered.
Discoverer does contain the older versions of CityNavigator as the autorouting operates on those maps not on the OS maps. When Discoverer was launched we had terrible trouble with CityNavigator maps appearing ontop of Discoverer! Firmware releases corrected the problem and now CityNavigator is hidden under the OS maps.
http://forums.Groundspeak.com/GC/index.php...p;hl=discoverer