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

Increase location precision #11837

New Issue
Closed
opened 2025-12-29 21:50:29 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:50:29 +01:00
Owner
Copy Link

Originally created by @SloCompTech on GitHub (Nov 17, 2025).

NetBox version

v4.3.6

Feature type

Data model extension

Proposed functionality

Can please latitude and longitude fields precision be extended to at least 8 decimal places ?

Use case

When documenting wireless device locations, correct and precise location is required, so line of sight, distance calculations can be preformed.

Database changes

Fields in models need to change max_digits and decimal_places. No fields will be added/removed.

External dependencies

None.

Originally created by @SloCompTech on GitHub (Nov 17, 2025). ### NetBox version v4.3.6 ### Feature type Data model extension ### Proposed functionality Can please *latitude* and *longitude* fields precision be extended to at least 8 decimal places ? ### Use case When documenting wireless device locations, correct and precise location is required, so line of sight, distance calculations can be preformed. ### Database changes Fields in models need to change `max_digits` and `decimal_places`. No fields will be added/removed. ### External dependencies None.
adam added the type: featurenetbox labels 2025-12-29 21:50:29 +01:00
adam closed this issue 2025-12-29 21:50:29 +01:00
adam commented 2025-12-29 21:50:29 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Nov 17, 2025):

The current 6 decimal places gets you within 11.1cm of precision (reference), which is realistically at the limit of what commercial GPS devices are capable of, especially indoors. Even if you could measure more precisely, it's unlikely that you could do so accurately. We actually went through and normalized all of our coordinates to 6 decimal places specifically because anything beyond that just gave a false sense of accuracy. Going to 8 decimal places takes you down to 1.11mm of precision, which not only seems excessive for your use case, but implies a level of accuracy that would be next to impossible to achieve.

@sleepinggenius2 commented on GitHub (Nov 17, 2025): The current 6 decimal places gets you within 11.1cm of precision ([reference](https://en.wikipedia.org/wiki/Decimal_degrees)), which is realistically at the limit of what commercial GPS devices are capable of, especially indoors. Even if you could measure more precisely, it's unlikely that you could do so accurately. We actually went through and normalized all of our coordinates to 6 decimal places specifically because anything beyond that just gave a false sense of accuracy. Going to 8 decimal places takes you down to 1.11mm of precision, which not only seems excessive for your use case, but implies a level of accuracy that would be next to impossible to achieve.
adam commented 2025-12-29 21:50:30 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Nov 19, 2025):

I concur with @sleepinggenius2. Unless you can document a use case that requires this level of precision, then I don't think this FR makes sense.

@jnovinger commented on GitHub (Nov 19, 2025): I concur with @sleepinggenius2. Unless you can document a use case that requires this level of precision, then I don't think this FR makes sense.
adam commented 2025-12-29 21:50:30 +01:00
Author
Owner
Copy Link

@SloCompTech commented on GitHub (Nov 23, 2025):

Thanks for the explanation.

@SloCompTech commented on GitHub (Nov 23, 2025): Thanks for the explanation.
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 netbox 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#11837
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?