Oleg Safiullin wrote:
Bob Armstrong wrote:
I have `geo location of OpenBSD developers' map at
http://pdp-11.org.ru/~form/openbsd/map/
and I can do something like that for HECnet if I have enough info :)
Well, there's a list of the cities in the list that I publish. Is there
an easy way to find a lat/lon for the center of each city?
Yes.
Just open http://maps.google.com/, find your location at satellite map, rightclick and select "Center here".
Then just press "Link" at right up corner of map and you'll get an URL with lat/long.
I think it would be better to use real coordinates, not just center of city, so we can look
at satellite map and see real location of node :)
Why am I starting to think something like X.500 makes more sense at this
point?
There's also the format used once up on a time by the UUCP mapping project
- we have basically the same problem that they did.
http://www.uucp.org/uumap/README
They're long gone now, but there are probably still lots of tools around for
processing data in this format.
Come to think of it, didn't they already have something to produce a
geographic map?
Bob
On 19 Oct 2009, at 16:16, Brian Hechinger wrote:
Why am I starting to think something like X.500 makes more sense at this
point?
Probably because we're building a distributed directory :)
In any case, yes, eventually a central X.500 directory would be wonderful - however the INFO.TXT + demon-spawn-of-CSV-infofields is probably a nice and quick hack to throw together in an afternoon. Hell, we can populate the X.500 dir from the textfiles eventually.
Sampsa
Bob Armstrong wrote:
I have `geo location of OpenBSD developers' map at
http://pdp-11.org.ru/~form/openbsd/map/
and I can do something like that for HECnet if I have enough info :)
Well, there's a list of the cities in the list that I publish. Is there
an easy way to find a lat/lon for the center of each city?
Yes.
Just open http://maps.google.com/, find your location at satellite map, rightclick and select "Center here".
Then just press "Link" at right up corner of map and you'll get an URL with lat/long.
On Mon, Oct 19, 2009 at 04:11:26PM +0100, Sampsa Laine wrote:
Contact address: I say we put in both, SMTP and DECNET.
I agree.
We should add a field for lat/long data in some standard format.
Good thinking.
I don't see why one host could not provide multiple tag lines, for
example the format below would allow for that (it has the node address
and name embedded in the data) - and since we're a nice cooperative
bunch we can trust others not to provide spurious information about
other machines.
Why am I starting to think something like X.500 makes more sense at this
point?
-brian
--
"Coding in C is like sending a 3 year old to do groceries. You gotta
tell them exactly what you want or you'll end up with a cupboard full of
pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
We should add a field for lat/long data in some standard format.
Lat/lon doesn't mean much to me, but I find it easy to build a mental
picture from reading the list of city names.
Of course, if Oleg can produce a map then I can always just look at that.
Bob
I have `geo location of OpenBSD developers' map at
http://pdp-11.org.ru/~form/openbsd/map/
and I can do something like that for HECnet if I have enough info :)
Well, there's a list of the cities in the list that I publish. Is there
an easy way to find a lat/lon for the center of each city?
Bob
I've bee meaning to make a comment about this, but just haven't come around to it.
I think that Sampsas suggestion for a INFO.TXT file is a pretty nice idea. But I also think that some standard form to it would be nice.
Any suggestions?
Johnny
Bob Armstrong wrote:
Obviously no one sent me any either. ;-)
http://www.avanthar.com:8080/nodes/
I was meaning to talk to you about that - the listing for CODA is
incorrect, too. I don't know where this list gets its information.
Clearly, keeping all these separate lists updated manually is getting to
be impossible.
If Sampsa's INFO.TXT file contained more information AND had a
standardized format that was not too hard to parse, then we could use that
as the basis for automatically generating all these lists. "If..." :-)
Bob
Contact address: I say we put in both, SMTP and DECNET.
As for the order of the fields, two options: Either label the fields or trust people to remember the order. I vote for trusting people :)
We should add a field for lat/long data in some standard format.
I don't see why one host could not provide multiple tag lines, for example the format below would allow for that (it has the node address and name embedded in the data) - and since we're a nice cooperative bunch we can trust others not to provide spurious information about other machines.
Sampsa
On 19 Oct 2009, at 16:04, Bob Armstrong wrote:
!HNINFO:1.401|CHIMPY|AlphaServer 800|OpenVMS 8.3|Comments go here|
That works for me, although everybody has to remember the correct order
for the fields :-)
I think there should also be an email address for the owner (DECnet or
SMTP, that's negotiable) just so somebody can contact him or her if there's
a question.
And I personally find it really interesting to know the geographic
location of the nodes. I always wanted to make a map of the world with the
HECnet links and sites marked, but I never got around to it. Is anybody
looking for something to do?
Oh, and it needs to be possible to put information for nodes other than
the current one (i.e. the one actually serving the INFO.TXT file) into the
file. That's to allow for machines that aren't up 24x7.
Bob
And I personally find it really interesting to know the geographic
location of the nodes. I always wanted to make a map of the world with the
HECnet links and sites marked, but I never got around to it. Is anybody
looking for something to do?
I have `geo location of OpenBSD developers' map at http://pdp-11.org.ru/~form/openbsd/map/
and I can do something like that for HECnet if I have enough info :)
