Add support for nautical units

[GoogleCodeExporter]

It would be useful to support nautical units for nautical and aviation 
purposes. This involves showing distances in nm and speed in kts (nm/h).

Original issue reported on code.google.com by rdama...@google.com on 24 Aug 2010 at 4:56

[GoogleCodeExporter]

I have raised the same issue, perhaps not as well phrased as here. Please! 
Pretty please?

Original comment by beards...@gmail.com on 24 Aug 2010 at 8:42

[GoogleCodeExporter]

I have no problem with someone doing this.  It would be a technically simple 
but tedious task.  Currently the units are stored in a binary flag in a lot of 
places.  Each of those pieces of code would need to be updated to handle at 
least 3 values.

The following search showed that at least 23 files would need to be changed to 
accommodate this:
http://www.google.com/codesearch?q=metric+package:http://mytracks\.googlecode\.c
om&origq=metric&btnG=Search+Trunk

Original comment by sandordo...@google.com on 24 Aug 2010 at 8:45

[GoogleCodeExporter]

beardsell - yes, I filed this from your suggestion :)

Sandor - yeah, I know and I'm willing to do it - it's also a good opportunity 
for some cleanup. It's not my highest priority, but I'll eventually do it.

Original comment by rdama...@google.com on 24 Aug 2010 at 8:48

[GoogleCodeExporter]

Original comment by rdama...@google.com on 1 Sep 2010 at 10:55

• Changed state: Started
• Added labels: Work-Large

[GoogleCodeExporter]

Really looking forward to this feature, for offshore sailing purposes.  Thanks 
guys!

Original comment by simm...@gmail.com on 9 Sep 2010 at 11:59

[GoogleCodeExporter]

I am excited for this update as well, it will be really appreciated for sailing 
and flying!

Original comment by paladi...@gmail.com on 10 Sep 2010 at 12:37

[GoogleCodeExporter]

brownie points to whomever add knots and NM as speed and distance units to my 
tracks. I use this to log my flights on my droid 2. one day, some google 
employee who has an instrument rating will find a way to make avcharts show up 
as a layer in maps, then I'll be REALLY happy!

Original comment by james.st...@gmail.com on 7 Dec 2010 at 1:13

[GoogleCodeExporter]

That google employee would be me :) Just haven't found the time to work on that 
yet - trying to finish the features that most users want first.

Original comment by rdama...@google.com on 7 Dec 2010 at 1:15

[GoogleCodeExporter]

Keeping as accepted since I haven't really started it yet.

Original comment by rdama...@google.com on 25 Feb 2011 at 4:07

• Changed state: Accepted

[GoogleCodeExporter]

This would be awesome feature. I used My Tracks this past weekend to record 3 
Regatta races. Everyone was very excited to see the My Tracks map of our three 
races and it was very valuable to see how our decisions to tack or stay on 
course were laid out on the lake. Nautical Measurements would have made the 
review even better. After the race we sailed 24.3 miles according to My 
Tracks...... just multipying by .85 ( which is not totally accurate) would give 
us 20.7 Nautical Miles. 

Original comment by alphacol...@gmail.com on 21 Mar 2011 at 8:38

[GoogleCodeExporter]

The changes related to issue 178 pave the way for this - I explicitly made 
"onUnitsChange" separate so it's just a matter of changing from the boolean 
"isMetric" to a unit enum (+ changing the formatting functions). Except this 
soon afterwards.

Original comment by rdama...@google.com on 21 Mar 2011 at 8:46

• Added labels: Work-Medium
• Removed labels: Work-Large

[GoogleCodeExporter]

I am very glad to read about this getting closer to becoming a feature set of 
My Tracks. Any idea on a timeline to see an App Update available? Thanks

Original comment by alphacol...@gmail.com on 1 Apr 2011 at 3:46

[GoogleCodeExporter]

I'd say we'll probably have an update in about 2 weeks (two members of our team 
are in paternity leave, so we're making slower progress), but it could be 
shorter or longer than that. I can't guarantee that the units change will be in 
this next one, but if it's not, it'll be done right after it.

Original comment by rdama...@google.com on 1 Apr 2011 at 6:17

[GoogleCodeExporter]

Original comment by rdama...@google.com on 30 Apr 2011 at 10:22

• Added labels: Targeting-1-2

[GoogleCodeExporter]

(just removing OpSys-Android label, all issues are in Android anyway)

Original comment by rdama...@google.com on 26 Jul 2011 at 1:00

• Removed labels: OpSys-Android

[GoogleCodeExporter]

I agree that a Nautical Miles and feet option would be great! I use this app to 
track my helicopter flights and we use knots and feet..

Thanks

Original comment by abriler...@gmail.com on 22 Oct 2011 at 8:22

[GoogleCodeExporter]

Please add the nautical miles units. This would make the app perfect. Thanks a 
lot!

Original comment by mstur...@gmail.com on 6 Apr 2012 at 9:30

[GoogleCodeExporter]

Issue 894 has been merged into this issue.

Original comment by jshih@google.com on 21 Jun 2012 at 6:25

[GoogleCodeExporter]

Issue 1055 has been merged into this issue.

Original comment by jshih@google.com on 31 Jul 2012 at 5:35

[GoogleCodeExporter]

Original comment by jshih@google.com on 28 Feb 2013 at 12:35

• Changed state: New

[GoogleCodeExporter]

Asked for Knots and NM some time back on "Comments". Was disappointed to find 
today that it hasn't progressed.
This is so good for sailing. 

Original comment by managerg...@gmail.com on 13 May 2013 at 7:08

[GoogleCodeExporter]

Currently I'm looking into making the tedious changes as mentioned by Sandor 
(comment #2).
I started with replacing the boolean metricUnits flag with an enum which would 
enable support for more than two unit systems. Now I'm at the point where 
everything is compiling and I'm looking into testing my changes (manually and 
via unit tests).

I'm wondering if any of the maintainers are available and would be willing to 
review the changes and to eventually merge them into the main line?

Also in the course of the refactoring some questions came up regarding the 
handling of resource strings (with units in them) which I would like to discuss.

Original comment by christia...@gmail.com on 6 Jan 2014 at 9:59

[GoogleCodeExporter]

Looking forward to the changes, I'm a yachty

Brian

Original comment by managerg...@gmail.com on 7 Jan 2014 at 9:52

[GoogleCodeExporter]

As a first step I made the changes to introduce the enum. The proposed patch 
for that is available at:
https://code.google.com/r/christiank2510-mytracks1/source/detail?r=c1ea77fc8d7b7
7f98408cde9f424897f44df376e

All unit tests are passing with the patch but it still needs some minor 
polishing (see TODO comments for details).

Original comment by christia...@gmail.com on 7 Jan 2014 at 9:27

[GoogleCodeExporter]

Maybe i don't appreciate how much work is involved but this was raised back in 
2010 and we're stilling holding our (collective) breath.
To those putting in the hard yards - good onya and we're still really keen to 
see the outcome

Original comment by managerg...@gmail.com on 14 Mar 2014 at 1:49