Route Importing Troubles

[zooitje]

I try to import a GPX route from predictwind to openCPN. After many, many failed attempts I was able to do it right once:
https://i.imgur.com/QYqRbKt.png

But for some reason I'm no longer able to do it again, and unable to figure out how it can be done. I keep ending up with this:
https://i.imgur.com/4BWN7Zs.png

What am I missing here?

[nohal]

Nobody can tell you without seeing the GPX file in question.

[zooitje]

Thank you for this response. This is an example of the GPX file. https://www.cruisersforum.com/forums...1&d=1675768655

The strange thing is, in OpenCPN the lat/lon is rounded off:

It is probably some setting but running over all corners of OpenCPN I'm at a loss here. Thanks again.

[nohal]

It is not strange at all, the "GPX" is malformed. It uses comma instead of a dot as decimal separator. You can either try to somehow convince Predictwind to produce correct GPX or fix it in a text editor before import.

[zooitje]

Thank you for this! It now works. I found the solution just before I found your response. I'm not sure if I'm the right person to convince predictwind of anything :-)

thanks again!

Opening the xml (GPX) file and find-replacing all comma's with dots solved it.
Now the coordinates are understood by OpenCPN. No wonder this is not mentioned anywhere. It is a weird functionality of predictwind combined with the lack of warnings in OpenCPN.

Glad it works now. I'm posting this here if someone has the same trouble in the future.

Thanks for the help all!

PS: I see this thread was posted multiple times accidentally. To the mods: these double entries can be removed.

[Pete7]

Originally Posted by zooitje

PS: I see this thread was posted multiple times accidentally. To the mods: these double entries can be removed.

That "Submit" button is quite dangerous isn't it

Don't worry, instead of reading a newspaper over lunch, I will tidy it up and remove the duplicates.

Pete

[zooitje]

I'm so sorry. I heard there's nothing new in the paper today except the date. So you should be good ;-)

PS: I reposted because I was confused my message was no longer to be found in my profile for some time and the link showed "not found" and no longer the post. I figured I did something wrong, but later a mod messaged me he was able to repost my old posts. He posted them all, not one.....
Thank you for your patience and help.

[Be Free]

Check your locale settings on your computer and on Predictwind. It sounds like one is using "," as the decimal indicator and the other is using ".".

[nohal]

Numbers in XML are locale agnostic, always use a period as decimal separator (See XML Schema 1.0 xsd:decimal - Complete documentation and samples on which https://www.topografix.com/GPX/1/1/#type_latitudeType is based). Yes, the bug in Predictwind is likely caused by it using locale while formatting numbers, which should be fixed.

[zooitje]

Nice! Great to see here what the bug actually is and what exactly causes it.

By now I already taught my wife to open the XML file and find-replace to get to decimals. So by now I hope predictwind doesn't change a thing anymore, so I don't need to unlearn stuff. HaHa :-D

Thanks all!

[Be Free]

No disagreement re: the standard, but if Predictwind is changing its behavior based on locale settings it may be an easier workaround to tell it to use a locale that uses "." than it is to wait for them to fix their incorrect implementation.