The (last known) location of the gateway will be stored in the database. When the gateway is equipped with a GPS, its location will be automatically updated after every stats update. Else, it can be manually set when creating or updating the gateway.
LoRa Server exposes the gateway statistics on a pre-configured aggregation intervals (see gateway configuration). By default these intervals are configured to: minute, hour and day.
Note that LoRa Server does not implement any retention of the gateway stats. In case you would like to keep
you could use the following queries (e.g. as a cron):
delete from gateway_stats where "interval" = 'MINUTE' and "timestamp" < now() - interval '1 day'; delete from gateway_stats where "interval" = 'HOUR' and "timestamp" < now() - interval '1 week'; delete from gateway_stats where "interval" = 'DAY' and "timestamp" < now() - interval '1 year';
If a gateway-profile is assigned to the gateway, LoRa Server will push configuration updates to the gateway to keep its channel-plan in sync with the configuration of the network. This is triggered when LoRa Server receives gateway statistics (which also contains the current configuration version of the gateway). If there is new version of the configuration available, then it will be pushed by LoRa Server to the gateway.
Note that this feature must also be configured in the LoRa Gateway Bridge configuration.