WCS supports the networked interchange of multi-dimensional and multi-temporal geospatial data as “coverages” through the “getCapabilities”, “describeCoverage” and “getCoverage” interfaces. WCS provides intact geospatial data products encoded in HDF-EOS, NITF, and GeoTIFF to meet the requirements of client-side rendering, multi-valued coverages, and input of scientific models and other clients beyond simple viewers. Demo... WSDL

URL	VERSION	DATA
http://laits.gmu.edu/cgi-bin/NWGISS/WCS1020	1.0.20	MODIS, ASTER
http://laits.gmu.edu/cgi-bin/NWGISS/NWGISS	1.0.0	MODIS, ASTER
http://geobrain.laits.gmu.edu/cgi-bin/gdalwcs/gdalwcs	1.0.0	Global Landsat

WFS supports the networked interchange of geographical vector data as "feature" which is described by a set of properties where each property can be thought of as a {name, type, value} tuple and at least one property is geometry-valued. The name and type of each feature property is determined by its type definition in its schema file. All feature data are encoded in Geographic Markup Language (GML) which is a kind of extensible markup language for support and storage of geographic vector data to meet the requirements of complex spatial analysis. Capabilities...

ACCESS URL	VERSION	DATA
http://geobrain.laits.gmu.edu:8099/geoserver/wfs	1.0.0	Nationwide states, counties, cities, rivers, roads and railroads

WMS supports the networked interchange of geospatial data as a "map", which is generally rendered in a spatially referenced pictorial image, such as PNG, GIF or JPEG, dynamically from real geographical data. Demo...

ACCESS URL	VERSION	DATA
http://laits.gmu.edu/cgi-bin/NWGISS/wms	1.1.1	MODIS, ASTER, Landsat
http://laits.gmu.edu:8099/geoserver/wms	1.1.1	Nationwide states, counties, cities, rivers, roads and railroads

CSW supports the registry and discovery of geospatial information resources. It plays a "directory" role in the open, distributed Web service environment: providers register their capabilities using metadata, and users can then query the metadata to discover interesting information. See introduction and detail. Demo...

URL	Description
http://geobrain.laits.gmu.edu:8099/LAITSCSW2/discovery	Search GeoBrain local archive.
http://geobrain.laits.gmu.edu:8099/LAITSCSF2/discovery	Search GeoBrain local archive and online data registered in ECHO.

URL	Description
http://laits.gmu.edu:8099/wics/classifiers/ISODATA	An unsupervised ISODATA image classification service. WSDL.... Demo...
http://data.laits.gmu.edu:8099/wics/classifiers/MinDistance	A supervised image classification service. WSDL...

URL	Description
http://geobrain.laits.gmu.edu:8099/axis/services/gdal_util	Data Format Conversion, resampling & subsetting. WSDL.... Demo...

Rerojects a coverage in HDF Grid format to another projection. Currently it supports all the projections defined in GCTP. The parameters of request include the URL of source HDF file, target projection type, resampling method, bounding box and the 15 float type projection parameters defined by GCTP, and the result is a URL point to the target HDF file. See WSDL. Demo...

URL

http://data.laits.gmu.edu/cgi-bin/WCTS/wcts

http://laits.gmu.edu/cgi-bin/WCTS/wcts

http://geobrain.laits.gmu.edu/cgi-bin/WCTS/wcts

We have developed SOAP based Webservice interfaces(please follow this link to learn about SOAP) to many non-interactive functions of GRASS (Geographic Resources Analysis Support System) software. See detail...

• BPELPower v1.0:
  • Based on the mainstream standards including BPEL, WSDL, WSIF, Xalan, Xerces, UDDI, AXIS, SOAP, JNDI, J2EE (servlets/EJBs/JSPs), Jetspeed (Portlets) and JMX. It runs on top of popular application servers, such as Tomcat, J2EE, JBoss, Weblogic and WebSphere. It now supports BPEL-based web service chain completely. It supports:
    • "deploy it". WSDL-based web services can be deployed in BPELPower, where their validations are checked.
    • "see it". WSDL-based web services can be displayed in BPELPower in different ways.
    • "try it". BEPLE-based web services chain can be executed in BPELPower dynamically. Different invocations (e.g., HTTP POST/GET, SOAP document/rpc, etc.) are well supported.
See detail at http://geobrain.laits.gmu.edu:8099/bpel.

Abstract model designer enables domain experts to use data types, service types and existing abstract models as basic components to construct abstract models, which represent the domain knowledge of the experts, in a clicking and dragging manner. The experts can choose to validate the abstract models and register those models into the Catalogue Service for Web (CSW), which will enable the abstract models available for later use. An abstract model can be instantiated and transformed into a concrete BPEL process, which can be executed in a BPEL engine (e.g. BPELPower ). See tutorial...

Enter...