-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
67 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
[.preface] | ||
== Preface | ||
|
||
//// | ||
All prefatory sections should be given the attribute `[.preface]` before their title, but this can be ommitted in the case of: | ||
|
||
Introduction Foreword Acknowledgements | ||
|
||
Which are recognised automatically as prefatory | ||
//// | ||
|
||
The 17^th^ International Hydrographic Conference held in May 2007, directed that CHRIS (now the IHO Hydrographic Services and Standards Committee - HSSC) establish a Marine Spatial Data Infrastructures Working Group (MSDIWG) to identify the Hydrographic Community inputs to National Spatial Data Infrastructures (NSDI). In 2015, the responsibility for the MSDIWG moved from HSSC to the Inter-Regional Coordination Committee (IRCC). This change reflected the ongoing nature of the work of the MSDIWG in tackling predominantly non-technical matters. The Terms of Reference of and other information about the MSDIWG are available at: | ||
|
||
... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
[[intro]] | ||
== Introduction | ||
|
||
//// | ||
Introductions are recognised automatically as belonging to the preface of the document | ||
//// | ||
|
||
The purpose of this document isto explain the way that a Hydrographic Office (HO) should promote, support, and participate in Spatial Data Infrastructures (SDIs). It is not definitive in its nature, preferring instead to provide guidance on how best to achieve this through practical advice, simple step by step processes, useful links to reference material and examples of best practice. | ||
|
||
... | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
//// | ||
The main body of the document follows the preface, and any number of top-level clauses can be added before the annexes. | ||
They in turn can contain any number of subclauses. | ||
|
||
It is good practice to insert anchors before all clauses, in case you need to cross-reference them from elsewhere | ||
in the document. | ||
//// | ||
|
||
[[first_clause]] | ||
== Clause name | ||
|
||
Spatial Data is the data or information that identifies the geographic location of features and boundaries on Earth and Space, such as natural or constructed features, oceans and space but also includes encoding attributes, observations and other metrics concerning these features and boundaries. | ||
|
||
Spatial data is usually stored as coordinates and topology, and is data that can be mapped. Spatial data is often accessed, manipulated or analyzed through Geographic Information Systems (GIS). | ||
|
||
... | ||
|
||
[[clause_1_1]] | ||
=== What constitutes an MSDI? | ||
|
||
An MSDI can be described as a framework comprising the key components shown in <<fig1>>. | ||
|
||
[[fig1]] | ||
.The Four pillars of MSDI | ||
image::image001.png["",622,350] | ||
|
||
... |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
//// | ||
All annexes are indicated with the role attribute `[appendix]` | ||
//// | ||
|
||
[[annexA]] | ||
[appendix] | ||
== SDI Best Practice | ||
|
||
Oil spills remain one of the most serious environmental risks for the oil and shipping industries as the environment and livelihoods can be considerably affected in the event of a significant incident. Although large spills from tankers and oil industry operations have become less frequent in the last few decades, accidents still happen and, because of their potential impact, they represent a serious risk that must be effectively managed. | ||
|
||
Annexes can contain abbreviations, glossaries, and links. They do not contain references sections; for that, see the S-100 series. | ||
|
||
... | ||
|