Why is there elevation data in a route created in basecamp, but when you convert it to a track inside basecamp, the elevation data is lost...
how come?
so after spending 100s of dollars to buy the gps and update it with backups on my computer, and it fails to route because a route is too long, the workaround I'm offered is basecamp which refuses to route for elevation???
so after spending 100s of dollars to buy the gps and update it with backups on my computer, and it fails to route because a route is too long, the workaround I'm offered is basecamp which refuses to route for elevation???
You'll have to be just a little bit more specific if you expect any help. Like which map did you try to route on, which device are you using, which profile are you using and where do you want to route from and to.
not sure how route is relevant (altitude is included on I-5, but not on I-70, perhaps?), but in case you were wondering why it is important, I was routing from Colton, CA to Anderson, IN. Routing was over Vale, with no consideration as to altitude, since altitude was not included (I checked)
