Beacon being broadcasted with reference GPS coordinates

[hosse005]

Is there a reason the beacon is being configured with reference GPS coordinates specified in the configuration file instead of the acquired GPS coordinates?

[nestorayuso]

GPS coordinates in .json file are fake/static coordinates for gateways without GPS.
If your gateway has GPS, delete these lines from .json file

[hosse005]

The code in lora_pkt_fwd.c file may need to be changed to use meas_gps_coord instead of reference_coord, for instance:

field_latitude = (int32_t)((reference_coord.lat / 90.0) * (double)(1<<23));

[mcoracin]

The initial reason to use the reference coordinate was to handle the case where we have multiple sectorial antennas on a same roof, to precisely differentiate the coordinates of each antenna/gateway.

But it would make sense to use the reference coordinate if it is given in the .json, and use the acquired coordinates otherwise.

[rbaldwin13]

In an effort to improve our customer support experience and in recognition that our support backlog on GitHub has historically exceeded the capacity of our engineering team, we have taken the difficult decision to focus on the most contemporary issues reported and to close all others without confirmation of resolution.

Our belief is that issues which have remained unresolved and unaltered for extended periods of time are less likely to continue to pose a significant problem to the user than when they were originally filed. More contemporary issues however may still be relevant and hence are more appropriate to prioritize.

For those users who remain interested in resolution of a reported issue that was closed, we are encouraging usage of our developer portal forums [https://forum.lora-developers.semtech.com/] and commercial support portal [https://semtech.force.com/ldp/ldp_support?__hstc=212684107.579a13689e43099691e328c9248e6ecc.1623103335314.1624470656297.1624635514661.6&__hssc=212684107.6.1624635514661&__hsfp=4176385453] as the preferred avenues to receive support. We will continue to monitor the GitHub issue trackers as well, but want to encourage all users to take advantage of the increased community presence on the developer portal. For commercial customers, we highly recommend using the commercial support portal which is uniquely tailored to service such support requests.