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

HIP 135: Transitioning to Templated MOBILE Coverage #1100

Open
abhay opened this issue Oct 9, 2024 · 0 comments
Open

HIP 135: Transitioning to Templated MOBILE Coverage #1100

abhay opened this issue Oct 9, 2024 · 0 comments
Labels
discussion economic Economic HIP MOBILE technical Technical HIPs updates edits/updates to an existing HIP voting now

Comments

@abhay
Copy link
Contributor

abhay commented Oct 9, 2024

HIP 135: Transitioning to Templated MOBILE Coverage


Summary

This HIP retroactively approves and updates the base coverage points of the emergency coverage templates that were deployed by Nova Labs as a result of a likely permanent outage in the Google Network Planner API that was previously relied on for the creation of modeled coverage objects. Specifically we propose using the median value of base CPs for all deployments of each radio/antenna type as the basis for deriving these templated coverage objects. These templated coverage objects have no impact on oracle hex multipliers or overlapping coverage and simply replace the clutter-adjusted objects previously provided by the Google Planner API.

Rendered View

https://github.com/helium/HIP/blob/main/0135-transitioning-to-templated-mobile-coverage.md

@waveform06 waveform06 added discussion updates edits/updates to an existing HIP technical Technical HIPs economic Economic HIP MOBILE voting soon voting now and removed voting soon labels Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion economic Economic HIP MOBILE technical Technical HIPs updates edits/updates to an existing HIP voting now
Projects
None yet
Development

No branches or pull requests

2 participants