Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account

TOPIC: Depth Units, problem with unit importing GPX

Depth Units, problem with unit importing GPX 11 years 1 week ago #5900

  • amaye
  • amaye's Avatar
  • Offline
Hello!

I am currently evaluating your tool which is absolutely brilliant. One thing I cannot figure out is how to get track imported with the right unit. I have a set of GPX files which all contains "<depthunits>feet</depthunits>" but the imported tracks/maps generated are using these values as "metres" Its like if the software discards this depthunits field in the gpx file.

Then all my feet depth are displayed as metres...

How can I work around issue, maybe I simply do something wrong?

Thanks,
Arnaud
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 11 years 5 days ago #5906

  • amaye
  • amaye's Avatar
  • Offline
Hello,

Nobody have an answer to that? It is really weird, my GPX have feet information, ie where the water is 9 feet deep, Reefmaster displays 9 metres deep.

I am unable to find a solution. I am only importing GPX files and all the depth information of this GPX files are assumed to be Metres instead of Feet. No conversion or what so ever. Simple what is 9 feet deep is assumed to be 9 metres deep by Reefmaster. If I change global unit to feet, then Reefmaster converts 9 metres to feet and display that..

Please help!!

Thanks,
Arnaud
Last Edit: 11 years 5 days ago by amaye. Reason: typos
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 11 years 5 days ago #5907

  • Matt
  • Matt's Avatar
  • Offline
Hi Amaye,
Sorry for the late reply - I missed this one.
The GPX format itself doesn't have a a standard way of including depths or specifying which units depths are in. Depths are always a proprietary extension provided by whichever entity is producing the file. As such we don't have a standard way of interpreting the files and in your case we are ignoring the units attribute and importing depths as metres.
If you can send us one of your GPX files (This email address is being protected from spambots. You need JavaScript enabled to view it. ) then we can take a look and make the necessary modifications to ReefMaster.
In the mean time, you might be able to convert the depths yourself. One option would be to import them into ReefMaster, then export the track(s) in CSV format. This would give you a CSV files with the wrong depths (approx 3 x too deep). You could then import the CSV file back into RM and set the depths setting to feet, which *should* perform the opposite conversion. Bit of a hack, I know, but it should get your data into RM.

Matt
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 9 years 7 months ago #8457

  • jkibele
  • jkibele's Avatar
  • Offline
I had a very similar problem with GPX files created by Navico's InsightGenesis software. Depth data are provided in feet rather than meters and in the 'depth' tag, rather than the 'ele' (elevation) tag that seems to be standard in most gpx files. I wrote a small Python script to fix the files. I'm not sure, but it may solve your problem as well. Please feel free to make use of it if it helps. You can find the script here: github.com/jkibele/InsightGenesisGPX
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 8 years 11 months ago #9842

  • kvdc
  • kvdc's Avatar
  • Offline
I tried the python script but I get an error when running. I installed the latest python for windows 3.6 Installing the script went fine but I get an error while executing. Also when calling the helpfile I get the same error. Any idees?

C:\Users\kvdc\Downloads>pip install insightgenesisgpx
Collecting insightgenesisgpx
Downloading InsightGenesisGPX-0.1.tar.gz
Installing collected packages: insightgenesisgpx
Running setup.py install for insightgenesisgpx ... done
Successfully installed insightgenesisgpx-0.1

C:\Users\kvdc\Downloads>insightgenesisgpx.py G:\Sonar\RECORD\Patrick\sept trips\HD_HV_VR.gpx G:\Sonar\RECORD\Patrick\sept trips\HD_HV_VR_NEW.gpx
File "C:\Users\kvdc\Downloads\insightgenesisgpx.py", line 7
<!DOCTYPE html>
^
SyntaxError: invalid syntax


C:\Users\kvdc\Downloads>insightgenesisgpx.py -h
File "C:\Users\kvdc\Downloads\insightgenesisgpx.py", line 7
<!DOCTYPE html>
^
SyntaxError: invalid syntax
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 8 years 6 months ago #10127

  • Thepato
  • Thepato's Avatar
  • Offline
Hi. I'm having a similar problem. I lost many of my sonar logs but was able to retrieve the GPX files from Insight Genesis. I now have a mixture of SL2 files and GPX files and all the GPX data is about 3x too deep. From what I can tell there is still no option to import depth in feet. I would love to see an option in Reefmaster where you can choose what units are being imported for each file. Is there an easier solution to this problem since it was last discussed here?
The administrator has disabled public write access.

Depth Units, problem with unit importing GPX 8 years 6 months ago #10128

  • Matt
  • Matt's Avatar
  • Offline
The issue really is that the depths should be stored in metres within the GPX file, but they are not. We could add an option here which would be a bit of a hack but useful I suppose. For now, I suggest following the "round trip" solution described above, which really doesn't take much time. So:

* Import all of your GPX files and export as CSV in metres.
* Re-import the files but tell RM that the values are feet.
* Delete the original (GPX imported) tracks.

Remaining tracks should now have the correct depths.
The administrator has disabled public write access.
SCROLL TO TOP