300:
397:. This usage was consistent with the coverage concept discussed here, in the sense that an ArcInfo coverage provided a one-to-one mapping from space to the thematic value or classification for each layer or coverage. However, ArcInfo coverages had a particular topological approach to ensure completeness and uniqueness, processed using the BUILD and CLEAN commands are 2D
284:
Many aspects of the real-world may be represented as features whose properties are single-valued and static. These conventional features provide a model of the world in terms of discrete objects located in it. However, in some applications it is more useful to use a model focussing on the variation
380:
Early GIS systems were often characterised as either 'raster' or 'vector' systems, depending on the underlying approach to handling geometry. Raster GIS could be interpreted as using a regular discrete coverage model, while Vector GIS are more feature-oriented. The term "coverage" was most notably
290:
Both viewpoints are required since they each express a fundamental meta-model of the world: as a space populated by things, or as a space within which properties vary. Furthermore, requirements relating to both viewpoints may occur in a single application, typically matching a data-flow: from
152:
The
European legal framework for a unified Spatial Data Infrastructure, INSPIRE, in its Annex II and III relies on the OGC definitions of coverages as well, but modifies them in places in a way making them less compatible and interoperable with the OGC standard. For example, components of the
275:, with the distinguishing characteristics that other features have one particular value associated (such as a road number, which remains constant over all the road's extent) whereas a coverage typically conveys different values at different locations within its domain.
132:
19123 - defines an abstract model of coverages. Many implementations are conceivable which all conform to this abstract model while not being interoperable. This abstract coverage model is concretized to the level of interoperability by the OGC standard
405:
information, thus a polygon "knows" which segments of its perimeter it shares with adjacent polygons. Due to the lack of processing power in computing at the time of its development, the
Coverage model employs indexed
333:
encoding (see Figure) where the first component encodes the coverage description (domain extent, range type, metadata, etc.) and the second part consists of the range set "payload" using some encoding format.
105:
However, coverages are more general than just regularly gridded imagery. The corresponding standards (see below) address regular and irregular grids, point clouds, and general meshes.
216:: a grid which is not necessarily equispaced (like satellite image time series where images do not arrive at regular time intervals, or curvilinear grids following river estuaries)
70:
A coverage is represented by its "domain" (the universe of extent) and a collection representing the coverage's values at each defined location within its range. For example, a
307:
The format-independent logical structure of coverages can be mapped to GML (such as for sensor time series) or to any of a series of data formats, such as
129:
43:
feature that acts as a function to return values from its range for any direct position within its spatial, temporal or spatiotemporal domain
128:
Coverages represent digital geospatial information representing space/time-varying phenomena. OGC Abstract Topic 6 - which is identical to
149:
grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information.
471:
365:(although coverages can only be served as a whole, making it unwieldy in face of the often high-volume coverages, like satellite maps)
326:
As some of these encoding formats are not capable of incorporating all metadata making up a coverage, the coverage model foresees a
561:
386:
210:: a regular, equispaced grid which is spatially referenced (like a satellite image which does have geo coordinates associated)
204:: a regular, equispaced grid which is not spatially referenced (like a raster image which has no geo coordinates associated)
320:
108:
An interoperable service definition for navigating, accessing, processing, and aggregation of coverages is provided by the
546:. IEEE Intl Workshop on Spatial and Spatiotemporal Data Mining (SSTDM-08), Pisa, Italy, 15 December 2008, pp. 408 - 413
94:. Generally, a coverage can be multi-dimensional, such as 1-D sensor timeseries, 2-D satellite images, 3-D x/y/t image
518:
543:
359:
which offers a multi-dimensional coverage query language for ad hoc processing, fusion, aggregation, and filtering
356:
117:
533:. DEXA 2009, August 31 - September 04, 2009, Vienna, Austria, Springer Berlin/Heidelberg, LNCS 5690, pp. 153-163
194:
This abstract coverage is refined into several concrete coverage types, which can be instantiated, for example:
57:
49:
353:
which offers a simple access protocol for coverage subsetting, as well as optional advanced functionality
398:
343:
109:
371:
which allows publishing any kind of algorithm through an advanced remote procedure call style protocol
87:
368:
279:(2nd Ed.) explains the relationship between features and coverages as follows (clause 7.2.2):
447:
394:
390:
486:
458:
436:
169:(indicating its close relation). An abstract coverage consists of the following components:
350:
153:
coverage concept are selectively recombined into new, different definitions of a coverage.
113:
8:
402:
362:
83:
239:: sets of values associated with surfaces located in space/time (such as iso-surfaces)
514:
233:: sets of values associated with curves located in space/time (such as trajectories)
478:
256:
245:: sets of values associated with solids located in space/time (such as CAD objects)
530:
79:
60:
75:
482:
327:
227:: sets of values associated with points located in space/time ("point clouds")
555:
531:
Efficient Map
Portrayal Using a General-Purpose Query Language (A Case Study)
299:
272:
64:
259:, used to analyse spatially distributed data such as rainfall measurements
510:
410:
to store spatial and attribute data separately as opposed to utilizing a
407:
291:
observation through interpretation, and then elaboration and simulation.
95:
99:
53:
459:
OpenGIS Geography Markup
Language (GML) Encoding Standard, OGC 07-036
276:
71:
35:
417:
This has changed with the advent of raster database technology like
418:
382:
262:
triangulated irregular network (TIN), often used for terrain models
34:
is the digital representation of some spatio-temporal phenomenon.
316:
308:
20:
437:
Topic 6 - Schema for coverage geometry and functions, OGC 07-011
421:
which makes efficient ad hoc filtering and processing feasible.
312:
285:
of property values in space and time, formalized as coverages.
544:
Speeding up Array Query
Processing by Just-In-Time Compilation
251:
Among the special cases which can be modeled by coverages are
411:
181:
177:
173:
coverage domain: the extent where valid values are available;
393:
formats into more spatially aware data that featured linked
346:
standards, coverages can be used by various service types:
330:
24:
184:") the coverage consists of, together with their locations
469:
146:
190:
metadata: a slot where any kind of metadata can be added
509:
Zeiler, Michael. Modeling Our World, The ESRI Guide to
187:
range type: a type definition of the range set values
448:
OGC GML Application Schema - Coverages, OGC 09-146r2
16:
Digital representation of spatio-temporal phenomenon
389:. At that time this was a novel concept, extending
375:
120:(WCPS), a spatio-temporal coverage query language.
553:
472:"Data Harmonization - GEOSS AIP-3 Contribution"
542:Jucovschi, C., Baumann, P., Stancu-Mara, S.:
529:Baumann, P.; Jucovschi, C.; Stancu-Mara, S.:
266:
102:, or 4-D x/y/z/t climate and ocean data.
298:
135:GML 3.2.1 Application Schema - Coverages
554:
470:A Woolf; S J D Cox; C Portele (2010).
294:
48:Coverages play an important role in
342:In Web services following the open
13:
14:
573:
156:
376:Industry Terminology: GIS format
271:A coverage is a special kind of
141:) which in turn is based on the
78:might record varying degrees of
562:Geographic data and information
357:Web Coverage Processing Service
176:range set: the set of values ("
118:Web Coverage Processing Service
536:
523:
503:
463:
452:
441:
430:
385:(ArcInfo) format developed by
50:geographic information systems
1:
424:
303:Different coverage encodings
123:
19:Not to be confused with the
7:
337:
10:
578:
513:Design. ESRI Press, 1999.
110:Open Geospatial Consortium
23:Coverage file format from
18:
483:10.13140/RG.2.1.1840.4569
221:multi-feature coverages:
214:ReferenceableGridCoverage
143:Geography Markup Language
38:provides the definition:
267:Relationship to Features
88:digital elevation models
401:datasets that maintain
86:, land cover data, and
381:applied to the legacy
369:Web Processing Service
304:
137:(often referred to as
56:content and services,
302:
208:RectifiedGridCoverage
351:Web Coverage Service
237:MultiSurfaceCoverage
161:Formally, in GMLCOV
114:Web Coverage Service
363:Web Feature Service
198:gridded coverages:
74:image derived from
305:
273:geographic feature
243:MultiSolidCoverage
231:MultiCurveCoverage
225:MultiPointCoverage
84:Aerial photography
295:Coverage encoding
257:Thiessen polygons
569:
547:
540:
534:
527:
521:
507:
501:
500:
498:
497:
491:
485:. Archived from
476:
467:
461:
456:
450:
445:
439:
434:
165:is a subtype of
163:AbstractCoverage
116:(WCS) suite and
577:
576:
572:
571:
570:
568:
567:
566:
552:
551:
550:
541:
537:
528:
524:
508:
504:
495:
493:
489:
474:
468:
464:
457:
453:
446:
442:
435:
431:
427:
378:
340:
297:
269:
167:AbstractFeature
159:
126:
80:light pollution
61:data processing
28:
17:
12:
11:
5:
575:
565:
564:
549:
548:
535:
522:
502:
462:
451:
440:
428:
426:
423:
377:
374:
373:
372:
366:
360:
354:
339:
336:
296:
293:
288:
287:
268:
265:
264:
263:
260:
249:
248:
247:
246:
240:
234:
228:
219:
218:
217:
211:
205:
192:
191:
188:
185:
174:
158:
157:Coverage model
155:
145:(GML) 3.2, an
125:
122:
76:remote sensing
46:
45:
15:
9:
6:
4:
3:
2:
574:
563:
560:
559:
557:
545:
539:
532:
526:
520:
519:1-879102-62-5
516:
512:
506:
492:on 2015-10-17
488:
484:
480:
473:
466:
460:
455:
449:
444:
438:
433:
429:
422:
420:
415:
413:
409:
404:
400:
396:
392:
388:
384:
370:
367:
364:
361:
358:
355:
352:
349:
348:
347:
345:
335:
332:
329:
324:
322:
318:
314:
310:
301:
292:
286:
282:
281:
280:
278:
274:
261:
258:
254:
253:
252:
244:
241:
238:
235:
232:
229:
226:
223:
222:
220:
215:
212:
209:
206:
203:
200:
199:
197:
196:
195:
189:
186:
183:
179:
175:
172:
171:
170:
168:
164:
154:
150:
148:
144:
140:
136:
131:
121:
119:
115:
111:
106:
103:
101:
98:or x/y/z geo
97:
93:
92:coverage data
89:
85:
81:
77:
73:
68:
66:
62:
59:
55:
51:
44:
41:
40:
39:
37:
33:
26:
22:
538:
525:
505:
494:. Retrieved
487:the original
465:
454:
443:
432:
416:
408:binary files
379:
341:
325:
306:
289:
283:
270:
250:
242:
236:
230:
224:
213:
207:
202:GridCoverage
201:
193:
166:
162:
160:
151:
142:
138:
134:
127:
107:
104:
91:
90:all provide
69:
65:data sharing
47:
42:
31:
29:
511:Geodatabase
403:topological
96:time series
496:2016-01-27
425:References
395:attributes
54:geospatial
328:multipart
277:ISO 19109
124:Standards
100:tomograms
72:satellite
36:ISO 19123
556:Category
419:rasdaman
383:ARC/INFO
338:Services
32:coverage
21:ARC/INFO
317:HDF-EOS
309:GeoTIFF
255:set of
52:(GIS),
517:
399:planar
313:NetCDF
182:voxels
178:pixels
139:GMLCOV
112:(OGC)
63:, and
490:(PDF)
475:(PDF)
412:RDBMS
319:, or
515:ISBN
387:ESRI
331:MIME
321:NITF
180:", "
25:Esri
479:doi
391:CAD
344:OGC
147:XML
130:ISO
58:GIS
558::
477:.
414:.
323:.
315:,
311:,
82:.
67:.
30:A
499:.
481::
27:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
