[Xastir] Search FCC database not working?

[William McKeehan]

I happen to have a high-speed connection...so

I am finding embeded Ctrl-M's in some of the records in the EN.dat

On Sat, January 22, 2005 4:45 pm, Tom Russo said:
> On Sat, Jan 22, 2005 at 04:11:12PM -0500, we recorded a bogon-computron
> collision of the <mckeehan at mckeehan.homeip.net> flavor, containing:
>> Looks like that was my problem too...thanks for the tip!
>
> You're welcome.  I glanced over the fcc_data.c code, and it does look like
> it depends on the lines of the EN.dat file conforming to the correct format.
> Don't know why the file from FCC has those busted lines.  Could be there's a
> control character or something in there that confuses "sort".  But with a
> 56k line I can't download the fcc data very often, and I don't keep the
> unsorted file around, so I can't look to see where they're coming from.
>
> Perhaps someone blessed with a high-speed connection can take a look?
>
>> On Sat, January 22, 2005 3:51 pm, Tom Russo said:
>> > On Sat, Jan 22, 2005 at 03:42:17PM -0500, we recorded a bogon-computron
>> > collision of the <mckeehan at mckeehan.homeip.net> flavor, containing:
>> >> Is anyone else having problems with the "Search FCC database" button not
>> >> finding call signs?
>> >>
>> >> I have fetched the data by using the fcc-get command, and when I grep
>> >> /usr/local/share/xastir/fcc/EN.dat for the call sign in question
>> >> (specifically, KE4FGW), I get one record. But when I search via the
>> Station
>> >> Information dialog, I get a "Callsign Not Found!" message.
>> >
>> > Yes, I have seen this happen.  Look carefully at the first and last few
>> > lines of your EN.dat file.  Last time I updated, these early and final
>> lines
>> > appeared to be scrambled --- it looked as if there were some corrupt lines
>> > of the input that got placed funny by the sort operation.
>> >
>> > When I deleted them and let xastir reindex the file (by removing the
>> > .xastir/data/appl.ndx file) the behavior went away.
>> >
>> > I'm not sure why the bogus lines confused the issue or where they came
>> from,
>> > but the solution was simple enough in my case that I never bothered
>> looking
>> > further.
>> >
>> > --
>> > Tom Russo    KM5VY     SAR502  DM64ux         http://www.swcp.com/~russo/
>> > Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1
>> >  "When life gives you lemons, find someone with a paper cut."
>> >
>> >
>>
>>
>> --
>> William McKeehan
>> KI4HDU
>> Internet: mckeehan at mckeehan.homeip.net
>> http://mckeehan.homeip.net
>
> --
> Tom Russo    KM5VY     SAR502  DM64ux         http://www.swcp.com/~russo/
> Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1
>  "When life gives you lemons, find someone with a paper cut."
>
>


-- 
William McKeehan
KI4HDU
Internet: mckeehan at mckeehan.homeip.net
http://mckeehan.homeip.net