docs: nest 19 files into audit/ clients/ infrastructure/ monitoring/ projects/ super-search/
This commit is contained in:
@@ -0,0 +1,60 @@
|
||||
# CoverZone — WISP Coverage Planning Analysis
|
||||
> Domain: coverzone.com (available)
|
||||
|
||||
## Source
|
||||
GridVisio (https://gridvisio.com) — discovered via WISPA community, Aug 7 2026.
|
||||
|
||||
## What It Is
|
||||
Browser-based coverage planning tool targeting small WISPs priced out of enterprise tools.
|
||||
Community-driven development — updates come directly from WISP feedback.
|
||||
|
||||
## Pricing
|
||||
| Tier | Price | Limits |
|
||||
|---|---|---|
|
||||
| Free | $0 | 1 project, 5 towers, 100 subscribers |
|
||||
| Starter | $19/mo | 3 projects, 20 towers, 1,000 subscribers |
|
||||
| Pro | $39/mo | Unlimited everything |
|
||||
| Trial | 14 days | No credit card required |
|
||||
|
||||
## Features
|
||||
### Core
|
||||
- Tower + sector antenna management (azimuth, beamwidth, radius) on Google Maps satellite
|
||||
- CSV subscriber import — auto-served/unserved classification
|
||||
- Hypothetical tower placement with unserved subscriber coverage simulation
|
||||
- White area detection — DBSCAN clustering identifies coverage gaps
|
||||
- Coverage overlap analysis — detect same-frequency sector interference
|
||||
- Drive test overlay — import GPS signal logs, see real vs planned coverage
|
||||
- Shareable read-only map links for clients (no login required)
|
||||
- LoS link check with Fresnel zone, PDF export, elevation data (SRTM, Copernicus GLO-30)
|
||||
- Lambert coordinate converter (WGS84 ↔ Lambert 72/2008/2005)
|
||||
- KMZ / PDF / PNG / XLSX / CSV export
|
||||
- BDC / BEAD grant filing export
|
||||
- Team collaboration with viewer/editor roles
|
||||
- Coverage Widget — embeddable in client websites for instant location coverage check
|
||||
|
||||
### Propagation Models (added based on WISP community feedback)
|
||||
- **ITM (Longley-Rice)** — selectable per-project and per-sector
|
||||
- **ITU-R P.1812** — default model
|
||||
- **FSPL + ITU-R P.526 diffraction** — automatic fallback for links above 20GHz where P.1812 and ITM don't apply
|
||||
|
||||
### Multipath/NLoS Handling (community-driven additions)
|
||||
- **Reflection-path check** — specular bounce candidate (ground/building) for Borderline/Obstructed links, non-coherently combined with direct path
|
||||
- **ITU-R P.2108** — statistical clutter-loss margin for dense suburban/urban links, implemented from the Recommendation's own equations
|
||||
- **ITU-R P.530 fade margin** — for Clear links, temporal/weather-driven multipath via ITU-Rpy for geoclimatic factor derivation
|
||||
|
||||
## Relevance to IT Pro Partner
|
||||
- Forefront Wireless is a WISP client — coverage planning tools are directly applicable
|
||||
- Existing CCR tower backup infrastructure could feed a competing product
|
||||
- Coverage Widget is a natural upsell for WISP client websites we host
|
||||
- Market gap: small WISPs priced out of enterprise tools, served by a community-responsive developer
|
||||
|
||||
## Competitive Angle
|
||||
- GridVisio is community-driven — feature velocity is high, trust is earned through WISPA engagement
|
||||
- Weakness: single developer? Small team? Could be out-executed by a faster, better-funded competitor
|
||||
- Opportunity: white-label or acquire if the developer doesn't have MSP/sales infrastructure to scale
|
||||
|
||||
## Questions for Later
|
||||
1. Who built it? Solo dev or team?
|
||||
2. What's their stack? (Google Maps API + browser-based = high API costs at scale?)
|
||||
3. Is the embeddable widget the real moat? (client-facing, no-login-required)
|
||||
4. Could we build a better version using our existing WISP tower data + MikroTik integrations?
|
||||
Reference in New Issue
Block a user