# Gateway location change and ttnmapper data **URL:** \ **Category:** Gateways\ **Created:** [May 1, 2018, 1:27pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-location-change-and-ttnmapper-data/13572 "2018-05-01T13:27:18Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![jpmeijers](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jpmeijers/32/44875_2.png) [@jpmeijers](https://www.thethingsnetwork.org/forum/u/jpmeijers)\ **Post date:** [May 4, 2018, 8:15am UTC](https://www.thethingsnetwork.org/forum/t/gateway-location-change-and-ttnmapper-data/13572/6 "2018-05-04T08:15:26Z")
All measurements are hidden when a gateway is moved to a new location (excluding GPS drift within a 100m area). When configuring your gateway’s location, please follow this logic flow to prevent confusion where the location information comes from: > [@Gateway GPS configuration in local\_conf.json](https://www.thethingsnetwork.org/forum/t/gateway-gps-configuration-in-local-conf-json/6176): > > Tags: location, gps, coordinates, local\_conf [image] To be consistent with the GPS coordinates for a gateway, we need to standardise the flow and origin of manually set coordinates. The flowchart above basically says that coordinates should always be set on the TTN console, unless the gateway has a GPS. In all other cases you should configure the gateway in such a way that either it does not send coordinates to the backend, in which case the coordinates from the console will be used, or fetch … Gateways are only shown on TTN Mapper by default if there are measured points for it. So you are right to see it hidden after the move. Do not delete and re-add your gateway on the console. You will not be able to re-register a gateway with the same ID on the current version of the console. --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/gateway-location-change-and-ttnmapper-data/13572)._