provide the platform, tools, and resources for a geoscience cyberinfrastructure barn raising
About USGIN Lab
A partnership of the Association of American State Geologists (AASG - state geological surveys) and the U.S. Geological Survey (USGS) formally agreed in 2007 to develop a national geoscience information framework that is distributed, interoperable, uses open source standards and common protocols, respects and acknowledges data ownership, fosters communities of practice to grow, and develops new web services and clients. The AASG and USGS have formed an interagency Steering Committee to pursue design and implementation of the U.S. Geoscience Information Network (USGIN).
| Who? | Organizations & Projects - USGIN parent organizations, funders, partners, projects, and giants we are building on |
|
| What? | Standards - International technical standards on geospatial data, metadata, protocols, and web services |
|
| Exactly what? | Profiles - Specifications for USGIN specific profile implementations of above standards |
|
| How? | Applications - Software applications that may support above standards and profiles |
|
| Making it real! | Implementations - Implement profiles and software applications together to create data, metadata, and web services |
|
| Help! | Community - Discussions and work groups on USGIN profile and implementation development |
USGIN System Overview
| Latest additions and changes |
|---|
|
Make Tomcat Work Through Port 80 | 12 years 8 weeks ago » On a machine running Tomcat and Apache, you can set things up so that instead of having to type Tomcat URLs with ":8080" on the end of the domain, you use a proxy to redirect that... |
|
GeoServer Complex-Feature WFS Configuration: Directory Structure | 12 years 8 weeks ago » At present, there is no user-interface component that helps you configure a complex-feature WFS in GeoServer. I'm sure that it is being worked on, but in the meantime, the configuration is done... |
|
GeoServer Workspace Configuration | 12 years 8 weeks ago » Workspace.xml is one of two configuration documents used to create a workspace in GeoServer The id element is GeoServer's internal identifier for the workspace The name element is the human-readable... |
|
GeoServer FeatureType Configuration | 12 years 8 weeks ago » This XML document tells GeoServer to treat a datastore as a featuretype -- that is, provide it as a featuretype that can be requested via WFS. For the most part, this document contains information... |
|
GeoServer Namespace Configuration | 12 years 8 weeks ago » The namespace.xml is one of two files that compose a workspace in GeoServer. This configures the namespace aspect of the workspace. The id element is GeoServer's internal identifier for the namespace... |
|
Geoserver | 12 years 8 weeks ago » GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source... |
|
deegree | 12 years 8 weeks ago » deegree is a Java Framework offering the main building blocks for Spatial Data Infrastructures. Its entire architecture is developed using standards of the Open Geospatial Consortium (OGC) and ISO/TC... |
|
Apache Tomcat | 12 years 8 weeks ago » Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed under the Java... |
|
GeoServer GeoSciML WFS | 12 years 8 weeks ago » By default, Geoserver's WFS server is capable of conveying only simple features. Basically, a simple feature has some number of attributes, and each attribute has a value. Think of it like a flat... |
|
A Sample GeoServer Mapping file for NCGMP09 to GeoSciML | 12 years 8 weeks ago » This is a snippet from a GeoServer/App-schema mapping file. The type mapping section is where you indicate what fields in your source data go into which fields in your output data. This particular... |
|
From NCGMP09 to GeoSciML (and back again) | 12 years 8 weeks ago » I'm almost done building a complete mapping file that will output GeoSciML MappedFeatures from polygon features in a database that follows the NCGMP09 schema. This schema, developed as part of the... |
|
GeoServer Complex-Feature WFS Configuration: Data Connections in the Mapping File | 12 years 8 weeks ago » When you configure a complex feature service, you have to manually map your data connection parameters into an XML document called a mapping file. I found that the easiest way to make this... |
|
GeoServer FeatureType Configuration | 12 years 8 weeks ago » This XML document tells GeoServer to treat a datastore as a featuretype -- that is, provide it as a featuretype that can be requested via WFS. For the most part, this document contains information... |
|
Metadata about Metadata for a Service That Provides Metadata | 12 years 8 weeks ago » ... kind of sounds like overkill, but there's reason behind the confusion! Imagine that you're trying to find some data. In the USGIN scheme, in order to find data you search through CSW ... |
|
OGC CSW APISO - OGC ISO19115/ISO19119 application profile for CSW 2.0 | 12 years 8 weeks ago » This document specifies a profile of the OGC Catalog Service for the Web (CSW) 2.0.2 using the ISO 19115/ISO19119 metadata content model, with support for XML encoding per ISO19139 and HTTP... |
 |
USGIN is supported by:
|
 |
