Jump to content

perfunctory butcher's

+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by perfunctory butcher's

  1. So far I am opening the saved kml in Google Earth and the saving as kml again. It's working so far but I have 33 routes on a future road trip to convert to PQ so it'a a bit of a faff. This is interesting : https://sites.google.com/site/gmapstips/export-my-map-as-kml
  2. So this BOM is a non ascii character that dosen't show up in Notepad? In that case, if I open the gpx file in Notepad and then save again, will Notepad effectively strip out the naughty BOM for me?
  3. That does not remove the Unicode BOM that Garmin software adds to the start of their files. Your best bet is to open the file in other software, such as Google Earth or EasyGPS, and save anew version from there.
  4. I can't find the export to kml option on Google maps anymore, have they removed it and if so, is there another way to get a kml route from Google Maps in a format that can be uploaded to Groundspeak so as to create a route for a pocket query along a route?
  5. I can't find the export to kml option on Google maps anymore, have they removed it and if so, is there another way to get a kml route from Google Maps in a format that can be uploaded to Groundspeak so as to create a route for a pocket query along a route?
  6. I want to upload a route from either a kml or gpx (to do a PQ along a route) but the function always returns a server 500 failure. I have generated these files from numerous sources, Google Maps, Basecamp, Tyre etc but they all seem to fail. Contacted GS whose reply was as follows: If you receive a 500 error when trying to upload a route, please consider the following: For KML and KMZ: Your file can ONLY have one path in the file and the file cannot contain polygons or placemarks. For GPX files: GPX files created with Garmin applications (MapSource or BaseCamp) add a byte order mark to the start of the file that causes the uploader to stop working. You will need to manually remove that BOM from the file or resave the GPX in another application that doesn't add that BOM (such as EasyGPS). I hope this helps. If you have further questions, please direct them to the Geocaching Forums. Well I then created a simple route, just two waypoints on a straight road, but same results. I don't know what they mean by only one path, I believe I have only one path since it's a short bit of road with no junctions. I have opened the gpx file in Notepad but there is no sign of a BOF tag so I can't remove that either! It's getting so frustrating now, is anyone on here using the excellent Tyre program, that's my ultimate aim, but although it generates kml or gpx files, GS can't seem to work with them :-(
  7. I've just installed a:drake and it's looking very promising but the only problem so far is finding help in English. Has anyone come across any active forums that I might find useful? I like that it uses Sqllite databases for it's offline storage so should be easy to play with the data.
  8. The reason I have been a fan of Memory-Map for a number of years is its ability to effortlessly 'connect to PDA' and 'connect to GPS' to transfer data. In this way I have been using a Garmin GPS and an iPaq PDA with Bluetooth GPS for my geocaching - the Garmin for its long battery life and rugged construction, the PDA with Memory-Map for its mapping and 3rd party geocaching support apps. They both connected to Memory-Map on the PC via USB and everything was perfect apart from lugging two devices around with me. The new Memory-Map Adventurer 3500 seemed at last to replace both these items. So, after a month, what do I think? I think it's going to be a massive step backward. First, the hardware: First impressions are a well made rugged unit, but looks deceive. The screen is so soft that even the supplied stylus will scratch it, I had my first scratch withing the hour whilst scrolling with the stylus. The neoprene sleeve looks the business but you have to remove it to plug the charger in, and to do that you need to remove the wrist strap. There are reports of the neoprene splitting under repeated removals. There is no touch screen lock, so unless you turn it off or place it in standby, you can’t put it in your pocket or rucksack (if you do turn it off or put in standby, it stops recording your track). The scrolling is a nightmare using a finger, even with the stylus it’s very erratic. The beep is a terrible sound, sounds like a cat being molested, and there are reports that some units make a continuous low level sound when on. Now the software: Anyone who has used Memory-Map will probably know it’s one of the best mapping programs out there. BUT, it would appear that, as far as Memory-Map on the PC is concerned, the 3500 is neither a PDA nor a GPS so any and all data transfers must now be made by saving various files and moving them between devices using Windows. No longer can you 'send to GPS' or 'send to PDA'. What we have is a rugged Windows CE custom built handheld device running the existing Memory-Map application. This is the same Memory-Map version that I used to run on my PDA and not a version written specifically for the new hardware. This explains all the issues with power-save and backlight settings etc Even worse, being Windows CE it will not run my 3rd party support apps such as CacheMate. Even though the opening screen has an ‘Apps’ button, you can’t install any. The backlight OFF timer setting only works when the Memory-Map application is not running, and even then it only dims the display rather than turning it off. So, for a long day caching you will need more than one battery, which is a right pain to change in the field if you have the neoprene sleeve and wrist strap fitted. There is a power down setting but the instructions tell you to leave this as ‘always on’, why include it then? The GPX import still ignores all the Groundspeak tags so for paperless caching you will continue to have to take a pocket PC with you. There are a number of bugs in the software. For example, if you put the device into standby it doesn’t always come back and on occasions the device refuses to turn off, both of these are only fixed by removing the battery. I really would have loved to recommend this unit to fellow geocachers but I can’t. I love Memory-Map mapping software, I love Cachemate for its GPX handling, I love iPaqs for their usability and I love Garmins for their robustness and battery life. I have always dreamed of replacing them all with one unit, but this isn’t it.
  9. I agree, what is the point? If you want the owner to know their bug is safe and well, fine, mention that you saw it in your normal log entry. Otherwise, take the bug and move it on, even if it's only a mile or so. We often include a note in our log IF a bug is not in the cache but is listed as being so - this is much more useful to the owner. There is nothing more frustrating than having a bug stalled in a cache and loads of people just "discovering" it. No, don't discover it, take it with you, snap a photo, show it to friends, anything, but MOVE it on. We get such excitement when one of our bugs moves; who took it? what did they do with it? where did they take it? did they take a photo? great fun. But to see an entry that someone just saw it, where's the fun in that?
  • Create New...