Strategic Intent

Provide the Opportunity to Reduce Duplication should become a nationally managed "access point" that provides a mechanism for all levels of government to participate or integrate with, thus creating a single location for citizens to access government data.


Submitted by
Share this idea:

Stage: Active

Feedback Score

55 votes

Idea Details

Vote Activity (latest 20 votes)

  1. Upvoted
  2. Upvoted
  3. Downvoted
  4. Upvoted
  5. Upvoted
  6. Upvoted
  7. Upvoted
  8. Upvoted
  9. Upvoted
  10. Upvoted
  11. Downvoted
  12. Upvoted
  13. Upvoted
  14. Upvoted
  15. Upvoted
  16. Upvoted
  17. Upvoted
  18. Upvoted
  19. Upvoted
  20. Upvoted
(latest 20 votes)

Similar Ideas [ 4 ]


  1. Comment

    Future efforts should enable all levels of government to provide their data to, and search/retrieve data from, a server 'cloud'. Cloud-hosted data resources could also be utilized in support of a great variety of web services.

    Contributors should receive usage statistics to help demonstrate business needs for the data and for data-sharing tools. Contributors should have the option of scheduling a 'reminder notification' to be sent to them before anticipated future update dates.

  2. Comment
    William Craig

    Some state and local governments may choose to adopt the existing standards and protocols, thus saving time and money otherwise spent designing their own systems. Others will want to push the envelope, innovating and adding new and useful features. Data.Gov should encourage such innovation and provide the basic tools to allow the innovators to provide linked access to both standard and enhanced data resources.

  3. Comment
    Mike Mahaffie

    This idea matches the vision for the NSDI -- a nationwide collection of geospatial data that originates in local, county and state agencies and is aggregated up to the national level. It is an approach that depends on a national effort to develop and promote data standards and to manage the integration of data from all levels of government.

  4. Comment
    Mike Vanhook should be a national data gateway that provides one click access to raw data (KML, XML, CSV, SHP, and other) and services (RSS, REST, JSON) of data sources. With an attempt to index and visualize common data and to provide statistics and services that leverage data access to produce national products that will enable the nation to innovate, evolve, and build upon public data resources.

    I think is a simple concept that is supported by a massive industry and social community growing out of live and accessible content so long as the data is accessible in as few clicks as possible.

    State and local agencies have been invited to participate by providing local data sites, but should be integrated when possible into the data catalogs to provide national statistics and data.

  5. Comment

    People from every sector frequently work across government boundaries (e.g. watersheds, regions, coastal issues) and need to find information from multiple government organizations/jurisdictions. It can be very frustrating when they find that they are required to 1) "learn" dramatically different interfaces in order to accomplish their searches, and 2) conduct searches against individual government agency systems. Encouraging all levels of government to participate in Data.Gov would result in effective and efficient access to their data that would translate to a huge time savings for the public and private sectors.

  6. Comment
    David Smith

    Toward reducing duplication, I would think it would make sense to also allow other governmental agencies, i.e. state agencies, to submit their metadata to

  7. Comment

    This effort will mirror what Maryalnd is trying to do for public access to data and web services. This will serve all sectors of the community in Maryland and it's neighbors - homeland security, emergency response, health, transportation, environment, etc.

  8. Comment
    Paul Wilkinson

    Nevada is also doing interesting things along the lines of using a common technical standard, XBRL, to help different state agencies communicate better with each other and thus streamline business compliance with state laws. The state published a paper at . A side benefit of using such a global standard is that there's already plenty of software available to improve the quality of data going too -- and therefore data coming from -- the government.

  9. Comment
    Khailaa Hosny

    Need to be careful about validity and quality of the centric data, in order to be usefull for analysis. Raw data, and environments under which the data is taken (applicability)must be available with the data.

    Need to avoid central storage of filtered data. Data provided from different sources for the same information must not be consolidated, instead both versions must be available.

  10. Comment
    Mike Vanhook

    "Some experts suggest that emphasis should shift toward the technical and institutional infrastructure to support the distribution of geographic information throughout society. These spatial data infrastructures (SDI) are frameworks that incorporate technologies, policies, standards and human resources to store, process and distribute vast amounts of data across many organizations and among governments."

    NGAC - The Changing Geospatial Landscape

    I think this goes for other public datasets and data types as well for concepts like

  11. Comment

    This idea is essential to realizing the full potential of at all levels of government. States and local government are currently encouraged to launch their own sites that share data, but this idea is not truly powerful until everyone works together.

  12. Comment

    while I agree with this and think that should be the "core" of almost all important datasets, I think it is KEY to maintain important, unique, specific datatools and report systems which agencies have developed at nearly the same level, to not let them take the back stage just because we're also making the process behind accessing their data more easy.

    Users should be invited to check out, but the presentation tools and reports should not be left out in some misguided effort to make all data presentation "consistent." Surely we should make a consistent means to access data, but we should allow redundant means of *presenting* that data to coexist.

    For example, College Navigator or the Occupational Outlook Handbook both present some really critical statistics about colleges and careers in our nation that should be located at (integrated well of course with pages on the agency's website contextualizing the data, the effort which attained it, the purpose, reliability, current uses, etc) However, College Navigator and the OOH themselves are VERY useful as means of presenting that data in an accessible way.

    Maybe data tools like College Navigator can be located on, but it is important to me that the many means of making data more understandable/useful to the public be maintained and kept prominent in a meaningful way even if the dataset they are based on has been modularized and congregated with other data-sets in a uniform manner.

  13. Comment

    to avoid confusion, in my above post where I say

    "For example, College Navigator or the Occupational Outlook Handbook both present some really critical statistics about colleges and careers in our nation that should be located at"

    I mean

    "For example, College Navigator or the Occupational Outlook Handbook both present some really critical statistics about colleges and careers in our nation and those raw statistics should be located at"

    I don't have a strong opinion about where reports should lay.

  14. Comment

    We should sharpen and broaden the "access point" concept to;

    GI_JOE: Government/Google Internet Journal of Original Entry, (mirror image for security purposes) using the concept of "perpetual inventory," adding all data with "pre-programmed" Google Analytics-like Motion Charts, graphs and data/information tables that include at least 10 to 15 years prior data, and 5 to 10 years statistical projections: high, low and most probable, with footnotes to explain high/low variations; e.g. 10 to 15 years of companies, and numbers of people, whose employer-paid health insurance has been dropped, projected into the future also showing the affect of "killing" the Advantage Plus subsidies and impact of companies paying more that, say, 12% health benefits who might prefer to drop their coverage and pay the 8.5% tax.

    This should eliminate, once and for all, static one year and one month "reports" in favor of multiple year/month reports, perhaps using the "add one, drop one," tables and (motion) charts (such as most "energy" companies now send to their customers).

Add your comment

Your comment will be published after it's approved by the moderators.