Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device GPS Coordinates #11305

Closed
arjenvri opened this issue Dec 24, 2022 · 5 comments
Closed

Device GPS Coordinates #11305

arjenvri opened this issue Dec 24, 2022 · 5 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@arjenvri
Copy link

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

@arjenvri arjenvri added the type: feature Introduction of new functionality to the application label Dec 24, 2022
@jeremystretch
Copy link
Member

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 jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Dec 27, 2022
@arjenvri
Copy link
Author

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 ☺️

@github-actions
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Mar 28, 2023
@stuntguy3000
Copy link
Contributor

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.

@jeremystretch
Copy link
Member

I do think the AP use case is compelling.

@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Apr 5, 2023
@jeremystretch jeremystretch added this to the v3.6 milestone May 5, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels May 5, 2023
@arthanson arthanson self-assigned this May 31, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

4 participants