This document discusses a project to enable more government tabular data to be used in a geographic context. The goals are to 1) make more data consumable for geographic applications and education, 2) increase demand for geographic technologies, and 3) create a positive impact on agencies and companies using geospatial technologies. The proposed solution is a platform to easily georeference non-spatial data through address geocoding, polygon matching, and catalog/search capabilities. This will allow data to be mapped and used in a variety of workflows including spreadsheets, GIS, and the web.

1. Enabling Use of Government Tabular Data in a Geographic ContextU.S. Federal Geographic Data Committee 2009 CAP Grant, Category 4

2. FGDC Cap Grant, Category 4Easy and productive access to geographic, tabular government dataReference location by Address, Code, or CoordinatesShared Public Web ServiceDiscoverable, Accessible, and Applicable to geographic contexts

3. Project GoalsEnable more data to be consumable in a geographic contextIncreases in geo-enabled data will cause an increase in demand for geographic applications and education Geo-enabled data creates a positive externality for the entire ecosystem of agencies and companies that leverage or provide geospatial technologiesMapping should be an option for every data work flow when there is a geographic component available (80-90% of the time)Make data available to a variety of workflows (spreadsheet data to GIS and GeoWeb) and provide dynamic loops (GIS data back to spreadsheets and GeoWeb) allow for collaboration and data sharing

4. Proposed SolutionDeliver a platform to provide easy georeferencing of non-spatial dataQuality Assurance and Error identification and remediation of contributed datasetsCatalog and store taxonomy of existing boundary data sourcesAdd OGC Catalog Services for the Web (CSW) support

6. CAP Added CapabilitiesGeoCoding Engine for Street Address georeferencingGeoJoin Engine for polygonal region georeferencingSpatial, hierarchical aggregationFederated search and discoveryOpenSearch and GeoRSS OGC Catalog Services for the Web (CSW)

7. GeoCommons ArchitectureWeb Services APIFinder!Maker!SearchCoreAnalysisEngineGeoJoinEngineFile ParsersGeoCoding EngineData Store

8. GeoCoding EngineModularized ArchitectureUS Address Parsing moduleUS TIGER/Line Database and importerReplaceable componentsOpen-SourceGeoCoding EngineWeb Service APIAddress String ParserRubyStreet DatabaseSQLite

9. GeoReferencing EngineStored GeoCommons boundary definitionsIntegration with existing georeferencing servicesJoin imported data with any GeoCommons dataset

10. GeoReferencing Process

11. Data Sharing

12. Data Attributes

13. Data Description with Metadata StandardsFGDC

14. ISO 19115

15. Microformats

16. Meta

17. HyperlinksData Sharing with Common, Open StandardsKML

18. Shapefile

19. CSV

20. Atom

21. JSON

22. WFS

23. SpatialiteExport data for GIS workflows (shapefile)

24. Export data for non-geographic workflows (.csv)

25. Export data to 3D Globes (.kml)

26. Data Findability

27. Geospatial Federated Search Search

28. Geospatial Federated Search Search

29. Candidate DatasetsFedStatsRecovery.govGrants.gov

30. Thank you