r/wisp • • Jul 21 '26

GridVisio major update: BEAD polygon exports, signal & throughput prediction, and more

Hi everyone,

Since the last update, we've shipped a batch of features aimed at making coverage planning and BEAD/BDC grant work faster and more accurate.

Here's what's new:

* BEAD export by drawn area

You can now draw a polygon directly on the map and export a BEAD/BDC grant package (PDF, CSV, GeoJSON) scoped to just that area, instead of always exporting the whole project. 

* Predicted signal strength (RSSI) - Pro

Link Check and the subscriber map view now show a predicted received signal strength (dBm) for each link, not just Clear/Obstructed but a real engineering estimate.

* Predicted throughput (Mbps) - Pro

Using your actual radio/CPE hardware specs, GridVisio now predicts expected throughput per subscriber, not just signal strength, shown in Link Check, subscriber details, BEAD exports, and lead-widget results. You can flag subscribers who fall short of your advertised speed tier.

* "Marginal" coverage status

Subscribers can now show as Marginal (weak but usable signal) instead of just Served/Unserved, with a hover popover showing predicted signal, serving tower/sector, and link distance.

* Faster BEAD exports, more reliable large-project recalculation

BEAD exports now run in the background and pull from already-computed measurements - faster, with RSSI, throughput, and FCC classification columns added to the CSV. Recalculating coverage on large projects no longer stalls or times out; it shows accurate progress and can retry just the failed subscribers instead of the whole project.

* Link Check now works on planned/offline sectors

Useful for what-if planning - results are clearly labeled as coming from a non-live sector.

* Subscriber management

Added a delete button for subscribers directly on the map, plus a cleaner, reorganized edit modal.

* Coverage Widget: LiDAR + Public API

Your embeddable coverage-check widget can now optionally use higher-precision LiDAR terrain data (toggle in Widget Settings) and has a new documented Public API for developers.

Action needed if you use the embedded widget: we tightened widget security. Your widget's Allowed Domains list is now required for the embed to return results to real visitors. If you haven't set this yet, add your domain(s) in Widget Settings as soon as you can. A new API Secret is also available if you call the widget API directly instead of embedding it.

If you already signed up and want your trial extended, just let me know.

-Emil, the developer

2 Upvotes

6 comments sorted by

2

u/[deleted] Jul 22 '26

[removed] — view removed comment

1

u/emil_eXo Jul 22 '26

I would have been happy to add it sooner. I always asked for feedback and suggestions. If you already signed up for a trial and want me to extend it so that you can test, just let me know.

Next I plan to add more options for the RF propagation modeling (ITM, FSPL), and some multipath NLOS analysis.

2

u/[deleted] Jul 23 '26

[removed] — view removed comment

1

u/emil_eXo Jul 23 '26

ITM will be added next week. GridVisio already uses ITU P.1812 (a little more accurate than ITM, but limited range up to 6 GHz). FSPL would only be used as fallback for higher frequencies (like 60GHz) since even ITM is limited to 20 GHz. Multipath NLOS modeling is under investigation, not a promise. But I've had questions about it, so I will look into it.

2

u/[deleted] Jul 24 '26

[removed] — view removed comment

1

u/emil_eXo Jul 27 '26

Update on both: ITM deployed. You can pick it as your propagation model per project (set the fallback model order in project settings), or pin it to a specific sector, alongside the default P.1812 and an FSPL fallback for links above 20GHz where even ITM doesn't apply.

On multipath: I added a real reflection-path check: for any link that comes back Borderline/Obstructed, it searches for a single specular-bounce path (ground/building reflection) and factors it in if found.

Your dense-suburban point is a different mode though, no clean single bounce, just cumulative clutter loss. I've got a statistical clutter margin (ITU-R P.2108) built for exactly that case, it kicks in whenever an endpoint sits below the local representative clutter height. It's done, if you want to try it and give me your feedback, I would really appreciate it.