Hey Topper ! Really good project !
Just a little thing, about the waypoint file: I think to replace "TURNING_POINT" by "WAY" or "PT". And by extension, "VOR", "BSE", "PAD" and finally "LOOP"
I think too to an "Orbiter-like" parameters syntax; so my version of the waypoint file would be like this :
Code:
# This is an waypoint example route for cape canaveral.
# The following options are possible for waypoints:
#
# for type "WAY":
# WAY: latitude longitude:size[ NAME]
#
# Name is optional, id+1 of the waypoint will be shown in MFD if name is not set here
#
# for type "LOOP":
# LOOP: latitude longitude size:ID_Loop_start[ NAME]
#
# Name is optional, the ID_Loop_start is the id of the waypoint to return to.
#
# id's would be genereated in the order they are written in this file.
# First waypoint id is 0
# for type "PAD":
# PAD: Base:PAD size[ NAME]
#
# for type "BSE":
# BSE: Base size[ NAME]
#
# Point will be centered in the center of the base.
#
# for type "RWY":
# RWY: Base:RWY_ID EndID size[ NAME]
#
# RWY_ID is the runway number (listed stating 0 and in order they are written in the base config)
# EndID is the end number (listed with END1 and END2)
#
WAY: 28.597 -80.682 500 Test0123
WAY: 28.632 -80.706 500 Test0124
WAY: 28.627 -80.620 500 Test0125
BSE: Cape Canaveral 500 Test0126
PAD: Cape Canaveral:1 500 Test0127
RWY: Cape Canaveral:1 2 500 Test0128
LOOP:28.585 -80.651:1 500 Test0129
Just a suggestion.
So far ok, but i prefere to call it POINT.
For a PAD i don't need to have the coordinates in the file, because i get them over the API. So i think, just base name and PAD - ID shoud be enogh.
How ever, i've thinked about to use a xml syntax, what do you think about this?:
Code:
<ROUTE>
<POINTS>
<ID=1>28.597, -80.682</ID>
<ID=2>2,28.632, -80.706</ID>
<ID=3>3,28.627, -80.620</ID>
</POINTS>
<WAY>
<TAKEOFF_POINT>
<END1> 1
<END2> 2
<DESC> Take off </DESC>
</TAKEOFF_POINT>
<TURNING_POINT>
<ALT> 500 </ALT>
<SPEED> 300 </SPEED>
<DESC> Turn around here </DESC>
</TURNING_POINT>
<VERTICAL_LANDING_POINT>
<BASE> Cape Canaveral </BASE>
<PAD_ID> 3 </PAD_ID>
</ID>
</WAY>
</ROUTE>
Maybe, it would be also be possible in a future version to parse kml- files....
Here is an example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2" xmlns:gx="http://www.google.com/kml/ext/2.2" xmlns:kml="http://www.opengis.net/kml/2.2" xmlns:atom="http://www.w3.org/2005/Atom">
<Document>
<name>Pfad ohne Namen.kml</name>
<Style id="s_ylw-pushpin_hl">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
</Style>
<Style id="s_ylw-pushpin">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
</Style>
<StyleMap id="m_ylw-pushpin">
<Pair>
<key>normal</key>
<styleUrl>#s_ylw-pushpin</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#s_ylw-pushpin_hl</styleUrl>
</Pair>
</StyleMap>
<Placemark>
<name>Pfad ohne Namen</name>
<styleUrl>#m_ylw-pushpin</styleUrl>
<LineString>
<tessellate>1</tessellate>
<coordinates>
-80.68293401534778,28.59767009415995,0
-80.70617220949629,28.63219633933067,0
-80.6209119036223,28.62760682133923,0
-80.60476529545372,28.60806496816723,0
-80.65128676992974,28.58546036272783,0
</coordinates>
</LineString>
</Placemark>
</Document>
</kml>
Does we can just add keys like speed, alt and kind of these points to the kml?
And does this is allowed? ( I don't know about licenses from google etc...)
[EDIT]
Oh I just read that [ame="http://en.wikipedia.org/wiki/GPS_eXchange_Format"]GPX - Format[/ame] is free and supports routes, tracks and waypoints
I think this is what i need...
(source: wikipedia)
Oh and speed and altitude is also optional...
look here:
"http://www.topografix.com/gpx_manual.asp]"
<speed>
Optional in: <wpt> <rtept> <trkpt>
Units: meters per second
<speed>4.23</speed>
Instantaneous speed at the point.
...
<ele>
Optional in: <wpt> <rtept> <trkpt>
Units: meters
<ele>1206.2</ele>
Elevation in meters of the point.
