Ampr-map: Difference between revisions
Added technical info |
No edit summary |
||
(4 intermediate revisions by the same user not shown) | |||
Line 12: | Line 12: | ||
Some technical info: | Some technical info: | ||
<blockquote> | <blockquote> | ||
<i>The | <i>The server uses the following incoming ports:<br> | ||
- ampr-ripd uses UDP/59001,<br> | - ampr-ripd uses UDP/59001,<br> | ||
- amprd uses UDP/59002,<br> | - amprd uses UDP/59002,<br> | ||
- all other http requests use TCP/59001<br> | - all other http requests use TCP/59001<br> | ||
Map events sent to your browser use websockets | Map events sent to your browser are in json format and use websockets or event-stream as a fallback.</i> | ||
</blockquote> | </blockquote> | ||
The map can be reached via these URLs: | The map can be reached via these URLs: | ||
http://www.yo2loj.ro/ampr-map/ | http://www.yo2loj.ro/ampr-map/ | ||
http:// | http://yo2loj.ampr.org/ampr-map/ | ||
== Sending the location to the map == | == Sending the location to the map == | ||
Line 47: | Line 46: | ||
Add your locator in the configuration file, under your interface section: | Add your locator in the configuration file, under your interface section: | ||
call_home = | call_home = N0CALL-T@KN05or | ||
Positions will be shown as blue dots. | Positions will be shown as blue dots. | ||
Line 56: | Line 55: | ||
Set up a cyclic job to run a script in which you request a specific URL, using the command, e.g. every 5 minutes: | Set up a cyclic job to run a script in which you request a specific URL, using the command, e.g. every 5 minutes: | ||
/tool fetch mode=http url="http://44.182.21.1:59001/mikrotik?id=N0CALL-T@kn01aa" keep-result=no | /tool fetch mode=http url="<nowiki>http://44.182.21.1:59001/mikrotik?id=N0CALL-T@kn01aa</nowiki>" keep-result=no | ||
Positions will be shown as pink dots. | Positions will be shown as pink dots. | ||
Line 67: | Line 66: | ||
To do this, do a periodic fetch on the following URL: | To do this, do a periodic fetch on the following URL: | ||
http://44.182.21.1:59001/radio_gateway?id=n0call-t@kn01aa | <nowiki>http://44.182.21.1:59001/radio_gateway?id=n0call-t@kn01aa</nowiki> | ||
For radio stations, the position time-out is 3 hours. | For radio stations, the position time-out is 3 hours. | ||
Line 78: | Line 77: | ||
For other (generic) systems, do a periodic fetch on the following URL: | For other (generic) systems, do a periodic fetch on the following URL: | ||
http://44.182.21.1:59001/generic?id=n0call-t@kn01aa | <nowiki>http://44.182.21.1:59001/generic?id=n0call-t@kn01aa</nowiki> | ||
Positions will be shown as grey dots. | Positions will be shown as grey dots. |
Latest revision as of 21:31, 28 August 2024
Viewing the map
We have a visual map of the AMPR network available, on which users can choose to voluntarily publish their callsign/locator, which is then shown on a vector map of the world. Generally, the positions will time out after 1 hour.
On click on the dots on the map, additional information will be shown: type, IP, locator and seconds since the last information received.
No information are permanently stored on the server side.
To opt out, just stop sending position reports...
Some technical info:
The server uses the following incoming ports:
- ampr-ripd uses UDP/59001,
- amprd uses UDP/59002,
- all other http requests use TCP/59001
Map events sent to your browser are in json format and use websockets or event-stream as a fallback.
The map can be reached via these URLs:
http://www.yo2loj.ro/ampr-map/ http://yo2loj.ampr.org/ampr-map/
Sending the location to the map
Depending on your system setup and node type, there are 5 methods to get your positions on the map.
Please replace the callsign and position with your own in the given examples.
Position reports are case insensitive and will all be converted to upper case.
- 1. ampr-ripd
Add the parameter '-L <callsign@<locator>' to the ampr-ripd command line.
ampr-ripd [...other parameters...] -L N0CALL-T@kn01aa
Positions will be shown as green dots.
- 2. amprd
Add your locator in the configuration file, under your interface section:
call_home = N0CALL-T@KN05or
Positions will be shown as blue dots.
- 3. Mikrotik routers
Set up a cyclic job to run a script in which you request a specific URL, using the command, e.g. every 5 minutes:
/tool fetch mode=http url="http://44.182.21.1:59001/mikrotik?id=N0CALL-T@kn01aa" keep-result=no
Positions will be shown as pink dots.
- 4. 'Radio' positions
These positions are dedicated to stations not directly reachable via 44net, and are sent out by other systems in their name.
To do this, do a periodic fetch on the following URL:
http://44.182.21.1:59001/radio_gateway?id=n0call-t@kn01aa
For radio stations, the position time-out is 3 hours.
Positions will be shown as yellow antenna symbols.
- 5. Generic position reports
For other (generic) systems, do a periodic fetch on the following URL:
http://44.182.21.1:59001/generic?id=n0call-t@kn01aa
Positions will be shown as grey dots.