Support import from computer to watch

GoogleCodeExporter commented 9 years ago

Some watches such as onMove 510 have a navigation function. GPX tracks can be 
imported and then followed during a training session. It would be interesting 
to add that functionnality to your tool.

Original issue reported on code.google.com by col.patr...@gmail.com on 15 Sep 2014 at 6:57

GoogleCodeExporter commented 9 years ago

Hello, 

this should be supported for all watches using Kalenji driver.
You just need to use -o Kalenji option. It is advised to use ReducePoints 
filter as it's not possible to upload a track with more than 200 points.

Here is an example of a command to do that. I suppose you have a file called 
'myTrack.gpx':

./kalenji_reader -D GPX -i myTrack.gpx -f 
FixElevation,ReducePoints,ComputeSessionStats -o Kalenji

There's even an helper script in svn repository: scripts/kalenji_export.sh.

Additionally, there's some explanation in the FAQ on how to create a GPX file 
from GoogleMap:
https://code.google.com/p/kalenji-gps-watch-reader/wiki/FAQ#How_can_I_easily_cre
ate_GPX_files_to_upload_to_my_watch_?

Tell me if you have an issue, or if anything is missing.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 15 Sep 2014 at 7:09

Changed state: Invalid
Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

Hi,

I didn't noticed you've already developped it! I've just tried but it
didn't work :

D:\GPS>kalenji-gps-watch-reader-4.9.1_win\kalenji-gps-watch-reader\kalenji_reade
r.exe -D GPX -i Tour_etang_viry.gpx -f
FixElevation,ReducePoints,ComputeSessionS
tats -o Kalenji
  Applying filter FixElevation
    Fixed elevation of 140 points.
  Applying filter ReducePoints
    Reduced session from 219 to 219 points (min angle = pi/64).
  Applying filter ComputeSessionStats
Ascent is 126 and descent is 126
Error: couldn't export to output Kalenji:USB device not found !

Here is what I have in my conf file :
device=OnMove710
import=new
source=Path
path=F:\
directory=D:\GPS

Where is the mistake?

Patrick

2014-09-15 21:09 GMT+02:00 <kalenji-gps-watch-reader@googlecode.com>:

Original comment by col.patr...@gmail.com on 16 Sep 2014 at 5:38

GoogleCodeExporter commented 9 years ago

Sorry, my bad !
This is not yet supported for OnMove510 and OnMove710. I must have been tired, 
when I read your message my mind thought "Keymaze 500 Hike" for which it's 
supported through Kalenji device.

Do you have more information on how the upload works for OnMove 510 / 710 ?
This device is mounted as a USB mass storage. Can you try to upload a session 
on it with the official software under windows and see if new files are 
created, and if yes which ones ?

Once done, can you please send them to me with the GPX file you used to create 
it so that I can understand how it works ? If you don't want to put them in 
attachment (in case you want to keep them private) you can send it to me by 
mail. 

Regards,
Colin

Original comment by colin.pi...@gmail.com on 16 Sep 2014 at 6:39

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

Original comment by colin.pi...@gmail.com on 16 Sep 2014 at 6:40

GoogleCodeExporter commented 9 years ago

Here is an example : a gpx file and the 2 files created on my watch after 
import. Let me know if you need anything else.

Original comment by col.patr...@gmail.com on 17 Sep 2014 at 2:51

Attachments:

Tour_etang_viry.zip

GoogleCodeExporter commented 9 years ago

Hello,

can you give me more details of what information is available for the session 
once imported on the watch ?

I see the file contains the name of the session (Tour_etang_viry). I also see 
the coordinates of the points. But I also have a few information that I don't 
know where to take from. In your example, I have the following numbers:
 - 40
 - 117 (the 40 and 117 could also be interpreted together as 10357, maybe the total distance in meters ?)
 - 135 (2 times, maybe ascent / descent ?)
 - 98

Does it ring a bell ? Do you have info visible on the watch or functionalities 
that would require some data it would represent ? 

Another 'problem' I have is how to name the file ... Could you try multiple 
export and see how the names vary ? If you copy a file and give it a custom 
name (for example TEST.GHR, or if it doesn't work something closer to the 
normal names like E9HG0000.GHR), does the watch see and recognize it ?

Once I have this information, implementing the export shouldn't be an issue.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 23 Sep 2014 at 8:06

GoogleCodeExporter commented 9 years ago

I forgot one point, it would help me to have 2 more examples with names of 
different length. Maybe one with a small name (4 or 5 letters) and one with a 
longer name (20 letters or more).

Regards,
Colin

Original comment by colin.pi...@gmail.com on 23 Sep 2014 at 8:28

GoogleCodeExporter commented 9 years ago

I just commited a first attempt to support the export.
It may not fully work, in particular because of filename and session name. If 
the session name is 15 letters (as in your example), I think this should be 
fine but shorter or longer may result in an invalid result. For the filename, 
if not recognized properly by the watch, I expect the session to not appear at 
all on it.

To test it:
kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -i 
Tour_etang_viry.gpx

Note that the filter ReducePoints is needed because it seems the file cannot 
contain more than 200 points (it has a fixed size).

Regards,
Colin

Original comment by colin.pi...@gmail.com on 24 Sep 2014 at 9:14

Changed state: Started

GoogleCodeExporter commented 9 years ago

I'd like to test it on my side. Can you give me a compiled version for
windows?

2014-09-24 23:14 GMT+02:00 <kalenji-gps-watch-reader@googlecode.com>:

Original comment by col.patr...@gmail.com on 25 Sep 2014 at 7:35

GoogleCodeExporter commented 9 years ago

Here is a windows version with this just for you.
Don't hesitate if you meet any issue with it.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 26 Sep 2014 at 3:55

Attachments:

kalenji_reader.exe

GoogleCodeExporter commented 9 years ago

Hello, 

did you have the opportunity to test it ? Does it work well ?

Regards,
Colin

Original comment by colin.pi...@gmail.com on 8 Nov 2014 at 9:55

GoogleCodeExporter commented 9 years ago

Hi,

Sorry, I've been injured for a few weeks and I didn't have any opportunity to 
test it. I'll let you know as soon as I've tried it, hopefully this week.

Best, 

Patrick

Original comment by col.patr...@gmail.com on 8 Nov 2014 at 10:39

GoogleCodeExporter commented 9 years ago

Hi,

Finally, I'm back on my running shoes and I've made some tests but results
are not so good. :-S

*Test 1* :
Unable to launch kalenki_reader.exe because libcurl.dll was missing =>
After copying and pasting all the dlls from the 4.9.1 version into the same
directory as the beta version you sent me, problem was solved.

*Test 2* : 20141125_131937.gpx (see enclosed)
Filename : less than 15 characters
Session name = 15 characters

Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i ..\Test\20141125_131937.gpx

kalenki_reader crashed (sorry crash details are in French) :
"Signature du problème :
  Nom d’événement de problème: APPCRASH
  Nom de l’application: kalenji_reader.exe
  Version de l’application: 0.0.0.0
  Horodatage de l’application: 5425884e
  Nom du module par défaut: ntdll.dll
  Version du module par défaut: 6.1.7600.16385
  Horodateur du module par défaut: 4a5bdb3b
  Code de l’exception: c0000005
  Décalage de l’exception: 00052374
  Version du système: 6.1.7600.2.0.0.256.48
  Identificateur de paramètres régionaux: 1036
  Information supplémentaire n° 1: 72a5
  Information supplémentaire n° 2: 72a5bd4f3bed0d3b12fe6df059653792
  Information supplémentaire n° 3: 92bf
  Information supplémentaire n° 4: 92bf38eb9a7c6c5f657f23af040ec631"

*Test 3* : 111111111111111.gpx
Filename : 15 characters
Session name = 15 characters
Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i ..\Test\111111111111111.gpx

kalenki_reader also crashed

*Test 4* : 111111111111111.gpx
Filename : 15 characters
Session name = 15 characters
Command used : kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -i 111111111111111.gpx

kalenki_reader also crashed (I thought that the problem was in the file
path but not...)

Best,

Patrick

2014-11-08 23:38 GMT+01:00 Collignon Patrick <col.patrick@gmail.com>:

Original comment by col.patr...@gmail.com on 4 Dec 2014 at 8:49

GoogleCodeExporter commented 9 years ago

Hello,

thanks for your feedback.
I think the crash you had are linked to issue 43.
I fixed it in svn, I'm attaching a fixed version for windows. Another way to 
test could be to use the following command:

kalenji_reader -D GPX -f ReducePoints,ComputeSessionStats -o
OnMove710 -p E:\ -i 111111111111111.gpx 

(assuming 111111111111111.gpx is in current directory and the watch is mounted 
on E:\)

Tell me if it doesn't fix your issue or if you encounter a new one.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 9 Dec 2014 at 8:03

Changed state: Accepted

Attachments:

kalenji_reader.exe

GoogleCodeExporter commented 9 years ago

Hello,

Perhaps I can be of any assistence. 
I have tested this file kalenji_reader with my Onmove710, using Win7.
Here is what I did:

First I run about 12 km with the watch.
Then I imported this file with the kalenji_reader.
I renamed this file to 123456789012345.gpx.
Then I tried to upload this file to the watch, using the following command:

kalenji_uploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G:\ 
-i 123456789012345.gpx 

(I renamed kalenji_reader to kalenji_uploader. Watch was mounted on G:).

During upload following errors occurred several times:
Warning: parsing of element 'bounds' in metadata not implemented in device::GPX
Warning: parcing of element 'TrackPointExtension' in trackPoint extensions not 
implemented in device::GPX
Warning: parsing of element 'lap' in trackPoint extensions not implemented in 
device::GPX

Here are the results after completing the upload process:

* Some data is imported in the watch. 

* Text on the screen says ^ no Name. This was retrieved from the Metadata in 
123456789012345.gpx.
   I changed the name in the Metadata to 123 and uploaded again. Then display shows ^ 123.

* The picture on the screen shows part of the route (seems to be the first 50 
points).
   I did tests with other files. Route seems always be limited to about 50 points.

* Text under the picture says 15009 km. Should be something like 12.44 km

Please, let me know how I can help you further.
FYI, I do have a Kalenji CW 700 too, so I can do tests on both watches. 

Best regards,
Nicolas

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 9:34

GoogleCodeExporter commented 9 years ago

Hello,

If you want me to do some test with specific gpx-files, please upload them. I 
will perform the tests and report about the results.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 11:12

GoogleCodeExporter commented 9 years ago

One thing I didn't noticed before. Route seems to be correct in the watch
when Metadata is filled with 'no name' (although limited to a certain maximum 
amount of point).

When changing the name in Metadata the route in the watch is corrupted.
The picture of the route is wrong and so is the text under it (something like 
-452926208 m).
The name out of the Metadata however is correctly displayed above the picture.

Original comment by eindhove...@gmail.com on 8 Mar 2015 at 12:45

GoogleCodeExporter commented 9 years ago


Hello, 

I have done some more testing. Here are the results.

* problems with the gpx-file *
I originally used an gpx-file generated by the kalenji-reader to avoid 
incompatibility-issues,
however it turns out that this file was causing problems after all. I replaced 
this gpx-file
by another and now uploading is working fine under some specific circumstances. 
If those
conditions are met, then the preview is oke and so are the data in the 
detailfield.

* requirements for uploading *
The gpx-file should be in the correct format. I don't know yet what caused the 
problems with
the first gpx-file. Should be investigated.

Furthermore the name of track as used in de gpx-file (metadata) should be
exactly 15 characters long, otherwise the route gets corrupted in the watch. So 
as
an example: 123456789012345 is working fine. Longer or shorter causes problems.

  <metadata>
    <name>123456789012345</name>
  </metadata>

The name of the gpx-file seems not relevant. Also the length of it seems not 
relevant.
For example, I tested with the same file under different names, e.q. 
123456789012345.gpx
and 12345678901234.gpx and 1234.gpx. Results were all the same and oke.

* Further testing *
If you can upload some specific gpx-files, I will upload them to the watch. I 
can do that
with the kalenji-reader and with the original uploader. The watch is mounted as 
an USB-device
and produces GHR-files. I can share these files with you. 

Other suggestions for testing are appreciated.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 9 Mar 2015 at 10:52

GoogleCodeExporter commented 9 years ago

Hello,

that's a lot of info :-)

So if I sum up:
 - you had an issue importing a GPX file created by kalenji_reader. Did you check this GPX file was what you expected with another software ? If it is, can you please attach the file so that I can try to understand what went wrong when importing it ?

 - length of the name must be 15 char so that it works. Did you try with kalenji_reader 4.9.2 available in download tab or with the executable I attached to my update #14 in this issue ? The latter should fix it but I never delivered it as I didn't get a confirmation !

 - you say that text on the screen shows "^ No name", is it expected ? (In particular, is the ^ an issue or is it the same display you have when uploading with the original uploader ?)

 - you said initially that map was wrong but I understand that with the right gpx this is OK ?

 - you said also that the distance was wrong, is this one fixed also with the right gpx when the name length is 15 char ? 

Thanks for your feedback.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 9 Mar 2015 at 3:38

GoogleCodeExporter commented 9 years ago


Hello Colin,

I will repeat the tests to be sure and to see if I can reproduce the results. I 
will describe the steps as detailled as possible.

Q: you had an issue importing a GPX file created by kalenji_reader. Did you 
check this GPX file was what you expected with another software ? If it is, can 
you please attach the file so that I can try to understand what went wrong when 
importing it ?

A: the file created by kalenji_reader is 20150305_165657.gpx. I will upload it. 
It's quite a large file (889 kB and it contains 2896 points). I imported this 
file in SportTracks 3.1 and it looks fine. Exactly the route as it's suppose to 
be. But something went wrong during upload process.

Q: length of the name must be 15 char so that it works. Did you try with 
kalenji_reader 4.9.2 available in download tab or with the executable I 
attached to my update #14 in this issue ? The latter should fix it but I never 
delivered it as 
I didn't get a confirmation !

A: I used above mentioned 20150305_165657.gpx. And I used the executable from 
update #14. I wil upload the executable so that you can check what version it 
is. I used command: 
kalenji_uploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G:\ 
-i 123456789012345.gpx 

I renamed kalenji_reader to kalenji_uploader. Watch was mounted on G. During 
upload the following happened:

* on the computer *
a lot of warnings on the screen
.
.
Applying filter ReducePoints
Reduced session from 2896 to 185 points (min angle = pi/59).
Applying filter ComputeSessionStat
Ascent is 143 and descent is 136
Transferred session No Name

* information on the watch *
preview screen:
No name
preview shows about the 1/3 of the route
8913 km

detailscreen:
8913 km
up: 7.54 km
down: 785 m

I opened 20150305_165657.gpx and noticed that the following was in the 
<metadata>:

  <metadata>
    <name>No name</name>
    <time>2015-03-05T15:56:57Z</time>
  </metadata>

I changed that to:

  <metadata>
    <name>123456789012345</name>
    <time>2015-03-05T15:56:57Z</time>
  </metadata>

I run the test again (exactly the same way) with the changed file. I did not 
change the filename. So filename remains 20150305_165657.gpx. During upload the 
following happened:

* on the computer *
a lot of warnings on the screen
.
.
Applying filter ReducePoints
Reduced session from 2896 to 185 points (min angle = pi/59).
Applying filter ComputeSessionStat
Ascent is 143 and descent is 136
Transferred session 123456789012345

* information on the watch *
preview screen:
123456789012345
preview shows correct route
11.03 km

detailscreen:
11.03 km
up: 143 m
down: 136 m

Conclusion: everything seems to be oke when the name in <metadata> is 15 
characters long.

Q: you say that text on the screen shows "^ No name", is it expected ? (In 
particular, is the ^ an issue or is it the same display you have when uploading 
with the original uploader ?)

A: During this test it did not show ^. So I don't think it's an issue.

Q: You said initially that map was wrong but I understand that with the right 
gpx this is OK ?

A: Everything is oke when the filename in de <metadata> is exactly 15 
characters long.

Q: you said also that the distance was wrong, is this one fixed also with the 
right gpx when the name length is 15 char ? 

A: Yes, when the filename in <metadata> is 15 characters long.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 9 Mar 2015 at 5:56

Attachments:

GoogleCodeExporter commented 9 years ago

Hello,

here is a new version of kalenji_reader.exe that I just compiled from svn.
Looking at the history, the fix I made is from Dec 13, 2014 so it can't be in 
the file I attached in comment #14. I shouldn't trust my memory :-)

This one should work with file name longer or shorter than 15 char, truncating 
it if it's longer.

I checked the parsing of the GPX file you attached and it works well (despite 
all the warnings that are just here to inform about data that is not considered 
during the import, I should remove them). So I think the issue you had were 
really only about the name needing to be a fixed 15 char string whereas I was 
sending a variable length one.

If you confirm this new kalenji_reader.exe fixes this issue, I'll redeliver a 
new version in Download section.

Regards,
Colin

Original comment by colin.pi...@gmail.com on 10 Mar 2015 at 4:04

Attachments:

kalenji_reader.exe

GoogleCodeExporter commented 9 years ago


Hello Colin,

Thank you for the good work! This version looks fine. I have three small 
remarks:

1. At first attempt I got the following error:

Error: c:\tmp\kalenji_import doesn't exist and I couldn't create it

So I created the directory c:\tmp\kalenji_import manually and then the 
programme works fine. The programme doesn't seem to use this directory however?

2. If name is emtpy, like <name></name>, then kalenji_reader gives following 
error:

error basic_string::_S_construct null not valid

3. Your suggestion to suppress warnings and non-critical-errors sounds good to 
me. Perhaps with a switch (on/off) in the command line? It isn't very important 
though, so forget it if it means a lot of work.

I have no further comments yet, but I will perform some thorough testing in the 
coming month. I will inform you if any new problems occur.

Regards,
Nicolas

Original comment by eindhove...@gmail.com on 10 Mar 2015 at 7:40

GoogleCodeExporter commented 9 years ago

Three valid remarks !
I will look deeper into it tomorrow.

Original comment by colin.pi...@gmail.com on 10 Mar 2015 at 8:22

ColinPitrat commented 9 years ago

Copy paste from google (issue updated while migrating to github):

Hello Colin,

issue during guiding *

After uploading the data, but before guiding, everything seems fine. The preview is oke. When I choose guiding, it still is. I see the route that I'am suppose to walk.

But when I actually press 'start guiding' an additional line appears. It's from the point where I am standing at to the side of the screen. I can zoom in or out, that doesn't matter. The line stays there. It seems to be directed to the most

remote point of the route, but that's not always the case. Sometimes the line crosses the route at the most remote point and sometimes I see 2 parallel lines.

I've done the same test with the official software. Everything was oke then. No problems. No additional lines. I also did the same test with your kalenji-reader and a Kalenjij 700. Than also everything was oke.

I hope that you can make something out of this.

Regards, Nicolas

Hello Colin,

During uploading I encoutered the following issues:

truncating session * Files containing a lot of points are compressed to 200 points using ReducePoints. But sometimes still an error appears: 'too much points to export - truncating session'. Example: truncation_error.gpx
too much compression * Files containing a lot of points should be compressed to 200 point using ReducePoints. But sometimes compression is much heavier. For instance reducing session from 250 tot 183 points. Example: compresses250to183.gpx
using gpsbabel * I tried to solve these two issues using gpsbabel and simplify the gpx-input-files to 200 points before calling kalenji-reader. That was not good enough. With simplify set on 199 points the problems were solved.
filename * I noticed that kalenji-reader displays session-name (information out of metadata) as name of the route. The official software uses the filename (the part before .gpx). This is not an issue. I prefer the method of the kalenji-reader. But I just wanted to mention it. Perhaps there's a relation with some other issues.
easing end-user experience * I wrote a little script that calls the kalenji-reader. I place all the files that have to be uploaded in a directory. The script processes all the files one-by-one (i.e. removes white-spaces out of names, reduces # points to 199) and uploads them to the watch. I don't have to bother about spelling the names correctly or so. It just uploads all files in the directory. I found that to be very easy.

Regards Nicolas

ColinPitrat commented 9 years ago

Concerning your last updates:

I'll try to understand why you have this straight line, it looks like the start point of the session is in the middle of the track, not near where you are !
The other problems you have comes from ReducePoint filter not being very nice: it iteratively reduce the min angle to consider until reaching a number of points below 200. Sometimes it ends up being way below 200, but it could add some points to be just at the limit (199 or 200, to be verified)
If I understand well, spaces should be removed from name because they are not properly handled by the device ? If both this and the ReducePoint filter were fixed, you script would only consist in looping on the files to import them.

Eindhoven562 commented 9 years ago

Hello Colin,

I don't know why I have this straight line. It's there right from the start. I can use guiding anyway (from start to finish), but all that time the line is present. It always starts at the point where I am standing at that moment. I don't think that it's going to the middle of the track. It's more like going to the most far end of the track (as the crow flies). Please let me know what I can do you help you further on this issue.

Your last remark is correct. The script is only used do handle multiple files in an easy way.

Eindhoven562 commented 9 years ago

Hello Colin,

I hope to help you out with the following information.

I have uploaded the file OnmoveTEST.gpx to the watch using both the official Geonaute-uploader and the Kalenji-gps-watchreader. The watch produced *.GHR-files. I will upload them here. I hope that you can analyze them and find the differences between them so that you can improve the program.

First uploaded with the official Geonaute-uploader. Preview displays says OnmoveTEST 8.98 km. Detailscreen displays 8.98 km. 385 m up. 386 m down. Guiding is oke. No additional lines on the screen. File in watch: F3SB2907.GHR

After that uploaded with the Kalenji-gps-watchreader Preview displays says Irrel 8.88 km. Detailscreen displays 8.88 km. 752 m up. 743 m down. Guiding is not oke. Additional lines on the screen. File in watch: E9HG0000.GHR.

Remark: Gibhub only supports a limited number of file types. .gpx or .ghr are not accepted. I therefore had to rename the files:

OnmoveTEST.gpx --> OnmoveTEST.jpg F3SB2907.GHR --> F3SB2907.jpg E9HG0000.GHR --> E9HG0000.jpg

Regards, Nicolas

e9hg0000 f3sb2907 onmovetest

Eindhoven562 commented 9 years ago

Hello Colin,

I did some further testing.

As mentioned before, guiding is not oke when the route consists out off approximately 200 points (additional line appears). But when the number of points is significantly reduced (for example to 100 points) then guiding seems to be oke (no additional line). I don't know exactly what the limit is, but a quick test shows that 150 points is still too much (guiding is not oke then).

I hope that this information helps you further.

Regards, Nicolas

Eindhoven562 commented 9 years ago

Hello Colin,

Some time ago I posted GHR-files produced with the official Geonaute-uploader (guiding was correct) and with the Kalenji-gps-watchreader (guiding with errors). Have you been able to compare them with each other to find out what causes the errors?

Is there anything I can do to help you?

Regards, Nicolas

Eindhoven562 commented 9 years ago

Hello Colin,

I still have problems with guiding.

If I use the official Geonaute-uploader everything is working fine. When using the Kalenji-gps-watchreader additional lines appear on the screen. This issue seems to occure only with a large number of points (say more than 100).

In my post dated March 28 I submitted the *.GHR files produced with both uploaders. Can you please compare them to see what is causing the problem? A fix would be great!

If you need any additional information or testing, please let me know.

Regard, Nicolas

ColinPitrat commented 9 years ago

Hello,

having a look at the files, the one produced by kalenji_reader contains 199 points which corresponds to the content of the GPX. All the points in the file produced by Geonaute-uploader can be found in the file produced by kalenji_reader, but there are additional points in the one of kalenji_reader. The additional points in the output of kalenji_reader are really intermediate points (the latitude / longitude are progressing from the previous point to the next point).

It seems Geonaute-uploader drastically reduce the number of points.

The only issue I could find is that the padding at the end of the file wasn't properly done by kalenji_reader. I fixed it, can you give it another try with a fresh build from git repo ? Or do you need me to redeliver one ?

Regards, Colin

Eindhoven562 commented 9 years ago

Hello Colin,

I don't understand what you mean by 'build it from git repo'. I need a Windows executable-file. Can you please deliver it? Thanks a lot!

Regards, Nicolas

ColinPitrat commented 9 years ago

Hello,

here is the link to the exe: https://drive.google.com/file/d/0BweL-sTrQlo_dXBqeXlCR2RIaUE/view?usp=sharing

Regards, Colin

Eindhoven562 commented 9 years ago

Hello Colin,

I'm sorry to inform you that the error is still there. This fix is not a solution. After starting guiding additional lines still appear at the screen.

You mentioned that there are additional points added when using the Kalenji-reader. Can that cause the problem? I did find out that guiding is working correctly when I reduce the number of points significantly. I just repeated that test. If I use a GPX-file that contains 100 points guiding works correct. If I use a GPS-file that contains 199 files, than the error occurs (and the additional lines appear).

Can there by some kind of overflow or something? The maximum capacity of the watch is limited at 199 points (or 200, I'm not sure). Can the adding of additional (intermediate) points cause this limit to be exceeded?

Regards, Nicolas

ColinPitrat commented 9 years ago

Hello,

if it works with less point, then maybe the limit is lower than 200 points ? Did you try with intermediate values (150 points typically, then 125 if it doesn't work, 175 otherwise etc ...) ?

It would be interesting to see what a big file uploaded with Geonaute-uploader gives. In your example, the file produced has only 63 points instead of the 199 contained in the gpx. Maybe because 199 is too much and the uploader had to apply a logic to reduce it ? If this is the case, it means you need to use ReducePoints with reduce_points_max set to a value lower than 200.

Regards, Colin

Eindhoven562 commented 9 years ago

Hello,

That's interesting! I knew that Geonaute-uploader reduces the number of points, but I thought that it only did so with files containing more than approximately 199 points. I have used the Geonaute-uploader for a big file (1646 points) en it produces a GHR-files that works fine. I will upload both files (renamed to .jpg). Can you please check out how many points this GHR-file contains? That is probably the limit.

I have tried Kalenji-reader some time ago with a lot of files, but I don't remember the exact details any more. As far as I can remember 200, 199, 180, 160 and 150 was too high. 100 was working fine. I will do some more testing to see what the actual limit is.

With regards, Nicolas 1646pointsgpx f8ui3949 ghr

ColinPitrat commented 9 years ago

Hello,

the GHR file contains only 75 points ! For a session of 21.8km it's about a point every 300m in average. Was the guiding precise ? If yes, it interests me much because from my experience, even with 200 points it's hard to obtain a precise guiding with ReducePoints filter. Maybe having a closer look at this example will give me idea to improve the precision.

I don't know how Geonaute-uploader behaves but for ReducePoints, the algorithm is executing multiple passes eliminating more points each time until it reaches a number of points below the maximum. It means that even if the maximum is 200 points and you have more than that, you can end-up with a bit less than 200 because the last pass removed more points than what was strictly needed. If Geonaute-uploader behaves the same way, maybe the max is 100 but the session was reduced of 25 extra points.

Regards, Colin

ColinPitrat commented 9 years ago

I extracted the map corresponding to the two files you sent me. I'll have a closer look but it seems like a good candidate for reducing points massively because there are a lot of straight lines. So despite the low number of points, the guiding can still be precise. We can clearly see the difference between the two paths and yet the guiding is still very precise.

75 points: https://drive.google.com/file/d/0BweL-sTrQlo_dUdHQXdVMUdGSms/view?usp=sharing

1.6k points: https://drive.google.com/file/d/0BweL-sTrQlo_ckZYaDl3N0JYcE0/view?usp=sharing

So basically, I think the max should be put to 100 points (but further testing to confirm it would be nice, if you have a collection of GHR you can send them to me in a zip file) and if the guiding is poor, the ReducePoints algorithm should be improved.

ColinPitrat commented 8 years ago

Hello,

do you confirm everything works well with a limit to 100 points ? Do you see a significant difference in the quality of the guiding between kalenji_reader and Geonaute-uploader ?

Regards, Colin

Eindhoven562 commented 8 years ago

Hello Colin,

Nice to hear from you again!

I have done some testing with a various number of points. It turns out that 119 points is the maximum for reliable guiding with the watch. Problems occure when using more than 119 points (then additional lines appear at the screen).

Guiding with 119 points is pretty good (seems to be as good as the Geonaute-uploader). However, I cannot judge the performance of the kalenji-reader-algorithm (Reducepoints), because I use gpsbabel to reduce the number of point.

With regards, Nicolas

ColinPitrat commented 8 years ago

Perfect, I'll close this issue then. Don't hesitate to open another one if you encounter some issues.

ColinPitrat / kalenji-gps-watch-reader

Support import from computer to watch #40