Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

show beacon transmitter on ttnmapper #3

Open
TwentySixer opened this issue Jan 31, 2020 · 1 comment
Open

show beacon transmitter on ttnmapper #3

TwentySixer opened this issue Jan 31, 2020 · 1 comment

Comments

@TwentySixer
Copy link

As already discussed in the chat here the issue ;)

Actually my colleagues and I have an idea to place LoraWAN nodes to fixes places to measure the coverage of our gateways.
We would also like to provide this data to the ttnmapper but there is a problem.
We do not want to send the geocoordinate data in the payload, since you would have to store them in the firmware and you cannot use the nodes flexibly.
In the ttn-console it is possible to maintain a location for each device, longitude, latitude, height.
This data is included in the metadata.

metadata:
{
"time": "2020-01-22T09:15:09.746106679Z",
"frequency": 867.1,
"modulation": "LORA",
"data_rate": "SF7BW125",
"coding_rate": "4/5",
"gateways": [
{
"gtw_id": "eui-60c5a8fffe74d441",
"timestamp": 1614987531,
"time": "",
"channel": 3,
"rssi": -73,
"snr": 8,
"latitude": 51.55006,
"longitude": 12.137772,
"altitude": 3,
"location_source": "registry"
}
],
"latitude": 51.549404,
"longitude": 12.138148,
"altitude": 97,
"location_source": "registry"
}

It would be nice if the entered coordinates of the TTN console are used if none are delivered in the payload

Thanks in advance

@jpmeijers
Copy link
Contributor

For TTNv2 this has been implemented a couple of months ago. It still needs to be added for TTSv3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants