SiliconFiend

You're welcome. I was looking around for a decent GPX viewer/editor and hadn't been satisfied but then I came across Viking and it looked pretty cool. I was particularly impressed by the inclusion of map tiles from OpenStreetMap (even a choice between Mapnik and Osmarender!). Since the main reason I wanted an editor is to organize/crop/clean up my GPX traces prior to upload to OSM, it's a great bonus (also lets me see quickly where I need to do some mapping). It would, that is, if it wouldn't crash under Windows... It may be something about my setup, but I can't know what it might be.

I just discovered this GPS data viewer/editor/manager: http://sourceforge.net/projects/viking/ I haven't had any luck running it under windows (downloading background maps makes it crash), but it might run better under Linux.

I have a Garmin 76CS and if I hold the Enter key I get a "Mark Waypoint" screen with the current icon showing a non-found cache. Also see my follow-up post where it mentions the same thing on page 7 of one of the Vista manuals. Yep, that's the "man overboard" mode, but it might not be called that. It's just a mark waypoint screen, but the coordinates default to your current location. The icon defaults to the last one you used. Either way will work, I just mentioned using the cursor on the map screen because you can get it close to where you want and you'll have to change fewer digits.

Note that this method defaults to the "man overboard" mode and the coordinates will initially be at your current location. If you want to put it elsewhere, it can be handy to move the cursor on the map near the spot where you want it, then click and say "yes" to new waypoint (if there's nothing under the cursor), or click to view the object under the cursor and then click Save. Then you can edit the coordinates of the waypoint and there will be fewer numbers to change. Edit: Oops. I hit reply on the wrong post. I meant to hit it on the one above, that recommended holding down the enter button. That activates the "man overboard" mode. Red90's method is great.

It's been there a few months. It's nifty.

I appreciate these free map projects undertaken by dedicated individuals but this is the reason why I encourage people to use OpenStreetMap. If you see a problem, you can fix it yourself and then you and everyone else can benefit. Check out mkgmap for creating Garmin maps from OSM data. Other projects are in the works, too.

http://wiki.openstreetmap.org/index.php/Ma...g_Weekend_Howto

With Google maps you can drag your route around to hit the roads you want. I don't know if there's an equivalent feature for a desktop application.

I can give you one for Kansas right now. It's a single contour, at 1000 feet.

I would vote for separate, transparent contours. At least as an option. When you're compiling your MP file, you could create one file with your roads and one file with the contours, and then combine them using the "include" functionality in a third MP file. That would let you keep the datasets separate and then just bring them together when you compile. You should coordinate with IndyJpr and others on this--they've been working on 24k-equivalent topos for a number of states. Do the contour intervals in feet so the generated contours match the other map products. If you do it right and include the contour height in the label with the right code it can be converted automatically to display in whatever units the user wants.

Use mine to collect tracklogs to contribute to OpenStreetMap (www.openstreetmap.org) Contribute yours and help make maps we can all use!

You can use ogr2ogr (www.gdal.org) to transform your shapefiles into different coordinate systems. You probably just want WGS84 as the output.

This is bugging me. I don't have hard evidence, but my Vista HCx just "feels" less accurate since the GPS software 2.60 update. Not 20 to 50 meters off, more like 5 to 10, even when EPE is reported as 2 to 3 meters. I would be thoroughly annoyed if Garmin changed something fundamental in the GPS software because of the people griping about the odometer, and now we have to live with a positional error, which is a far worse problem.

That's actually a pretty simple math problem. Just convert the coordinates to decimal degrees and take the average of the two components from the two waypoints. In other words, lat3 = (lat1 + lat2)/2, lon3 = (lon1 + lon2)/2. Then you can convert the result back to degrees decimal minutes if needed.

I don't have that software but I think it's supposed to work on your 60CSx. A couple things to check--did you check the box that says "include routing info" (or something like that) when you downloaded the maps to your unit? Also, check your routing setup and make sure you're in "Pedestrian" mode, not Car/Motorcycle. It's likely those trails are marked as restricted for anything but pedestrian.

Yes, you will. You can also get the Topos and but Metrogold for 6 bucks to make the Topo autoroute.... You mean MetroGuide and MetroGold, not Topo. Only the (older?) Canadian Topos will autoroute, and they don't need Metrogold to do it.

Actually, there's good evidence that they do. They just don't post (at least not representing Garmin). Several forum members have spoken to support personnel and Garmin definitely knows about this forum, particularly since the Colorado was released and all its issues they've been dealing with.

Garmin WorldMap will give you basic "base map" standard maps for the whole globe, which may or may not be adequate for your needs. You can "road test" it on-line at Garmin's MapSource Map Viewer, to see if it is worth having before you buy: http://www8.garmin.com/cartography/ontheRoad/ You can find a lot of free user-generated maps at Garmin Map Search: http://garminmapsearch.com/ Quality and content is extremely variable, but it is always worth a browse when going to new territory, to see if there is anything worthwhile for the area you are travelling. Hope this helps! You might also check out OpenStreetMap and mkgmap (some assembly required). Coverage of Africa is somewhat spotty, but almost certainly better than a basemap. Plus, while you're there you can collect tracks and then contribute them to make OSM better.

I have 2.60/2.60 and I had this happen to me this week. Had to power cycle to get it back. I've only seen it that one time, though.

Maybe Garmin skipped 2.50 because of this thread, just to mess with all of you.

Holy smokes, you're complaining about a 5 foot error? Your GPS will get you within 10 feet on a really good day (there's always the chance you'll get lucky and nail it right on). I've seen imagery alignment problems on the order of 50 feet, more in Google Maps than in Google Earth; for some weird reason they seem to have different imagery or alignment.

Probably worse. It's not that the coordinate system used by Google Earth is bad, but the imagery may not line up perfectly. For geocaching, all your coordinate systems/datums should be set to WGS84. That's the default all around for your GPS and GE.

Maybe it's not necessarily a bug but a difference in expected behavior. I can see how that might be something useful, if you were planning a future fishing/boating trip and you wanted to check several tide stations for that day. It would save you from having to change the date for each one you check. I agree it shouldn't persist after a power cycle, though.

Some unsolicited advice: In my opinion, you're taking too big of a bite to chew. Best to nibble at the project. Treat your ultimate flexible goal as a high want and do today that which is achievable with known resources. As the project matures, you can come back to the the lofty goals. You'll pick up volunteers as you have a measure of success. I looked at the seeded maps and they're very good. Put up a mission statement and seek people with targeted skills to help. This needn't all fall on only your shoulders. FWIW Well, thanks for the advice, but I don't think it's too much to bite off. I have a nice design (I think so, anyway) for how the customization can work, in terms of an example XML rules file. But I have to figure out how all the pieces are going to interact, then write the parser for the rules file, etc. I have it in my mind how it will work, but I need to get it written down so I can solve the sticky problems before I get to writing code. I have some good mentors to help me out in the architecture department (probably where I'm lacking the most), and I have ideas for the features I want to implement, and the phases in which that will happen. Also, I'm writing this as a plugin for an existing utility which takes care of a lot of the plumbing for me, allowing me to focus on the parts I care about. This is partly an exercise in software engineering for me, so I want to take on something that's a meaningful size, but not too big. I think this fits.

Is routeable the real issue and the value? Since I'm city phobic, I could care less, but for the masses, I believe, having routable maps is the holy grail. I don't know if it's the "real issue", but I do think free, auto-generated, easily updated (and user-correctable) routable maps is indeed the holy grail. I'm working on a project to create routable Polish-format maps from OSM data. Those files would then need to be fed into cGPSMapper (until someone else decodes the routing file format). The thing that's holding me up is that I want to make it completely flexible so if you want only trails, you can create a map with that, or if you want a bike-centric one, you can have that instead. It's a complex problem and it's tricky finding the right approach.