Hi, I am once again playing around with all the files needed for XCSoar. Let me think out loud a bit:
Until now, I have just used what came with a standard installation and downloaded waypoint data now and then, but now I find there are some minor glitches in the data I found, some abbreviations used truncate the TP or field names beyond recognition, a few fields even seem to be missing, some are already closed, and while trying to correct them, I find it is a bit strange to have turn points and airfields in the same list and then airfield info in yet another. That makes keeping them up to date and synced a bit difficult. Depending on from which field I take off, I like to load a turnpoint list that is limited to the region of that field. It just makes finding points a lot faster. No use in having the alps populating the list while flying over Northern Germany and vice versa. So, I have a separate turnpoint list, respective several lists, of which I use the one I need. Now that the turnpoints live conveniently in their own list, it made sense to have a dedicated airfield file, too. So I loaded the 'all in one' .xcw file in a spread sheet, sorted it and and extracted only the airfields. So far - so good. That takes care of the airfields becoming available again: Airfields in WP file 1, Turnpoints in WP file 2, and their handling is improved quite some. Now, in this data, airfields have all the data that is relevant for them as far as they act as turnpoints, but that's it, then. There is apparently one more file that can be used, and that is an airfields file in txt format, which - as far as I understand - needs to list the airfields with the same names as used in the WP file, but can hold additional info such as RWY info, radio frequency and comments. Now, things get difficult, respectively editing them takes a lot of effort. Woudn't it make sense to: A) Have the airfields and all the corresponding info in one airfields file that can exist in parallel to one (or more) turnpoint file(s)? B) Use a spread sheet compatible format for all the data files, and unify the format so that kind of an expandable matrix is established that can take the info of any given point? Soaring Turnpoint Exchange is suggesting something similar. We could still import data with other known formatting into the matrix. BTW.: It would also make sense, if after we abort a task and goto a near field, this field's radio freqency and such was automatically displayed, as this info will most probaly be needed just now (Or does it just not work for me because of mismatched files?). Just thinking ... Martin --- ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
