Content deleted Content added
Added wikilinks; removed template |
GoingBatty (talk | contribs) m General fixes, replaced: 1990s → 1990s (2) |
||
Line 2:
{{external links|date=October 2012}}
{{Orphan|date=January 2017}}}}
The Spatial Archive and Interchange Format (SAIF, pronounced ''safe'') was defined in the early
'''SAIF Dataset'''
Line 20:
'''Object Referencing'''
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 [[
'''Multimedia'''
Line 34:
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 [http://www.gwg.nga.mil/ntb/baseline/docs/digest/part1.pdf DIGEST] (Digital Geographic Information Exchange Standard) and [[SDTS]] (Spatial Data Transfer Specification, later accepted as the Spatial Data Transfer Standard). These were considered as too inflexible and difficult to use. Consequently, the [[Executive Council of British Columbia|Government of British Columbia]] decided to develop SAIF and to put it forward as a national standard in [[Canada]].
SAIF became a Canadian national standard in
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 [http://www.safe.com/reader_writerPDF/saif.pdf Reader and Writer] software that became part of the Feature Manipulation Engine.
|