Convert to .FPL to use on Garmin 430

[oswaldocostaneto]

Not yet. But if there is demand - and a donation: let's start.

Okay, I just did my part. I do not know what the final donation number you need, but I just made one of this.

[routeconverter]

Okay, I just did my part. I do not know what the final donation number you need, but I just made one of this.

Well, something that is reasonable for a couple of leisure time hours and given the amount of time you're saving.

I'll try to provide a prerelease of RouteConverter that enforces the rules you have given:

> There are no two or more waypoints with equal <identifier>
> In the <identifier> and <comments> fields there should only be letters (in the upper case) and numbers, with no spaces or special characters
> In the <route-name> field same thing as the previous item

When there is such a prerelease I need your help to test it.

[oswaldocostaneto]

wonder!

Then add to the rules the following topic that I just received by email from Garmin staff:

> Flightplan Migrator only accepts <waypoints> with no more than 5 characters (respecting previous rules)


I also ask if I can put Routeconverter to work on a computer in my work for my use, after all this one I'm using and testing the files are in the notebook and I would like to put it on another computer that is not a personal one, so that I can export files .FPL without limits. How to login? Would i need internet whenever i want to use it? Sometimes we need to change routes in flight (we do search and rescue missions) and up there it is difficult to have internet ...

I'll be waiting for the pre-launch to test. I believe that other people who also need the same tool as I will in the future manifest themselves.

[routeconverter]

Then add to the rules the following topic that I just received by email from Garmin staff:

> Flightplan Migrator only accepts <waypoints> with no more than 5 characters (respecting previous rules)

What exactly does than mean? That the <identifier> of <waypoints> is limited to 5 characters?

Is <comment> limited?

I also ask if I can put Routeconverter to work on a computer in my work for my use, after all this one I'm using and testing the files are in the notebook and I would like to put it on another computer that is not a personal one, so that I can export files .FPL without limits. How to login?

Use the same login that you've used for the error report.

Would i need internet whenever i want to use it? Sometimes we need to change routes in flight (we do search and rescue missions) and up there it is difficult to have internet ...

No, you don't Internet. At least not for the conversion. Better double check if it works for you.

I'll be waiting for the pre-launch to test. I believe that other people who also need the same tool as I will in the future manifest themselves.

I've just uploaded a new prerelease. Does it create valid files for the Flightplan Migrator?

What I found during testing is that this rule

> In the <identifier> and <comments> fields there should only be letters (in the upper case) and numbers, with no spaces or special characters

forces the user to change every waypoint. This is tedious.

Please check if any of the rules could be relaxed. Because if not, the completion dialog should make better suggestions. What do you think?

[oswaldocostaneto]

What exactly does than mean? That the <identifier> of <waypoints> is limited to 5 characters?

yes.

Is <comment> limited?

Yesterday I did a test with a file generated by Routeconverter in flight. I did not succeed. The Garmin 430 could not understand some information from the <waypoint>, so I went back to the codes to see what might be different from a .FPL that worked. I noticed that in the .FPL files that were successful, the <comment> field is EMPTY. thus:
<Comment> </ comment>

I realized that Routeconverter did not allow me to create waypoints without the <comment> field, because when I deleted the information, it was automatically generated "User, Waypoint". So this can be a path. Remove the <comment>


I also noticed that the <waypoints> described as Airport have <elevation> information in the .FPL files that were successful when used in Garmin. On the contrary, the file that tested .FPL generated by Routeconverter does not have this information in the codes. I do not know if this is a required item, though that's what I realized.

I've just uploaded a new prerelease

Sorry about this question, but, how can i download this prerelease ?

[routeconverter]

I realized that Routeconverter did not allow me to create waypoints without the <comment> field, because when I deleted the information, it was automatically generated "User, Waypoint".

You're talking about the <type> field, or?

So this can be a path. Remove the <comment>[/font][/size][/color]

Unconditionally?

I also noticed that the <waypoints> described as Airport have <elevation> information in the .FPL files that were successful when used in Garmin. On the contrary, the file that tested .FPL generated by Routeconverter does not have this information in the codes.

RouteConverter does write <elevation> information if there is any.

Sorry about this question, but, how can i download this prerelease ?

Go to the homepage, go to downloads, go to prerelease

[oswaldocostaneto]

You're talking about the <type> field, or?

No, I'm talking about the <comment> field. Leaving as in this code (it is a 100% accepted code by Garmin)

Code:

   <waypoint>
     <identifier>SBBE</identifier>
     <type>AIRPORT</type>
     <country-code>SB</country-code>
     <lat>-1.384722</lat>
     <lon>-48.4788889</lon>
     <comment></comment>
     <elevation>17.0688</elevation>
   </waypoint>
   <waypoint>
     <identifier>WP1</identifier>
     <type>USER WAYPOINT</type>
     <country-code></country-code>
     <lat>-0.230333</lat>
     <lon>-47.1385000</lon>
     <comment></comment>
   </waypoint>

Unconditionally?

Yes, after all, the <comment> field does not add anything to the air navigation.



I think it's not too complicated to make everything work properly.

Even the <identifier> field could be automatically renamed to the Garmin accepted standard. Maybe it could put for when exporting into .FPL to transform the points into

WPT1
WPT2
WPT3
WPT4

This would prevent the user from wasting time in renaming point to point, but doing so only at the points where he really wanted to rename.

I say this because I work with search and rescue flights and any time spent or lost with planning is time that the survivor is still missing. For us time is not money, time is life!

[routeconverter]

[color=#212121][size=medium][font=arial, sans-serif][color=#212121][size=medium][font=arial, sans-serif][color=#212121][size=medium][font=arial, sans-serif]I think it's not too complicated to make everything work properly.

Did you test with the prerelease? If not please to so since I've tried to implement the rules you stated here.

Even the <identifier> field could be automatically renamed to the Garmin accepted standard. Maybe it could put for when exporting into .FPL to transform the points into

WPT1
WPT2
WPT3
WPT4

This would prevent the user from wasting time in renaming point to point, but doing so only at the points where he really wanted to rename.

So you're proposing to have that pattern as a preset for the dialog?

[oswaldocostaneto]

---

Did you test with the prerelease?

Yes, it is tested and approved! worked perfectly. Follow photos of the inserted search route









However, I still have to edit point by point, because the software that generates the .GPX file delivers all waypoints with the <identifier> and <comment> fields as follows: "Position 1"; "Position 2"; "Position 3", etc.

This ends up spending a lot of time having to edit all waypoints. In an ascending square type search and rescue flight, there are more than 40 points in a route, having to rename them all to the "WPT1" format; "WPT2"; "WPT3". Both in the <identifier> field and in the <comment> field.

So you're proposing to have that pattern as a preset for the dialog?

Yes, this would definitely save a lot of time! Is it possible for you to do this?

[routeconverter]

However, I still have to edit point by point, because the software that generates the .GPX file delivers all waypoints with the <identifier> and <comment> fields as follows: "Position 1"; "Position 2"; "Position 3", etc.

This ends up spending a lot of time having to edit all waypoints. In an ascending square type search and rescue flight, there are more than 40 points in a route, having to rename them all to the "WPT1" format; "WPT2"; "WPT3". Both in the <identifier> field and in the <comment> field.

So you're proposing to have that pattern as a preset for the dialog?

Yes, this would definitely save a lot of time! Is it possible for you to do this?

Of course, let's optimize this.

So the pattern would be WPTx for <identifier>? Does it have to be WPTx?
And why not WPT01, WPT02, WPT03?


Regarding <comment> there is software out there like AirNavPro that fills the GPX <description> with reasonable values that I've matched to FPL <comment>. Which software are you using?