122:
72:(WMS), which portrays spatial data to return static maps (rendered as pictures by the server), the Web Coverage Service provides available data together with their detailed descriptions; defines a rich syntax for requests against these data; and returns data with its original semantics (instead of pictures) which may be interpreted, extrapolated, etc., and not just portrayed.
110:
one communication protocol and at least one data encoding format. To ease overview, extensions have been grouped along five categories: data model, encodings, service model, protocols, and usability. Application
Profiles, finally, establish domain-oriented "bundles" of the WCS Suite. Some of these specifications are briefly presented below.
109:
The WCS suite is organized as a Core, which every WCS implementation must support, and a set of extensions defining additional functionality. Implementers can choose which extension to support, but there are some basic rules to be obeyed - for example, every WCS implementation must support at least
235:
Range subsetting (not to be mixed up with the (domain) subsetting of the WCS Core) allows extracting components from structured cells ("pixels", "voxels") of a coverage. Cells are structured if they contain several components, such as the three components red, green, and blue in color images.
293:
OGC provides the free, open-source
Compliance and Interoperability Test Engine (CITE) to determine compliance of a particular implementation with a given OGC specification. A list of all specification tests made available by OGC can be found on the OGC compliance page.
239:
For example, from a 7-band
Landsat satellite image a range subsetting request may extract the near-infrared, red, and green range components ("bands", "channels"). The geospatial extent is unchanged, that is: "pixels" from all the coverage's locations get delivered.
279:
The forthcoming WCS Coordinate System
Extension allows retrieving coverages in Coordinate Reference Systems (CRSs) different from the Native CRS in which the coverage is stored on the server - in other words, it allows reprojection.
102:
83:
domain to a (possibly multidimensional) range of properties. As such, WCS focuses on coverages as a specialized class of features and, correspondingly, defines streamlined functionality.
429:
86:
WCS uses the coverage model of the OGC GML Application Schema for
Coverages. Thus, WCS supports all coverage types supported by said Application Schema; it is not constrained to
50:
A WCS provides access to coverage data in forms that are useful for client-side rendering, as input into scientific models, and for other clients. The WCS may be compared to the
267:) that is independent from any other OGC service standard. The WCS Processing Extension establishes linkage of WCPS into the WCS suite, introducing an additional request type,
781:
392:
61:(WMS). As with WMS and WFS service instances, a WCS allows clients to choose portions of a server's information holdings based on spatial constraints and other
302:
Implementations where OGC officially acknowledges compliance can be found on the authoritative OGC page. See also the discussion "compliant vs implementing".
774:
79:(WFS), which returns discrete geospatial features, the Web Coverage Service returns coverages representing space/time-varying phenomena that relate a
402:
647:
380:
767:
679:
327:
248:
WCS-T (T standing for transactional) establishes how to upload complete coverages to a server or modify existing coverages on a server.
557:
305:
This below is an unofficial, not checked, and not OGC endorsed list of software that supports WCS as a client and/or server:
224:
129:
The WCS Core establishes basic spatial and temporal extraction. There are two types of subsetting, which can be combined:
934:
315:- server and client (read/write); adopted OGC Reference Implementation for WCS 2.0.1 Core, Reference Implementation for
271:, which accepts a WCPS query string and returns a list of response items resulting from server-side WCPS evaluation.
259:(WCPS) defines flexible ad-hoc processing and filtering on coverage sets. This is an abstract query language (like
467:
316:
256:
151:: delivers an XML-encoded description of service properties and the data holdings offered by the server inquired;
833:
163:: delivers a coverage (or part thereof), either as original data or processed, in some suitable data format.
803:
633:
848:
791:
457:
51:
20:
929:
823:
651:
212:
759:
426:
PYXIS Studio - Free client integrates multiple sources of data on a hexagonal discrete global grid
337:
PYXIS Studio - Free client integrates multiple sources of data on a hexagonal discrete global grid
181:
144:
Technically, WCS Core establishes three request types, inline with the OGC Web
Service definition:
340:
IBL "Moving
Weather" and "Visual Weather" - also implements WCS MetOcean Application Profile draft
858:
828:
141:
performs a cut at the position indicated, thereby reducing the dimension of the result coverage.
80:
903:
697:
683:
853:
584:- free and open-source Big Array Data Analytics server, including Web client toolkit (raswct)
499:
544:
157:: delivers XML-encoded descriptions of coverages (such as their location in space and time);
908:
898:
8:
888:
838:
561:
479:
76:
54:
137:; the result has the same dimension (i.e., number of axes) as the original coverage.
121:
873:
893:
473:
211:
WCS format encodings allow to deliver coverages in various data formats, such as
69:
58:
101:
31:
511:
923:
711:
522:
462:
414:
375:
87:
35:
868:
680:"PCI Geomatics' Web Coverage Server successfully passes compliancy testing"
605:
533:
172:
WCS requests and responses can make use of one of the following protocols:
134:
90:
62:
192:
808:
177:
818:
789:
749:
366:
332:
321:
39:
843:
735:
619:
398:
312:
878:
436:
220:
216:
96:
665:
593:
813:
420:
264:
408:
202:
protocol for transferring XML data and binary coverage data.
195:
protocol for transferring XML data and binary coverage data.
863:
386:
199:
113:
Adopted WCS standards are available from the OGC WCS page.
581:
500:
https://portal.opengeospatial.org/files/?artifact_id=48553
545:
http://www.opengeospatial.org/resource/products/compliant
369:- reference implementation server for WCS 1.x (serve WCS)
260:
185:
372:
42:
information representing space/time-varying phenomena.
502:
OGC GML Application Schema for
Coverages, OGC 09-146r1
423:- LuciadLightspeed and LuciadFusion server and client
512:
OGC Web
Coverage Service standard document download
523:Compliance and Interoperability Test Engine (CITE)
442:QGIS - client (supports both version 1.0 and 1.1)
133:extracts a sub-area of a coverage indicated by a
921:
97:WCS Core, Extensions, and Application Profiles
775:
283:
251:
782:
768:
167:
16:Technical standard for retrieving GIS data
288:
206:
120:
100:
230:
922:
297:
93:coverages like previous WCS versions.
763:
184:(KVP) encoded requests and receiving
274:
13:
243:
188:metadata and binary coverage data.
14:
946:
750:"CARIS Spatial Fusion Enterprise"
594:OGC Network: Web Coverage Service
558:"FAQ: compliant vs implementing"
401:- client (read WCS) and server (
742:
728:
704:
690:
672:
658:
640:
626:
612:
468:Web Coverage Processing Service
430:CARIS Spatial Fusion Enterprise
317:Web Coverage Processing Service
257:Web Coverage Processing Service
598:
587:
575:
550:
547:OGC list of compliant products
538:
527:
516:
505:
493:
1:
712:"Hexagon Geospatial Products"
486:
7:
666:"GDAL Web Coverage Service"
451:
116:
45:
10:
951:
935:Open Geospatial Consortium
792:Open Geospatial Consortium
458:Open Geospatial Consortium
445:TerraPixel Streamap Engine
393:Geomatica Web Server Suite
358:TerraPixel Streamap Engine
21:Open Geospatial Consortium
799:
716:www.hexagongeospatial.com
284:Software support for WCS
252:WCS Processing Extension
634:"OGC TWiki WCSMetOcean"
168:WCS Protocol Extensions
105:WCS Suite: Logical View
77:OGC Web Feature Service
606:"MapServer WCS Server"
534:OGC Compliance Testing
289:OGC Compliance Testing
126:
106:
439:data server) - server
435:Unidata TDS (THREDDS
207:WCS Format Extensions
180:protocol for sending
124:
104:
698:"ESRI ArcGIS Server"
231:WCS Range Subsetting
198:SOAP/XML: using the
191:POST/XML: using the
34:-based retrieval of
26:Interface Standard (
24:Web Coverage Service
839:OGC Reference Model
480:Web Feature Service
432:- server and client
417:- server and client
411:- client (read WCS)
395:- client and server
383:- server and client
355:OpenLayers - client
298:WCS Implementations
176:GET/KVP: using the
70:OGC Web Map Service
55:Web Feature Service
38:– that is, digital
127:
125:WCS trim and slice
107:
917:
916:
790:Standards of the
275:WCS CRS Extension
942:
930:Web Map Services
784:
777:
770:
761:
760:
754:
753:
746:
740:
739:
732:
726:
725:
723:
722:
708:
702:
701:
694:
688:
687:
682:. Archived from
676:
670:
669:
662:
656:
655:
650:. Archived from
644:
638:
637:
630:
624:
623:
616:
610:
609:
602:
596:
591:
585:
579:
573:
572:
570:
569:
560:. Archived from
554:
548:
542:
536:
531:
525:
520:
514:
509:
503:
497:
346:ESRI ArcGIS 10.3
269:ProcessCoverages
155:DescribeCoverage
950:
949:
945:
944:
943:
941:
940:
939:
920:
919:
918:
913:
795:
788:
758:
757:
748:
747:
743:
734:
733:
729:
720:
718:
710:
709:
705:
696:
695:
691:
678:
677:
673:
664:
663:
659:
646:
645:
641:
632:
631:
627:
618:
617:
613:
604:
603:
599:
592:
588:
580:
576:
567:
565:
556:
555:
551:
543:
539:
532:
528:
521:
517:
510:
506:
498:
494:
489:
474:Web Map Service
454:
403:GeoMedia WebMap
389:- client (read)
300:
291:
286:
277:
254:
246:
244:WCS-T Extension
233:
223:, CF-netCDF or
209:
170:
149:GetCapabilities
119:
99:
81:spatio-temporal
59:Web Map Service
48:
17:
12:
11:
5:
948:
938:
937:
932:
915:
914:
912:
911:
906:
901:
896:
891:
886:
881:
876:
871:
866:
861:
856:
851:
846:
841:
836:
831:
826:
821:
816:
811:
806:
800:
797:
796:
787:
786:
779:
772:
764:
756:
755:
741:
736:"PYXIS Studio"
727:
703:
689:
686:on 2012-10-22.
671:
657:
654:on 2011-04-06.
648:"ERDAS APOLLO"
639:
625:
620:"PYXIS Studio"
611:
597:
586:
574:
549:
537:
526:
515:
504:
491:
490:
488:
485:
484:
483:
477:
471:
465:
460:
453:
450:
449:
448:
447:
446:
443:
440:
433:
427:
424:
418:
412:
406:
396:
390:
384:
378:
370:
361:
360:
359:
356:
353:
350:
347:
344:
341:
338:
335:
330:
325:
319:
299:
296:
290:
287:
285:
282:
276:
273:
253:
250:
245:
242:
232:
229:
208:
205:
204:
203:
196:
189:
182:key-value pair
169:
166:
165:
164:
158:
152:
118:
115:
98:
95:
57:(WFS) and the
47:
44:
15:
9:
6:
4:
3:
2:
947:
936:
933:
931:
928:
927:
925:
910:
907:
905:
902:
900:
897:
895:
892:
890:
887:
885:
882:
880:
877:
875:
872:
870:
867:
865:
862:
860:
857:
855:
852:
850:
847:
845:
842:
840:
837:
835:
832:
830:
827:
825:
822:
820:
817:
815:
812:
810:
807:
805:
802:
801:
798:
793:
785:
780:
778:
773:
771:
766:
765:
762:
751:
745:
737:
731:
717:
713:
707:
699:
693:
685:
681:
675:
667:
661:
653:
649:
643:
635:
629:
621:
615:
607:
601:
595:
590:
583:
578:
564:on 2010-12-28
563:
559:
553:
546:
541:
535:
530:
524:
519:
513:
508:
501:
496:
492:
481:
478:
475:
472:
469:
466:
464:
461:
459:
456:
455:
444:
441:
438:
434:
431:
428:
425:
422:
419:
416:
415:ArcGIS Server
413:
410:
407:
404:
400:
397:
394:
391:
388:
385:
382:
379:
377:
374:
371:
368:
365:
364:
362:
357:
354:
351:
348:
345:
342:
339:
336:
334:
331:
329:
326:
323:
320:
318:
314:
311:
310:
308:
307:
306:
303:
295:
281:
272:
270:
266:
262:
258:
249:
241:
237:
228:
226:
222:
218:
214:
201:
197:
194:
190:
187:
183:
179:
175:
174:
173:
162:
159:
156:
153:
150:
147:
146:
145:
142:
140:
136:
132:
123:
114:
111:
103:
94:
92:
89:
88:quadrilateral
84:
82:
78:
73:
71:
66:
64:
60:
56:
53:
43:
41:
37:
33:
29:
25:
22:
883:
869:TransducerML
744:
730:
719:. Retrieved
715:
706:
692:
684:the original
674:
660:
652:the original
642:
628:
614:
600:
589:
577:
566:. Retrieved
562:the original
552:
540:
529:
518:
507:
495:
373:PIXIA Corp's
304:
301:
292:
278:
268:
255:
247:
238:
234:
210:
171:
160:
154:
148:
143:
138:
135:bounding box
130:
128:
112:
108:
85:
74:
67:
49:
27:
23:
18:
343:RSI OPS GIS
161:GetCoverage
30:) defines
924:Categories
809:GeoPackage
721:2019-03-03
568:2012-07-11
487:References
376:HiPER LOOK
65:criteria.
40:geospatial
819:GeoSPARQL
463:coverages
367:GeoServer
363:WCS 1.x:
333:GeoServer
328:EOxServer
322:MapServer
309:WCS 2.0:
193:HTTP POST
36:coverages
844:SensorML
582:rasdaman
452:See also
399:GeoMedia
324:- server
313:Rasdaman
178:HTTP GET
131:Trimming
117:WCS Core
46:Overview
879:WaterML
834:O&M
437:OPeNDAP
349:OPenDAP
221:HDF-EOS
217:GeoTIFF
139:Slicing
75:Unlike
68:Unlike
814:GeoRSS
470:(WCPS)
421:Luciad
381:APOLLO
265:XQuery
794:(OGC)
482:(WFS)
476:(WMS)
409:gvSIG
352:Pyxis
63:query
899:WMTS
864:SRID
387:GDAL
263:and
225:NITF
200:SOAP
91:grid
19:The
909:WRS
904:WPS
894:WMS
889:WFS
884:WCS
874:TMS
859:SLD
854:SFA
849:SOS
829:KML
824:GML
804:CSW
261:SQL
213:GML
186:XML
52:OGC
32:Web
28:WCS
926::
714:.
227:.
219:,
215:,
783:e
776:t
769:v
752:.
738:.
724:.
700:.
668:.
636:.
622:.
608:.
571:.
405:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
