I also added a notification method for generic systems (they will appear as grey dots).
Schedule a 5 min cron job (or whatever is needed to get it done) with the following instruction:
wget -O /dev/null http://44.182.21.1:59001/generic?id=test@AA00AA
Replace test@AA00AA with your gateway_call@qth_locator
This also will only work from 44net sources only.
Have fun,
Marius, YO2LOJ
With much respect and admiration to Marius for this great (and really cool!) work, is this really what we want to do? That is, do we really want to create yet another separate and proprietary system? What happened to the DNS LOC record idea?
Michael N6MEF
-----Original Message----- From: 44Net [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Marius Petrescu Sent: Thursday, June 1, 2017 8:05 AM To: AMPRNet working group 44net@hamradio.ucsd.edu Subject: [44net] Map notification for generic systems.
(Please trim inclusions from previous messages) _______________________________________________ I also added a notification method for generic systems (they will appear as grey dots).
Schedule a 5 min cron job (or whatever is needed to get it done) with the following instruction:
wget -O /dev/null http://44.182.21.1:59001/generic?id=test@AA00AA
Replace test@AA00AA with your gateway_call@qth_locator
This also will only work from 44net sources only.
Have fun,
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Let's do it... But how?
Re-register the DNS entries after DNS robot update? Ask Chris to get some new fields into the gateway tool and use that one to update the entries?
The idea is that there's some logistics in place. And even if that one will give us the locations. it is not live data. And the "live" is the nice idea.
On 01.06.2017 18:41, Michael Fox - N6MEF wrote:
(Please trim inclusions from previous messages) _______________________________________________ With much respect and admiration to Marius for this great (and really cool!) work, is this really what we want to do? That is, do we really want to create yet another separate and proprietary system? What happened to the DNS LOC record idea?
Michael N6MEF
If you make your input parameter to the existing daemon a DNS LOC record instead of callsign@gridsquare, you'd have the Lat/Long immediately available for updating the map, and we'd have the data for updating the DNS at some later time.
Remember that a DNS LOC record is a simple string consisting of <callsign> IN LOC <latitude> <longitude> <altitude> <accuracy> much of which is optional.
for example, a site located at the coordinates 52°22'23"″North 4°53'32"″East would send
'W1AW IN LOC 52 22 23.000 N 4 53 32.000 E -2.00m 0.00m 10000m 10m' or 'W1AW IN LOC 52 N 4 E -2m'
You could update the map from that. And later it would go into the DNS as w1aw.ampr.org's LOC record. All that would be necessary is for the map daemon to call a defined program with the record as an input parameter. That program (to be supplied later) would handle the DNS update, perhaps via some DDNS function.
(You could even make it backwards compatable by having the map daemon convert callsign@gridsquare to a LOC record. You'd lack the altitude part of the data, but you could assume it's zero for conversion purposes.)
The map would still be realtime, and the DNS somewhat historical.
See the wikipedia article https://en.wikipedia.org/wiki/LOC_record or RFC1876 for details on the record format. - Brian
On Thu, Jun 01, 2017 at 06:45:11PM +0300, Marius Petrescu wrote:
Let's do it... But how?
Re-register the DNS entries after DNS robot update? Ask Chris to get some new fields into the gateway tool and use that one to update the entries?
The idea is that there's some logistics in place. And even if that one will give us the locations. it is not live data. And the "live" is the nice idea.
http://dnsloc.net is an online site where you click on your location on the map and it generates the LOC record for you. - Brian
On Thu, Jun 01, 2017 at 09:11:09AM -0700, Brian Kantor wrote:
Remember that a DNS LOC record is a simple string consisting of <callsign> IN LOC <latitude> <longitude> <altitude> <accuracy> much of which is optional.
Brian.
That's cool, indeed!
Best regards. Tom - SP2L
_______________________________________________ http://dnsloc.net is an online site where you click on your location on the map and it generates the LOC record for you. - Brian
hi everybody
is there a way to be shown on the map using jnos, as I am running jnos at vk7hdm.ampr.org (vk7hdm-6)
On 2/06/2017 1:04 AM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ I also added a notification method for generic systems (they will appear as grey dots).
Schedule a 5 min cron job (or whatever is needed to get it done) with the following instruction:
wget -O /dev/null http://44.182.21.1:59001/generic?id=test@AA00AA
Replace test@AA00AA with your gateway_call@qth_locator
This also will only work from 44net sources only.
Have fun,
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Hi Danny,
I don't know exactly how to do it, but you need to send a http request to 44.182.21.1 on port 59001 requesting '/generic?id=yourcall@yourlocator'.
It even works in a web browser...
e.g. http://44.182.21.1:59001/generic?id=n0call@AA00AA
So if jnos has this possibility, just send the request and you're on the map.
On 02.06.2017 10:30, Danny Moss via 44Net wrote:
hi everybody
is there a way to be shown on the map using jnos, as I am running jnos at vk7hdm.ampr.org (vk7hdm-6)
-
Brian Kantor -
Danny Moss -
Marius Petrescu -
Michael Fox - N6MEF -
SP2L