starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Device GPS Coordinates #7418

New Issue
Closed
opened 2025-12-29 20:23:10 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:23:10 +01:00
Owner
Copy Link

Originally created by @arjenvri on GitHub (Dec 24, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.4.1

Feature type

Data model extension

Proposed functionality

Add fields latitude and longitude to the device model

Use case

Currently site coordinates are well supported. For mapping of the physical location of devices like access points and non rack mount switches it would be very useful to have similar functionality for the device model.
It would allow to create floorplans based on device data in netbox. Especially with larger sites knowing that an access point is in a site is not enough to find the device.

Database changes

No response

External dependencies

No response

Originally created by @arjenvri on GitHub (Dec 24, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.4.1 ### Feature type Data model extension ### Proposed functionality Add fields latitude and longitude to the device model ### Use case Currently site coordinates are well supported. For mapping of the physical location of devices like access points and non rack mount switches it would be very useful to have similar functionality for the device model. It would allow to create floorplans based on device data in netbox. Especially with larger sites knowing that an access point is in a site is not enough to find the device. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 20:23:10 +01:00
adam closed this issue 2025-12-29 20:23:10 +01:00
adam commented 2025-12-29 20:23:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 27, 2022):

Adding GPS coordinate fields to the rack model was proposed under #3406 a few years back and rejected as impractical. I feel the same arguments apply to this proposal.

If anything, it might make sense to add GPS coordinates to a location (which was previously known as a "rack group"), which seems like it would be more practical than trying to specify the exact position of each device.

(Also note that decimal custom fields can be used for this purpose in the absence of core support.)

@jeremystretch commented on GitHub (Dec 27, 2022): Adding GPS coordinate fields to the rack model was proposed under #3406 a few years back and rejected as impractical. I feel the same arguments apply to this proposal. If anything, it _might_ make sense to add GPS coordinates to a location (which was previously known as a "rack group"), which seems like it would be more practical than trying to specify the exact position of each device. (Also note that decimal custom fields can be used for this purpose in the absence of core support.)
adam commented 2025-12-29 20:23:10 +01:00
Author
Owner
Copy Link

@arjenvri commented on GitHub (Dec 27, 2022):

Thank you, understood. I feel that for access points this is less ideal since one location has possibly many access points. Maybe this makes more sense to add now that wireless is part of the core data model as well ☺️

@arjenvri commented on GitHub (Dec 27, 2022): Thank you, understood. I feel that for access points this is less ideal since one location has possibly many access points. Maybe this makes more sense to add now that wireless is part of the core data model as well ☺️
adam commented 2025-12-29 20:23:11 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 28, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 28, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:23:11 +01:00
Author
Owner
Copy Link

@stuntguy3000 commented on GitHub (Apr 3, 2023):

Looking at wireless control systems like Meraki, you get highly functional maps where access points are laid out according to their GPS positioning.

Very handy stuff and something I can see being valuable in Netbox with a lot of expansion potential. e.g. wireless maps and coverage charts.

@stuntguy3000 commented on GitHub (Apr 3, 2023): Looking at wireless control systems like Meraki, you get highly functional maps where access points are laid out according to their GPS positioning. Very handy stuff and something I can see being valuable in Netbox with a lot of expansion potential. e.g. wireless maps and coverage charts.
adam commented 2025-12-29 20:23:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 5, 2023):

I do think the AP use case is compelling.

@jeremystretch commented on GitHub (Apr 5, 2023): I do think the AP use case is compelling.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7418
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?