Search results
From Earth Science Information Partners (ESIP)
- What links here: REST vs. SOAP The business world has long ago made the jump from URL(REST) to SOAP-based service interface, and all of the scientific1 KB (219 words) - 22:35, May 9, 2006
- the emergence of internet-based web service architectures (e.g. JSR 168, SOAP, etc.). The advent of these web services will allow the parties to share6 KB (989 words) - 21:41, January 6, 2008
- temporal, spatial, and many other metadata characteristics. ECHO's offers a SOAP API for data discovery, but is also developing an OpenSearch compliant capability5 KB (769 words) - 08:04, October 30, 2009
- be considered. We need to agree on: a messaging exchange scheme (perhaps SOAP or KVP or HTTP/REST?) a common definition of layer (that is, what if a model20 KB (3,141 words) - 09:56, July 4, 2011
- team is also working to provide the option to output data in XML and as XML SOAP responses.12 KB (634 words) - 09:53, October 8, 2021
- Protocol HTTP HyperText Transfer Protocol JAVA JAVA programming language SOAP Simple Object Access Protocol SQL structured query language - a standard76 KB (1,411 words) - 10:36, November 27, 2018
- folks need to get beyond the barrier of making their first SOAP services call. See Talk:REST vs. SOAP Here is an explanation of SciFlo's data space/time query7 KB (1,165 words) - 22:41, May 9, 2006
- for CSV. This is the only supported standard for query inputs. Others, like SOAP over HTTP-POST, don't add enough value to deserve support. The big advantage5 KB (654 words) - 17:32, December 14, 2010
- beginning. We need to agree on: (1) a messaging exchange scheme (perhaps SOAP or KVP or HTTP/REST?), (2) a common definition of layer (that is, what if10 KB (1,631 words) - 13:04, November 28, 2008
- information about the wide variety of web-based services (e.g., OGC, REST, SOAP, etc.) and interfaces available from ESIP members. Ultimate Benefit: Better8 KB (1,216 words) - 14:47, April 16, 2009
- related issues, is very important. Other network transport mechanisms like SOAP can be added, and any implemented web services don't need to change. The34 KB (5,082 words) - 02:53, September 16, 2011
- information about the wide variety of web-based services (e.g., OGC, REST, SOAP, etc.) and interfaces available from ESIP members. Ultimate Benefit: Better10 KB (1,416 words) - 13:38, May 15, 2009
- standardized web services, callable through well-defined Internet protocols (SOAP, REST). Homogenization can also be accomplished by physically transferring32 KB (4,599 words) - 09:52, September 13, 2010
- to geospatial processes, models and operations. Services may be wrapped in SOAP web services for combined functionality. Those are some of the key standards42 KB (6,424 words) - 09:53, October 8, 2021
- terrific! Next week we can expose our SOAP services that can be chained: Data Access to spatial point data (WCS SOAP, netCDF_Table out) - AIRNOW, VIEWS_OL10 KB (1,547 words) - 14:28, June 18, 2006
- adapters); Semantic web service chaning (description/matching beyond WSDL and SOAP enveope.. More ideas"> Rhusar I think the distinction between these two is14 KB (1,800 words) - 15:24, May 27, 2008
- browser is also an editor for data processing workflows using a dedicated SOAP-based workflow engine. A typical workflow for map view is shown in Fig. XX47 KB (7,201 words) - 12:06, August 12, 2008
- interoperability - service semantics, service description/matching beyond WSDL and SOAP enveope.. rhusar Connecting AQ data providers with decision makers: Federal8 KB (1,045 words) - 01:30, January 16, 2006
- Remote Sensing or related field preferred • Experience with WMS/WCS, Java, SOAP, REST, AXIS, XML • Understanding of remote sensing and/or GIS concepts •1 KB (182 words) - 12:32, December 28, 2009
