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 a field for height #9362

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

Originally created by @mrtn-r on GitHub (Mar 17, 2024).

NetBox version

v3.7.4

Feature type

Data model extension

Proposed functionality

Add a field for "height" in the "Location"-section of the device under "longitude", together with a "units" field.

The "height" field should accept any positive or negative numeric value, while the "units" field should accept anything.
Examples (height; units):

  • "1.5; Level" Height could be a level in a building
  • "-5; m NAP" Physical height with accompanying vertical reference 1

Use case

When having multi-story buildings, latitude and longitude are just not enough to locate a device on a map.

Database changes

Two new fields are required

External dependencies

No response

  1. There are multiple vertical reference points, depending on the country you're in, see for example https://en.wikipedia.org/wiki/Vertical_datum#/media/File:Vertical_references_in_Europe.svg ↩︎

Originally created by @mrtn-r on GitHub (Mar 17, 2024). ### NetBox version v3.7.4 ### Feature type Data model extension ### Proposed functionality Add a field for "height" in the "Location"-section of the device under "longitude", together with a "units" field. The "height" field should accept any positive or negative numeric value, while the "units" field should accept anything. Examples (height; units): - "1.5; Level" Height could be a level in a building - "-5; m NAP" Physical height with accompanying vertical reference [^1] [^1]:There are multiple vertical reference points, depending on the country you're in, see for example https://en.wikipedia.org/wiki/Vertical_datum#/media/File:Vertical_references_in_Europe.svg ### Use case When having multi-story buildings, latitude and longitude are just not enough to locate a device on a map. ### Database changes Two new fields are required ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:49:00 +01:00
adam closed this issue 2025-12-29 20:49:00 +01:00
adam commented 2025-12-29 20:49:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 18, 2024):

This would make sense only for a handful of cases, and would be confusing in others. (What is the "height" of a building or room? Why would we care?) You can add a custom field to the location model in your NetBox deployment to track this information if it makes sense for your use case.

@jeremystretch commented on GitHub (Mar 18, 2024): This would make sense only for a handful of cases, and would be confusing in others. (What is the "height" of a building or room? Why would we care?) You can add a [custom field](https://docs.netbox.dev/en/stable/features/customization/#custom-fields) to the location model in your NetBox deployment to track this information if it makes sense for your use case.
adam commented 2025-12-29 20:49:01 +01:00
Author
Owner
Copy Link

@mrtn-r commented on GitHub (Mar 20, 2024):

Maybe you misread, i meant the location-section of devices, not locations itself.
I mean the locations section where devices got the coordinate fields as it has been implemented for #11305

@mrtn-r commented on GitHub (Mar 20, 2024): Maybe you misread, i meant the location-section of devices, not locations itself. I mean the locations section where devices got the coordinate fields as it has been implemented for #11305
adam commented 2025-12-29 20:49:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 20, 2024):

I'm afraid that doesn't make any more sense. Again, you can add a custom field to hold this data if it makes sense for your specific use case.

@jeremystretch commented on GitHub (Mar 20, 2024): I'm afraid that doesn't make any more sense. Again, you can add a custom field to hold this data if it makes sense for your specific use case.
adam commented 2025-12-29 20:49:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 26, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Mar 26, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 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#9362
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?