on my GW the poly_forwarder supports setting GPS coordinates manually in local_conf.json under gateway_conf
{ "gateway_conf": { "ref_latitude": x.xxx, /* put your latitude here */ "ref_longitude": y.yyy, /* put your longitude here */ "ref_altitude": z, /* put your altitude here */ } }
I’ve been at it over 24 hours and in all that time I missed one line of instruction.
*Edit /etc/init.d/lora-network-server. Around line 17 you need to change from using * basic_pkt_fwd to using poly_pt_fwd: pkt_fwd=/opt/lora/poly_pkt_fwd
This is insanely hard…
Still another node on line, just need to start sending some data and stuff now
Small update: the status and coordinates of the gateways on the main website (http://thethingsnetwork.org) are now updated live, based on the API. So if you have a live gateway, be sure to add it - including eui identifier - to the community platform using your own account.
The map on thethingsnetwork is a static map I guess. It contains (at least in Nijmegen) a lot of gateways that are not there (yet) or that are not active.
The lpwan.uk maps looks nice. Too bad that a lot of gateways still do not reveal their location. This would make life for node developers so much brighter.
But then, anyone who claims to have - what they call - a gateway can add this to the map. A Raspberry Pi with a single channel sx1276 board will (and a lot do) show up as a gateway. In my very humble opinion that’s not a gateway but a testing tool. If you place a gateway on the map it should be a “real” gateway that at least listens on the 3 default channels and is also able to do stuff like OTAA. Also make sure it’s always online - or at least try to have it online. The network is now building up and it is time to leave the phase of “development” where network and gateways go on and off at irregular intervals.
As soon as I can guarantee that my gateway is stable and runs 24/7 with 99% up-time I’ll add my GPS coordinates. Until then it’s just one of those “location not disclosed” testing things.
Nope; see the explanation of the colors on top: Active, Inactive, Deactivated, Planned. So indeed some are not active yet (including Kickstarter pledges), but some have been added automatically upon receiving the first packet (or the first status message, not sure), where the coordinates are taken from the status messages. This includes single-channel gateways that have coordinates set.
Also, though I agree a single-channel gateway is just for testing, at this moment I like to see them, as they show people’s activity.
However it would be nice if they could easily be recognized, or even better filtered, as they are non standard and provide false information regarding the availability of TTN at those locations.