I'm in the process of creating Garmin compatible maps of wilderness areas by state (see California Wildernesses, which is the first state that I did), but I also want to provide a more universal option for people who don't have Garmin units or to use for other purposes. So I thought about using gpx.
Here's the dilemma though: Wilderness boundaries aren't really tracks or routes and they're large and complex enough geographically that generalizing them to any significant degree results in too much loss of detail. Ungeneralized boundaries, however, contain thousands of points and, as I discovered when I tried to transfer a test file to my GPS unit (gpsmap 60csx), units truncate at 200-250 points. So I created the attached file that breaks a single boundary into multiple routes, each with less than 200 points. This file is of the Rattlesnake Wilderness in western Montana.
Is this the best format for maximum compatibility with a variety of GPS units and other devices?
Here's the dilemma though: Wilderness boundaries aren't really tracks or routes and they're large and complex enough geographically that generalizing them to any significant degree results in too much loss of detail. Ungeneralized boundaries, however, contain thousands of points and, as I discovered when I tried to transfer a test file to my GPS unit (gpsmap 60csx), units truncate at 200-250 points. So I created the attached file that breaks a single boundary into multiple routes, each with less than 200 points. This file is of the Rattlesnake Wilderness in western Montana.
Is this the best format for maximum compatibility with a variety of GPS units and other devices?
Support GPSFileDepot
Contact Us
Subscribe to RSS Feed
Share on FaceBook