[Xastir-dev] args to data_add()

[Wendell Turner]

> > Actually, if I were looking at it, what I'd be doing is using the
> > GPS NMEA string from the simulated panel-mounted GPS (OK, I'm
> > making an assumption here, but, I suspect it's fairly safe) into
> > XASTIR as the "my station" input.  I'd also use synthetic APRS
> > strings for other aircraft to potentially simulate TCAS.  The TCAS
> > stuff might require adding some capabilities to XASTIR (3D
> > awareness kind of things), but, those could be generically useful.
> 
> Yes, if it would solve the purposes, that is exactly how I'd go
> about it as well.  It fits our paradism quite well.

So then, how about:

- accepting either NMEA or APRS for targets (either "my station"
  or "other stations")

- somehow identifying inside db.c that a target be drawn using
  non-APRS tagged type (if I were to use synthetic APRS, then I
  would be limited to APRS symbology, correct?)

- a udp input routine in the main loop (optional, I'll look into
  using gpsd instead, since that is the 'xastir way')

> > Anyway, I think this has some interesting possibilities.  I agree
> > that non-XASTIR functionality should be kept external,

Ok, that would be fine, if there were hooks or APIs for such an
external interface.

> > Realistically, I think XASTIR is evolving into a generic
> > GIS/Tracking/Solution Plotting system with APRS and NMEA as
> > primary inputs, rather than just another APRS widget.
> > That's a good thing!
> 
> Agreed.  It also fits into the Unix philosophy of "small" tools that
> can be strung together to perform the larger task, although we're
> severely pushing the "small" category.

Yes.  This seems to be an extremely nice and capable mapping
package (now that I've found out how to display IFR data on it
also)!

Wendell