Navionics Boating App - Importing Line, Tracks, Route Help

I can import the waypoint files into Navionics Boating App, but I can't import any line, track, or route file into the app.
I get an error message stating, "The file is corrupted or invalid." The file works for my Lowrance Fish Finder and other applications but can't import to Navionics.

I have been trying to import the 50 Fathom RCA line to Navionics without success.  I was able to import the file into Google Earth & Lowrance FF.
 

Any suggestions?

Paul

I bet I can help, but I don't have the Navionics app.  What I do know is there is a awesome file converter out there that can take one data format and convert to another very easily.  So when working with my lowrance I found it easiest to import GPX format, but I had lots of other formats.  Easily able to convert them as needed to a format that worked.  The utility is here: https://www.gpsbabel.org/. but you will have to figure out what to try as what I can try and help though if you get stuck.

I learned about this with a desire to be able to copy my GPS data between FF's and have one master database.  What I came up with is a Raspbery PI that when you insert a USB with your SDHC card on it it backs it up, merges the data with the existing database and spits out a new file to import on my FF.  So then I just import it back in to both FF's and have both sets of data, and a backup of all of it.

Thank you for your assistance.

I am familiar with file conversion and have been doing that for several years.
I use https://www.gpsvisualizer.com/ to convert files to GPX format per Navionic's requirement.
IT WORKS FINE when I do it for point/waypoint files, but not for line/track files.
This YouTube video explains the issue: https://youtu.be/OotuLHvwBCc?si=E1RjDj-DR6WsglbH

Paul

So it looks to me like there is just missing GPX headers that the software is expecting and calls it corrupted if not found.  I'm pretty sure if I had both data formats I could figure it out easily and create a python script to fix any data file for you, or you could probably fix them manually too.

So it looks to me like there is just missing GPX headers that the software is expecting and calls it corrupted if not found.  I'm pretty sure if I had both data formats I could figure it out easily and create a python script to fix any data file for you, or you could probably fix them manually too.

I think you understand the issue fully understood.
I will email several samples of both file formats.

Paul

Using AI quickly able to see it's just a field conversion issue.  ChatGPT helped me create a converter and a test file worked for Paul when I sent it to him.  Finished the conversion program and he should be able to import it.  If anyone else with Navionics would like a copy just send me a DM

I didn't think ChatGPT would know this type of nuances. It's scary to think this type of knowledge exists in a non-human being. I don't have a need for the program yet, but if I do, I know who to ask. Is it a python script?

Also, it seems Navionics should fix their problem, especially when they had just up'd their annual subscription to 50 bucks.

I didn't think ChatGPT would know this type of nuances. It's scary to think this type of knowledge exists in a non-human being. I don't have a need for the program yet, but if I do, I know who to ask. Is it a python script?

I'm not an expert in AI or anything, but if using it for things like parsing data is so super easy it's ridiculous.  So I gave sample data to ChatGPT of each file format and just asked it to tell me what the difference was and it was able to parse and compare the data given in seconds.

This is the "good" format, that Navionics likes:

<?xml version="" encoding="">
<gpx xmlns="" version="" creator="">
    <metadata>
        <link href="" />
    </metadata>
    <rte>
        <name></name>
        <time></time>
        <rtept lat="" lon="" />
        <rtept lat="" lon="" />
    </rte>
</gpx>



And this is what the format is from the exported data of the 50FA RCA Lines:

<?xml version="" encoding="" standalone="">
<gpx version="" creator="" xmlns="" xmlns:xsi="" xsi:schemaLocation="">
    <trk>
        <name></name>
        <desc></desc>
        <trkseg>
            <trkpt lat="" lon=""></trkpt>
            <trkpt lat="" lon=""></trkpt>
            <trkpt lat="" lon=""></trkpt>
        </trkseg>
    </trk>
</gpx>

Same structure of the format, but using trks instead of routes.  So making a converter was super easy after seeing the commonality in structure.  I just asked ChatGPT to figure out how to convert it, and it did it in the first try, but it made some mistakes that had to be fixed.

I am reviving an old topic now since we have to be outside the 50 ftm or within the 20 ftm line for the upcoming rockfish season.
Was anyone successful in importing these lines into the Navionics Boating App?
If yes how?
Thanks!

Yep, we have the new 20fa line and 50fa line tracks with mlpa zones.  I don't actually have Navionics, but I believe Paul does and probably has the process down to import them.

I am reviving an old topic now since we have to be outside the 50 ftm or within the 20 ftm line for the upcoming rockfish season.
Was anyone successful in importing these lines into the Navionics Boating App?
If yes how?
Thanks!

I have 50fa w MLPA converted to Navionics App file format by AlsHobieOutback. The 20fa file is in general GPX file format and cannot be imported directly into the Navionics App, but you should be able to import it into your fish finder.

You will see all the downloadable GPX files on this website: https://paul95255.wixsite.com/non-motorized-vessel

Paul

Thank you Paul and AlsHobieOutback !

Also, it seems Navionics should fix their problem, especially when they had just up'd their annual subscription to 50 bucks.

ouch, I haven't purchased the app yet (hate subscriptions) almost had myself over the hump on $25...but I won't pay $50 for a different presentation of data provided free by the government.

it would be cool to add the line as Paul is doing though, good for situational awareness.

Also, it seems Navionics should fix their problem, especially when they had just up'd their annual subscription to 50 bucks.

ouch, I haven't purchased the app yet (hate subscriptions) almost had myself over the hump on $25...but I won't pay $50 for a different presentation of data provided free by the government.

it would be cool to add the line as Paul is doing though, good for situational awareness.

I have enjoyed using their Relief Shading overlay option for the last two years, but I don't think it is worth $50 per year.
I plan not to renew my subscription when it expires in July 2024.

Paul