215:
113:
25:
66:
606:
Surveys and
Resource Mapping Branch. Spatial Archive and Interchange Format, Release 3.2, Formal Definition. 1995. (also Release 3.1 (1994); 3.0 (1993); 2.0, (1992); 1.0 (1991); and 0.1, (1990)) Surveys and Resource Mapping Branch, British Columbia Ministry of Environment, Lands and Parks. 258p. Also
594:
Sondheim, M., P. Friesen, D. Lutz, and D. Murray. 1997. Spatial
Archive and Interchange Format (SAIF). in Spatial Database Transfer Standards 2: Characteristics for Assessing Standards and Full Descriptions of the National and International Standards in the World. edited by Moellering H. and Hogan R.
443:
SAIF became a
Canadian national standard in 1993 with the approval of the Canadian General Standards Board. The last version of SAIF, published in January 1995, is designated as CGIS-SAIF Canadian Geomatics Interchange Standard: Spatial Archive and Interchange Format: Formal Definition (Release 3.2),
418:
approach. It was recognized that scripts to carry out such transformations could in fact add information content. When Safe
Software developed the Feature Manipulation Engine (FME), it was in large measure with the express purpose of supporting such transformations. The FMEBC was a freely available
410:
The primary advantage of SAIF was that it was inherently extensible following object oriented principles. This meant that data transfers from one GIS environment to another did not need to follow the lowest common denominator between the two systems. Instead, data could be extracted from a dataset
447:
The work on the SAIF modeling paradigm and the CSN classes was carried out principally by Mark
Sondheim, Henry Kucera and Peter Friesen, all with the British Columbia government at the time. Dale Lutz and Don Murray of Safe Software developed the Object Syntax Notation and the Reader and Writer
317:
used to define a dataset's schema. The second is the Object Syntax
Notation (OSN), a data language used to represent the object data adhering to the schema. The CSN and OSN are contained in the same physical file, along with a directory at the beginning of the file. The use of ASCII text and a
381:
Object referencing can be used as a means of breaking up large monolithic structures. More significantly, it can allow objects to be defined only once and then referenced any number of times. A section of the geometry of the land-water interface could define part of a
365:, a feature defined in the SAIF standard. All user defined classes must belong to a schema, one defined by the user or previously existing. Different schemas can exist in the same dataset and objects defined under one schema can reference those specified in another.
554:"CGIS-SAIF Canadian geomatics interchange standard: Spatial archive and interchange format: Formal definition (Release 3.2) / Prepared by the Ministry of the Environment, British Columbia. : P29-171-001-1995E - Government of Canada Publications - Canada.ca"
350:. These can be considered as forming a base schema. Using CSN, a user defines a new schema to describe the features in a given dataset. The classes belonging to the new schema are defined in CSN as subclasses of existing SAIF classes or as new enumerations.
427:
The SAIF project was established as a means of addressing interoperability between different geographic information systems. Exchange formats of particular prominence at the time included DIGEST (Digital
Geographic Information Exchange Standard) and
590:
Sondheim, M., K. Gardels, and K. Buehler, 1999. GIS Interoperability. pp. 347–358. in
Geographical Information Systems (Second Edition), Volume 1, edited by Paul A. Longley, Michael F. Goodchild, David J. Magurie and Davide W.
419:
software application that supported a wide range of transformations using SAIF as the hub. The FME was developed as a commercial offering in which the intermediary could be held in memory instead of as a SAIF dataset.
130:
38:
411:
defined by the first GIS, transformed into an intermediary, i.e., the semantically rich SAIF model, and from there transformed into a model and format applicable to the second GIS.
394:
boundary. This geometric feature can be defined and given an object reference, which is then used when the geometry of the coastline, municipality and marine park are specified.
432:(Spatial Data Transfer Specification, later accepted as the Spatial Data Transfer Standard). These were considered as too inflexible and difficult to use. Consequently, the
402:
Multimedia objects can also be objects in a SAIF dataset and referenced accordingly. For example, image and sound files associated with a given location could be included.
44:
455:, and then to those working on the initial version of the Open Geospatial Interoperability Specification (OGIS), the first efforts of what became the
177:
149:
459:(OGC). A series of 18 submissions to the ISO SQL Multimedia working group also helped tie SAIF to the original ISO work on geospatial features.
83:
75:
156:
433:
652:
163:
452:
600:
276:
258:
236:
196:
52:
145:
330:
SAIF defines 285 classes (including enumerations) in the Class Syntax
Notation, covering the definitions of high-level features,
302:
301:) was defined in the early 1990s as a self-describing, extensible format designed to support interoperability and storage of
134:
318:
straightforward syntax for both CSN and OSN ensure that they can be parsed easily and understood directly by users and
415:
170:
456:
647:
642:
463:
314:
229:
223:
524:
313:
SAIF has two major components that together define SAIFtalk. The first is the Class Syntax
Notation (CSN), a
123:
622:
240:
628:
Safe Software, 2010, FME Readers and Writers, (Spatial Archive and Interchange Format, pp. 183 - 191)
319:
596:
491:
322:. A SAIF dataset, with a .saf or .zip extension, is compressed using the zip archive format.
617:
553:
373:
SAIF supports multiple inheritance, although common usage involved single inheritance only.
567:
500:
467:
343:
636:
627:
414:
This notion of model to model transformation was deemed to be realistic only with an
462:
Today SAIF is of historical interest only. It is significant as a precursor to the
387:
357:
for example could be defined with attributes including age, species, etc. and with
451:
SAIF was brought to the attention of Michael Stonebraker and Kenn Gardels of the
391:
112:
485:
347:
335:
331:
436:
decided to develop SAIF and to put it forward as a national standard in
479:
525:"Spatial Archive and Interchange Format:Formal Definition Release 3.2"
607:
published by the Canadian General Standards Board, CAN/CGSB-171.1-95.
437:
532:
466:
and as the formative element in the development of the widely used
383:
429:
339:
448:
software that became part of the Feature Manipulation Engine.
208:
106:
59:
18:
444:
issue CAN/CGSB-171.1-95, catalogue number P29-171-001-1995E.
618:
Government of Canada Publications, CGIS-SAIF Release 3.2
496:
Pages displaying short descriptions of redirect targets
406:
Model transformations and related software applications
87:
137:. Unsourced material may be challenged and removed.
16:Historical storage format for geospatial data
8:
53:Learn how and when to remove these messages
519:
517:
277:Learn how and when to remove this message
259:Learn how and when to remove this message
197:Learn how and when to remove this message
222:This article includes a list of general
146:"Spatial Archive and Interchange Format"
513:
482: – JSON subset for geospatial data
291:Spatial Archive and Interchange Format
7:
453:University of California at Berkeley
135:adding citations to reliable sources
88:move details into the article's body
228:it lacks sufficient corresponding
14:
346:coordinate system components and
34:This article has multiple issues.
213:
111:
64:
23:
503: – Geospatial ETL Software
342:coordinates and relationships,
122:needs additional citations for
42:or discuss these issues on the
434:Government of British Columbia
1:
494: – Standard of encoding
468:Feature Manipulation Engine
361:specified as a subclass of
669:
653:Open Geospatial Consortium
457:Open Geospatial Consortium
464:Geography Markup Language
315:data definition language
595:Elsevier, Netherlands.
488: – GIS data format
390:boundary and part of a
243:more precise citations.
386:as well as part of a
359:ForestStand::MySchema
355:ForestStand::MySchema
131:improve this article
568:"Freeing the Data"
529:Geographic Data BC
377:Object referencing
492:File format (GIS)
326:Schema definition
287:
286:
279:
269:
268:
261:
207:
206:
199:
181:
105:
104:
84:length guidelines
57:
660:
648:GIS file formats
643:Interoperability
623:SAIF Release 3.1
583:
582:
580:
578:
564:
558:
557:
550:
544:
543:
541:
540:
531:. Archived from
521:
497:
363:GeographicObject
282:
275:
264:
257:
253:
250:
244:
239:this article by
230:inline citations
217:
216:
209:
202:
195:
191:
188:
182:
180:
139:
115:
107:
100:
97:
91:
82:Please read the
68:
67:
60:
49:
27:
26:
19:
668:
667:
663:
662:
661:
659:
658:
657:
633:
632:
614:
587:
586:
576:
574:
566:
565:
561:
552:
551:
547:
538:
536:
523:
522:
515:
510:
495:
476:
425:
416:object oriented
408:
400:
379:
371:
338:relationships,
328:
311:
303:geospatial data
283:
272:
271:
270:
265:
254:
248:
245:
235:Please help to
234:
218:
214:
203:
192:
186:
183:
140:
138:
128:
116:
101:
95:
92:
81:
78:may be too long
73:This article's
69:
65:
28:
24:
17:
12:
11:
5:
666:
664:
656:
655:
650:
645:
635:
634:
631:
630:
625:
620:
613:
612:External links
610:
609:
608:
604:
592:
585:
584:
559:
545:
512:
511:
509:
506:
505:
504:
501:FME (software)
498:
489:
483:
475:
472:
424:
421:
407:
404:
399:
396:
378:
375:
370:
367:
327:
324:
310:
307:
285:
284:
267:
266:
221:
219:
212:
205:
204:
119:
117:
110:
103:
102:
72:
70:
63:
58:
32:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
665:
654:
651:
649:
646:
644:
641:
640:
638:
629:
626:
624:
621:
619:
616:
615:
611:
605:
602:
601:0-08-042433-3
598:
593:
589:
588:
573:
569:
563:
560:
555:
549:
546:
535:on 2001-05-17
534:
530:
526:
520:
518:
514:
507:
502:
499:
493:
490:
487:
484:
481:
478:
477:
473:
471:
469:
465:
460:
458:
454:
449:
445:
441:
439:
435:
431:
422:
420:
417:
412:
405:
403:
397:
395:
393:
389:
385:
376:
374:
368:
366:
364:
360:
356:
351:
349:
345:
341:
337:
333:
325:
323:
321:
316:
308:
306:
304:
300:
297:, pronounced
296:
292:
281:
278:
263:
260:
252:
242:
238:
232:
231:
225:
220:
211:
210:
201:
198:
190:
179:
176:
172:
169:
165:
162:
158:
155:
151:
148: –
147:
143:
142:Find sources:
136:
132:
126:
125:
120:This article
118:
114:
109:
108:
99:
89:
85:
79:
77:
71:
62:
61:
56:
54:
47:
46:
41:
40:
35:
30:
21:
20:
575:. Retrieved
571:
562:
556:. July 2002.
548:
537:. Retrieved
533:the original
528:
461:
450:
446:
442:
426:
413:
409:
401:
380:
372:
362:
358:
354:
352:
329:
312:
309:SAIF dataset
298:
294:
290:
288:
273:
255:
249:January 2022
246:
227:
193:
187:January 2022
184:
174:
167:
160:
153:
141:
129:Please help
124:verification
121:
96:October 2012
93:
76:lead section
74:
50:
43:
37:
36:Please help
33:
392:marine park
369:Inheritance
336:topological
241:introducing
637:Categories
577:5 November
539:2010-11-24
508:References
486:GeoPackage
398:Multimedia
320:developers
224:references
157:newspapers
39:improve it
388:municipal
384:coastline
332:geometric
86:and help
45:talk page
474:See also
348:metadata
344:geodetic
340:temporal
480:GeoJSON
423:History
334:types,
237:improve
171:scholar
599:
591:Rhind.
438:Canada
226:, but
173:
166:
159:
152:
144:
178:JSTOR
164:books
597:ISBN
579:2022
572:XYHt
430:SDTS
299:safe
295:SAIF
289:The
150:news
133:by
639::
570:.
527:.
516:^
470:.
440:.
353:A
305:.
48:.
603:.
581:.
542:.
293:(
280:)
274:(
262:)
256:(
251:)
247:(
233:.
200:)
194:(
189:)
185:(
175:·
168:·
161:·
154:·
127:.
98:)
94:(
90:.
80:.
55:)
51:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
