From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] radar
Date: Wed, 5 Oct 2011 02:31:40 -0400 [thread overview]
Message-ID: <bb222df1361fba6e1c096ae3571274be@chula.quanstro.net> (raw)
In-Reply-To: <911644f6ac123bb16f56a392ac4950a9@brasstown.quanstro.net>
> > I added: LGX Langley Hill WA to lib/stations and LGX 47.109 -124.100
> > (approx) to lib/stationlat
> >
> > There is an interesting read about getting the array going and what it
> > will do for Western Washington here: http://tx0.org/2uy
>
> i think it's already there. what you saw was probablly a bug in
> finding the station code. i had "..." instead of "???". what was
> that dek quote, "i define unix as 30 definitions of regular expressions
> living under one roof."
>
> (pull radar again. sorry.)
>
> ; grep ATX /lib/radar/*
> /lib/radar/stationlat:ATX 48.18960544933 -122.4886090504
> /lib/radar/stations:ATX Everett/Seattle-Tacoma WA
ack! misread. i've pushed out /lib/radar/genlat which automaticly
generates the latitude listings given the station listing to save you
from guessing.
anybody know where a current station listing can be had? i scraped
mine from a pulldown, but there's got to be an automatic way to do this?
contributions gladly accepted. the stationlat should be self-updating
like /sys/lib/scsicodes.
- erik
next prev parent reply other threads:[~2011-10-05 6:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 3:06 erik quanstrom
2011-10-05 9:09 ` smj
2011-10-05 5:43 ` erik quanstrom
2011-10-05 6:31 ` erik quanstrom [this message]
2011-10-05 11:55 ` smj
2011-10-05 8:44 ` Andy Spencer
2011-10-05 13:56 ` erik quanstrom
2011-10-06 16:11 ` erik quanstrom
2011-10-07 10:35 ` Gorka Guardiola
2011-10-05 10:47 ` Steve Simon
2011-10-05 11:01 ` dexen deVries
2011-10-05 11:20 ` Steve Simon
2011-10-05 11:43 ` dexen deVries
2011-10-05 13:37 ` erik quanstrom
2011-10-05 13:45 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2011-10-03 4:18 erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb222df1361fba6e1c096ae3571274be@chula.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).