[Xastir-dev] args to data_add()

[Owen DeLong]

> So then, how about:
>
> - accepting either NMEA or APRS for targets (either "my station"
>   or "other stations")
>
Sounds good.

> - 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?)
>
I'm not sure about this.  I think there is a way to tell it to use an
alternate symbol set for APRS using the network name or something, but,
my memory is very fuzzy about this since I never actually used it.

> - a udp input routine in the main loop (optional, I'll look into
>   using gpsd instead, since that is the 'xastir way')
>
I think GPSD would be a better way to go.  Alternatively, you could code
up a new GPS interface in XASTIR (similar to the GPSD and Serial NMEA
routines there now) and hook that in.  Adding udp input to the main routine
doesn't make a lot of sense to me and seems contrary to the current code
structure (or at least my limited recollection of it).

>> > 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.
>
I think there are.  I think you can do most of what you want with the
existing TCP based GPSD and APRS Internet Feed interfaces.

Your code could either be a GPS for GPSD, or, pretend to be GPSD and
have XASTIR connect to your codes socket.  Similarly, your code could
pretend to be an internet APRS feed and have XASTIR connect to that
socket as well.  No modifications to XASTIR required for that part.

Where I think you might need mods would be:

	Displaying aircraft the way you want, especially for TCAS

	Making sure XASTIR keeps track of a 3D world (I think it's pretty
	two-dimensional right now), but I'm not sure.

If you really want to write code for XASTIR to get NMEA and APRS strings
from your software a special way or you're dead set on UDP, then, you could
code up new GPS and TNC interfaces for XASTIR (it's not too hard, modified
one of the existing TNC interfaces to provide support for some of the newer
Kantronics TNCs a while back, and, believe me, I'm no programmer).

> 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)!
>
Wow... That's pretty cool... I'm still trying to figure out how to reliably
GET TFR data.

Owen
KB6MER
Private Pilot, Airplane Single Engine Land
Instrument Airplane


-- 
If it wasn't crypto-signed, it probably didn't come from me.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://xastir.org/pipermail/xastir-dev/attachments/20040414/d45348dc/attachment.sig>