Invalid Track Points on Import

Hello,

Brand new to qmapshack (expert at basecamp). I have a few issues/questions:

• When I import GPX files with tracks, I get The Track "xxx" has NNN invalid points out of YYY visible points. Do you want to remove the invalid points now?" popup dialog.
  • This is very annoying and I can't figure out how to disable it. I want to import hundreds of tracks and every time I do I get these popups. Even if I select "no", the next time I display a track I get this same popup. I don't care if my track points are missing timestamps or elevation data. I just want to import the lat/lon values so I cand display and edit. Is there a way to disable this checking?
• Is there a way so set the displayed line width for tracks? The default is very thin line on the maps and the tracks are very hard to see.

Thanks.

Please consider removing this check or how about making it a configuration option?

When you say "corrupted beyond repair", I'm not sure what you mean. To me, a track is a series of points (possibly with or without other metadata such as time and elevation). I'm not sure how any software would determine what "corrupt" means unless the points were out of legal lat/lon range (ie, a given track could define all sorts of points on Earth and it would be hard to tell why that track which is illegal). I have thousands of tracks that are made up from many different sources (often cut and pasted together). Many have nothing but lat/lon (ie, no elevation or timestamps). These are not corrupt. When you create a track from scratch, there is no timestamp or elevation data (at least when you use basecamp to create them).

Thanks for your consideration.

Zitat von kiozen

I am quite tempted to remove that feature. This was introduced when a user complained about no feedback when loading corrupted tracks from his shitty device. QMS does not calculate secondary data for corrupted tracks. As there was no feedback from QMS the user wondered why for some tracks data was derived and for some not.

Anyway it's a pain to click that dialog over and over again. And in almost all cases the tracks are corrupted beyond repair. Shitty tracks are shitty tracks. And the feature is a good example of how the petitions of a single user resulting in strongly demanding "fixes" can spoil software if you listen to the demand.

On the other hand side: Stop using shitty tracks or devices that produce them. In that case you never see that dialogue.

Zitat von kiozen

To get large collections of tracks into shape I would write a small Python script to strip all the useless junk from the tracks to get plain tracks with 2 dimensions. Keep your data clean and tidy instead of messing with a sloppy and clunky data Behemoth.

Instead of forcing people to run scripts and clean up data, please make a configuration option to ignore everything except lat/lon. I see no reason to name-call people's tracks "frankenstein" and refuse to process them. There are many reasons track don't have all metatdata (including gps units failing to put it in). 99% of users want the geo track itself and care little about timestamps or elevation data. We just want to know where we've been or where we are going.