<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>But it has to fit within a standard 6-character callsign. One of my software users asked me for an APRS-IS passcode for their tactical callsign that was seven characters long, and the APRS-IS wouldn't accept it. They had to use their real (6-character) callsign and put the tactical callsign in an object record at the same geographical position.<br><br>Andrew, KA2DDO<br>author of YAAC ("Yet Another APRS Client")<br><br><div>> Date: Thu, 6 Aug 2015 17:15:52 -0700<br>> To: david@davidandrzejewski.com; aprssig@tapr.org<br>> Subject: Re: [aprssig] Location-based Callsign on -IS?<br>> From: aprssig@tapr.org<br>> <br>> On Thu, Aug 6, 2015 at 2:36 PM, David Andrzejewski via aprssig<br>> <aprssig@tapr.org> wrote:<br>> > So, as is recommended on http://aprs.org/fix14439.html, I have changed the<br>> > callsign of my home digi from my callsign (KD8TWG-1) to the digi's location<br>> > (PPRPKE, for Pepper Pike). This is effective on the air. However, it's<br>> > also an RX/TX igate, and it's logging into -IS using KD8TWG-1 still. Is it<br>> > legal with the APRS-IS to use a location-based callsign? I would think not.<br>> <br>> There are no laws on APRS-IS. Anything is legal. I have my digis log<br>> in with their tactical callsign.<br>> <br>> Tom KD7LXL<br>> _______________________________________________<br>> aprssig mailing list<br>> aprssig@tapr.org<br>> http://www.tapr.org/mailman/listinfo/aprssig<br></div> </div></body>
</html>