From: <ro...@ru...> - 2009-01-28 13:17:54
|
Martin, I completely agree with you. But, and a big but, it is getting very difficult to actually get the AIP data into openair and provide a reasonable equivalent to a map, which, lets face it many of us use it as. As a result I am begining to consider openair not fit for purpose. So, I am left with the following: 1) expand openair 2) write a loader for other formats 3) do nothing 2 requires a bit of work but is possible. However AFAICS the free ones have similar limitations but in different areas. The only ones that don't have this problem are the commercial ones like jeppersen but they cost and the format is propriatory. Don't think 3 is supportable. This is all a side effect of the lack of a digital source by the CAA and the increasing complexity of the UK data. Robin ma...@gr... wrote: > > Thirdly, I would be most comfortable with having support for an extended > > version of OpenAir if the extensions were accepted by whoever is > > responsible for "owning" the standard. Anyone know who that is? > > > I think that adhering to the standard format is a basic requirement. > Extensions should not be added unless the entire OpenAir community > agrees: compatibility is vital, especially when so much of the software > the reads OpenAir files is embedded in PDAs and panel-mounted > instruments. > > In the past people/organisations who have added custom extensions to > standards that don't allow for extension have caused immense problems > for everybody, including themselves. Look at the mess Microsoft has > caused with its proprietary extensions to HTML. Now they're finding that > their new standards-compliant IE 8 needs a horrible, barely usable > kludge to display websites with specific IE 5 and IE 6 extensions. Its > release has been delayed as a direct result. Is that poetic justice or > what? > > The first step toward an extendable OpenAir format is straight forward > in theory. All software using OpenAir files merely needs the ability to > ignore any extensions it doesn't implement. This should be a simple > change, but the devil is in the detail of getting every copy of these > programs upgraded. If that's not managed properly, uploading the first > extended OpenAir file to the Soaring Exchange will cause much brown > stuff to impact the ventilation impeller. > > > Martin > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Xcsoar-user mailing list > Xcs...@li... > https://lists.sourceforge.net/lists/listinfo/xcsoar-user > |