Integration with QtVlm - Data files and Import/Export

[cagney]

Originally Posted by sinbad7

maitai..

Sorry to interrupt you guys trying to improve the integration,BUT, using the Routing function,having first selected and downloaded the Grib area,I keep getting the attached message. The grib is set for 8 days and the area marcation covers the indicated route. (Own boat - POI-1)

I have adjusted the length of the route down to a day or two sailing but still the same error message. What am I doing wrong?

Tore

Tore

Please ask these questions in the dedicated qtVlm thread in the Navigation forum. I'm sure Maitai is happy to answer you there.
Show some respect for JesperWe, and his attempt to coordinate programming efforts and integration with qtVlm.
Thank you for your cooperation.

Thomas

[JesperWe]

OK, I have pushed some initial code to https://github.com/JesperWe/OpenCPN/tree/KMLSupport

It only has 40% of the functionality so far but importantly you can Copy a route. (Cursor on route, Context menu > Route > Copy to QtVlm)

Copy to Google Earth will give you a pure KML without the QtVlm <extradata>

Paste of waypoints works too, including merging of <extradata> onto existing waypoints.

Copy waypoint (simple) and paste/merge track/route (lots of work) left to do.

Too bad you will be using QtXml to parse, otherwise you could have taken some of my parser code

[maitai]

Don't worry with QtXml, it will do the job (probably after some contorsions, ok). I'll be on that one next week

[JesperWe]

Here's a question for you: I suppose that when you export your routing, there will be a lot of points that are the calculated intermediate points between the original route's waypoints.

Is it OK that I assume that any points that has <extradata> tags in their description are original route points, and the points between them will have no content in their <description>?

(I need a way to tell the route points and the routing points apart...)

[maitai]

Yes.

In fact there is such a point every "vacation step". In case of a boat-real it is hardcoded to 5mn, I can make that a parameter if needed.

When you have something ready can you send me an XML sample so I can compare with mine and test a bit the iimport? I'll send you my email by PM.

[maitai]

In fact there is a subtle issue:

The route almost never passes exactly on a POI. In fact if a POI is within a vacation step (5mn) it is considered as reached, and we head toward the next one. So the route actually passes very close to the POIs, but not exactly on it. This is because since we work with a step of 5mn, it is almost impossible to be exactly on a POI.

That's the reason why when exporting a route in qtVlm, it asks you whether you want to export the POI list, or the vlmPoint list (the details option).

Maybe best is to send you 2 lists separatly? One would be the POIs list to be imported as WPs but not a track/route, and another one containing the vlmPoints that would be the track? Or I can send you only the vlmPoints, but with a tag indicating in each vlmPoint which are the current coordinates, name, etc of the target POI. A bit like the route's log in route->edit.

When you send me back the route I need just the POI list in fact.

[JesperWe]

I like the second alternative, but with small modification: A tag on every vlmPoint makes the logic more complicated. Can you just put a POI tag on the last vlmPoint before a POI should be reached? (And also one on the very first vlmPoint corresponding to the starting POI)

Then I import the pointlist as a track, and for each point with the POI tag I can check and merge data against the route waypoints.

[maitai]

Oki then.

The first vlmPoint and the first POI (which maybe is not a POI, but the boat), are on the same position exactly. We cannot arrive exactly on a POI, but there is no problem to start exactly from a position.

[JesperWe]

Moving forward fast....



Routes and tracks from QtVlm and Google Earth can be pasted straight into O!
Single waypoints too.
QtVlm settings on the routes are preserved, even if a route is originally created in O, Copied to QtVlm, and then pasted back.

[JesperWe]

Success! Bidirectional copy/paste between O and QtVlm.
The actual weather routing does not make sense to me for now, but I probably need to learn QtVlm better :-).
But the integration works fine! Will be in next beta release.

[maitai]

Yes it's nice, and it copy/paste to GE too

When is the next beta and release of O due?

[JesperWe]

That's Dave's call. We just did one a week or so ago, but it had a high impact bug in Tides&Currents and some other issues, so would I guess we want a new rather sooner than later.

[bdbcat]

All...

Sooner. Maybe 12 August or so.

Dave

[sinbad7]

Great,but what is the difference between exporting/importing between qtVlm and OCPN and the same using copy/paste? In both cases you have to store the .gpx files somewhere.

My examples attached uses a POI in a suitable place on the map to call up the latest page of route properties.

I have done the same for the Android OruxMaps on my Galaxy S II.

Tore

[sinbad7]

Here is another optimized route exported/imported to OruxMaps covering the stretch English Channel to Gibraltar Strait. I have the same for OCPN.

Tore