RouteConverter Forum

Full Version: conversion from .kml to .pln or .flt files
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4
Hi guys, I would need to convert .KML file to .PLN or .FLT file.  Could somebody help?  
Do you have examples of the formats and a file format specification?
(14.03.2021, 21:46)routeconverter Wrote: [ -> ]Do you have examples of the formats and a file format specification?

Hi Christian, yes, I have. I sent you the examples enclosed.  I sent you PM as well. Best, Jaro
Hi @Jaro

RouteConverter has no problems to read your input files.
I fear @Christian requires examples of .pln and .flt files.
(14.03.2021, 21:46)routeconverter Wrote: [ -> ]Do you have examples of the formats and a file format specification?

Hi Christian,

Enclosed I have requested examples of .pln and .fpl files.  I sent you my .kml files - examples in my previous e-mail. Thank you for your support.
(15.03.2021, 07:12)kumo Wrote: [ -> ]Hi @Jaro

RouteConverter has no problems to read your input files.
I fear @Christian requires examples of .pln and .flt files.

Hi kumo, I just sent the examples of .pln and .flt files to Christian. Best, Jaro
Hi @Jaro,

your BARBADOS.FLT can be opened with a text editor. It is clear text but many variables like aircarft and engine parameters, velocities along aircraft axis and many other things are not related to the main purpose of RouteConverter: To work with tracks and routes

Coordinate informations are just departure, destination and pre-planned waypoints:
Code:
[ATC_ActiveFlightPlan.0]
title=Grantley Adams Intl to Punta Cana Intl
description=Grantley Adams Intl to Punta Cana Intl
type=VFR
routetype=0
cruising_altitude=8500
departure_id=TBPB, N13° 4.48', W59° 29.53', +000164.50
departure_position=
destination_id=MDPC, N18° 34.25', W68° 21.97', +000040.75
departure_name=Grantley Adams Intl
destination_name=Punta Cana Intl
waypoint.0=, TBPB, , TBPB, A, N13° 4.48', W59° 29.53', +000164.50, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.1=, , , TIMECRUIS, U, N15° 18.73', W62° 58.71', +008500.00, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.2=, , , TIMEDSCNT, U, N16° 24.65', W64° 44.93', +008500.00, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.3=, MDPC, , MDPC, A, N18° 34.25', W68° 21.97', +000050.00, , , , , , NONE, 0, 0, -1, 0, 0, +

Your file TBPBMDPC_MFS_16Mar21.pln can be opened with a text editor as well.
This file contains more coordinates. Departure airport, Intersections/ATC waypoints, destination airport:
Code:
<DepartureID>TBPB</DepartureID>
        <DepartureLLA>N13° 4' 29.00",W59° 29' 32.00",+000169.00</DepartureLLA>
        <DestinationID>MDPC</DestinationID>
        <DestinationLLA>N18° 34' 14.81",W68° 21' 58.27",+000047.00</DestinationLLA>
        <Descr>TBPB to MDPC created by SimBrief</Descr>
        <DepartureName>Grantley Adams Intl</DepartureName>
        <DestinationName>Punta Cana Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="TBPB">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N13° 4' 29.00",W59° 29' 32.00",+000169.00</WorldPosition>
            <RunwayNumberFP>9</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>TBPB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ETBIG">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N13° 19' 35.00",W60° 3' 3.00",+023900.00</WorldPosition>
            <ICAO>
                <ICAORegion>TT</ICAORegion>
                <ICAOIdent>ETBIG</ICAOIdent>

A big plus: Plain text. So there is a chance to extract coordinates from your files.
BUT you requested to convert a *.kml file into .flt and/or *.pln formats.

Let's see what @Christian thinks about this...
(17.03.2021, 09:54)kumo Wrote: [ -> ]Hi @Jaro,

your BARBADOS.FLT can be opened with a text editor. It is clear text but many variables like aircarft and engine parameters, velocities along aircraft axis and many other things are not related to the main purpose of RouteConverter: To work with tracks and routes

Coordinate informations are just departure, destination and pre-planned waypoints:
Code:
[ATC_ActiveFlightPlan.0]
title=Grantley Adams Intl to Punta Cana Intl
description=Grantley Adams Intl to Punta Cana Intl
type=VFR
routetype=0
cruising_altitude=8500
departure_id=TBPB, N13° 4.48', W59° 29.53', +000164.50
departure_position=
destination_id=MDPC, N18° 34.25', W68° 21.97', +000040.75
departure_name=Grantley Adams Intl
destination_name=Punta Cana Intl
waypoint.0=, TBPB, , TBPB, A, N13° 4.48', W59° 29.53', +000164.50, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.1=, , , TIMECRUIS, U, N15° 18.73', W62° 58.71', +008500.00, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.2=, , , TIMEDSCNT, U, N16° 24.65', W64° 44.93', +008500.00, , , , , , NONE, 0, 0, -1, 0, 0, +
waypoint.3=, MDPC, , MDPC, A, N18° 34.25', W68° 21.97', +000050.00, , , , , , NONE, 0, 0, -1, 0, 0, +

Your file TBPBMDPC_MFS_16Mar21.pln can be opened with a text editor as well.
This file contains more coordinates. Departure airport, Intersections/ATC waypoints, destination airport:
Code:
<DepartureID>TBPB</DepartureID>
        <DepartureLLA>N13° 4' 29.00",W59° 29' 32.00",+000169.00</DepartureLLA>
        <DestinationID>MDPC</DestinationID>
        <DestinationLLA>N18° 34' 14.81",W68° 21' 58.27",+000047.00</DestinationLLA>
        <Descr>TBPB to MDPC created by SimBrief</Descr>
        <DepartureName>Grantley Adams Intl</DepartureName>
        <DestinationName>Punta Cana Intl</DestinationName>
        <AppVersion>
            <AppVersionMajor>11</AppVersionMajor>
            <AppVersionBuild>282174</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="TBPB">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N13° 4' 29.00",W59° 29' 32.00",+000169.00</WorldPosition>
            <RunwayNumberFP>9</RunwayNumberFP>
            <ICAO>
                <ICAOIdent>TBPB</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="ETBIG">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N13° 19' 35.00",W60° 3' 3.00",+023900.00</WorldPosition>
            <ICAO>
                <ICAORegion>TT</ICAORegion>
                <ICAOIdent>ETBIG</ICAOIdent>

A big plus: Plain text. So there is a chance to extract coordinates from your files.
BUT you requested to convert a *.kml file into .flt and/or *.pln formats.

Let's see what @Christian thinks about this...

Thank you Matthias for your information. For my purpose I don´t need to add any aircraft data just GPS data, so the best solution, if it is possible is to convert .kml to .pln it means as a flight plan . The file .flt is a special format generated directly from MSFS 2020, if you want to save your flight in MSFS and reload it later again.  File.PLN is mostly used as a flight plan - you import it to MSFS and you flight according to the plan.  Please share this information with Christian, if it is possible. Thank you. Best, Jaro
Hi Jaro,

I've got two questions
(17.03.2021, 13:48)routeconverter Wrote: [ -> ]Hi Jaro,

I've got two questions

Hi Christian, 

Regarding my .kml file expample,  GPS positions are generated by logger on the aircraft. Regarding .pln files, yes you are right  about the link you sent. It is .pln file uploaded from external sources to MSFS2020. It´s as a flight plan. I did not tried to minimize .kml files and I don´t know max size of the file could be imported to MSFS2020. I expected all .pln files could be imported, but I don´t know how to convert it. Thank you Christian for your help.  Jaro
Pages: 1 2 3 4