Convert to .FPL to use on Garmin 430

[oswaldocostaneto]

Hi,

Thanks for the answer.

However, the "standalone" line has no relation to the problem. I was able to check this when I tried to use Flighplan Migrator.

When trying to understand where Routeconverter's compatibility problem comes from with Flightplan Migrator, I found the following:

Code:

<comment>SBBE; Val de Cans</comment>

Flightplan Migrator does not recognize the ";" And the letters without CAPS LOCK.





And also the following:
The code has two equal <waypoints>, which means a flight leaving and returning to an aerodrome.

Code:

      <waypoint>
          <identifier>SBBE</identifier>
          <type>AIRPORT</type>
          <country-code>SB</country-code>
          <lat>-1.3847222</lat>
          <lon>-48.4788889</lon>
          <comment></comment>
      </waypoint>
      <waypoint>
          <identifier>SBBE</identifier>
          <type>AIRPORT</type>
          <country-code>SB</country-code>
          <lat>-1.3847222</lat>
          <lon>-48.4788889</lon>
          <comment></comment>
      </waypoint>

After modifying the <identifier> of the second <waypoint> and removing the <comment>, Flightplan Migrator seamlessly imported the file without errors. The code remained as follows:

Code:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<flight-plan xmlns="http://www8.garmin.com/xmlschemas/FlightPlan/v1">
<created>2017-07-04T13:48:31Z</created>
  <waypoint-table>
      <waypoint>
          <identifier>SBBE</identifier>
          <type>AIRPORT</type>
          <country-code>SB</country-code>
          <lat>-1.3847222</lat>
          <lon>-48.4788889</lon>
          <comment>SBBE</comment>
      </waypoint>
      <waypoint>
          <identifier>WP1</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.55</lat>
          <lon>-48.0</lon>
          <comment>WP1</comment>
      </waypoint>
      <waypoint>
          <identifier>WP2</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.349996</lat>
          <lon>-48.0</lon>
          <comment>WP2</comment>
      </waypoint>
      <waypoint>
          <identifier>WP3</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.349996</lat>
          <lon>-47.96666</lon>
          <comment>WP3</comment>
      </waypoint>
      <waypoint>
          <identifier>WP4</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.55</lat>
          <lon>-47.96666</lon>
          <comment>WP4</comment>
      </waypoint>
      <waypoint>
          <identifier>WP5</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.55</lat>
          <lon>-47.933315</lon>
          <comment>WP5</comment>
      </waypoint>
      <waypoint>
          <identifier>WP6</identifier>
          <type>USER WAYPOINT</type>
          <country-code></country-code>
          <lat>-0.349996</lat>
          <lon>-47.933315</lon>
          <comment>WP6</comment>
      </waypoint>
      <waypoint>
          <identifier>SBBE1</identifier>
          <type>AIRPORT</type>
          <country-code>SB</country-code>
          <lat>-1.3847222</lat>
          <lon>-48.4788889</lon>
          <comment>SBBE</comment>
      </waypoint>
  </waypoint-table>
  <route>
      <route-name>SBBE/SBBE</route-name>
      <route-description>C:\Users\operador\Desktop\ART - PATNAV 1.rpk</route-description>
      <flight-plan-index>1</flight-plan-index>
      <route-point>
          <waypoint-identifier>SBBE</waypoint-identifier>
          <waypoint-type>AIRPORT</waypoint-type>
          <waypoint-country-code>SB</waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP1</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP2</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP3</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP4</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP5</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>WP6</waypoint-identifier>
          <waypoint-type>USER WAYPOINT</waypoint-type>
          <waypoint-country-code></waypoint-country-code>
      </route-point>
      <route-point>
          <waypoint-identifier>SBBE</waypoint-identifier>
          <waypoint-type>AIRPORT</waypoint-type>
          <waypoint-country-code>SB</waypoint-country-code>
      </route-point>
  </route>
</flight-plan>

In short:

I noticed that Flightplan Migrator does not accept the characters:
> Lowercase letters;
> ";" "," And other special characters
> Space between words


So, in order for the ".FPL" file generated by Routeconverter to be accepted by Flightplan Migrator, you must:

> 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




However, having to enter the code to correct those minor details is bad for the purpose of the program, which should make things easier, including because other pilots will use the tool and not everyone has the intimacy with those codes.

Can there be any solution to this case?