Search results

From Earth Science Information Partners (ESIP)
Results 1 – 20 of 53
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  • Services Collaboration Scenarios Service Interoperability Tests WCS - SOAP Mapping Example SOAP Envelope [1],, WSDL [2] DataFed_OGC_Services_by_DataType, Point
    664 bytes (50 words) - 23:13, February 19, 2008
  • guest account. Access is via 5 SOAP web services or a “Direct Interface” query builder (which is just a GUI on top of the SOAP web services). Quality assurance
    4 KB (610 words) - 13:06, April 30, 2008
  • SOAPifying WCS (category SOAP) (section SOAP Envelope)
    WCS SOAP interface (e.g a WCS wsdl) should be defined, to improve interoperability of SOAP-based WCS clients and servers. We would recommend SOAP service
    8 KB (1,012 words) - 03:15, June 7, 2006
  • Services through both SOAP and REST protocols (Paper-PDF).]] The data access and processing services are accessible through the SOAP-WSDL protocol, which
    8 KB (825 words) - 10:48, June 8, 2010
  • </wcs:GetCoverage> </soap:Body> </soap:Envelope> """ render_point_query = """ <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <rmp:Render
    8 KB (826 words) - 17:47, July 11, 2007
  • using some of the key Web service protocols. We will start by examining the SOAP vs REST debate in the context of Earth science applications. We will use
    607 bytes (92 words) - 09:24, July 9, 2008
  • going to demonstrate several web service chains and register all of our (SOAP) services in the ECHO services registry. We plan to use this wiki to coordinate
    3 KB (453 words) - 15:14, March 8, 2017
  • through both standard SOAP-WSDL as well as through URL interfaces. Consequently, web applications can be built either through SOAP-based chaining engines
    7 KB (869 words) - 14:59, March 20, 2008
  • the Web can be inserted into the workflow as a step, whether it is built as SOAP (Simple Object Access Protocol) services or as REST (Representational State
    1 KB (166 words) - 13:33, July 21, 2008
  • WSDL to describe SOAP messaging over HTTP, which defines the operations, or can be implemented as an abstraction purely on top of SOAP (e.g., WS-Transfer)
    8 KB (1,256 words) - 13:03, November 28, 2008
  • performs WCS SOAP query to datafed # INPUT: the soap query, similar to example_soap_in # output: the data stream def query_datafed_wcs(soap_in_text): #
    7 KB (800 words) - 18:29, October 4, 2012
  • Clearinghouse (ECHO) has historically provided a SOAP-based programmatic interface to its metadata holdings. The SOAP interface provided a full-featured set of
    24 KB (3,299 words) - 15:41, August 31, 2012
  • for SMARTFIRE <- Should be a property What Links here on ESIP wiki 400px SOAP/WSDL Service
    428 bytes (24 words) - 04:07, March 10, 2009
  • W*S OGC REST (URL) interfaces. Finally, the SOAP interface is offered to access data, through formal SOAP-based web services. The strong typing of this
    12 KB (953 words) - 14:35, June 18, 2006
  • extensions support dynamic server interface changes, with support for both SOAP and CORBA. The overarching technological contribution of this project is
    48 KB (6,809 words) - 19:50, June 2, 2012
  • links (rel=). Tentatively, the enumeration of service types could be: SOAP - for SOAP/WSDL services REST - for REST (one-line URL services), possibly described
    9 KB (1,369 words) - 18:17, July 22, 2008
  • guest account. Access is via 5 SOAP web services or a “Direct Interface” query builder (which is just a GUI on top of the SOAP web services). Station based
    2 KB (202 words) - 09:53, October 8, 2021
  • include OGC Services developed and hosted by ORNL, UAH, DataFed and EDAC; SOAP services hosted by UAH, DataFed and EDAC; and registry portals developed
    3 KB (458 words) - 13:41, March 27, 2009
  • information for more information about the service Type of Service (e.g. REST, SOAP, WMS, WFS, WCS, RSS) The service metadata link (i.e. WxS GetCapabilities
    1 KB (157 words) - 13:39, February 18, 2009
  • Spatial-temporal processing service suite (something like GRASS for SOA - GMU has SOAP interfaces to GRASS, maybe we can try those?) Example: Extract grid values
    2 KB (183 words) - 06:26, December 20, 2007

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)