MLI Data Standards Committee

Background

Go to top

Parcel Identification Numbers - PINs

Manitoba Conservation

• What is metadata?

• Why bother with metadata?

• How can metadata be produced?

• Why use standards?

• What standards should be used?

• What data is available
• Whether the data meets specific needs
• Where to find the data
• How to access the data

• Why use metadata?

FGDC Secretariat c/o U.S. Geological Survey 590 National Center Reston, Virginia 22092 Telephone: (703)648-5514 Facsimile: (703)648-5755 Internet: gdc@usgs.gov   Anonymous ftp://fgdc.er.usgs.gov  ftp://fgdc.er.usgs.gov/gdc/html/fgdc.html

Items in red bold and italics like this are necessary to comply with the Federal Geographic Data Committee (FGDC) standard.

Items in bold like this are necessary if you are filling out the section they are in. For example section 2.5, lineage, is not mandatory for the FGDC, but is recommended by Manitoba Conservation GIS Section. If you chose to complete that section you need to complete all the items in this type (or fill in N/A or unknown) to comply with the Federal Geographic Data Committee (FGDC) standard and related software.

ITEMS IN CAPS AND BOLD ARE NOT REQUIRED, BUT ARE ITEMS MANITOBA CONSERVATION GIS STEERING COMMITTEE MEMBERS FEEL WOULD ADD A GREAT DEAL TO THE DOCUMENTATION. WE WOULD LIKE PEOPLE TO DOCUMENT THEM FOR FWS METADATA IF POSSIBLE.

There are a number of items in regular print, some with numbers in front of them. Generally these are headings, and are needed to run the data through a compiler to create files to serve on the Internet or be searchable by the FGDC search engine. If we can keep data consistent with the FGDC, sharing the information with other agencies, partners, etc will be much easier. Other items in regular print are sample data.

Any explanatory notes are in italics

General Notes on the Metadata Sections

1. Identification Information

Most of this section is Mandatory  to comply with the FGDC standard. It is basic identification information about the data set you have created. The data set may be one or multiple files; generally you will document one file at a time.

In some of the sections (for example 1.3 - Time Period) you will need to chose the option appropriate for your data and delete (if you are using the template) or ignore (if you are using a program) the others. This one is simple - you created the data on one day, several days, or a range of days. If it's one file, it's probably one day. Multiple files (like 1:20000 topographic data) could be many dates or a range. Please note - in this sample all the selections have been left for you to view. In a real metadata file, only the applicable ones should be used.

2. Data Quality Information
   
   This section (along with 3, 4, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Basic notes on data quality are very useful. Most GIS staff have wrestled with data that did not document what the attribute codes stood for, or files that did not match at the edges. Any items you can complete here would be useful.

3. Spatial Data Organization Information

This section (along with 2, 4, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

This section can be very simple or very detailed. At a minimum we would like to know if the data is point, vector, raster, or some non-referenced data set! If you wish to go beyond that point, the type of file directs which other fields you need.

4. Spatial Reference Information

This section (along with 2, 3, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Section 4 is guaranteed to give a majority of GIS users in Manitoba Conservation either heartburn or a headache the first time they read it. It goes into very technical detail, including many items geographers may understand but most biologists have never heard of. There are, however, some important basic items here that should be documented. This is another mandatory if applicable section, but certainly some of it SHOULD be applicable!

Section 4 offers some choices depending on your data. You may have geographic data (lat/long - section 4.1), planar data (section 4.2 - includes UTM and state plane data), or local (table inches - some autocad type data). It will not be all of these at once. Your data entry is simplified, but the potential number of choices make the documentation look forbidding. In addition to the horizontal coordinates, some data needs the vertical coordinates. It may be river depth data, perhaps DEM or other topographic data - vertical coordinates are not listed here, but are in the base template if needed.

5. Entity and Attribute Information

This section (along with 2, 3, 4, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

For this section an office would probably use either 5.1 or 5.2, depending on the amount of detail needed to describe the data, or the amount of detail available. If an office chose to give an overview description (5.2 ) of a vegetation layer, for example, they could also cite a reference such as the GAP or TNC vegetation classification standard to give the user further details about the data. If they chose to use 5.1, they could include all the details in the metadata. If the reference is widely available, doing an overview and referencing other documents is probably easier.

6. Distribution Information

This section (along with 2, 3, 4, and 5) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Basically, how can someone get the data from you? Is in "on-line"? Who do they contact? Your own circumstances will dictate what gets filled in here. If the distributor is the same as the contact person in Section 7, it could be left out here. Often, however, they will be different staff or offices. (Hint: if you want to enter the contact information here and sections 1 or 7, and the information is very similar, you can cut and paste in Windows. Just be sure to copy the headings and data for the section.)

7. Metadata Reference Information

   Who documented the data, when and using what type of documentation? This can be important if the data was documented 10 years after it was created versus as it was created. The quality of the metadata will vary. Bold and italicized sections here are mandatory for the FGDC.

   The following pages contain an outline of the basic data elements, with short "cheat sheet" type notes and sample data. These should be used only as guidelines.

For additional information regarding this document, contact mailto:ldonnelly@gov.mb.ca

(FGDC COMPLIANT)

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Red – Items in bold, italic and red are mandatory to comply with the FGDC standard

GREEN – ITEMS IN CAPS AND BOLD AND GREEN ARE MANDATORY IF APPLICABLE (ITEMS IN CAPS AND BOLD ARE NOT REQUIREED BUT ARE ITEMS THE METADATA WORKING GROUP FEEL WOULD ADD A GREAT DEAL TO THE DOCUMENTATION. WE WOULD LIKE PEOPLE TO DOCUMENT THEM)

Bronze – Items in bold and bronze are necessary if you are filling out the section they are in. For example section 2.5 lineage, is not mandatory for the FGDC but is recommended by the Metadata Committee. If you choose to complete that section you need to complete all the items in this type (or fill in N/A or unknown) to comply with the FGDC standard and related software

Example:

Data Set Name: Manitoba Conservation Regional / District Boundaries

1 Identification Information:

1.1 Citation: {who created this data set - numbering changes as this information can be used elsewhere in the documentation}

Possible selections	8	Citation Information:
	8.1	Originator:   Manitoba Conservation
	8.2	Publication Date:   20020305
	8.4	Title:   MB Conservation Regions and Districts

1.2 Description
1.2.1 Abstract:  {background information about the data set}

The Regional Boundaries file shows the areal extent of each of the six regions within Manitoba Conservation and the Districts that make up these Regions.

1.2.2 Purpose:  {Why did you want the data in the first place?}

The Regional Operations Division of Manitoba Conservation delivers integrated natural resource management and environmental protection programs from six regional centers across the province. Each region covers a specific geogaphic area and is administered from a regional office as follows: Northwestern - The Pas Northeastern - Thompson Interlake - Gimli Eastern - Lac du Bonnet Red River - Winnipeg Western - Brandon.

1.3 Time Period {time frame of data set - you need to choose one}

Possible selections	9	Time Period Information
	9.1	Single Date/Time
	9.1.1	Calendar Date:
	9.2	Multiple dates/Times
	9.2.1	Calendar Date: 20020305
	9.2.1	Calendar Date:
	9.3	Range of Dates/Times
	9.3.1	Beginning Date:
	9.3.2	Ending Date:

1.3.1 Currentness Reference: {publication or creation date of sources such as aerial photography}  publication date

1.4 Status
1.4.1 Progress:  {is it done or not? In progress?}   Complete
1.4.2 Maintenance and Update Frequency: {How frequently, if at all?} As needed

1.5 Spatial Domain
1.51 Bounding Coordinates {latitude/longitude coverage limits; important data for Internet data sharing}

1.5.1.1 West Bounding Coordinate: -102.378157

1.5.1.2  East Bounding Coordinate: -88.170168

1.5.1.3  North Bounding Coordinate: 60.065892

1.5.1.4  South Bounding Coordinate: 48.701275

1.6 Keywords  {Keywords of any type are used for locating data when it is documented in a searchable database. The theme and place keywords will probably be the mostly commonly used for MB Conservation data. As with any use of keywords, thought should be given to assigning words the users may search on, or words you will remember in 5 years! Multiple keywords are allowed.}

1.6.1.1 Theme Keyword Thesaurus:  None

1.6.1.2  Theme Keywords:  administrative, region, regional, boundary, district, administration

1.6.2.1 PLACE KEYWORD THESAURUS: {Manitoba Toponymic Database

1.6.2.2 PLACE KEYWORDS: {province name would be very helpful: RM, city, township, refuge are other possibilities}

Manitoba, Red River, Interlake, Eastern, Northwest, Northeast, Western, Churchill, Lynn Lake, Leaf Rapids, Gillam, Thompson, Gods Lake Narrows, Cranberry Portage, Flin Flon, Wabowden, Snow Lake, Norway House, Island Lake, The Pas, Grand Rapids, Riverton, Mafeking, Winnipegosis, Lake Winnipeg East, Swan River North, Gypsumville, Hodgson, Swan River South, Grandview, Ashern, Dauphin, Bisset, Winnipeg Beach, Pine Falls, Lundar, Lac du Bonnet, Neepawa, Grand Beach, Virden, Birds Hill, Selkirk, Seven Sisters, Portage la Prairie, Beausejour, Rennie, Brandon, West Hawk, Hadashville, Carberry, Steinbach, Falcon Lake, Killarney, Manitou, Morris, Sprague, Turtle Mountain, Shoal Lake, Roblin

1.7 Access Constraints:  {Are there legal restrictions or prerequisites for access? An example might be the need to protect the exact location of archaeological sites.}  None

1.8 Use Constraints:  {Legal restrictions, limits due to data quality, etc}  None

1.9 Point of Contact (Section 10 - Contact Information) {who can you get it from- this information is available elsewhere (section 6 and 10) in the documentation; it can be entered here also if the contact is completely different}

1.10 BROWSE GRAPHIC {Some of the most useful documentation incorporates a picture of what the data looks like. That is what a browse graphic is - an illustration. Remember the old a picture is worth a thousand words?.... If you use this section, you need all three items below}

1.10.1 Browse graphic file name

1.10.2 Browse graphic file description

1.10.3 Browse graphic file type

1.13 NATIVE DATA SET ENVIRONMENT: {This section can also include information about the size of the dataset; Kb, MB, etc}

ArcInfo Coverage

2 Data Quality Information

{Just how good is the data anyhow?? - basic plain English description of attributes, the actual lines or topology, the geographic registration, and the original hard copy data that was automated. NOTE - the report is more descriptive, the assessment more specific or measurable. Your choice will depend on the type and quality of your data. It generally would not be necessary to do both}

2.1 Attribute Accuracy

2.1.1 ATTRIBUTE ACCURACY REPORT:

Attribute accuracy is tested by manual comparison of the source with hard copy printouts and/or symbolized display of the digital regional boundaries

2.2 Logical Consistency Report: {how well does everything line up? How was it checked? General description}

Polygons intersecting the neatline are closed along the border. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. Line segments are a set of sequentially numbered coordinate pairs. No duplicate features exist nor duplicate points in a data string. Intersecting lines are separated into individual line segments at the point of intersection. Point data are represented by two sets of coordinate pairs, each with the same coordinate values. All nodes are represented by a single coordinate pair which indicates the beginning or end of a line segment.

2.3 Completeness Report: {how complete is the cover - the whole province/RM/etc? Were parts left out? Size of items mapped?}

All regions and districts are mapped.

2.4 Positional Accuracy

Horizontal positional accuracy is tested by visual comparison of the data with hard copy maps and on-screen with existing data sets that cover the same area. How accurate are you in feet or meters? NOTE: horizontal will be more common than vertical - note NA if not needed.

2.4.1.1 HORIZONTAL POSITIONAL ACCURACY REPORT:

Horizontal positional accuracy for the digital data is tested by visual comparison of the source with hard copy plots.

2.4.2.1 VERTICAL POSITIONAL ACCURACY REPORT:

2.5 LINEAGE

2.5.1.1 Source Citation {Where did the original data come from? Surveys and Mapping? Historic maps?}

Possible selections	8	Citation Information:
	8.1	Originator:   Manitoba Conservation
	8.2	Publication Date:   20020305
	8.4	Title:   MB Conservation Regions and Districts

2.5.1.3 Type of Source Media: 1:1000000 paper map

2.5.1.4 Source Time Period of Content: {choose just one}

Possible selections	9	Time Period Information
	9.1	Single Date/Time
	9.1.1	Calendar Date:
	9.2	Multiple dates/Times
	9.2.1	Calendar Date: 20020305
	9.2.1	Calendar Date:
	9.3	Range of Dates/Times
	9.3.1	Beginning Date:
	9.3.2	Ending Date:

2.5.1.4.1 Source Currentness Reference: source photography date

2.5.1.5 Source Citation Abbreviation:

2.5.1.6 Source Contribution:

2.5.2.1 PROCESS DESCRIPTION: {How was the data entered - digitized? scanned? General steps}

The geographic area served by each regional office was determined by staff and executive within Manitoba Conservation, considering several factors, such as; - traditional associations among communities - economic linkages, travel corridors, market routes - ties by specific communities to certain lands - travel distances, road networks, available means of access to remote areas - locations of rural District Offices, from which many department services are directly delivered -boundaries of Rural Municipalities -eco-region boundaries -location, type, amount and degree of exploitation of natural resources -location and type of clients licensed and permitted by the department -forest fire incidence -etc. Having established the general geographic area for each region based on the above factors, boundary lines were drawn by regional staff on a 1:1000000 map following identifiable physical features, such as roads, railways, rivers and lakeshores or following theoretical lines such as township lines or municipal boundary lines, or where necessary, drawing a point to point line between such features. Where roads form the boundary the arcs were snapped to the 1:1000000 roads layer and township lines were snapped to the 1:1000000 arcs. The provincial boundary used is the boundary on the MLI site.

2.5.2.3 Process Date: 2003

3 Spatial Data Organization Information

{what kind of data is it? Raster, point, vector map inches - depending on that answer, other information may be needed Choose 3.1 OR 3.2. Then , if you wish more detail, chose 3.3 or 3.4 and enter the related items}

3.1 Indirect Spatial reference

3.2 DIRECT SPATIAL REFERENCE METHOD: {raster, point, vector}  Vector

3.3 POINT AND VECTOR OBJECT INFORMATION

3.3.1 SDTS Terms Description

3.3.1.1 Point and Vector Object Type

3.3.2 VPF Terms Description

3.3.2.1 VPF Topology Level

3.3.2.2 VPF Point and Vector Type

3.4 RASTER OBJECT INFORMATION

3.4.1 Raster Object type

4 Spatial Reference Information

{is it Lat/Long, or some other type of coordinate system such as UTM? That answer controls which other questions you need to answer on map projections, grids, etc. It may even be in table inches (local system - 4.1.3). You need to choose 4.1.1 OR 4.1.2 OR 4.1.3}

4.1 HORIZONTAL COORDINATE SYSTEM DEFINITION:

4.1.1 Geographic

4.1.1.1 Latitude Resolution:

4.1.1.2 Longitude Resolution:

4.1.1.3 Geographic Coordinate Values:

4.1.2 Planar {Choose 4.1.2.1 OR 4.1.2.2}

4.1.2.1 Map Projection:

4.1.2.1.1 Map Projection Name:

4.1.2.2 Grid Coordinate System

4.1.2.2.1 Grid Coordinate System Name: Universal Transverse Mercator

4.1.2.2.2.1 UTM Zone Number: 14

4.1.2.4 Planar Coordinate Information

4.1.2.4.1 Planar Coordinate Encoding Method coordinate pair

4.1.2.4.2 Coordinate Representation { or choose 4.1.2.4.3}

4.1.2.4.2.1 Abscissa Resolution 0.61

4.1.2.4.2.1 Ordinate Resolution 0.61

4.1.2.4.3 Distance and Bearing Representation

4.1.2.4.4 Planar Distance Units meters

4.1.3 Local

4.1.4 Geodetic Model:

4.1.4.1 Horizontal Datum Name: North American Datum of 1983

4.1.4.2 Ellipsoid Name: Geodetic Reference System 80

5 Entity and Attribute Information

{What type of information is in any related database? An office may certainly chose to use section 5.1, which gives very detailed attribute information, much like database documentation. This includes values for the attributes such as the region name Section 5.2 will give a more general description of the items, or reference users to other documentation. You can use both 5.1 and 5.2 or just one of them.}

5.1 DETAILED DESCRIPTION

5.1.1 Entity Type:

5.1.1.1 Entity Type Label:  b154_mb.aat

5.1.1.2 Entity Type Definition: Arc attribute table

5.1.1.3 Entity Type Definition Source:  ESRI

5.2 OVERVIEW DESCRIPTION

5.2.1 Entity and Attribute Overview:

5.2.2 Entity and attribute detail citation:

6 Distribution Information

6.1 DISTRIBUTOR

Possible selections	10	Contact Information:
	10.1	Contact Person Primary
		{or may be 10.2 Contact Organization Primary, 10.2.1 contact organization and 10.2.2 contact position - your choice}
	10.1.1	Contact Person: Lindsay Donnelly
	10.1.2	Contact Organization: Manitoba Conservation
	10.4	Contact Address
	10.4.1	Address Type: mailing and physical address
	10.4.2	Address: 200 Saulteaux Cres
	10.4.3	City : Winnipeg
	10.4.4	State or Province: Manitoba
	10.4.5	Postal Code : R3J3W3
	10.5	Contact Voice Telephone: 204.945.5526
	10.8	CONTACT ELECTRONIC MAIL ADDRESS:

6.3 Distribution Liability: None

6.4 Standard Order Process {choose 6.4.1 or 6.4.2 - the clearinghouse software will not recognize both as a standard process}

6.4.1 Non-digital Form:

6.4.2 Digital Form:

6.4.2.1.1  Format name: e00

6.4.2.2 Digital Transfer Option:

6.4.2.2.1.1.1.1 Network Resource Name:

6.4.3 Fees None

7 Metadata Reference Information

{when and how was this data documented - as done? 10 years later? and who?}

7.1 Metadata Date:  20020305

7.4 Metadata Contact:

Possible selections	10	Contact Information:
	10.1	Contact Person Primary
		{or may be 10.2 Contact Organization Primary, 10.2.1 contact organization and 10.2.2 contact position - your choice}
	10.1.1	Contact Person: Lindsay Donnelly
	10.1.2	Contact Organization: Manitoba Conservation
	10.4	Contact Address
	10.4.1	Address Type: mailing and physical address
	10.4.2	Address: 200 Saulteaux Cres
	10.4.3	City : Winnipeg
	10.4.4	State or Province: Manitoba
	10.4.5	Postal Code : R3J3W3
	10.5	Contact Voice Telephone: 204.945.5526
	10.8	CONTACT ELECTRONIC MAIL ADDRESS:

7.5 Metadata Standard Name:

FGDC Content Standards for Digital Spatial Metadata

7.6 Metadata Standard Version: 19940608

Items in red bold and italics like this are necessary to comply with the Federal Geographic Data Committee (FGDC) standard.

Items in bold like this are necessary if you are filling out the section they are in. For example section 2.5, lineage, is not mandatory for the FGDC, but is recommended by Manitoba Conservation GIS Section. If you chose to complete that section you need to complete all the items in this type (or fill in N/A or unknown) to comply with the Federal Geographic Data Committee (FGDC) standard and related software.

ITEMS IN CAPS AND BOLD ARE NOT REQUIRED, BUT ARE ITEMS MANITOBA CONSERVATION GIS STEERING COMMITTEE MEMBERS FEEL WOULD ADD A GREAT DEAL TO THE DOCUMENTATION. WE WOULD LIKE PEOPLE TO DOCUMENT THEM FOR FWS METADATA IF POSSIBLE.

There are a number of items in regular print, some with numbers in front of them. Generally these are headings, and are needed to run the data through a compiler to create files to serve on the Internet or be searchable by the FGDC search engine. If we can keep data consistent with the FGDC, sharing the information with other agencies, partners, etc will be much easier. Other items in regular print are sample data.

Any explanatory notes are in italics

General Notes on the Metadata Sections

1. Identification Information (required)

Most of this section is Mandatory  to comply with the FGDC standard. It is basic identification information about the data set you have created. The data set may be one or multiple files; generally you will document one file at a time.

In some of the sections (for example 1.3 - Time Period) you will need to chose the option appropriate for your data and delete (if you are using the template) or ignore (if you are using a program) the others. This one is simple - you created the data on one day, several days, or a range of days. If it's one file, it's probably one day. Multiple files (like 1:20000 topographic data) could be many dates or a range. Please note - in this sample all the selections have been left for you to view. In a real metadata file, only the applicable ones should be used.

2. Data Quality Information (desirable but, optional)
   
   This section (along with 3, 4, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Basic notes on data quality are very useful. Most GIS staff have wrestled with data that did not document what the attribute codes stood for, or files that did not match at the edges. Any items you can complete here would be useful.

3. Spatial Data Organization Information (desirable but, optional)

This section (along with 2, 4, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

This section can be very simple or very detailed. At a minimum we would like to know if the data is point, vector, raster, or some non-referenced data set! If you wish to go beyond that point, the type of file directs which other fields you need.

4. Spatial Reference Information (desirable but, optional)

This section (along with 2, 3, 5, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Section 4 is guaranteed to give a majority of GIS users in Manitoba Conservation either heartburn or a headache the first time they read it. It goes into very technical detail, including many items geographers may understand but most biologists have never heard of. There are, however, some important basic items here that should be documented. This is another mandatory if applicable section, but certainly some of it SHOULD be applicable!

Section 4 offers some choices depending on your data. You may have geographic data (lat/long - section 4.1), planar data (section 4.2 - includes UTM and state plane data), or local (table inches - some autocad type data). It will not be all of these at once. Your data entry is simplified, but the potential number of choices make the documentation look forbidding. In addition to the horizontal coordinates, some data needs the vertical coordinates. It may be river depth data, perhaps DEM or other topographic data - vertical coordinates are not listed here, but are in the base template if needed.

5. Entity and Attribute Information (desirable but, optional)

This section (along with 2, 3, 4, and 6) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

For this section an office would probably use either 5.1 or 5.2, depending on the amount of detail needed to describe the data, or the amount of detail available. If an office chose to give an overview description (5.2 ) of a vegetation layer, for example, they could also cite a reference such as the GAP or TNC vegetation classification standard to give the user further details about the data. If they chose to use 5.1, they could include all the details in the metadata. If the reference is widely available, doing an overview and referencing other documents is probably easier.

6. Distribution Information (desirable but, optional)

This section (along with 2, 3, 4, and 5) is considered mandatory only if it applies to your data. The items in CAPS AND BOLD are those the service GIS coordinators feel are important. The items in this section in bold are those items that need to be filled in both to comply with the standard and to make the FGDC clearinghouse software work properly if the section in question is used.

Basically, how can someone get the data from you? Is in "on-line"? Who do they contact? Your own circumstances will dictate what gets filled in here. If the distributor is the same as the contact person in Section 7, it could be left out here. Often, however, they will be different staff or offices. (Hint: if you want to enter the contact information here and sections 1 or 7, and the information is very similar, you can cut and paste in Windows. Just be sure to copy the headings and data for the section.)

7. Metadata Reference Information (required)

   Who documented the data, when and using what type of documentation? This can be important if the data was documented 10 years after it was created versus as it was created. The quality of the metadata will vary. Bold and italicized sections here are mandatory for the FGDC.

   The following pages contain an outline of the basic data elements, with short "cheat sheet" type notes and sample data. These should be used only as guidelines.

For additional information regarding this document, contact mailto:ldonnelly@gov.mb.ca

Definition of Provincial Reference Systems in Manitoba

NAD83(CSRS98)  will become the standard for new work.

Related Terms