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

Add GPS position of rack #2789

New Issue
Closed
opened 2025-12-29 18:22:10 +01:00 by adam · 6 comments
adam commented 2025-12-29 18:22:10 +01:00
Owner
Copy Link

Originally created by @chas0rde on GitHub (Aug 7, 2019).

Proposed Functionality

Extend the Longitude / Latitude feature of sites to racks

Use Case

We use Netbox for Datacenter and IDF documentation
It would be handy to also link the GPS position to the rack (in our case the IDF) so netbox (as a single source of truth) might hold that information for other systems that allow mapping to positions of the components

Originally created by @chas0rde on GitHub (Aug 7, 2019). ### Proposed Functionality Extend the Longitude / Latitude feature of sites to racks ### Use Case We use Netbox for Datacenter and IDF documentation It would be handy to also link the GPS position to the rack (in our case the IDF) so netbox (as a single source of truth) might hold that information for other systems that allow mapping to positions of the components
adam closed this issue 2025-12-29 18:22:10 +01:00
adam commented 2025-12-29 18:22:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2019):

Can you describe a use case where you know the site at which a rack exists, but cannot locate it using any means other than GPS coordinates?

@jeremystretch commented on GitHub (Aug 7, 2019): Can you describe a use case where you know the site at which a rack exists, but cannot locate it using any means other than GPS coordinates?
adam commented 2025-12-29 18:22:11 +01:00
Author
Owner
Copy Link

@chas0rde commented on GitHub (Aug 8, 2019):

We structure as follows:
Regions: DE > Campus
Sites: Building on Campus
Rack group: Set for datacenters
Rack: Rack in Datacenter, IDF for rest of buildings

This way we are able to document datacenter as well as campus cabling with netbox

So a building (site) might be 3000sqm in size (with machinery in it and so-forth) and have some racks (maybe 3 IDFs) located at different specific positions within the building.

So if the rack would have a (precise) GPS location this would make a big difference to the sneaker-admin getting send somewhere to e.g. patch some port.

@chas0rde commented on GitHub (Aug 8, 2019): We structure as follows: Regions: DE > Campus Sites: Building on Campus Rack group: Set for datacenters Rack: Rack in Datacenter, IDF for rest of buildings This way we are able to document datacenter as well as campus cabling with netbox So a building (site) might be 3000sqm in size (with machinery in it and so-forth) and have some racks (maybe 3 IDFs) located at different specific positions within the building. So if the rack would have a (precise) GPS location this would make a big difference to the sneaker-admin getting send somewhere to e.g. patch some port.
adam commented 2025-12-29 18:22:11 +01:00
Author
Owner
Copy Link

@millijuna commented on GitHub (Aug 13, 2019):

This would be useful for me as well. I'm using Netbox to track the IDFs and other gear across a 25 acre/10 hectare campus. I tread the main campus as one site, and our remote gear off-campus as different sites.

Within the campus itself, I can generally locate everything based on a building name/room description. However, in continuing with the mantra of "Source of Truth" having geographical coordinates would allow the linking into OpenStreetmap or similar to produce a visual representation.

@millijuna commented on GitHub (Aug 13, 2019): This would be useful for me as well. I'm using Netbox to track the IDFs and other gear across a 25 acre/10 hectare campus. I tread the main campus as one site, and our remote gear off-campus as different sites. Within the campus itself, I can generally locate everything based on a building name/room description. However, in continuing with the mantra of "Source of Truth" having geographical coordinates would allow the linking into OpenStreetmap or similar to produce a visual representation.
adam commented 2025-12-29 18:22:12 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Aug 13, 2019):

This sort of thing is a fringe use case. Can you please explain why custom fields would not cover your needs? This is exactly why they exist.

@lampwins commented on GitHub (Aug 13, 2019): This sort of thing is a fringe use case. Can you please explain why custom fields would not cover your needs? This is exactly why they exist.
adam commented 2025-12-29 18:22:12 +01:00
Author
Owner
Copy Link

@chas0rde commented on GitHub (Aug 14, 2019):

Of course it could be done with custom field. But so could it be on sites ;)
My point is that with coordinates being on rack other things for visualization would also become possible (e.g. floor plans)

@chas0rde commented on GitHub (Aug 14, 2019): Of course it could be done with custom field. But so could it be on sites ;) My point is that with coordinates being on rack other things for visualization would also become possible (e.g. floor plans)
adam commented 2025-12-29 18:22:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2019):

Of course it could be done with custom field. But so could it be on sites ;)

Tracking the GPS coordinates for individual sites is a far more common use case than for individual racks, which is why the site model has these fields built-in and the rack model does not. I'm going to pass on this one since it seems like a pretty niche requirement, and as @lampwins points out can be met using custom fields anyway.

@jeremystretch commented on GitHub (Aug 15, 2019): > Of course it could be done with custom field. But so could it be on sites ;) Tracking the GPS coordinates for individual sites is a _far_ more common use case than for individual racks, which is why the site model has these fields built-in and the rack model does not. I'm going to pass on this one since it seems like a pretty niche requirement, and as @lampwins points out can be met using custom fields anyway.
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
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#2789
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?