Garmin question-extracting/uploading files

I'm able to export a GPX from Motion Based, but unable to upload it to BT. Wondering if it's too big at 227kb, I get the same error screen as if I attempted to upload too big of a picture.

Also was hoping to bypass the MotionBased site, looking to BT for one-stop shopping.

This was partly a configuration issue which has been corrected and for some files, like the one the bear is trying to upload, it looks like a coding issue. I'll try to get the coding part resolved later this evening (After my run. I missed too much training working on this lately. Sorry Green team). 

bear, the file you sent me isn't valid. It's missing some required data at the end.

Can you try exporting it again? There isn't much we can do with an invalid route file.

Once you import the file, click on the Bike icon and save the route. 

'Sport' is something that's not defined in the standard, so every site and device manufacturer is going to have a different way of storing it.  In the few motionbased files I've seen there doesn't appear to be anything that defines the sport at all.

Here's a free program to do it offline.

http://www.easygps.com/download.asp

I have installed it and looks very promising though I havn't had time to run any data through it yet but it has support for garmin 301, 305 and tons of other gps's.

It will export as .gpx

oh yeah, great job on the mapping section.

BT Rocks!!!!!!!!!!!!!!!!!!! Nice Job MarmaDaddy

There are no membership level restrictions on any functions related to the routes.

Email the gpx file to the BT 'support' email address and I'll take a look.

I uploaded a fix last night, should be working. As to all uploaded routes defaulting to 'Run', I'll look at that this evening, shouldn't be too complicated.

I'd like some input here from you GPS device users: some of these things are plotting points every 3 feet or so. That's a lot of data for this purpose and slows things down more than it's worth. I'm probably going to throttle it by adding some "if this point is less than n meters from the previous one, ignore it" logic when uploading.

My question to you is "how many meters should n be?".

I think this would only be an issue if it cut off a corner, like a 90 degree corner.

If it was set to 9 and you ran 4 meters from the last point to a turn, then ran 5 more before the program tagged it, you would read the 6 meter angle instead of the 9 (90 degrees = 4-5-6).

if you ran a lot of city streets, 10 corners would equal a 30 meter loss.