Jump to content

BMW JEDI

Banned
  • Posts

    165
  • Joined

  • Last visited

Everything posted by BMW JEDI

  1. I have nearly 50k geocaches loaded on an Oregon 650. Nearly 22k geocaches surrounding Seattle, WA: And another 24k + geocaches loaded covering a large portion of the state of Arizona: Hope this helped answer your questions
  2. I suspect you will be pleasantly surprised. IMHO, the current firmware is already more polished than most of my other Garmin GPSr units at launch. And they are still polishing daily
  3. I provided the requested link. And I pointed out another link error on the same page. The FAQ is full of wiki links, so I am very confused by your 'fishing' statement.
  4. Going to need more information.. What version Communicator? What OS? How as it connected, was the eTrex 20 in Mass Storage Mode? What steps have you taken, what results do you have?
  5. Also, in the FAQ page, the Montana Wiki link is improperly linked to the Colorado wiki. A new Oregon wiki is under construction for the soon to be released Oregon 6x0 series, may want to add that.
  6. HaHaHa!!!! See what you did there? Funny!!!
  7. Interesting.... I did not see any drops or erratic tracking.... Didn't see you stop at many intersections either....
  8. Look here for some general guidance.
  9. Sounds like you are looking at the Geocaching Dashboard, which ALWAYS points to the nearest geocache. Try using the Compass, or change the dashboard to something else, like the standard Compass dashboard, for example. No idea without seeing your GPX files. How 'wrong' are they?
  10. Thank you Red90 for your patience while I learned what I didn't know and un-learned what I did know
  11. It is quite clear they are going to replace the ENTIRE UNIT for $149. Not a bad deal after 5 years of use Edit: Adding, they are making spare parts and repairs reasonably available. You are getting a completely new unit for a fraction of the original cost.
  12. How do I find the "good deals"? This is a good deal. This is a Great Deal!
  13. Exactly, Gallet was only whining about reasonable and normal wear for a device of this kind and age. Now, speaking poorly of socialism apparently will get Groundspeak moderator attention, as we all know where Groundspeak is based, in the land of never ending rainbows and magic unicorns.... and 'Puff the Magic Dragon..." They like to call it 'Freemont'.
  14. It seemed to import all my find via API (took nearly an hour), but I cant for the life of me figure out how to make them show up in any database. When you import data in GSAK, it is put in the open Database. Apparently, Geoget hides this data somewhere I cant see... so I have no idea how to move it to a database... What am I missing?
  15. Huh? If something wears out after 5 years, well past the warranty period, on a device that has not been made for years, you want the government to fix it for you? Very sad. Exactly. Socialism is a disease. Get help man!
  16. I just created and saved a 'Test' waypoint on my Garmin GPSr. Opened the GPX file with a text editor and this is what I see: <?xml version="1.0" encoding="UTF-8" standalone="no" ?><gpx xmlns="http://www.topografix.com/GPX/1/1"'>http://www.topografix.com/GPX/1/1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3"'>http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:wptx1="http://www.garmin.com/xmlschemas/WaypointExtension/v1"'>http://www.garmin.com/xmlschemas/WaypointExtension/v1" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1"'>http://www.garmin.com/xmlschemas/TrackPointExtension/v1" creator="Oregon 650" version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www8.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/TrackStatsExtension/v1 http://www8.garmin.com/xmlschemas/TrackStatsExtension.xsd http://www.garmin.com/xmlschemas/WaypointExtension/v1 http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd"><metadata><link href="http://www.garmin.com"><text>Garmin International</text></link><time>2013-03-26T17:22:56Z</time></metadata><wpt lat="34.862194" lon="-111.761384"><time>2013-03-26T18:52:24Z</time><name>Test</name><sym>Final Location</sym></wpt></gpx> What part of that file tells the GPSr what Map Datum to use? If the information is present, and GPS devices can read it and adjust properly on the fly, why do we need the option to change Map Datum in the GPS settings? Thank you for your help!
  17. Thank You for the clarification. That information will be helpful.
  18. That's an interesting comment. Why do you make that assertion? Based on my personal experience with an Oregon 650, and the experiences of others I have read about online. The screen appears to be very robust. Can I assume that the Oregon 600 series screen is made from a different material than previous Garmin screens? If so, other than being scratch resistant, are there any additional user benefits to be derived from the new type of screen? Thanks for all of your interesting and valuable insight. I have one to test, but I have yet to get any specific information from Garmin regarding the screen material. From all the Garmin GPSr I have handled, this screen certainly appears to be the most durable to date. Of course, more time and experience will tell us more, but I have no intention of putting a screen protector on my Oregon 6xx.
  19. That's an interesting comment. Why do you make that assertion? Based on my personal experience with an Oregon 650, and the experiences of others I have read about online. The screen appears to be very robust.
  20. Did the old etrex Vista's work that way? I didn't think they had a mass storage mode.
  21. Then you were had. Not had. I didn't buy it. My memory isn't what I thought it was. I thought it was more expensive. SO much for using facts...
  22. Got that backwards. The GPSr datum must match the datum the coordinates were created with. I don't think so. When you transfer coordinates (i.e. waypoints) to your GPS, manually or 'electronically', the GPSr has no idea what map datum was in use when the coordinates were created, and certainly has no ability to magically convert them to whatever map datum you have your GPSr set to. If this were the case, you would not need an option to change the map datum on your GPSr. As stated, The GPSr datum must match the datum the coordinates were created with.
×
×
  • Create New...