robertlipe

Moderator here, taking an interrupting from today's episode of Groundhog Day. Odourless, there's a book for 12 year old GPSes. Got it. Please quit re-posting and then having the mods close the thread when it doesn't go your way. Other posters, please remember that whole "treating other posters with respect" thing. Closing duplicate thread that provides no new info and is generating no constructive conversation - nor is it likely to, based on previous times this was covered.

Moderator Note. This thread, like many lately, has veered wildly off topic and bordering on abusive. Please keep all replies on topic, helpful, and refrain from personal attacks. When you see something naughty or abusive, please report it and let the volunteer moderators handle it. Engaging in one-to-one combat only brings the thread further off topic. Thank you.

[ Moderator note. ] Please keep responses courteous, on topic, and in compliance with the forum guidelines. When you see something naughty, please click 'report' so a volunteer moderator can deal with it - don't quote it as that just gives us more to clean up. Thanx for helping to keep the place family friendly.

Closing a train-wreck of a thread at OP's request. If I'd seen this earlier, I'd have issued reminders about treating other forum members with respect.

See http://forums.Groundspeak.com/GC/index.php?showtopic=323195&st=0&p=5391369entry5391369 for the official word on this.

Please don't bump years-old threads with unrelated content just to stir trouble.

Please don't bump threads from years ago with unrelated content.

Please don't bump years-old posts about unrelated topics to post a new question. This misleads readers into thinking there is an active beta for 610. Please start a new thread (with a good subject) for a new question. Thank you.

Not strange. A physical USB port with a proprietary PITN protocol is different than a "standard USB interface" in all of the electrical, physical, AND protocol senses. USB2 != a specific speed. USB2 includes high speed, full speed, and low speed. I'll just leave "SuperSpeed" and USB3 here on the nightstand. (USB3 similarly doesn't equate to a specific speed; it's a specification, electrical, physical, and protocol, that can include a variety of speeds.) I'm bummed to be that pedantic dude...

If it's db3 it's probably sqlite3. If it's VCF, GPSBabel can read a pocket query and write vcard. Honestly, I haven't heard anyone using vcard in years. http://www.gpsbabel.org/htmldoc-development/fmt_vcard.html It looks like our vcard writer knows about geocaches. gpsbabel -i gpx -f reference/gc/GCGCA8.gpx -o vcard -F - BEGIN:VCARD VERSION:3.0 N:Oozy rat in a sanitary zoo;GCGCA8;;; ADR:N35 55.300 W86 51.700 URL:http://www.geocaching.com/seek/cache_details.aspx?guid=cda94cd6-d657-49bd-8e7e-0031ef1b2613 NOTE:The cache is not at the coordinates above. These coords will get [ ... ] geo-mojo and go find it. \n \n\nHINT:\n END:VCARD

Actually, if we're going to play CPU trivial pursuit (which, as moderator, I should probably discourage) ARM actually roots back to the Acorn from very early 80's. While the later Palm/OS products used ARM (the originals used Dragonball - with roots in 68K systems of similar vintage) such as early OMAP or XScale, they were of the 100-150Mhz variety and quite different than the ARM cores you're find in today's phones, tablets, Chromebooks, DVRs, etc. While STA2065 isn't exactly Exynos ( 6 or S) or Snapdragon 800, the higher level of integration, onboard GPS and focus on things like battery life over, say, an OpenGL GPU capable of driving a super high res screen conspire to probably make it a better choice in a GPS-like substance. ARM-based processors are darned near *everywhere* these days and they span a huge breadth of power (both in wattage and capabilities), die size, cost, and integrated peripherals. In pretty much any place where power consumption (think battery life or cooling) and size and price is key (that $30 Chromecast and $35 Raspberry Pi are both ARM based) you'll find ARM as the dominant technology and it's an astonishingly wide swath of applications. All the processors of any relevance today have roots in the 70's or 80's. Calling an Oregon 600 a Palm Pilot is about as accurate as calling Nexus 5 a hopped up Newton or your i7 a hopped up Tandy 1200. There's a shred of truth to it in that we all build on the works of others, but don't extrapolate too much. In case I need credentials, my day job is producing code that runs on ARM devices; many of which aren't even public yet. [ Edit ] Insig is spot-on.

Use GPSBabel's track splitter. http://www.gpsbabel.org/htmldoc-1.5.0/filter_track.html

GPSBabel knows how to keep names are always unique, and it knows the traits of the device it's talking to, and it knows how to make "better" names than using raw record numbers. "TROLL" > GC1A37 when you're trying to pick it on the screen or remember what you're looking for.

It was a documented outage that took the entire GLONASS fleet out for over ten hours. http://gpstracklog.com/2014/04/fooling-april-1-gnss-fix-issue-returns.html https://support.smartnetna.com/entries/48609248-RESOLVED-GLONASS-Ephemeris-Issue-April-1-2014 http://www.insidegnss.com/node/3979

This conversation could quickly degrade into one of pedantry. Etrex H was a serial model, not a USB one. You could argue that there isn't "one USB cable for ALL Garmins" because not all Garmins are USB-capable. Similarly, there are new/current Garmin products (not particularly well suited for Geocaching...) that don't use USB Micro B at all, such as the Forerunner 620 for the Tactix. Assuming it's not a trick question, the huge majority of Garmins that a normal person would use for geocaching that have a USB cable all use an industry standard USB Micro B connector. There's no magic to them; a commodity $.99 cable will be just fine in them. I have probably a hundred or more of these cables in my life and mix them up with my GPSes - and I have a fleet of Garmins - all the time. (I tend to buy scores of cheap cables and not assume they'll be family heirlooms; if I leave a $1 cable in a hotel room or it breaks, there are four more in my pack...) That said, these devices get plugged and unplugged a lot more than, say, a typical external DVD-Rom and the connectors are both exposed to more dirt and gunk and mechanical forces so they are known to often come loose from the circuit board inside. So cables DO break and sockets DO get finicky, but if you have a cable that looks like it should work, it should work.

GSAK is a nifty program and if you need what it does, it's at the front of the class. If you just want to ship a pocket query to a GPS (because you've done all the appropriate filtering when creating the pocket query) installing VirtualBox and Windows and GSAK and Export macros and so on are overkill. It's kind of baffling that your recipe involves installing compilers, assemblers, and linkers[1]. If you have a old GPS that needs funky files (Explorist x00, instead of x10) or a custom protocol (Garmin 60, 60C, 60CS, anything with a serial port, etc.) use native Linux GPSBabel - even the GUI - and choose GPX as the file input and the appropriate device/format/protocol for output. If your GPS is pretty much anything designed in the the 6-8 years (i.e. it's geocaching aware and supports pocket queries) just copy the GPX file to the device. For this class of devices, you can still use GPSBabel to "fix" names, suppress duplicates, and so on, but it really is optional. You might even find inspiration in http://www.gpsbabel.org/tips/geocaching.html or (the admittedly aging) http://www.gpsbabel.org/tips/browser.html ,though you can adjust that for newer devices. [1] And, yes, I DO know what those are; I was a maintainer of several of packages long ago. There is a directory in G++ testsuite named "robertl" - that's me.)

Closing duplicate post in favor of http://forums.Groundspeak.com/GC/index.php?showtopic=320373 ...and a reminder to everyone about treating fellow posters with courtesy and respect.

[ Moderator note ] I've deleted the link as it's highly unlikely that they're Garmin authorized. If you own Garmin products, you know how grumpy they are about transferring maps between devices. Garmin statement Please refrain from using Groundspeak's resources from promoting distribution of questionable repute. Garmin maps from Garmin dealers (that are much less shady) and many truly open/free options are plentiful.

Agreed. For that city, at this time, Bing "wins" as the images there aren't obliques or even shot with particularly awesome cameras. Looking at the bottom of the page, it looks like it's licensed imagery. All the players (well, at least some of them) are racing to serve up better data all the time. I don't think that there's a strong case that any one company is "winning" everywhere. It's awesome to have competition and choices.

Your question is incoherent, but I think you're looking for "Smart Names" that have been there for 10+ years.. http://www.gpsbabel.org/htmldoc-1.4.4/all_options.html By design, GPSBabel works the same no matter what OS you're one. I used to design OSes...

No apologies needed. The planet is a big place and taking "the best" picture of it all at once and serving it up usefully is really hard. It's a reality that some places will be better than others. I just spot-checked the capital section of Nashville and the Bat Buiding. It looks like Bing provides high contrast for the buildings by destroying the saturation of the ground colors (see how the ground, but not the buildings, looks like it's been run through a sepia filter?) Google Maps overlays road network data, road shields, and POI data. In this shot, Bing does a better job of keeping the buildings perpendicular to the ground. I know why it's this way, but Nashville is the Athens of the South, not the Pisa of the south; our buildings really don't lean like that. :-) So gold star to them for that. I have no axe to grind. Use whatever works best for you in the areas you care about. If you remember The Bad Old Days when your choices were crappy Tiger data or $5,000 monthly ESRI subscriptions with optinally purchased aerial data (none of which was nearly as good as either of those products) you won't miss them and you'll welcome the choices. http://i.imgur.com/CDBH4Iy.jpg http://i.imgur.com/LnOqomn.jpg

This is a landmine of conflated issues. Unrooted Nexus 7 doesn't allow writes to USB mass storage mode. 60CSx doesn't transfer waypoints - read or write - via SD card. 60CSx requires Garmin protocol to transfer waypoints. I know of no Android implementation of Garmin protocol. For Garmin devices that really, really support SD card (not the half-baked implementation that's in 60CSx) writing to SD is the way to go IF you have a tablet with an SD slot; solutions requiring external USB OTG cables are more dicey because of (1). So it worked well in my TF101, but I'd expect an unmodified SL101 to not work.

[ Since I apparently have to say this, this is not a post as a moderator/volunteer of Groundspeak. Your mileage may vary. Some assembly required. yadda yadda. ] Google employee here within Geo. Gitchee-Gumme's answer is the closest so far to "right". The definition of "correct" is fuzzier than you might first think. If you really want to engage in conversations of orthorectification and survey data and such, but be prepared to talk science and reality instead of smack talk. Coordinates are somewhat ambiguous if you associate them with a precision (which few do). Flat pictures of a non flat object (surely we'll agree the planet isn't flat...) are subject to distortion.

Most of the participants here are familiar faces here, so I won't cite chapter and verse. None of you are wildly out of line, but it's worth a reminder to please play nice with each other. Don't be mean. Be professional-ish. yada yada...

The 60c has no mass storage mode. There is nothing to unmount. Its Garmin protocol only.