Please document the expected behavior

[jz-josm@…]

I have installed the fit plugin into Josm 18646. Unfortunately nothing has change. I can not open fit files, as I would have expected. Since I can not find any documentation that tells me what to expect after installing the fit plugin, I have no idea if this is a bug.

[gaben]

Please try updating to the latest JOSM version first.

The fit plugin working fine for me, although the distance and speed fields are weird (cc @taylor).

---

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

[taylor.smock]

I'm going to go with gaben's response: Please try updating to the current latest JOSM (r19067).

You should be able to open FIT files using any standard opening method (drag'n'drop, Files -> Open, etc.).

The fit plugin working fine for me, although the distance and speed fields are weird

@gaben: Everything in the FIT plugin except for the basic parsing (and some other things that were openly documented and did not require a license to sign) is black-box reverse engineered. In other words, the only reason that GPX data is working is I made some educated guesses on how it was calculated given the expected lat/lon and the recorded information, and it was close enough.

[gaben]

The plugin is perfectly fine, just the units are.. odd? :D For speed the unit seems like mm/s. Why, Garmin?

[taylor.smock]

Well, mm/s is probably something they considered was small enough to not need fractions (AKA floats/doubles). I have no clue why they decided to avoid floating point numbers whenever possible, but it might just be a relic of 20 years ago.

It could also be inches/second. But it is probably mm/s.

I don't mind converting it from mm/s to m/s, but I'd have to look and see if that is what is expected in GPX data.

[jz-josm@…]

You should be able to open FIT files using any standard opening method (drag'n'drop, Files -> Open, etc.).

Thanks, would be nice to have that documented somewhere, just a short
snippet. My issue was that I could not determine if it was not working
or if I was missing somthing obvious.

I won't update now, gpsbabel will do for the time to the next Debian
release.

[gaben]

Ah, yeah the floating point numbers. So probably because the floating point calculations are more expensive without dedicated hw, thus eating more battery on wearables. Now it makes sense.

[taylor.smock]

In 36265/osm:

See #23662: Add short section in README for non-developers