Pages

• #40739 (no title)
• 2020 Goal
• AAPI Data Catalog
• About Data.gov
• About Ocean Community
• Accessibility
• Add Your Data Catalog to Data.gov
• Additional Resources
• Additional Resources
• Agency Developer Resources
• Aging Data Catalog
• agriculture
• Agriculture Highlights
• Agriculture Intro
• Agriculture Page
• Agriculture: About
• Agriculture: Collaborate
• Agriculture: Statistics
• All Categories Blog
• All Hazards
• An Introduction to Smart Disclosure Policy
• APIs
• Applications
• Apps & Tools
• Arctic Data
• Arctic Featured Content
• Arctic Framing Objectives
• Arctic Hightlights
• Arctic Intro
• Arctic Maps
• Arctic Tools
• Artificial Intelligence for Ecosystem Services (ARIES)
• Best Practices Teaser
• Blog
• Blog posts
• Blogs/News
• BREAD Ideas Challenge
• Browse Ethics Datasets
• Business Challenges
• Business Highlights
• Business Intro
• Call to Action: Open Data
• Catalog Help
• Categories
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Challenges
• Champions Nomination
• Cities – Challenges and Opportunities
• Cities – Policies
• Cities Highlights
• Cities Intro
• City Apps
• Climate FAQ
• Climate Highlights
• Climate Intro
• Climate Model Projections
• Climate Model Projections Guidance Notes
• Coastal Flooding – framing questions
• Coastal Flooding Framing Questions
• Coastal Flooding Intro
• Code for Livability
• Communities
• Communities List
• Conference Agenda and Presentations
• Conference Presenters
• consumer apps list view
• Consumer Blogs
• Consumer Categories
• Consumer Challenges
• Consumer Data Page
• Consumer Feedback
• Consumer Feedback Form Confirmation
• Consumer Highlights
• Consumer Intro
• Contact
• Contact Us
• Contact Us Confirmation
• Counties – Challenges
• counties – developers
• counties – Mobile Applications
• counties – more challenges
• counties – officials
• Counties – Policies
• counties – Residents
• Counties Apps
• counties apps list view
• Counties Data
• Counties Highlights
• Counties Intro
• Creation – Food
• Data – Food Community
• Data Archiving
• Data Call – Food Community
• Data Harvesting
• Data Hubs
• Data Issue
• Data Issues
• Data Policy Statements
• Data Publishing and Exchange Subpage
• Data Quality and Documentation
• Data Quality and Documentation
• Data Request
• Data Requests
• Data Story
• Data.gov Blogs
• DATA.GOV CELEBRATES THIRD ANNIVERSARY
• Data.gov Celebrates Third Anniversary
• Data/Tools
• Dataset Suggestion Sent
• Datasets
• Datasets Published per Month
• Datasets Published per Month – Full History
• Detailed Sitemap
• Developer-Apps
• Developer-Collaborate
• Developer-Compete
• Developer-Data
• Developer-Participate
• Developers
• Developers
• Developers apps list view
• Developers Highlights
• Developers Intro
• Developers: Blogs
• Developers: Semantic Web
• Disasters Introduction
• Disclaimer
• Do you have questions or feedback for the Agriculture Topic?
• Do you have questions or feedback for the Business Topic?
• Do you have questions or feedback for the Climate Topic?
• Do you have questions or feedback for the Consumer Topic?
• Do you have questions or feedback for the Ecosystems Topic?
• Do you have questions or feedback for the Education Topic?
• Do you have questions or feedback for the Energy Topic?
• Do you have questions or feedback for the Finance Topic?
• Do you have questions or feedback for the Health Topic?
• Do you have questions or feedback for the Local Government Topic?
• Do you have questions or feedback for the Manufacturing Topic?
• Do you have questions or feedback for the Maritime Topic?
• Do you have questions or feedback for the Ocean Topic?
• Do you have questions or feedback for the Public Safety Topic?
• Do you have questions or feedback for the Science & Research Topic?
• Earthquakes
• EcoINFORMA
• Ecosystem Vulnerability Framing Questions
• Ecosystem Vulnerability Framing Questions
• Ecosystem Vulnerability Hightlights
• Ecosystem Vulnerability: framing questions
• Ecosystems Data Categories
• Ecosystems Highlights
• Ecosystems Intro
• Ecosystems Vulnerability Topic Intro
• Education apps list view
• Education Developers Homepage Panel
• Education Highlights
• Education Intro
• Education Students
• Education Students Homepage Panel
• Education Teachers
• Education Teachers Homepage Panel
• Education Web Apps
• Education: Challenges
• Education: Developers
• Education: Grants
• Energy – Additional Resources
• Energy – Challenges
• Energy – Welcome
• Energy apps list view
• Energy Blogs
• Energy Data and Tools
• Energy Data Initiative
• Energy Highlights
• Energy Infrastructure Framing Questions
• Energy Infrastructure Highlights
• Energy Infrastructure Intro
• Energy Infrastruture Framing Questions
• Energy Intro
• Energy Maps
• Energy Resources
• Ethics Highlights
• Ethics Intro
• Featured Content
• Featured Content
• Featured Content
• Featured Content
• Featured Data
• Featured Data
• Featured Data
• Federal Agency Participation
• Federal Agency Participation
• Federal Data Resources
• Federal Government Challenges
• Feedback
• Feedback API
• Feedback: What Else Should We Be Doing?
• Finance Apps Page
• Finance Challenges
• Finance Feedback Form Confirmation
• Finance Highlights
• Finance Intro
• First Responders
• Floods
• Food – GeoCategories
• Food Applications List
• food community – agriculture tab pic
• food community – food tab pic
• food community – rural tab pic
• Food Data – Categories
• Food Page
• Food Resilience Data
• Food Resilience Framing Questions
• Food Resilience Highlights
• Food Resilience Intro
• Food-Regional Crop Areas and Climatic Profiles
• Frequently Asked Questions
• Frequently Asked Questions (FAQs)
• Frontpage
• GeoPlatform Web Map Viewer
• Geospatial Highlights
• Geospatial Intro
• Get Involved
• Global Development Highlights
• Global Development Intro
• Global Development Intro
• Glossary of Terms
• Got Feedback Confirmation
• Got Feedback?
• Got Feedback?
• Government Officials
• Health Highlights
• Health Intro
• Highlights
• Highlights
• Highlights
• Highlights
• Human Health Framing Questions
• Human Health Highlights
• Human Health Hightlights
• Human Health Topic Intro
• Hurricanes
• Image Map
• Impact Introduction
• In the News
• Innovation at RPI
• Innovator Challenge
• International
• International Education
• Jefferson Release on Next.Data.gov
• Jobs & Skills Highlights
• Jobs and Skills Intro
• Join the Movement
• Labs
• Law – Additional Resources
• Law – Data and Tools available on Data.gov
• Law Highlights
• Law Intro
• Law-Focus on Data
• List View
• list-view-maps
• Local Government Hightlights
• Local Government Intro
• Local open government data powers software applications that help people make informed decisions – from when the next bus will arrive to how neighborhoods are zoned.
• Login
• Manufacturing – Additional Resources
• Manufacturing – Entrepeneurs
• Manufacturing – Manufacturers
• Manufacturing – Researchers
• Manufacturing – Welcome
• Manufacturing Data
• Manufacturing Data Header
• Manufacturing Highlights
• Manufacturing Intro
• Manufacturing Services
• Manufacturing-Categories
• Manufacturing: Blog
• Manufacturing: Challenges
• Manufacturing: Research and Technologies
• Maps
• Maps
• Maps
• Maps
• Maps
• Maps
• Maps
• Maps
• Maps
• Marine Planning Portal Network
• Marine Planning Portal Network Teaser
• Maritime
• Maritime Hightlights
• Media
• Media Inquiries
• Medicare Data
• Meta – The Data.gov Blog Highlights
• Migration Notification
• National Day of Civic Hacking Challenges
• No Access
• nomination form receipt
• Ocean – Best Practices
• Ocean – Community Practice Block
• Ocean – Data Publishing and Exchange
• Ocean – Data Quality and Documentation
• Ocean – FAQ
• Ocean – Get Involved
• Ocean – Map Gallery
• Ocean – Quick Reference
• Ocean – Regional Planning Efforts
• Ocean – Regional Planning Efforts – Alaska/Arctic Region
• Ocean – Regional Planning Efforts – Caribbean Region
• Ocean – Regional Planning Efforts – Great Lakes Region
• Ocean – Regional Planning Efforts – Gulf of Mexico Region
• Ocean – Regional Planning Efforts – Mid-Atlantic Region
• Ocean – Regional Planning Efforts – Northeast Region
• Ocean – Regional Planning Efforts – Pacific Islands Region
• Ocean – Regional Planning Efforts – South Atlantic Region
• Ocean – Regional Planning Efforts – West Coast Region
• Ocean – Tools
• Ocean Datasets
• Ocean Feedback Form Confirmation
• Ocean Highlights
• Ocean Introduction
• Ocean Map National
• Ocean Map Regional
• Ocean Technical
  • Sharing Your Data in the Ocean Community of Data.gov
• Open Data Sites
• Open Government
• Open government data powers science and research software applications.
• Open government data powers software applications that help businesses make informed decisions, create new services, and reach new customers.
• Open government data powers software applications that help consumers make informed decisions.
• Open government data powers software applications that help manufacturers make informed decisions.
• Open government data powers software applications that help people make informed decisions on alternative fuels, green buildings, efficiency, and managing household energy.
• Open government data powers software applications that help people make informed decisions on public safety.
• Open government data powers software applications that help people make informed decisions on agriculture, food, and nutrition.
• Open government data powers software applications that help people make informed decisions on education decisions.
• Open Source
• Opengov – Challenge
• Opengov – Footer
• Opengov – International Open Gov
• Opengov – Learn More
• Opengov – Learn More
• Opengov – OGPL
• Opengov – Recovery
• Opengov – USASpending
• Other Challenges
• Other Data Source
• Other Datasets Consumer
• Outcomes – Food
• Past Winners!
• Pick a Market Sector
• Prior Datasets Published per Month
• Privacy and Website Policies
• Project Open Data Metrics
• Public Safety Highlights
• Regional Planning
• Regional Planning Efforts and Resources
• Registration for the 2012 Intl Open Govt Data Conference
• Related Data.gov Topics
• Research – Additional Resources
• Research – Apps Left
• Research – Resources
• Research – What’s New Middle
• Research apps list view
• Research Data
• Research Resources Links
• Research what’s new page
• Resources
• Resources and Other Data
• Rural Page
• Safety Intro
• SAMHSA Data
• Science & Research Highlights
• Science and Research Intro
• Search Results
• Search Results
• Searching and Subscribing to Energy Resources
• See More Challenges
• Selecting the Appropriate DST
• Semantic Web Recent Stories
• Severe Winter Weather
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback
• Share Your Feedback Form Confirmation
• Shared Facilities
• Sharing Your Data in the Ocean Community of Data.gov
• Sharing Your Data in the Ocean Community of Data.gov
• Shopping Sheet Adoption
• Shout Out to Teachers
• Sitemap
• Smart Disclosure Policy
• Smart Disclosure Policy Resources
• Source Code Repositories
• Space Weather
• State – Challenges
• State Policies and Developer Resources
• States – Apps
• States – Data
• States – Developers
• States – Mobile Apps
• States – More Challenges
• States – Residents
• States – State Officials
• states apps list view
• States Highlights
• States Intro
• Supplycain – Apparel
• Survivors
• Tech Entrepreneurs
• temp open gov
• Tools
• Tools
• Tools
• Tools
• Tools
• Tools
• Tools
• Tornadoes
• Transportation Featured Content
• Transportation Framing Questions
• Transportation Highlights
• Transportation Tools
• Transportation Topic Intro
• Tribal Nations Data
• Tribal Nations Featured Content
• Tribal Nations Framing Questions
• Tribal Nations Hightlights
• Tribal Nations Intro Page
• Tribal Nations Maps
• Tribal Nations Tools
• Tribal Nations Tools – Adaptation
• Tribal Nations Tools – Alaska Natives/Arctic
• Tribal Nations Tools – All
• Tribal Nations Tools – Assessment & Planning
• Tribal Nations Tools – Capacity Building
• Tribal Nations Tools – Disaster Risk Reduction
• Tribal Nations Tools – Mitigation
• Tribal Nations Tools – Relocation
• Types of Disasters
• usa_search
• video
• Virtual Conference
• Vision – Food
• Vistor Stats
• Volunteers
• Water Framing Questions
• Water topic intro
• Weather Highlights
• Weather Highlights
• Weather Intro
• Weather Intro
• Welcome to Education Data Community
• Welcome to the Green Button!
• White House Energy Datapalooza
• White House Safety Datapalooza
• Wildfires
• World Map
• World Map

Posts by category

• Category: Aging
• Category: Agriculture
  • Agricultural Marketing Service
  • Agricultural Productivity in the United States
  • Agricultural Research Service Germplasm Resources Information Network
  • Apps for Farmers
  • Dive Deeper into USDA Data with New APIs
  • Dr. Woteki on Scientific Integrity
  • Economic Research Service ARMS API
  • ERS Food Access Research Atlas API
  • Farmers Market API
  • FarmPlenty
  • Food and Nutrition Service
  • From Data to Decisions: Using Data to Improve Public Access and Knowledge
  • Global Agriculture Data
  • Global Open Data Initiative for Agriculture and Nutrition…
  • Introducing New Rural Housing Data from USDA
  • Introducing OpenFDA from the Food and Drug Administration
  • Join the ‘Data Revolution’
  • National Agriculture Statistics Service QuickStats
  • National Agriculture Statistics Service QuickStats API
  • National Institute for Food and Agriculture’s Research, Education, and Economics Information System
  • Open Ag Data
  • Open Data Revolution to Fight Global Hunger
  • Participants in Open Data Roundtables Guide USDA on Ways to Provide High Quality Data to Users
  • USDA Blog
• Category: Asian Americans and Pacific Islanders
• Category: Business
  • Price for Exports?
  • Resources to Help Grow Your Business
  • Starting an Open Data Business? Get Help From BusinessUSA
  • U.S. International Trade in Goods and Services
  • USDA Partners with Service Organizations to Help Veterans Find Careers
• Category: Cities
  • 5 Reasons Why Good Governments Should Embrace Open Data
  • Digital Cities from the Ground Up
  • Hacking for Change? Tips for the National Civic Day of Hacking
  • Las Vegas Open Data Site
  • National Civic Day of Hacking
  • Open Data Census
  • Save the Date…the National Day of Civic Hacking is Coming June 6!
  • Seattle Real-Time Fire 911 Calls
• Category: Climate
  • 2014 AWRA Annual Water Resources Conference
  • A multi-university initiative makes global climate information more accesible to farmers
  • Category: Arctic
    • Climate Data in Action
    • Coastal Flooding Theme Adds Eleven New Datasets
    • Coastal Flooding Theme Adds Thirteen New Datasets
    • Ecosystem Vulnerability Launch
    • Ecosystem Vulnerability Theme Adds Eleven New Datasets
    • Ecosystem Vulnerability Theme Adds Five New Datasets
    • Ecosystems.data.gov and EcoINFORMA
    • Food Resilience Theme Adds Seven Datasets
    • Infrastructure and Geographic Map Data for Climate-Preparedness
    • Launch of Ecosystem-Vulnerability theme of Climate.Data.Gov
    • Launch of Energy & Infrastructure Resilience theme of Climate.Data.Gov
    • Launch of Food Resilience theme of Climate.Data.Gov
    • Launch of Health theme of Climate.Data.Gov
    • Launch of Water theme of Climate.Data.Gov
    • Microsoft Launches “Innovation Challenge” around Food Resilience
    • NASA Invites Citizens to Collaborate on Coastal Flooding Challenge
    • NASA launches Earth Science Challenges
    • NOAA and NASA Launch Coastal Vulnerability Innovation Challenge
    • Obama Administration Unveils New Climate Resilience Tools
    • Release of Infrastructure and Geographic Map Data for Climate-Preparedness
    • Water Theme Adds Eight New Datasets
    • Water Theme Adds New Content
    • Welcome to Climate.Data.gov!
    • What Kind of Climate Data Can I Find?
  • Category: Coastal Flooding
  • Category: Ecosystem Vulnerability
  • Category: Energy Infrastructure
  • Category: Food Resilience
  • Category: Human Health
  • Category: Transportation
    • First International Conference on Surface Transportation System Resilience to Climate Change and Extreme Weather Events
  • Category: Tribal Nations
  • Category: Water
• Category: Consumer
  • U.S. Treasury Department: Innovators Using Federal Data to Help Consumers Make Informed Decisions
  • Arne Duncan: Tweet on Higher Ed
  • CFPB: Does your college help you know before you owe?
  • CFPB: Our new mortgage visualization tool
  • Consumer Financial Protection Bureau
  • Consumer Financial Protection Bureau
  • Department of Education: Education Datapalooza: Unleashing the Power of Open Data to Help Students, Parents, and Teachers
  • Energy Tweet
  • Financial Services Consumer Complaint Database
  • MyData for Education
  • Office of Ed Tech: Tweet on Higher Education
  • OfficeOfEdTech: Tweet on distance ed
  • ONC & HHS: Winners of Blue Button + Co-Design Challenge
  • ONC: Advancing the use of patient-generated information to improve health and care
  • ONC: Consumer Engagement via eHealth & Blue Button, Year-in-Review
  • ONC: The Blue Button Movement: Kicking off National Health IT Week with Consumer Engagement
  • Open Retirement and Employee Benefit Plan Data
  • Product Recalls
  • Recommendations of the Investor Advisory Committee Regarding the SEC and the Need for the Cost Effective Retrieval of Information by Investors
  • SafetyDataGov Tweet 11-27-2013
  • SafetyDataGov Tweet 11-30-2013
  • SafetyDataGov Tweet 12-3-2013
  • SEC Open Data on Public Companies and Mutual Funds
  • Sophie Raseman
  • The Legal Entity Identifier (LEI) Is Good News for Financial Technology Developers
  • Tweet – @Energy wants your best ideas for how to use energy data! Enter the American Energy Data Challenge today http://energychallenge.energy.gov #opendata
  • Tweet – Consumer Financial Protection Bureau
  • Tweet – Consumer Financial Protection Bureau
  • Tweet – DOT Rail Crossing App
  • Tweet – Keep your kids safe, use the #OpenData from @NHTSAgov to find out more about child safety seats http://1.usa.gov/160bqDt
  • Tweet – Sophie Raseman
  • Tweet – U.S. Treasury Department
  • U.S. Department of Education: Innovators Come Together to Brainstorm Solutions and Take Action
  • U.S. Treasury Department: A One-Stop-Shop for Innovators
  • U.S. Treasury Department: Building Apps and Services for Financial Empowerment
  • U.S. Treasury Department: Encouraging Innovations that Help Americans Take Control of Their Financial Lives
  • US AID tweet: Global Nutrition and Ag Open Data Initiative
  • White House OSTP & U.S. Treasury Department: Empowering Consumers through the Smart Disclosure of Data
  • White House OSTP and the U.S. Treasury Department: Consumer.Data.Gov is Live!
  • White House: Open Data Round Up
• Category: Counties
  • County Business Patterns
  • Montgomery County Employee Salaries
• Category: Developers
  • Data.gov Mashathon 2010: an Energy Data Mashup
  • “Think Globally – Act Locally”- A New Chapter for Data.gov…
  • A Primer on Machine Readability for Online Documents and Data
  • A Se-mash Hit
  • Adams Release on Next.Data.gov
  • Announcing the Apps for Vehicles Challenge
  • API Now Available From Federal Register 2.0
  • Baby Names Dataset
  • Cleaning Up Metadata Messiness
  • Data.gov Paper Wins Award in International Semantic Web Challenge
  • Data.gov’s Journey Continues
  • Department of Energy Implements APIs in the Cloud
  • Designing for Open Data: Improvements to Data.gov
  • Developers Corner
  • Energy Department Announces Apps for Vehicles Challenge Winners
  • EPA Moving Forward with Publishing Linked Open Data
  • Every Sufficiently Large Open Dataset…
  • Geoplatform is Live
  • Google Places API Challenge
  • Government APIs
  • Help Improve Next.Data.gov
  • Here’s to Your Health
  • Introducing Project Open Data
  • Introducing: Project Open Data
  • It’s All About the Data…
  • It’s All About the Data…
  • Jefferson Release on Next.Data.gov
  • Linked Data Goes With DERI
  • Mixing government healthcare and environmental data on the Web
  • National Day of Civic Hacking at the White House
  • Obama Administration Releases Historic Open Data Rules to Enhance Government Efficiency and Fuel Economic Growth
  • Open Data Executive Order
  • Open Government Platform
  • Opening Up Our Data
  • PARDON OUR DUST – Census.gov Transformation
  • Participate in Challenges
  • Repositories on GitHub
  • Request an API
  • Revitalizing the Metadata Working Group
  • Science Hack Day
  • Support for schema.org at Data.gov
  • Taking Open Government to the Next Level
  • The Web is Evolving
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Tweet from usdatagov
  • Two Days, One Great Mashup
  • U.S. Government Dataset Search Opens Data.gov to Scientists
  • usdatagov: Tweet on DeveloperWeekLA
  • Using 21st Century Technology to Solve Age-Old Problems
• Category: Disasters
  • “Lantern Live” Mobile App Lights Way for Citizens Impacted by Disasters
  • 10 Things To Do for National Preparedness Month
  • Announcing the White House Innovation for Disaster Response and Recovery Initiative Demo Day
  • Calling Citizen Scientists: You Can Help When Disasters Strike!
  • Hardware Hacking for Disaster Response in Red Hook, Brooklyn
  • Innovating to Improve Disaster Response and Recovery
  • Innovation for Disaster Response and Recovery goes Global with State Department & USAID’s Tech Camp in the Philippines
  • Join the Third Annual Safety Datapalooza Livestream
  • Launching Disasters.Data.Gov to Empower First Responders and Survivors with Innovative Tools and Data
  • Launching Disasters.Data.Gov to Empower First Responders and Survivors with Innovative Tools and Data
  • More than 1,500 people participate in the White House Innovation for Disaster Response and Recovery Demo Day
  • Second Annual White House Safety Datapalooza
  • Taking Action for America’s PrepareAthon!
  • Taking Action for Disaster Preparedness: Technology and Innovation in Support of America’s PrepareAthon!
  • Unleashing Innovation for Disaster Response and Recovery
  • Upping Our Game for Disaster Preparedness and Response
  • What Startups Taught the White House During Disaster
• Category: Earth Science
• Category: Earthquakes
• Category: Ecosystems
  • Bird Data & Information for Research, Management and Conservation of Birds
  • Ecosystem and Biodiversity Data: The Foundations for Environmental Research, Management and Conservation
  • Ecosystem Services and Federal Policy Guidance
  • Ecosystem Vulnerability Resources in Climate Resilience Toolkit
  • Ecosystems.data.gov and EcoINFORMA
  • Formal Release of EcoINFORMA, Ecosystems.data.gov, and Two New Themes of Climate.data.gov
  • Invasive Species Data and National Invasive Species Awareness Week
  • Invasive Species Data, Information & Tools
  • Pollinator Data from USGS and Partners
  • Release of the 2011 Alaska National Land Cover Database in MRLC
• Category: Education
  • Assessment Systems Online Community
  • Bullying Rates Drop
  • College Scorecard
  • Data in the Classroom
  • Digging Deeper into ED Open Data: New ED Data Inventory
  • Digital Learning Day, February 1, 2012
  • Ed Games Week Highlights the Emergence of Video Games in Education
  • Education and Training Data
  • Education in the World
  • FAFSA Application Volume Data
  • FAFSA MyStudentData
  • Federal Student Aid
  • Federal Student Aid
  • Federal Student Aid Tool Publishes FAFSA Completion Numbers for the High School Graduating Class of 2015
  • Games for Learning Summit: Expanding the Conversation Between Educators and Game Designers
  • High School Education
  • Higher Education Datasets
  • My Brother’s Keeper Data Jam: Old World Values with New World Strategies and Tools
  • New Tools to Support Students in Preparing for College and a Call for Innovative Ideas
  • Open Badges
  • Post-Secondary Universe Survey 2010 – Directory information
  • Projection of Education Statistics to 2020
  • Public Elementary/ Secondary School Universe Survey 2009-10
  • Public School Teacher Characteristics (Video)
  • Student Performance Data
  • Teamwork + Data = Big Gains at Jones Elementary School
  • U.S. Department of Education Grant Visualizations
  • U.S. Department of Education: College Ratings Listening Tour: College Value and Affordability
  • U.S. Department of Education: Education Department Releases Updated Financial Aid Shopping Sheet to Provide Students with Additional Transparency in College Costs
  • U.S. Department of Education: Financial Aid Shopping Sheet Updated to Provide Students with More Transparency
  • Welcome to Education Data Community
• Category: Energy
  • America’s Home Energy Education Challenge
  • APIs from the Energy Information Administration
  • Challenges
  • Code for Livability
  • Creating the Emissions and Generation Resource Integrated Database (eGRID)
  • Energy Data Initiative
  • Hourly Electric Grid Monitor reports new information on U.S. electricity demand, net generation, and interchange collected by the U.S. Energy Information Administration
  • Introducing the U.S. Energy Information Administration (EIA) redesigned International Energy Portal
  • Modeling a Green Energy Challenge after a Blue Button
  • More than 1000 votes for Popular Choice GreenApp Fueled by Communities, Engagement
  • Rooftop Solar Challenge
• Category: Ethics
• Category: Finance
  • CFTC: CFTC Announces Mutual Acceptance of Approved Legal Entity Identifiers
  • Consumer Financial Protection Bureau
  • Federal Student Loan and Financial Aid Open Data
  • New Steps to Make It Easier to Discover and Use Treasury Data
  • Open Bank Data
  • Small Business Lending with Open Data
  • Treasury Department
• Category: Geospatial
  • AirAtlas: Air Quality in National Parks
  • Everything you ever wanted to know about earthquakes? Yeah, we’ve got that.
  • National Water Information System
  • Rivers of Data – Inland Electronic Navigation Charts
• Category: Global Development
  • A Quick Guide to Feed the Future’s New Progress Report
  • Demographic and Health Surveys
  • Development Credit Authority
  • Famine Early Warning Systems Network
  • Global Agriculture Data
  • Global Development Intro
  • Millennium Challenge Corporation
  • The Positive Impacts of Transparency
  • USAID tweet: Feed The Future
  • Why Open Data Matters: G-8 and African Nations Increase Open Data for Food Security
  • Women’s Empowerment in Agriculture Index: Proof of Concept
• Category: Health
  • 2011 County Health Rankings
  • ACEP’s Report Card on America’s Emergency Care Environment
  • African American History Month: A Time for Reflections on Health Disparities
  • Become the Ultimate Matchmaker: Apply to be the Next Innovator In Residence
  • Calling All Health Innovators: Health Data Palooza Live June 9th
  • Clinical Quality Linked Data on Health.data.gov
  • CMS Modifies Policy on Disclosure of Physician Payment Information
  • Coders! Developers! Data Scientists! Meet the Code-a-Palooza!
  • College & University Students to Take Health Data Viral – to Improve Health!
  • Disrupting Post-Acute Care With Data: A Q&A With Aidin’s CEO, Russ Graney
  • Expanding Patient Access to Medical Records
  • Health Data Initiative Forum III
  • Health Datapalooza IV Tops Off a Huge Year in Health Data Liberation & Innovation
  • Health Indicators Warehouse APIs
  • Health IT Catalog Released and Ready to Access
  • HHS 2013 Year in Health Data Highlights
  • Honoring African American History by Increasing Access to Information Protecting and Promoting Your Health
  • Hospital Charge Data
  • Interview with Halle Tecco, Rock Health
  • Launch of Global Health Data Exchange
  • Leading Pharmacies and Retailers Join Blue Button Initiative
  • Learning about Employee Benefit Survey Data
  • Million Hearts Epi-Exchange
  • More Social Services Data
  • New York Data: More Opportunities To Improve Health
  • RadLex
  • The Health Consequences of Smoking—50 Years of Progress, Five Decades of Data
  • The Need For A Smart Approach To Big Health Care Data
  • The new release of the County Health Rankings is terrific!
  • Tom Frieden: Data Wonk
  • Welcome to HealthData.gov!
• Category: Impact
  • AccuWeather
  • Alltuition
  • Calcbench
  • Carfax
  • Cattlefax
  • City-Data
  • Clean Power Finance
  • Climate Corporation
  • Enigma
  • Esri
  • Estately
  • FarmLogs
  • Foursquare
  • HD Scores
  • Humetrix
  • Kayak
  • LinkedIn
  • Mapbox
  • Mercaris
  • Opower
  • Palantir
  • Panjiva
  • Propeller Health
  • Realtor.com
  • Simple Energy
  • SoFi
  • Spot Crime
  • Trulia
  • Zillow
  • Zoc Doc
• Category: Jobs & Skills
  • American Community Survey
  • American Housing Survey
  • Job Openings and Labor Turnover Survey
  • Occupational Information Network (O*NET)
  • Small Area Income and Poverty Estimates
• Category: Law
  • EPA Consent Decrees
  • Federal Register
  • New Datasets from Department of Justice
• Category: Local Government
  • Get your Local Government on Data.gov
  • Innovating with Open Data from Zillow and HUD at “Hack Housing”
  • Local Severe Weather Warning Systems in Missouri
• Category: Manufacturing
  • Annual Capital Expenditures Survey
  • Database of State Incentives for Energy Upgrades to Plants and Facilities
  • Federal R&D Facilities for Entrepreneurs and Innovators
  • Federal R&D Facilities: Open for Collaboration
  • Industrial Production and Capacity Utilization Index
  • Made In America: Helping Revitalize U.S. Manufacturing
  • Manufacturing and Construction Statistics from the U.S. Census Bureau
  • Manufacturing Energy Consumption Survey
• Category: Maritime
  • A Decade of Shipment Tonnage and Value Summaries
  • A Maritime Topic for a Maritime Nation
  • By the numbers: port statistics for some of the largest U.S. ports
  • Ferrying data to the public through the USDOT National Census of Ferry Operators
  • Harvesting Grain Data
  • Northeast Ocean Data Portal – Providing a Common Picture of New England’s Ocean Uses
  • Of Sturgeon and Ships
  • Safety at Sea – U.S. Coast Guard Marine Casualty and Pollution Data for Researchers
  • Stormy weather: 150+ years of hurricane tracks in the Atlantic Ocean
  • The California Seafloor and Coastal Mapping Program benefits from shared data
  • Trends in Recreational Boating Safety, U.S. Coast Guard Recreational Boating Safety Statistics Tool
  • Visualizing ocean traffic on Marine Cadastre
• Category: Meta - The Data.gov Blog
  • Data.gov Gets Updated: A Closer Look | InformationWeek Government
  • .Site Navigation skipped – Main Content area Starts here FGDC Releases Newest Version of the Geoplatform | Geoplatform.gov
  • 10 Big Data Sites to Watch – By Gil Press | Foreign Policy
  • 2007 Crime in the United States
  • 2008 Medicare and Medicaid Statistical Supplement
  • 2010 Code of Federal Regulations in XML
  • 2011 Open Government News Archive | Open Government at SSA
  • 2011 United States Government Manual in XML
  • 2012 International Open Government Data Conference
  • 3 Creative Ways to Use Public Data for Digital Marketers | ClickZ
  • 5 Helpful Online Services From Uncle Sam | InformationWeek Government
  • 55 New APIs: Cigna, Pearson and Data.gov | Programmable Web
  • 7 Ways Companies Are Using the Government’s Open Data | Mashable
  • 7 Years of Open Data
  • A Global Movement to Democratize Data
  • A small price for transparency—The Roanoke Times
  • A Smarter, More Innovative Government for the American People | OSTP Blog
  • A Year of Open Government Data: Transparency, but also Innovation—Nodalities Blog
  • Adams Release on Next.Data.gov
  • Administration releases more guidance to open up agency data | Federal Times
  • Africa: Conflicts Without Borders 2009
  • Agencies get how-to on open data compliance | FCW
  • Agriculture
  • Aircraft Wildlife Strike Data
  • Airline On-Time Performance and Causes of Flight Delays
  • Airport Status Web Service
  • American Community Survey
  • American Community Survey
  • An Award-winning Legacy
  • Announcing the Data.gov Help Desk
  • APIs – You Ain’t Seen Nothin (And You Never Will)
  • April 2010 USCIS FOIA Log
  • Beth Noveck testifies in Canada on the power of Open Government—Gov in the Lab Blog
  • Big Data Analysis Vs. Government Spending |Info Week Government
  • Budget Deals Deep Cuts to Obama Administration’s Transparency Sites—Pro Publica Blog
  • Business Licenses and Permits Search
  • By State and DC since 1910
  • Can open data change the culture of government? | Federal Computer Week
  • Can the government solve Silicon Valley’s identity crisis with open data? | VentureBeat
  • Celebrating Innovation and Open Data at the Energy Datapalooza
  • Census – Health Coverage
  • Check out Data.gov’s new Metrics Page
  • Chopra Reflects on Year of Open Gov—ExecutiveGov Blog
  • Citizens by a 3 to 1 Margin Are More Likely to Vote for Politicians Who Champion Open Government – Despite broad support for the idea of open government 65% of citizens remain unaware of Open Data initiatives.—Marketwire
  • City and County Web Dataset
  • CKAN: the Horizon for Data.gov 2.0
  • Communities Bring Data to Life
  • Community Developed Applications
  • Congressman Darrell Issa (R-Calif.) moves to keep federal government transparency sites such as data.gov running—Federal Computer Week
  • Counties
  • Creating a Status Feed for Contracting Data | Washington Post
  • Creative Class County Codes
  • creative-class-county-codes
  • Credit Card Complaints
  • Cuts could close door on ‘open government’—Kane County Chronicle
  • Darfur – Damaged-Destroyed Villages Sept 2009
  • Data 2.0 Coming Next Week as Data.gov Future Uncertain—Programmable Web Blog
  • Data in Action: the Red Cross Hurricane App
  • Data Market Articles on AOL Gov
  • Data that empowers consumers
  • Data USA: Visualizing Government Data
  • Data, Tigers & Innovation; oh my! A recap of Health Datapalooza IV
  • Data.gov 3rd Anniversary
  • Data.gov at Ten and the OPEN Government Data Act
  • Data.gov begins move to cloud to allow social sharing, more visualization tools—Federal Computer Week
  • Data.gov Catalog Update
  • Data.gov Celebrates Third Anniversary
  • Data.gov CKAN Catalog
  • Data.gov Clarity—Sunlight Foundation Blog
  • Data.gov embraces open source data management | FedScoop
  • Data.gov et al. Budget Slashed by 75%—ReadWrite Web
  • Data.gov Evangelist Accepts Fed 100 Award
  • Data.gov expands toolkit for citizen developers | GCN.com
  • Data.gov gets an open-source revamp | ComputerWorld
  • Data.gov gets makeover | FedScoop
  • Data.gov in crisis: the open data movement is bigger than just one site—The Guardian Blog
  • Data.gov Infrastructure Migration – Notice to Federal and Non-Federal Users
  • Data.gov is a project for the few – but they really matter, says Tom Steinberg—The Guardian Blog
  • Data.gov Launches New Catalog and APIs
  • Data.gov Launches New Catalog and APIs
  • Data.gov Migrating to Cloud Platform—Forbes
  • Data.gov Pilots an Easier Way to Manage APIs | GCN
  • Data.gov Places as a Top 8 Finalist for 2015 Innovation Awards
  • Data.gov redesign preview modernizes public data delivery | Engaget
  • Data.gov Revamp | FlowingData
  • Data.gov Turns Six!
  • Data.gov’s New E-newsletter: Big Data Express
  • DataFerrett
  • Datapaloozas Blossoming Everywhere | Health Data Consortium
  • Datapaloozas – and More – on the Horizon
  • Deepwater Horizon Response
  • Digital Strategy: Delivering Better Results for the Public | The White House Blog
  • Drupal and U! Come for the Code and Stay for the Community
  • Duplicate Entries Removed from Data.gov Catalog
  • E-gov services beat offline alternatives on satisfaction study—Federal Computer Week
  • E-government funds slashed in newly-introduced budget—Fierce Government IT
  • Energy Usage Analysis System
  • Environmental Compliance and Enforcement Data
  • Expanding access to Arctic data and tools
  • Expanding Markets and Innovation through Open Data
  • Expanding Opportunity with Open Data: A White House Demo
  • Explore Federal Research Data
  • Facility Quality and Safety Report
  • Famine Early Warning System Network (FEWS NET)
  • Farmers Market Geographic Data
  • FarmPlenty: an #opendata impact
  • FCC’s data guru Greg Elin eyes new opportunity | FedScoop
  • Featured Resource on the Web: Data.gov | San Jose Public Library
  • Federal Advisory Committee Act (FACA) Data-1997-2008
  • Federal Agencies Get Guidance On New Data-Sharing Mandate | HPC Wire
  • Federal Data Center Consolidation
  • Federal Register
  • Federal Student Loan Program Data
  • Federal websites might be unattended or go dark during furloughs—Federal Computer Week
  • FedOSS: Open data gets a direct order | fedscoop
  • Feds to Open Data Access in a Big Way | e-Commerce Times
  • FedScoop Guide: Digital Government Strategy turns 1 | FedScoop
  • FedScope: Easy Stats on the Federal Workforce
  • FEMA app
  • Final Critical habitat for the California Condor
  • Final Critical habitat for the California Red-legged Frog
  • Final Critical Habitat for the Marbled Murrelet
  • Final Critical habitat for the Mount Graham red squirrel
  • Final Critical habitat for the Whooping crane
  • FinancialStability.gov TARP Transactions Data
  • Find a Health Center
  • First Look at Next.Data.gov | White House Blog
  • Five Years of Open Data—Making a Difference
  • Foreign Assistance
  • Freedom of Information Act Annual Reports – Fiscal Year 2008
  • General Land Office Records System
  • GEO Viewer
  • Get creative with the developer resources on Data.gov | TechRepublic
  • Get Local Data. Build Apps. Win the National Challenge.
  • GOOD 100: Meet Todd Park, Fueling Innovation Through Free Data | GOOD
  • Good Data: The Foundation of Open Government | Brookings Institution
  • Government pushes for open data | Washington Post
  • Government releases ‘unprecedented amount of data’ for the National Day of Civic Hacking | VB
  • Government via mobile apps | The Washington Post
  • Green apps could spark environmental engagement
  • GSA Answers the Call of the Digital Government Strategy | The GSA Blog
  • GSA Provides Easier Public Access to Federal Advisory Committee Information—GSA Press Release
  • GSA revisits improvements to USA.gov search­—Federal News Radio
  • GSA’s Fall 2015 Hackathon
  • Happy First Anniversary Data.gov, 47 to 251,028
  • Happy Second Anniversary Data.gov!
  • Harvard Business School Case Study on Data.gov
  • Health Datapalooza IV Tops Off a Huge Year in Health Data Liberation & Innovation
  • Health Datapalooza IV Tops Off a Huge Year in Health Data Liberation & Innovation | White House blog
  • Help Us Strengthen Open Government
  • HHS Developer Resources
  • House member says he can save feds’ transparency websites—Federal Computer Week
  • House restores some e-gov funding in CR—Federal News Radio
  • How the Global Open Data Movement is Transforming Journalism | Wired
  • IDC: Open government, mobile and ‘smart’ technologies will change federal IT in 2011—Fierce Govt IT
  • Improving our digital services to better serve you
  • Indexing Datasets on Next.Data.gov
  • Innovators Address the Wage Gap with Apps and Open Data | White House Blog
  • Innovators Using Federal Data to Help Consumers Make Informed Decisions
  • International Best Track Archive for Climate Stewardship (IBTrACS)
  • International Open Government Data Conference
  • Introducing Data.Gov Next Generation
  • Introducing: Project Open Data | The White House Blog
  • IRS Migration Data
  • Issa rejects federal transparency bill—Federal Computer Week
  • IT Dashboard – Federal IT Spending (all investments)
  • Join us @ the Earth Day Hackathon
  • Launching the Police Data Initiative
  • Liberating data for public value: The case of Data.gov
  • Linking the Worlds of Data
  • Loans & Grants Search
  • Marine Geology Data and Information Viewer
  • Marion Royal and Hyon Kim: Data.gov’s dynamic duo : FCW
  • Massive Catalog of Streaming Government Data Coming Thursday | NextGov
  • Massive Data Institute
  • Measuring America: 30-Year-Olds [Then and Now]
  • MEET 43 SMART PEOPLE WHO PLAN TO MAKE GOVERNMENT WORK BETTER | NextGov
  • Meet the Round 2 Presidential Innovation Fellows | White House Blog
  • Mine Inspections
  • Minister Clement Launches Next Generation Open Data Portal | MarketWatch Canadian Press Release
  • Moving from Open Data to Open Knowledge: Announcing the Commerce Data Usability Project
  • MY NASA DATA
  • MyPyramid Food Raw Data
  • National Assets
  • National Bridge Inventory
  • National Data.gov Site Features Montgomery County | MC Press Release
  • National Day of Civic Hacking – Citizens Wanted
  • National Operational Hydrologic Remote Sensing Center Snow Water Equivalents
  • National since 1879
  • New Data.gov / Search App
  • New G8 Open Data Charter | Sunlight Foundation Blog
  • New mobile tools gives agencies ‘giant innovation permission slip’ |Federal News Radio|
  • New Study: What do you think about Open Government?—Code for America Blog
  • New Updates
  • New website will track federal agencies’ performance—Federal Computer Week
  • Next.Data.Gov is a Slick Replacement for the Federal Records Site | Latinos Post
  • Next.Data.gov | GovLab Digest
  • next_data
  • NSA’s intell gathering puts the spotlight on metadata | GCN
  • Nuclear Power Reactor Inspections Reports
  • Obama Calls for ‘Smarter, More Innovative’ Government | PC Mag
  • Obama Calls for Sleeker, Smarter Government | Epoch Times
  • Obama Calls for Tech Expertise in Government | Live Science
  • Obama Makes Open Data the Default for Federal Government | Laserfiche
  • Obama Management Agenda: President Highlights Technology, Private Sector To Improve Government Services | International Business Times
  • Obama Opens Government Data So Devs Can Build New Products | Mashable
  • Obama Reboots Technology Mission To Improve Government | Information Week
  • Obama talks bureaucratic revamp amid domestic, international crises | The Daily Caller
  • Obama touts free and open data, says it creates jobs | ComputerWorld
  • Obama touts technology in State of the Union address—Fierce Govt IT
  • Obama turns to tech to help gov’t pack a punch | Associated Press
  • Obama wants ‘smarter’ government to be more high tech, user friendly | Syracuse Post-Standard
  • Obama’s CIO Kundra says the UK’s Data.gov is groovy like the Beatles, or something—LA Times Blog
  • Obama: All Government Data Will Be Open | Bloomberg TV
  • OECD Gender Data Portal
  • OECD Regional Database
  • One Click and We’ll Give You Millions
  • One year of public safety data at Safety.Data.gov!
  • Online government information—The Daily Journal, Florida Times-Union
  • OP-ED: OPEN DATA IS RE-DEFINING GOVERNMENT IN THE 21ST CENTURY
  • Open Data Building a Stronger Economy | White House
  • Open Data Executive Order Shows Path Forward
  • Open Data for Agriculture Offers Lift-Off for Global Food Security
  • Open Data Going Global | White House Blog
  • Open Data Is Good for America | Huffington Post
  • Open Data Roundtables
  • Open Data Spells Success
  • Open Data | Drupal
  • Open Data, Transparency Sites That Helped Gov’t Save Billions To Be Shut Down Over $30 Million?—TechDirt
  • Open Data: A History
  • Open Data: A new goldmine | The Economist
  • Open Data: Empowering Americans to Make Data-Driven Decisions
  • Open gov: So far, so good, but further still to go—Federal Computer Week
  • Open Government Data Ramps Up | GovWin Network
  • Open Government Directive Agency Datasets
  • Open Government Platform
  • Open Letter: Congress Must Protect Transparency Programs in Budget Negotiations—SunLight Foundation via Targeted News Service
  • Open with Apps
  • OpenGov Voices: Data.gov relaunches on open source platform CKAN | Sunlight Foundation Blog
  • Opening the World to Open Data
  • Opening Up US National Data
  • Outpatient Latest Payment Information
  • Patent Grant Bibliographic Data
  • PISA 2009
  • President Obama on His Management Agenda: White House Video
  • President Obama says ‘government is us’ and ‘we’re tracking weather’ well | The Global Dispatch
  • Progress Toward Opening Government Data Resources | White House
  • Progress Toward Opening Government Data Resources | White House
  • Project OpenData Adds OpenData Implementation Guide | GISuser.com
  • Provider Charge Data
  • Public Elementary and Education School Data
  • Public Housing Physical Inspection Scores
  • Public Open Data: The Good, the Bad, the Future | PBS Idea Lab
  • Putting open data to use | FCW
  • Quarterly Report on Bank Derivatives Activities
  • Quick Stats
  • RADNET
  • Recreation Information Database – RIDB
  • Reference: Data.gov Launches New Catalog and APIs | Infodocket/Library Journal
  • Remarks by the President Presenting New Management Agenda : White House Briefing Room
  • Report measures open gov benchmarks—Federal News Radio
  • Residential Energy Consumption Survey (RECS) Files, All Data, 2005
  • Revamped Data.gov Includes API Catalog | TechPresident
  • Revamped Data.gov to highlight real-world uses of government information | Federal News Radio
  • Revitalizing American Manufacturing
  • Roundtable on Open Data for Economic Growth
  • Safety Homepage
  • sandy damage
  • SBA Licenses and Permits
  • ScienceCinema
  • SciTech Connect
  • SESTAT
  • Sherman Act Violations Yielding Fines of $10 Million or more
  • Six-month budget slashes e-gov fund by 76 percent—Federal News Radio
  • Small Business Loans and Grant Program
  • Smart Disclosure Makes Consumers Happier and Markets Better | Nextgov
  • Spending bill to prevent shutdown and furloughs targets IT programs—Federal Computer Week
  • States
  • States Community
  • Sunshine Week
  • Sunshine Week
  • Technology is at the Heart of Obama’s Second-term Management Agenda | Nextgov
  • The American Dream, Aided By Open Government Data | White House Blog
  • The Best Thing Obama’s Done This Month | Slate
  • The Esri Human Health and Climate Change App Challenge
  • The Next Data.Gov: More Data Transparency Through Improved Design | Visual.ly Blog
  • The Next Generation of Open Government—WAMC Public Radio Blog
  • The Next Step is Yours
  • The Northeast Regional Ocean Council and Maritime Data
  • The People’s Choice: Distrust | The Wall Street Journal
  • The Third U.S. Open Government National Action Plan
  • The White House is giving Data.gov a face lift – and it all looks awfully familiar | Digital Trends
  • The White House launches Next.Data.Gov on WordPress | VIP WordPress.com
  • The White House Open Data Innovation Summit
  • There’s Gold Out There
  • They Gave Us The Beatles, We Gave Them Data.gov—The White House Blog
  • Thoughts on the White House Executive Order on open data | opensource.com
  • Thousands of Americans Innovate for Good on the National Day of Civic Hacking
  • Thousands of Americans Innovate for Good on the National Day of Civic Hacking | White House Blog
  • Thousands of Federated Datasets on Data.gov Cities, States and Counties Communities
  • Top 25 most inflluential people under 40 in gov and tech | FedScoop
  • Total Wildland Fires and Acres burned from 1960 through 2008
  • Tour Data.gov 2.0
  • Toxics Release Inventory National data file of all US States and Territories
  • Track Hurricane Sandy
  • Tracking the Progress of the White House Open Government Directive—Huffington Post
  • Transparency train keeps rolling with President’s open data executive order | California Forward
  • Transparency websites hit by budget ax—Government Executive.com Blog
  • Tsunami Message | Data.Gov | Open Federal Data
  • Tsunami Warning
  • U.S. City and County Web Data
  • Under the Hood of the Open Data Engine
  • Upcoming Digital Health Opportunities: Codeathons and the SXSW Accelerator
  • USA Spending Contracts and Purchases
  • USAID Announces Launch of New Improved Data Repository
  • USCIS National Processing Volumes and Trends
  • USDA Meat, Poultry, and Egg Product Inspection Directory
  • USGS Global Visualization Viewer for Aerial and Satellite Data
  • VanRoekel pins initial open data hopes on economics | Federal News Radio
  • VanRoekel reviews 1 year under Digital Government Strategy | Fierce Government IT
  • Veterans Affairs Geographic Distribution of Expenses
  • Veterans Affairs Veteran Population Model
  • Veterans Health Administration Hospital Report Card
  • Visit Agriculture Community
  • Visit the New Education Community
  • Visit the New Energy Community
  • Visit the new Health Data Community
  • Visit the New Ocean Community
  • Visit the new Smart Disclosure community
  • Wanted: A rockstar developer for Data.gov | FCW
  • Watch Us Grow – It’s Not Just the Numbers
  • We Want Your Input … | White House Blog
  • Weekly Fatality Reports
  • Welcome to the Community for the Open Government Platform
  • We’ve Upgraded Our CMS!
  • What is NASA doing with Big Data today? – open.NASA
  • What’s next for digital government?
  • Where Are The Jobs
  • White House Expands Guidance on Promoting Open Data | Nextgov
  • White House Interview: The New Open Data Policy | Open Data Now
  • White House Issues Executive Order on Open Data | AIDS.gov Blog
  • White House issues guide … Open Data Policy | Fierce Government IT
  • White House previews new Data.gov website | Softonic
  • WHITE HOUSE PROMISES OPEN GOVERNMENT 2.0 | Nextgov
  • White House Releases New Tools for Digital Strategy Anniversary | Nextgov
  • White House Revamps Government Data Trove | Nextgov
  • White House shares API standards guide
  • White House unveils more deliverables on anniversary of the Digital Government Strategy (Fierce Government IT)
  • White House unveils redesigned Data.gov that looks a lot like Google+ | The Verge
  • White House’s Last-Minute Call for Transparency Input | Nextgov
  • Why the U.S. Should Stand Behind its Commitment to Open Government Data—Mashable Blog
  • Wireless Spectrum Research & Development Senior Steering Group’s Testbed Information Portal
  • With e-gov fund cuts, will citizen-developed apps discontinue?—Federal News Radio
  • Worldwide Government Open Data Infrastructure Takes Shape | ProgrammableWeb
  • Worldwide M1+ Earthquakes, Past 7 Days
  • Your Open Data Story
  • “Hiding” Right Out There in the Open
• Category: Ocean
  • AIS Data for Vessel Traffic Patterns
  • Federal Data Resources
  • MarineCadastre.gov
  • Maritime Limits and Boundaries of the United States
  • New Report – Data Categories for Marine Planning
  • NOAA’s Ship Tracker
  • Tweet on Sea Temps
  • Virginia Atlantic Coast Recreational Use
  • Water Column Sonar Data Collection
  • Webinar: “Monitoring the US Ocean and Great Lakes Economy”
  • Webinar: “Using Participatory GIS to Map Ocean Uses in the Mid-Atlantic”
  • Webinar: Vessel Tracking Data Used for Ocean Planning
• Category: Open Data
• Category: Regulatory
• Category: Safety
  • Administration Safety Data Initiative Challenges App Developers
  • Check out talks from the first Safety Datapalooza
  • Data in Action: the SaferBus App
  • Data in Action: the SaferCar App from NHTSA
  • Data tells a safety story
  • New Railroad Safety APIs
  • NHTSA releases SaferCar APIs and mobile app
  • Obama Administration drives release of car safety data, unveils new NHTSA SaferCar app for iOS
  • Results of the Second Annual Safety Datapalooza
  • Taking Data and Making It Easier to Understand
  • Tweet – DOL Safety Deficiencies
  • Tweet – FEMA Fire Data
  • Tweet – OSHA Chemical Exposure
  • Tweet – OSTP Worker Safety App Suggestions
  • Ultra-High Speed (UHS) Application Challenge prize winners announced
  • US Department of Transportation Data Challenge
  • View other data related to safety
  • Welcome to Safety.Data.gov!
  • WeMakeItSafer
• Category: Science & Research
  • Food Price Outlook
  • Energy Information Portal: License IP from the Federal Government
  • Explore Federal Research Data
  • License Technology from Federal Labs
  • Research.gov
  • Resources
  • Science.gov
  • The Guardian Article on Open Access
• Category: Semantic Web
• Category: Space
• Category: States
• Category: Uncategorized
  • Science Hack Day
  • Tweet – Mine Inspection
  • Tweet – NHTSA Recalls
• Category: USAID
• Category: Weather
  • Space Weather: Live from Boulder, Colorado
  • Weather Service Data

Challenges

• Microsoft Launches Innovation Challenge: Food Resiliency and Data Science
• The Esri Human Health and Climate Change App Challenge
• Research Data Alliance Climate Change Data Challenge
• Microsoft Azure for Research program
• NASA and USGS Launch Challenge for Imagining Data Applications for Resilience
• Data Visualization Challenge: Using Data to Improve Justice
• U.S. Food and Drug Administration 2014 Food Safety Challenge
• NASA Launches Earth Science Challenges with OpenNEX Cloud Data
• Esri’s Global Disaster Resilience App Challenge
• Private Sector Support for Data Innovators: CartoDB Grants Program
• U.S. Department of Transportation Data Innovation Challenge
• NOAA and NASA Coastal Flooding Innovation Challenge
• Space Apps Challenge
• Private Sector Challenge: Esri Climate Resilience Challenge
• The American Energy Data Challenge
• Ultra-High Speed Apps to Improve Criminal Justice Operations
• Delivering Mission Critical Voice Communications for Law Enforcement and Public Safety Responders in the COTS LTE Environment
• State of the Environment "Locations" Photo Challenge
• Campus RainWorks 2013
• Respirator Trusted-Source Mobile Application Challenge
• Legislative XML Data Mapping
• Sample Return Robot Challenge - 2014
• Delivering Mission-Critical Voice Communications in a Public Safety COTS LTE Environment
• MTConnect Challenge 2
• Presenting Arts Data Artfully
• Ultra-High-Speed Apps: Using Current Technology To Improve Criminal Justice Operations
• Develop Ability to Use Toxicity Data to Predict Lowest Effect Level Dose in Animal Studies
• Game On! HIV/STD Prevention Mobile Application Video Game Challenge
• The Beauty of Health Data
• Predict the Influenza Season Challenge
• Help NASA build the Solar System Internetwork!
• Predicting Hydrodynamic Forces for Renewable Ocean Energy
• SunShot Prize: Race to the Rooftops
• American Energy Data Challenge
• White House Student Film Festival
• Campus RainWorks Challenge
• SME Financing Challenge
• Blue Button Co-Design Challenge
• Louisville, Kentucky International Open Data Day
• Blue Button Mash Up Challenge
• Health Design Challenge
• healthfinder.gov Mobile App Challenge
• Apps for Vehicles Challenge
• Small Business Innovation Research (SBIR) Success Stories
• Small Business Innovation Research (SBIR) Hall of Fame
• Creating a Collaborative Nano-Bio Manufacturing Institute
• Badges for Vets
• National Clean Energy Business Plan Competition
• What's your energy innovation?
• Sustainable Urban Housing: Collaborating for Liveable and Inclusive Cities
• 2011 Presidential Green Chemistry Challenge awards
• NASA's Green Flight Challenge
• Data Visualization Student Challenge
• America’s Home Energy Education Challenge
• 2011 ENERGY STAR National Building Competition: Battle of the Buildings
• Code for Livability
• Rooftop Solar Challenge
• Build your own challenge for energy efficiency
• C2i: Gaming Challenge
• Startup America Policy Challenge
• National Education Startup Challenge
• NIH Lessons About Bioscience (LAB) Challenge
• America’s Home Energy Education Challenge
• Cook County Big Data Week
• MyMoneyAppUp IdeaBank Challenge
• MyMoneyAppUp Challenge
• The Million Hearts Risk Check Challenge
• SMART-Indivo Challenge
• USDA Drought Code Sprint
• MADD - Tie One on for Safety® Infographic Challenge
• National Institute of Justice Body Armor Challenge
• US DOT Motorcoach Safety Data Student Challenge
• My Air, My Health Challenge
• Blue Button Mash Up Challenge
• Google Places API Developer Challenge
• Federal Challenges
• NYC Big Apps
• Evergreen Apps
• Department of Labor Worker Safety and Health App Challenge
• US DOT Motorcoach Safety Data Student Challenge
• Reporting Patient Safety Events Challenge
• Apps for the Environment
• College Net Price Calculator Student Video Challenge
• Surgeon General's Healthy Apps Challenge
• Apps for Communities
• Healthy People 2020 Leading Health Indicators App Challenge
• VA Blue Button for All Americans
• Ensuring Safe Transitions
• Innovate 4 Healthcare Challenge
• Smart Disclosure Research and Demonstration Design Competition
• America's Home Energy Education Challenge
• WESTEC Manufacturing Challenge Contest
• International Bicycle Design Competition
• Imagine H20 Water Efficiency Competition
• 2011 World Skills Competition: Manufacturing Team Challenge
• Bright Tomorrow Lighting Prize (L Prize) Competition
• Dream !t Do !t Manufacturing 4 the Future Student Challenge
• ASME Student Manufacturing Design Competition
• ASEE-SME Annual Design and Manufacturing Competition
• Computational Fluid Dynamics App Challenge
• The Export Experiment

Applications

• Branchspot
• Nutritionix Track
• LiveStories
• Bonnie
• Woozy: Recalls & Safety Alerts
• IDPsTracker
• Vendor Rank
• FEMA app
• Elder Care Finder
• FlockPlenty - Chicken Egg Tracker
• BankLocal
• Dynamic Proportional Reporting Ratio (PRR) for a Drug-Event Combination
• Proportional Reporting Ratio (PRR) for a Drug
• Red Cross Earthquake App
• Red Cross Hurricane App
• Head Start Resources
• eRecall
• Range
• Zoc Doc
• USDA FoodKeeper
• Gate Guru
• Citymapper
• Healthy Out
• Spot Crime
• Neighborhood Scout
• iCitizen
• City Data
• Healthy Hive
• Medicaid Long Term Care Guide
• Redfin
• Realtor.com
• PublicStuff
• LoopNet Commercial Real Estate Search
• Estately Flip
• Safe Eats
• Civic Request Tracker
• Climate FieldView™
• State Smart
• Bankrank.org
• U.S. Navy Credentialing Opportunities On-Line (COOL)
• Revaluate
• SNAP retail locator
• Food Frequency Method Online
• Super Tracker
• Food Security Portal
• Lose It
• GoodGuide
• Fooducate
• EyeNote®
• IDEAL Currency Identifier ®
• Social Security Benefits Planner
• Papaya Head
• Home Energy Saver
• Power Profiler
• Search for Public School Districts
• College Affordability and Transparency Center
• Product Recalls
• Safety Book
• WeMakeItSafer
• Radiation Emergency Medical Management (REMM)
• National Assessment of Education Progress-NAEP
• Roadify
• Leafully
• DataFerrett - U.S. Census
• SBIR.gov Awards Search
• Base Directory (Military)
• Labor Wage Statistics
• Where are the jobs?
• Smithsonian Collections Search Center
• Leafsnap
• Search for Private Schools
• Search for Public Schools
• Search for Public Libraries
• AIRNow
• Standby Power
• Petroleum Reduction Planning Tool
• EnergyIQ
• Alternative Fueling Station Locator

Featured Content

• Highlights
• Topic Introduction

Application Categories

• Education
• Energy & Environment
• Finance
• Food & Nutrition
• Global Food Security
• Health
• Safety
• Transportation

Application Agencies

• Agricultural Research Service
• Bureau of Justice Statistics
• Bureau of Labor Statistics
• Centers for Disease Control and Prevention
• Centers for Medicare and Medicaid Services
• Consumer Financial Protection Bureau
• Department of Agriculture
• Department of Commerce
• Department of Defense
• Department of Education
• Department of Energy
• Department of Health and Human Services
• Department of Homeland Security
• Department of Housing and Urban Development
• Department of Justice
• Department of Labor
• Department of the Interior
• Department of the Interior
• Department of the Treasury
• Department of Transportation
• Economic Research Service
• Energy Information Administration
• Environmental Protection Agency
• Federal Deposit Insurance Corporation
• Federal Emergency Management Agency
• Federal Housing Finance Agency
• Food and Nutrition Service
• Foreign Agricultural Service
• General Services Administration
• Institute of Museum and Library Services
• National Aeronautics and Space Administration
• National Agricultural Statistics Service
• National Archives and Records Administration
• National Center for Education Statistics
• National Highway Traffice Safety Administration
• National Oceanic and Atmospheric Administration
• National Weather Service
• Overseas Private Investment Corporation
• Social Security Administration
• U.S. Geological Survey
• US Agency for International Development
• US Census Bureau
• US Consumer Product Safety Commission
• US Food and Drug Administration

Announcements and News

• Announcement
• In the News
• New Features

Application Types

• Apps
• Featured
• Federal Data
• Maps
• Mobile
• Web

Migrate legacy Tags

• agency
• alpha.data.gov
• API
• app
• application
• application programming interface (API)
• Apps
• BLM
• car
• Carl Fillichio
• CFR
• challenge
• cities
• civic hacking
• CKAN
• CMS
• code
• consumer
• counties
• data
• Data Publishing
• Data.gov
• Datapalooza
• dataset
• DC.
• Department of Agriculture
• Department of Energy
• department of the treasury
• department of transportation
• DERI
• developer
• developer. APIs
• developers
• digital government strategy
• Dr. Catherine Woteki
• Drupal
• efficiency
• energy
• Energy Data Initiative
• entrepreneur
• Environmental Protection Agency
• EPA
• extensibility
• FACA
• Facilities Registry
• farmer's market
• Fed 100
• Federal Register
• federated data
• federation
• financial capability month
• financial data
• FLU
• format
• fuel
• G-8
• G-8 International Conference on Open Data for Agriculture
• geo
• GITHUB
• GLD
• GLO
• glossary
• gov 2.0
• Government Linked Data
• GPS
• Green
• green vehicles
• GSA
• hackathon
• hacking
• Health
• Health and Human Services
• health data
• health data initiative
• healthdata
• HealthData.gov
• HHS
• Hospital Compare
• international
• Labor Department data
• linked data
• LinkedData
• machine readable
• Metadata
• nasa
• Next.data.gov
• Obama
• Office of Management and Budget
• Office of Science and Technology Policy
• OGD
• OGPL
• OMB
• OPEN DATA
• Open Data Policy
• open government
• Open Government Data
• Open Government Platform
• Open Knowledge Foundation
• open source
• OpenGov
• OSTP
• outcomes
• patent
• Project Open Data
• PTO
• readability
• RPI
• safety
• satellite
• SDKs
• search
• smart disclosure
• software development kits
• space
• States
• syndication
• technology
• test
• Todd Park
• tool
• transformation
• truck
• TWI
• U.S. Environmental Protection Agency
• US Census Bureau
• USAID
• vehicle
• vehicles
• vision
• W3C
• Washington
• Web transformation
• welcome
• white house