From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Here's how the Broadband Fabric should be built.
Date: Wed, 10 May 2023 07:46:49 -0700 [thread overview]
Message-ID: <CAA93jw5KinP9-PpkO-DLecVzMG_dc+Boc98idOB9L78CbEVDJA@mail.gmail.com> (raw)
In-Reply-To: <699f0e1d-e6ae-2489-b307-5676c6f5059e@thexlab.org>
[-- Attachment #1: Type: text/plain, Size: 2939 bytes --]
---------- Forwarded message ---------
From: Sascha Meinrath <sascha@thexlab.org>
Date: Wed, May 10, 2023 at 7:30 AM
Subject: Here's how the Broadband Fabric should be built.
To: National Broadband Mapping Coalition <bbcoalition@marconisociety.org>
Hi Everyone,
A national team of GIS experts have been collaborating on an open source,
address-level, free broadband availability map -- the PA beta is now live
here:
https://internetxplorer.org
***
As you will quickly see, the map has information down to the address level
--
and it enables easy zooming to whichever level you're interested in (unlike
the
FCC's map). *AND* we have also pointed out households that *should* be in
the
Fabric but are not (along with a bunch of highway mile markers that will
need to
be cleaned out -- an artifact of pulling locations from E911 databases).
Most of
the Turquoise dots represent challenges that should have been made -- and
there
are areas in North Central and SW PA where there are thousands upon
thousands of
households currently missing from the Fabric data.
This map is freely and publicly available for non-commercial use, and it's
built
with open source code -- so we'd welcome both collaborators, re-use by more
states, inquiries from devs who want to help, as well as your feedback
(there's
a handy "reach out" link at the top of the map that'll e-mail the team).
The dev team is particularly keen to accelerate additional features (e.g.,
drawing an arbitrary polygon and having it compute # of households, # & %
unserved, # & % underserved; and mash-ups with demographic data from the
2020
census [which would enable the first-ever empirical look at de facto
digital
redlining]).
Long story short, this was pulled together by an independent team because
the
country and state continues to misappropriate funding for disastrously
unusable
broadband maps. We wanted to back up our critique by demonstrating what is
possible. This particular map is purpose-built to show eligible areas for
the PA
Capital Project Fund RFP (coming out today), but it serves as an exemplar
showing how feasible building an free and open, accessible, cheaper, and
more
usable map actually is.
I hope folks like it.
Best,
--Sascha
--
Sascha Meinrath
Director, X-Lab
Palmer Chair in Telecommunications
Penn State University
--
You received this message because you are subscribed to the Google Groups
"National Broadband Mapping Coalition" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to BBCoalition+unsubscribe@marconisociety.org.
To view this discussion on the web visit
https://groups.google.com/a/marconisociety.org/d/msgid/BBCoalition/699f0e1d-e6ae-2489-b307-5676c6f5059e%40thexlab.org
.
--
Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 4126 bytes --]
next parent reply other threads:[~2023-05-10 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b5e9e68a-a766-2ae9-f520-bb451556b761@thexlab.org>
[not found] ` <699f0e1d-e6ae-2489-b307-5676c6f5059e@thexlab.org>
2023-05-10 14:46 ` Dave Taht [this message]
2023-05-11 19:50 ` dan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5KinP9-PpkO-DLecVzMG_dc+Boc98idOB9L78CbEVDJA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox