26.07.2017, 20:23
Quote: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>
Quote: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!
