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':./kalenjireader -D GPX -i myTrack.gpx -f FixElevation,ReducePoints,ComputeSessionStats -o Kalenji There's even an helper script in svn repository: scripts/kalenjiexport.sh. Additionally, there's some explanation in the FAQ on how to create a GPX file from GoogleMap: ateGPXfilestouploadtomywatch? Tell me if you have an issue, or if anything is missing. Regards, Colin Original comment by [email protected] on 15 Sep 2014 at 7:09. Changed state: Invalid.
Added labels: Type-Enhancement. Removed labels: Type-Defect.
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':./kalenjireader -D GPX -i myTrack.gpx -f FixElevation,ReducePoints,ComputeSessionStats -o Kalenji There's even an helper script in svn repository: scripts/kalenjiexport.sh. Additionally, there's some explanation in the FAQ on how to create a GPX file from GoogleMap: ateGPXfilestouploadtomywatch? Tell me if you have an issue, or if anything is missing. Regards, Colin Original comment by [email protected] on 15 Sep 2014 at 7:09. Changed state: Invalid.
Added labels: Type-Enhancement. Removed labels: Type-Defect. Hi, I didn't noticed you've already developped it! I've just tried but it didn't work: D: GPSkalenji-gps-watch-reader-4.9.1win kalenji-gps-watch-reader kalenjireade r.exe -D GPX -i Touretangviry.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: Original comment by [email protected] on 16 Sep 2014 at 5:38. Hi, I didn't noticed you've already developped it! I've just tried but it didn't work: D: GPSkalenji-gps-watch-reader-4.9.1win kalenji-gps-watch-reader kalenjireade r.exe -D GPX -i Touretangviry.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: Original comment by [email protected] on 16 Sep 2014 at 5:38. 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 [email protected] on 16 Sep 2014 at 6:39.
Changed state: Accepted. 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 [email protected] on 16 Sep 2014 at 6:39. Changed state: Accepted.
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 (Touretangviry). 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 [email protected] on 23 Sep 2014 at 8:06.
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 (Touretangviry). 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 [email protected] on 23 Sep 2014 at 8:06.
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: kalenjireader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -i Touretangviry.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 [email protected] on 24 Sep 2014 at 9:14. Changed state: Started.
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: kalenjireader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -i Touretangviry.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 [email protected] on 24 Sep 2014 at 9:14. Changed state: Started.
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: kalenjireader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p E: -i 11111.gpx (assuming 11111.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 [email protected] on 9 Dec 2014 at 8:03. Changed state: Accepted Attachments:. 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: kalenjireader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p E: -i 11111.gpx (assuming 11111.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 [email protected] on 9 Dec 2014 at 8:03. Changed state: Accepted Attachments:. Hello, Perhaps I can be of any assistence. I have tested this file kalenjireader 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 kalenjireader. I renamed this file to 12345.gpx. Then I tried to upload this file to the watch, using the following command: kalenjiuploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G: -i 12345.gpx (I renamed kalenjireader to kalenjiuploader. 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 12345.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 [email protected] on 8 Mar 2015 at 9:34. Hello, Perhaps I can be of any assistence. I have tested this file kalenjireader 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 kalenjireader. I renamed this file to 12345.gpx. Then I tried to upload this file to the watch, using the following command: kalenjiuploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G: -i 12345.gpx (I renamed kalenjireader to kalenjiuploader. 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 12345.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 [email protected] on 8 Mar 2015 at 9:34. 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: 12345 is working fine. Longer or shorter causes problems. 12345 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. 12345.gpx and 1234.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 [email protected] on 9 Mar 2015 at 10:52. 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: 12345 is working fine.
Longer or shorter causes problems. 12345 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. 12345.gpx and 1234.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 [email protected] on 9 Mar 2015 at 10:52. Hello, that's a lot of info:-) So if I sum up: - you had an issue importing a GPX file created by kalenjireader. 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 kalenjireader 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 [email protected] on 9 Mar 2015 at 3:38. Hello, that's a lot of info:-) So if I sum up: - you had an issue importing a GPX file created by kalenjireader. 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 kalenjireader 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 [email protected] on 9 Mar 2015 at 3:38. 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 kalenjireader. 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 kalenjireader is 20157.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 kalenjireader 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 20157.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: kalenjiuploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G: -i 12345.gpx I renamed kalenjireader to kalenjiuploader. 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 20157.gpx and noticed that the following was in the: No name 2015-03-05T15:56:57Z I changed that to: -03-05T15:56:57Z I run the test again (exactly the same way) with the changed file. I did not change the filename.
So filename remains 20157.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 12345. information on the watch. preview screen: 12345 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 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 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 is 15 characters long. Regards, Nicolas Original comment by [email protected] on 9 Mar 2015 at 5:56 Attachments:. 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 kalenjireader. 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 kalenjireader is 20157.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 kalenjireader 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 20157.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: kalenjiuploader -D GPX -f ReducePoints,ComputeSessionStats -o OnMove710 -p G: -i 12345.gpx I renamed kalenjireader to kalenjiuploader. 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 20157.gpx and noticed that the following was in the: No name 2015-03-05T15:56:57Z I changed that to: -03-05T15:56:57Z I run the test again (exactly the same way) with the changed file. I did not change the filename. So filename remains 20157.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 12345. information on the watch. preview screen: 12345 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 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 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 is 15 characters long. Regards, Nicolas Original comment by [email protected] on 9 Mar 2015 at 5:56 Attachments:. Hello, here is a new version of kalenjireader.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 kalenjireader.exe fixes this issue, I'll redeliver a new version in Download section. Regards, Colin Original comment by [email protected] on 10 Mar 2015 at 4:04 Attachments:. Hello, here is a new version of kalenjireader.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 kalenjireader.exe fixes this issue, I'll redeliver a new version in Download section. Regards, Colin Original comment by [email protected] on 10 Mar 2015 at 4:04 Attachments:. 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 kalenjiimport doesn't exist and I couldn't create it So I created the directory c: tmp kalenjiimport manually and then the programme works fine. The programme doesn't seem to use this directory however? If name is emtpy, like, then kalenjireader gives following error: error basicstring::Sconstruct 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 [email protected] on 10 Mar 2015 at 7:40.
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 kalenjiimport doesn't exist and I couldn't create it So I created the directory c: tmp kalenjiimport manually and then the programme works fine. The programme doesn't seem to use this directory however?
If name is emtpy, like, then kalenjireader gives following error: error basicstring::Sconstruct 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 [email protected] on 10 Mar 2015 at 7:40. 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 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: truncationerror.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.
Best Free Driver Updater
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.
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 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: truncationerror.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.
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. 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.
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. 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. 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.
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. 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.
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. 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. 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. 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.
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. Hello, having a look at the files, the one produced by kalenjireader 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 kalenjireader, but there are additional points in the one of kalenjireader.
The additional points in the output of kalenjireader 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 kalenjireader. 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. Hello, having a look at the files, the one produced by kalenjireader 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 kalenjireader, but there are additional points in the one of kalenjireader.
The additional points in the output of kalenjireader 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 kalenjireader. 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. 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. 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. 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 reducepointsmax set to a value lower than 200. Regards, Colin. 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 reducepointsmax set to a value lower than 200.
Regards, Colin. 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).
And for the most vengaboys shalala lala mp3 free, it is here commercial. Up in most alerts, it cannot award for refusing down geometrical sensor notes, Visiting. Vengaboys shalala lala mp3 song free download. Shalala Lala MP3 Song by Vengaboys from the album Greatest Hits. Download Shalala Lala song on Gaana.com and listen offline.
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. 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. 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. 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. 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: 1.6k points: 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. 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: 1.6k points: 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.
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. 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.
The Decathlon Coach app is a sports app that enables you to measure all your sports, monitor your progress session by session, and find your running training plan and power walking training plan, tailored to your goals:starting or returning to running and walking, losing weight and keeping fit, preparing for a race. Using the Decathlon Coach sports app you can connect your cardio belt to display data from your cardio belt. Decathlon Coach also offers the option of sharing your session AND comparing yourself to your friends and family using the friends ranking.
PyKMaze Abstract Geonaute Keymaze 500/700 GPS watch devices are shipped with a Windows-only application software. Pykmaze alleviates this issue and allows to transfer data from/to the device with any host. Features Pykmaze is a pure Python command-line application that does not offer a graphical interface as the original application software does, but nevertheless allows to download recorded tracks and upload waypoints. Its produces and reads Google Earth.KML file, so that tracks and waypoints may be observed and edited with the Google Earth application.
Important notice The Keymaze 500/700 protocol has been reverse-engineered from scratch. Pykmaze code is not based on published information and may fail to comply with the communication protocol the Keymaze device expects. Use it at your own risk. Supported devices Although it seems that Keymaze 500 and 700 share the same communication protocol, no test has been run with Keymaze 700 GPS devices yet. It seems that the Geonaute device is a rebranded GlobalSat GH-615B device, so pykmaze might also be able to communicate with these devices. Pykmaze is not compatible with earlier devices such as Keymaze 300 that may use a different communication protocol. Check out the project if you're looking for Keymaze 300 device support.
Both projects are fully unrelated. For now, pykmaze has been successfully run on an Intel Mac OS X Snow Leopard 64-bit host. It should run fine on any Linux host.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |