Posted February 18th, 2011 by Michael Byrne - Geographic Information Officer
Posted in Data , Developer , Api , Maps
Posted February 17th, 2011 by Anne Neville - Director, State Broadband Initiative – NTIA
Welcome to the first-ever public, searchable nationwide map of broadband access.
The National Broadband Map is an unprecedented project created by NTIA, in collaboration with the FCC, and in partnership with each state, territory and the District of Columbia. We created the map at the direction of Congress, which recognized that economic opportunities are driven by access to 21st Century infrastructure.
With funding from NTIA’s State Broadband Data & Development Program, our state partners have gathered and worked to validate broadband data from thousands of providers across the country. Together, we developed a dataset and website that includes more than 25 million searchable records displaying where broadband Internet service is available, the technology used to provide the service, the maximum advertised speeds of the service, and the names of the broadband providers. Whether you are a consumer seeking more information on the broadband options available to you, a researcher or policymaker working to spur greater broadband deployment, a local official aiming to attract investment in your community, or an application developer with innovative ideas, the National Broadband Map can help. And if you don’t find the answer you’re looking for on the map itself, you can download the entire dataset.
Posted in Wireless , Open Government , National Broadband Plan , Data , Developer , Api , Maps
While the launch of this map is a huge accomplishment, today is just the beginning. Our partners in the states are working to expand and update this important dataset, and we will update the map with new data every six months. In the meantime, you can help. Each time you search the map, you have the opportunity to tell us about the data you’re seeing. This crowdsourced feedback will be an important tool to improve and refine the data.
We invite you to explore the many features and functionalities the National Broadband Map offers. To start, search for broadband by address. Or go straight to our analysis tools and compare one area to others, and make sure you spend some time with our maps. Want more? Download the dataset, use our APIs and please tell us how you’re using the data.
We expect the map will be a valuable tool as we work to bridge the technological divide, expand economic opportunities, and leverage the power of broadband to address many of the nation’s most pressing challenges. We hope you will make full use of its capabilities and let us know what you think and how we can improve.
Posted February 16th, 2011 by Michael Byrne - Geographic Information Officer
We’re really proud and humbled by the splash that IssueMap made last week. Thanks to the team at FortiusOne for rolling out a high-quality product that obviously hit the mark.
It’s exciting to see some of the cool IssueMaps that are shared over social networks. You can follow @IssueMap on Twitter to catch the shared IssueMaps published there. We’ve also put up a new Reboot page that collects a few FCC data sets and maps them on IssueMap.
We continue to hold strong to the belief that -- done right -- mapping will significantly change the way we understand data, solve problems, and tell compelling stories.
Here are some of the different angles on IssueMap:
Posted in Reform - Redesign , Open Government , Reform - Data , Data , Developer , Api , Maps
Keep posting your IssueMaps, and stay tuned for more mapping news very soon.
Posted January 14th, 2011 by James Brown - Wireless Telecommunications Bureau
Today the Federal Communications Commission released two new Application Programming Interfaces (APIs) on our developer page at fcc.gov/developer. The new APIs leverage data from the Spectrum Dashboard and provide the developer community with direct access to these assets.
Managing spectrum is one of the FCC's primary responsibilities. These APIs are tools that unlock our substantial databases related to spectrum ownership, spectrum use, and spectrum capabilities at different locations.
Below is snapshot of the two APIs.
When we released the first set of APIs back in September, we did so as part of our Data Innovation Initiative efforts towards better data transparency and open government. We continue with those efforts by releasing the second set of APIs today.
Your feedback has been essential to improving these API releases and making them more valuable to developers in the wild (see previous conversations here and here). Let us know what uses you might have for APIs like these, recommended tweaks, or suggest APIs you want to see in the future.Posted in Wireless Telecommunications Bureau , Wireless , Open Government , Spectrum Dashboard , Reform - Data , Data , Developer , Api
Posted January 5th, 2011 by Steven VanRoekel - Managing Director, Federal Communications Commission
For months, we've been hearing from a committed community of citizens that care deeply about preserving the foundational principles of the Internet.
Many of the same people have been involved with the FCC over the last few months through our FCC.gov Developer community. Now that the FCC has released the Open Internet order, we’re calling on that developer community to help us meet a new challenge.
The Open Internet Apps Challenge, released by the FCC, asks this community -- particularly the researchers and developers -- to help build the strongest safeguards possible to preserve these principles and innovate online.
This is an opportunity for the FCC to tap talent in a variety of fields -- technology development, research, monitoring, and more -- to build a powerful toolkit that protects and informs consumers. These software tools could, for example, detect whether a broadband provider is interfering with DNS responses, application packet headers, or content.
The winners of this challenge will have their work widely seen and used. We think that there a number of interesting opportunities in this challenge, particularly for researchers with deep experience in highly-technical and specified fields of industry and academia.
We've called on the FCC Developer community before, like the Open Developer Day we hosted in October, and this challenge presents a new opportunity for the agency to partner with innovators and researchers working towards important goals.
Check out all the details for the Open Internet Apps Challenge at Challenge.gov.
Posted December 7th, 2010 by Steven VanRoekel - Managing Director, Federal Communications Commission
In the modern federal landscape, the FCC finds itself increasingly at the intersection of technology, law, and citizen participation. It’s a challenging place to be -- these arenas change quickly, and move in ways that advancements in one ripple out and can change the others. But the opportunity to make progress on these fronts has never been greater.
Modernizing the rulemaking process -- keeping up with these changes to best serve the American public -- was the focus of an event hosted by the Brookings Institute last week. As an invited member of the Digitization – Past, Present, and Short-Term Future panel , I spoke about two key benefits that new technology offers to the rulemaking process.
First, erulemaking can make government work smarter. Moving from a largely paper-based system -- the norm very recently -- to a digital system has led to a rulemaking process that’s accessible, searchable and less weighed down by troves of paperwork.
Second, moving rulemaking online has allowed the FCC to open a process that was closed for too long. Traditionally, access to rulemaking required access to the expert legal mechanisms typically out of the reach of most citizens, yet the rules we are creating are created for all and often impact people who don’t have access to legal support. We’ve made strides on this front - You may be familiar with our online comment crowdsourcing platforms, the ability to integrate blog comments into the public record, and our other moves to make the FCC process as open as possible – there’s more to come.
Something most people don’t know: the FCC is also developing ways to help citizens that lack access to the Internet participate in rulemakings remotely via voicemail, powered by increasingly accurate speech-to-text technologies. It’s another way that the spirit of open government is pushing us to tinker with the process, open up closed structures, and empower citizen experts to meaningfully engage with rulemaking.
With the help of open technologies, agencies like the FCC increasingly find themselves as repositories of valuable insight generated by citizen experts. New technology makes that information available as data outputs that are easily shared, syndicated, and mashed-up against other data sets. As part of our team’s effort to reimagine a new FCC.gov, we’re revamping the Electronic Comment Filing System that allows for bulk download, RSS subscription to particular rulemakings, and infusing our own processes more with the web services model that’s ubiquitous in the modern Internet.
An open and participatory FCC is in line with the spirit of President Obama’s Open Government Directive -- passed one year ago today -- that is creating a more open, transparent, and participatory government.
On this anniversary, we think it is worth looking back and compiling the agency’s open government accomplishments. Take a look, then add your voice in the comments and help us continue improving the FCC’s rulemaking process.
Posted November 18th, 2010 by James Brown - Wireless Telecommunications Bureau
On Wednesday, November 17, the first in a series of enhancements to the Spectrum Dashboard were released. Along with this release, we are excited to announce that the Dashboard is no longer in beta.
The response we’ve received about the Dashboard has been remarkably positive and in the eight short months since its initial release, almost 200,000 searches have been conducted. To crunch those numbers further – the Dashboard is being searched about 25,000 times a month or in other words, 800 times a day. Wow! What’s more impressive is the volume of activity has been pretty consistent month-to-month.
While this week’s release may not be the biggest or the flashiest, it is however, the starting point for bigger and better things to come. For example, in the next few months, the Dashboard will include additional releases to track leased spectrum, search for licenses across tribal lands, customize maps, and use Application Program Interfaces (APIs) to access data from the Dashboard. We don’t plan to stop there. We will continue to evaluate potential candidates for future enhancements.
Here are some of the changes to the Dashboard released this week.
• Advanced Search. The Advanced Search replaces the “License Categories” search and includes several different search criteria located at the same place, including the ability to search for licenses by channel block. For example, a user can search for all of the licenses in the 700 MHz band or can tailor a search by only searching for A-block licenses in the 700 MHz band.
• Auto Complete for Name Search. The auto complete function allows a user to search by a name and the Spectrum Dashboard will display all names that include the string of letters/characters entered. For example, by entering “Wire,” a list of all names that include “Wireless” will be displayed.
• Changes to Filters. The filters have been enhanced to allow a user to open and close filters, as they deem appropriate and to include an additional filter for channel blocks.
• Downloading Results. When a user downloads results by clicking on the “Export Results” link, the results will download automatically if the results are 65,000 rows or less. If the results are more than 65,000 rows a user will receive an e-mail when the results are available.
We are looking forward to improving the Dashboard even more and encourage you to continue providing feedback.
Posted November 12th, 2010 by Greg Elin - Chief Data Officer
On Monday, November 11, the FCC successfully held (we think) a first-of-its-kind event in the U.S. federal government!
FCC Open Developer Day attracted about 100 web developers and other technology professionals to our headquarters building in Washington. We spent a day learning about open data sets and APIs, brainstorming together about how they could be combined to benefit citizens with new apps, and starting coding projects toward those goals.
One focus of FCC Open Developer Day was accessible technology. By facilitating the use of fully-accessible technologies - in line with the FCC’s support for our Accessibility and Innovation Initiative - the FCC is promoting innovation and collaborative problem-solving in the field. One exciting fact: FCC Open Developer Day marked the first time many developers in attendance sat and chatted as a group with others using assistive technologies.
The most valuable take-away from this first foray was the opportunity to build the FCC developer community. The momentum from this event will hopefully help bring the popular activity of Developer Day and "hack-a-thons" to the a federal agency. We were grateful, and a bit surprised, at the number of people who came in from out of town to this event. It was incredibly exciting to the see the Commission Meeting Room, usually set up for formal hearings and presentations, organized in tables for eight people and laptops plugged into power strips.
Here are some cool things we got from having the event:
One day is too short to get much hacking done, so we are planning to do more developer days to make them a regular activity at the FCC.
P.S. Eager to participate in a gov-related developer day? December 4 is International Open Data Hackathon. FCC will be there. Will you?
(This is cross-posted on Blogband. Please leave your comments there.)Posted in Reform - Redesign , Events , Open Government , Data , Developer , Api , Accessibility
Posted November 9th, 2010 by Steven VanRoekel - Managing Director, Federal Communications Commission
In a packed Commission Meeting Room on Monday, a coalition of tech developers and accessibility advocates made FCC history.
By organizing and hosting the FCC’s first Open Developer Day – one of the first of its kind in the federal government, and the first hosted at a federal HQ – the Commission took another big step towards realizing the full potential of the broad community of folks that FCC data and FCC tools have the potential to impact.
The success of the event proved that citizen developers are eager to engage in open collaboration with the FCC to find innovative uses for government data. Cooperative efforts like this help find efficiencies for users, open the door to new economic and creative opportunities, and stretch the value of the .gov dollar in ways we’re continuing to explore.
Open Developer Day also highlighted the ways that FCC initiatives can create efficiencies across the landscape of other government agencies – a pillar of the Gov 2.0 approach. The long-term success of these methods depends on agencies’ ability to cultivate an active community. I think this event shows us that we’ve made a great start, and we’re learning how we continue to improve on the steps we’ve taken so far.
Our own wrap up of Open Developer Day is coming, but I wanted to share this great video interview shot in our new, soon-to-be-released FCC TEC lab. O’Reilly Media’s Alex Howard sat down with Gina Trapani – a Developer Day veteran herself – to talk about the take-aways from the event. If you attended in person, watched via the livestream, or participated on the #fccdevday hashtag, leave your thoughts in the comments below. Tell us what you thought worked well, or pass on your ideas for the next FCC Open Developer Day for us to read.
Posted October 13th, 2010 by Michael Byrne - Geographic Information Officer
Based on your comments and suggestions, we've just released updates to our FCC.gov/developer API’s. In particular we have made two enhancements: one to help navigate the complexities of census geography, and one that's purely stylistic.
Census geography changes, while small or obscure, can be significant. A tiny change in a census boundary can mean that a rate based calculation includes a completely different denominator for population or demographic value. These changes, if not watched for carefully can be significant to the results of querying large federal databases.
To assist the community of developers building off FCC tools, we'll try and point out these small but significant changes when we see them.
The biggest change between 2000 census boundaries and 2009 census boundaries was the addition of a sub identifier to the smallest unit of boundary, the block. This addition allows for finer resolution to the map base. However, because of other changes like population growth, demographic switches, and land use changes, the external boundaries of the block boundaries have also changed.
In order to keep up with these issues, we are supplementing our FCC Census Block API with the ability to query for the current year as well as previous years. From now on, the current (e.g. 2009) year search will be the normal REST query on the documentation page like this;
To gain access to a previous year, all you need to do is insert the year in the url like this;
The stylistic change we made removes the @ symbol from the return, moving to a natural JSON notation to allow for better integration with some client libraries.
These changes are live now. Here's a preview of /Developer updates coming down the pipeline:
See below for a more complete description of the most recent changes. Happy Coding, and don’t forget to let us know what kind of applications you are building with FCC Developer tools.
1)Changed JSON output to follow the natural convention for Block and Speed Test APIs. This changes the output from:
Please note that the @ symbol has been removed from the attributes within a JSON object. This should make it easier for these data structures to be consumed from some libraries such as jQuery.
2) Added version year for census block geospatial search
There is an additional option to request Census Block data for Census 2000. The original call will return the most recent Census Block information (2009)
Original query for Census information (current information)
<Response executionTime="0.054" status="OK">
<County name="Merced" FIPS="06047"/>
<State name="California" code="CA" FIPS="06"/>
Census 2000 block information
<Response executionTime="0.052" status="OK">
<County name="Merced" FIPS="06047"/>
<State name="California" code="CA" FIPS="06"/>
3) Fixed the following bug
When passing wrong coordinate information (i.e. outside of the U.S. and territories) the response returned a badly formed XML if no format for the response type was specified.