not everybody uses Dashware
it is meant for people who look only into CSV file, so they would see those values in imperial units
Sure sure, totally agree there.not everybody uses Dashware
it is meant for people who look only into CSV file, so they would see those values in imperial units
not everybody uses Dashware
it is meant for people who look only into CSV file, so they would see those values in imperial units
Just made this in dashware from your converter
this is not such a bad idea, but it would bring two problems:is there a way for you to specify feet,meters, f/s , m/s in the field names for clarification?
this is not such a bad idea, but it would bring two problems:
1. if somebody had already created dashware profile on current column names, he will have to change it
2. if user selects metric units and creates CSV and then he selects imperial units and creates another CSV, column names will be different in those two CSVs
if this is acceptable, I can add units to all column names
please, send me that TXT too, thanksTried your converter on a P3P TXT file
new version is out, with these changes:
- added option to choose units
- column names now contain units too
- that 02/HOME error reported by @flyNfrank should be fixed (I can't confirm it, because I have no TXT log from P4)
- if Dashware uses columns according to their order, then WARNING: I rearanged the columns in a way, that altitude is always before longitude (so now it's finally easy to copy it into Google Maps)
next I'll look into Inspire logs and I'll try to figure out, if I can make it work
and yes, @Fdnyfish, I have that height.running_max on my mind too
this belongs to the Inspire log, right?Rows D&F need to move the decimal place over to the left once (don't think I was going 444.8mph.... 44.5 seems more like it)
We use essential cookies to make this site work, and optional cookies to enhance your experience.