Ok, it's a CAD file (just tried it) but it still works since it would list all the vertices of the fence (I forgot how to close a polygon in Xastir but it was enough). It's a nice, clean, parseable format. So you get the benefit of the map combined with the benefit of an external application.
--- On Fri, 12/4/09, Alex Carver <[email protected]> wrote: > From: Alex Carver <[email protected]> > Subject: Re: [Xastir] Possible Feature Suggestion > To: "Xastir - APRS client software discussion" <[email protected]> > Date: Friday, December 4, 2009, 12:10 AM > Actually you could do something of a > hybrid now with the current version. If I recall, the > current version will generate shape files for lines drawn on > the map (or something similar to a shape file). So you > draw your geo-fence, export the shape file, and then feed it > into the external application. > > --- On Fri, 12/4/09, Craig Anderson <[email protected]> > wrote: > > > From: Craig Anderson <[email protected]> > > Subject: Re: [Xastir] Possible Feature Suggestion > > To: "Xastir - APRS client software discussion" <[email protected]> > > Date: Friday, December 4, 2009, 12:06 AM > > I understand the sentiment but I > > think it needs to be part of Xastir because you need > to > > define those geo-fences on the map. This will not be > a > > problem in version 2.0, where the graphical interface > is > > separate from other parts. > > > > As to your question, yes you can receive all position > > reports, send reports, send and receive messages all > through > > the server ports; i.e. everything goes everywhere that > it is > > enabled. What you're suggesting, as a separate > > application, is fully possible. > > > > Craig > > > > On Dec 3, 2009, at 8:45 PM, Alex Carver wrote: > > > > > Lots of useful ideas but a lot of this could > probably > > be made as an external program which connects to > Xastir's > > server ports instead. That keeps the Xastir code > > unchanged and essentially keeps Xastir as a gateway > rather > > than the functional application. This also makes it > > easier to tweak and add functionality without having > to > > rebuild all of Xastir. > > > > > > > > > I haven't played much with the server port much > so a > > question to the group: > > > > > > If a packet arrives at the server port, will it > be > > transmitted to all interfaces that have transmit > enabled > > (assuming global transmit is enabled) or will it only > go out > > on specific interface types? > > > > > > --- On Thu, 12/3/09, Craig Anderson <[email protected]> > > wrote: > > > > > >> From: Craig Anderson <[email protected]> > > >> Subject: Re: [Xastir] Possible Feature > Suggestion > > >> To: "Xastir - APRS client software > discussion" > > <[email protected]> > > >> Date: Thursday, December 3, 2009, 11:40 PM > > >> Cool idea! This could be > > >> extended to include geo-fencing. A message > > gets sent > > >> to any station, or a specific station, that > > reports from > > >> within a specified area. You could define > > "warning > > >> areas" and "danger zones" for flooding or > other > > hazards. > > >> > > >> Or send a message to someone else if a > specific > > call sign > > >> enters or leaves a defined area or crosses a > > boundary. > > >> If a rider has gone outside the race boundary > for > > example. > > >> > > >> Or run a script on a call sign entering or > leaving > > an area; > > >> e.g. a home-automation script that starts > the > > coffee maker > > >> because you're almost home. > > >> > > >> Time schedules and limits could be defined > for any > > of the > > >> above. > > >> > > >> Gee, we could go crazy with this! :-) > > >> > > >> Craig > > >> n6yxk > > >> > > >> On Dec 3, 2009, at 7:15 PM, Chip G. wrote: > > >> > > >>> I'm not up for attempting to code this > right > > now, but > > >> just thought I'd mention it in case any one > was > > interested. > > >> One of the many functions/features of Xastir > and > > APRS is the > > >> ability to send messages to other APRS users. > But > > often the > > >> station you'd like to send a message to is > not > > there at the > > >> time. Xastir has a good decay routine for > resends, > > but the > > >> delay between attempts can get quite long. > What if > > there was > > >> the ability to send a delayed message. And > because > > APRS has > > >> the ability to know when a station > "checks-in," > > why not link > > >> the message send to the receipt of a new > position > > (or other) > > >> packed from the desired station. > > >>> > > >>> So for example, if I want to send to my > wife's > > car > > >> (N1MLG-4), but she hasn't left work yet. I > would > > bring up > > >> the delayed message window. I would enter in > her > > callsign > > >> & SSID and then the message and click > send. > > Xastir would > > >> begin to monitor and as soon as the next > packet > > was received > > >> it would send the message back by either the > > default path, > > >> by the return path, or by a path I specify. > A > > fancy > > >> variation would include an abort option (if > not > > sent within > > >> the specified time it aborts lets the user > know). > > >>> > > >>> Thanks for considering the idea, > > >>> > > >>> > > >>> 73, > > >>> --de Chip (N1MIE) FN41bn > > >>> > > >>> > > _______________________________________________ > > >>> Xastir mailing list > > >>> [email protected] > > >>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > > >> > > >> > _______________________________________________ > > >> Xastir mailing list > > >> [email protected] > > >> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > > >> > > > > > > > > > > > > _______________________________________________ > > > Xastir mailing list > > > [email protected] > > > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > > > > _______________________________________________ > > Xastir mailing list > > [email protected] > > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > > > > > > _______________________________________________ > Xastir mailing list > [email protected] > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir > _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
