|
Nova Scotia's
Geographic Information
Standards
Chapter 4
Data Quality and Accuracy
(Continued)
4.8 Data Currency Statements for Digital and Cartographic Products
4.8.1 Purpose:
To provide the user of the data with sufficient details regarding changes
made to the data.
4.8.2 Background:
There comes a point in most digital and hardcopy data set life cycles
when revision is necessary. This revision is done either as part of a
revision cycle or because of requirement by a particular client. In the
case of general revision cycles, unless all users are aware of the revision
periods all too often existing clients (and for that matter potential
ones) are not aware that an update is available. In some instances updates
of older material are very important to application modelling and therefore
a notice of update would be prudent.
The general trend on the data production side has been that it is up
to the client to seek out these updates with little or no notice given
to the prospective client. Such action would be acceptable if the revision
cycle for a given digital product was well documented and only carried
out after ALL the data is brought through a maintenance cycle. (For example
a database consisting of 100 files. If during a revision cycle file number
54 is updated 5 times and file number 72 is updated 2 times, there is
no consistency upon which the client can depend.)
4.8.3 Standard: Digital data currency
The data providers will ensure that information is attached
to the data sharing agreements which highlight the type of updates which
have been carried out on the data.
4.8.4 Standard: Cartographic Product data currency
The data providers will ensure that sufficient information is included
in the surround portion of the product highlighting the types of updates
which have been carried out on the map sheet.
4.9 Topic: User Guides for Digital Products
4.9.1 Purpose:
To provide the user of digital geographic data with sufficient information
upon which to access and manipulate the data.
4.9.2 Background:
Here is a situation - A client walks off the street and asks for a copy
of a digital file for a specific area. After a prolonged process of obtaining
the particulars for the client, the data provider obliges and provides
the client with his/her requested file. Two days later the client is unable
to read the data because they do not understand its content. A number
of calls are made to the data provider who in turn spends 40 minutes "walking
the client through" the particulars of the data. Sound Familiar !! How
can this be eliminated or at least reduced. The answer: User Guides.
A users guide can provide the potential client with a series of instructions
and information specific to a data set. These instructions would in turn
allow the client to (a) better understand the particulars of ordering
the given data and (b) better understand the product they are about the
order.
4.9.3 Standard: Primary Data Product Users Guides
for Digital Products
All primary digital data products will have an associated Users Guide.
4.9.4 Guideline: Primary Data Product Users Guides
for Digital Products
As a guideline for providing a standard Users Guide the following
content should be considered as part of the Guide:
|
|
|
|
| - |
Purpose of Guide |
|
| - |
Scope of Guide |
|
| - |
Organization of Guide |
|
| - |
Content of the Product |
This section will provide the client with some general
information surrounding the product. In many respects the material in this
section will highlight to "building blocks" for the product. |
| |
About the Product |
|
| |
About Source Id's |
Including definitions and conventions used to assigning
ids |
| |
About Feature Codes |
Including definition of the rationale behind the codes |
| |
About the Spatial Framework |
Including highlights of projection, datums, etc. |
| |
About Logical Consistency (Topology) |
Indicating the levels of topology which should be
anticipated for the product. |
| - |
Ordering the Product |
This section will alert the client to the types of information
they must consider when ordering data. |
|
| |
Preparing to Order
the Product |
|
| |
What do you need to
know |
|
| |
License Agreement
|
Highlighting the fact that such are required. |
|
|
|
Price List |
Details specific to the product and or pointing to
the Policy |
|
|
Choosing Media and Format |
|
|
|
Background |
Including details on What to order, From who and How
to |
|
|
Table of Availability
|
Providing a list of formats available for product |
|
|
Order Form
|
A generic form which will appear in all product guides
providing the necessary pick lists for specific ordering. |
|
|
Typical File Sizes |
Providing the client with an indication of how big
data for a given product can get. |
| - |
|
Installation of Product |
This section will highlight basic instructions on what
the client can expect to receive and how to install the data. |
|
|
Receiving Product Files |
|
|
|
Media(s) available |
|
|
|
Formats Available |
|
|
|
Data to be Provided |
Provides an indication of files which will be received
e.g. Readme files, Lineage Documentation, product files, etc. |
|
|
Extracting Data from
Media to Your Environment |
|
|
Verifying Installation |
Providing tips in case things don't appear to work
right. |
| - |
|
Working with the Product |
This section will provide information related to the basic
characteristics of the product including some data collection practices. |
|
|
Characteristics of the Deliverable |
|
|
|
File Names |
|
|
|
File Extensions |
|
|
|
File Formats |
Including notes related to the internal structure
characteristics for the product. |
| - |
|
Data Collection Practices |
[The sections here will provide the client with flags
that cover the intent of the product and in some instances the products
limitations.] |
|
|
Working with the Spatial Framework
|
Including guidelines on integration of product with
other products |
|
|
Working with File Resolution |
|
|
|
Geometric Effects in the Product |
|
| - |
|
Address for Ordering Products |
This section is provided to highlight to the client where
data can be obtained. This section will highlight addresses of LIC's and
the NSGC. |
| - |
|
Appendix A : Glossary |
| - |
|
Other Appendices (as required
depending on the product guide): |
|
|
-
|
Feature Code Appendix (e.g. DEM Guide will require a feature
code list for exclusion areas) |
|
|
-
|
Scale Dependent Details |
4.9.5 Guideline: Thematic Data Product Users Guides for Digital Products
Thematic data providers should also provide clients with Users Guides
for their respective product(s). As a further guideline, these guides
should contain similar information to that outlined in the guideline for
primary data product Users Guides.
Chapter 4 continued -
[Sections 4.0 to 4.3] [Sections
4.4 to 4.7]
[Sections 4.10 to 4.11] [Sections
4.12 to 4.16]
[Sections 4.17 to 4.19]
Chapter Four Table of Contents
|
