Skip to end of metadata
Go to start of metadata

Geoportal Link


NAP Field Descriptions

 

Metadata Record Information

Contact

Spatial Representation Info

Reference System Info

Identification Info

Distribution Info

Data Quality Info

Metadata Maintenance

SP Custom Fields

 

Metadata Record Information       
       
        File Identifier
        File URI
        Language
        Character Set
        Hierarchy Level
        Date Stamp
        Metadata Standard Name
        Metadata Standard Version

Contact

        Organization Name
        City
        Administrative Area
        Country
        Linkage
        Role
        E-mail

Spatial Representation Info

        Geometric Object Type Code
        Geometric Object Count
        (Raster Data only)
            Number of Dimensions
            Dimension Name Type Code
            Dimension Size
            Resolution
            Resolution Unit of Measure
            Cell Geometry Code    

Reference System Info

        Code
        Code Space

Identification Info

        Title
        Alternative Title
        Date
        Date Type
        Edition
        Responsible Party
           Organization Name
           City
           Administrative Area
           Country
           Role
        Series
        Abstract
        Purpose
        Status
        Spatial Representation Type
        Denominator
        Distance
        Distance Unit of Measure
        Language
        Dataset Character Set
        Topic Category
        Supplemental Information
        Environment Description
        Maintenance and Update Frequency
        Graphic Overview
            File Name
            File Description
            File Type
        Extent
            West Bound Longitude
            East Bound Longitude
            South Bound Longitude
            North Bound Longitude
            Extent Description
        Temporal Extent
            Description
            Begin Position
            End Position
        Keywords (Free Text)
        Keywords (LAC Thesaurus)
        Keywords (MNR Thesaurus)
        Keywords (Place)
        Use Limitations
        Access Constraints
        User Constraints
        Other Constraints 

Distribution Info

        Linkage
        Protocol
        Description
        Transfer Options
            Transfer Size
        Distribution Information
            Organization Name
            City
            Administrative Area
            Country
            Role

Data Quality Info            

        Scope Level
       Data Lineage Statement
        Data Source Description

        Process Step Description

Metadata Maintenance

        Maintenance Note
        Organization Name
        City
        Administrative Area
        Country
        Role
   

SP Custom Fields

        Data Holdings
      User Guide Links
            Guide Label
            Guide Link

        External Links
            External Label
            External Link


   

File Identifier: (Mandatory) Unique phrase or string which uniquely identifies the metadata file. Usage Note: Each metadata record shall have a unique file identifier to distinguish it from other resources. System supplied: the structure of the number has no meaning. *Important Note: This field is automatically populated by the database when you submit your record and SAVE this section.
Example:
 4baf22ce-5427-440d-9a6d-9153192b7b4f


File URI
: (Mandatory) File name as it appears in the database. It is consistent with service name / dataset name. Each metadata record shall have a file name to distinguish it from other files and link to the corresponding data it is describing. The structure of the name has meaning.
Example:
NAP/DMTI_POI_Aerodromes.xml
*Note: All file names are given the folder name “NAP/” which must be entered at the time of the file creation.

Language
: Language of the metadata composed of an ISO 639-2/T three letter language code and an ISO3166-1 three letter country code. Usage Note: This attribute describes the primary language of free text attributes (in the metadata). The language code is given in lower case, and the country code is given in uppercase. Language codes: http://www.loc.gov/standards/iso639-2/php/English_list.php. Country codes: http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html. When more than one language is given in the metadata then the attribute locale (5.2.11) is mandatory.
Example:
eng; CAN


Character Set: (Mandatory) Character coding standard in the metadata. Usage Note: Restricted to ‘utf8’.
Example:
utf8
 
Hierarchy Level: (Mandatory) Dataset level to which the metadata applies. Usage Note:
Select from Code List. Options include: attribute, attributeType, collectionHardware, collectionSession, dataset, series, nonGeographicDataset, dimensionGroup, feature, featureType, propertyType, fieldSession, software, service, model, tile.  
Usage Note: If hierarchy is unknown, then default value is “dataset”.
Example:
A record describing an individual dataset in the “CanMap RouteLogistics” package would be at the “dataset” hierarchy level. A record describing “CanMap RouteLogistics” would be at the “series” hierarchy level.
 
Date Stamp: (Mandatory) Metadata creation date. Current practice in SP is to include the date the record was first created at Scholars Portal. Any metadata creation date provided by data producer is removed.
Example:
2009-06-30 (follows the year, month, and day e.g. 2006-10-01)
 
Metadata Standard Name: (Mandatory) Name of the metadata standard/profile used. Usage Note: In Metadata Editor, this entry is filled in by default.
Example:
North American Profile of ISO19115:2003 – Geographic information – Metadata
 
Metadata Standard Version: (Mandatory) Version of the metadata standard/profile used. Usage Note: In SP Metadata Editor, this entry is filled in by default.
Example:
2009  

Organization Name: (Mandatory) The party responsible for the metadata content. Usage Note: Name of the responsible organization.
Example:
Map and Data Library, University of Toronto
 
City: (Optional) City of the address.
Example:
Toronto
 
Administrative Area: (Optional) State or province of the address. Usage Note:
Lists of states and provinces are available at http://www.usps.com/ncsc/lookups/usps_abbreviatio
ns.htm (US) and http://www.canadapost.ca/common/tools/pg/manual/PGaddress-e.asp (Canada)
Example:
Ontario
 
Country: (Optional) Country of the address. Usage Note:
The country name shall be taken from the ISO 3166 code list available at http://www.iso.org/iso/en/prodsservices/ISO 3166ma/02iso-3166-code-lists/index.html. The full country name must be entered, not the code.
Example:
Canada

Linkage: (Optional) Internet location (address) for on-line access which uses a Uniform Resource Locator address or similar addressing scheme such as www.isotc211.org or ftp.isotc211.org.
Example:
www.mdl.library.utoronto.ca 
 
Role: (Mandatory) Function performed by the responsible party. Usage Note: Select from Code List. Options include: resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author, collaborator, editor, mediator, rightsHolder
 
Additional Usage Note:
The following is an outline of how different role codes should generally be used in a SP metadata record.
·    distributor – the organization which distributed the dataset to Scholars Portal.
·    principalInvestigator – the primary authoring organization of the data. In some cases this is the same organization as the publisher – this is generally the case for Statistics Canada data.
·    publisher – the producer of the dataset (under Data Identification Information). A responsible party with this role code MUST be provided in all records. If the data producer also has another role, add the responsible party twice. For example, Statistics Canada is both the principalInvestigator and a publisher.
·    originator – this role code is typically used only in the Metadata Maintenance Information section, to describe the organization from which the source metadata originated.
·    pointOfContact – each record will include at least one organization as a general point of contact. Scholars Portal should be the point of contact for both metadata enquiries (Metadata Maintenance Information section) and data enquiries (Contact section).
*Note for Metadata Contact, always use the ‘pointOfContact’ code
Example:
distributor (Could display in user interface as ‘Distributor’)
 
E-mail: (Optional) The electronic mailbox address of the responsible organization.
Example:
gis@scholarportal.info

 

Geometric Object Type Code: (Mandatory) Name of point or vector objects to locate zero, one, two or three dimensional locations on the dataset. Usage Note: Select from Code List. Options include: complex, composite, curve, point, solid, surface
Usage Note: Definition of composite: “connected set of curves, solids or surfaces.” Definition of a curve: “bounded, 1-dimensional geometric primitive, representing the continuous image of a line.” Definition of a surface: “bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane.”
Example:
composite

Geometric Object Count:
(Optional) Total number of point or vector objects in the dataset.
Example:
5235

Number of Dimensions:
(Mandatory)* The number of independent spatio-temporal axes. Usage Notes: This information is usually found under Spatial Respresentation Information in ArcCatalog as part of the automated metadata created using ESRI’s ArcGIS suite.
* For Raster data only
Example:
2
 
Dimension Name Type Code: (Mandatory) Axis name. Usage Note: Select from Code List. Options include: row , column, vertical, track, crossTrack, line, sample, time
Example:
line
 
Dimension Size: (Mandatory) Number of elements along the axis.
Example:
4
 
Resolution: (Optional) Degree of detail in the grid dataset. Usage Note:  A measure is made of a value and a unit of measure.
Example:
10cm
 
Resolution Unit of Measure: (Optional) Degree of detail in the grid dataset. Usage Note:
A measure is made of a unit of measure.
Example:
cm
 
Cell Geometry Code(Mandatory) Identification of grid data as point or cell. Usage Note:
Select from Code List. Options include: point, area, voxel
Example:
area

Code: (Mandatory) Alphanumeric value identifying the source reference system. Usage Note:

CRS (coordinate reference system) should be taken from a register such as EPSG (www.epsg.org).  A dataset that has both a horizontal and a vertical CRS shall use a compound reference system with the horizontal CRS documented first and the vertical CRS documented second.
 
Example:
4269  (This code represents NAD83 UTM zone 17N)

Code Space: (Optional) Identifier/ namespace of the system in which the code is valid.
Example:
www.epsg.org
 
Title: (Mandatory) Name by which the cited resource is known. Usage Note: Generally, use title supplied by vender. When vendor supplies a title which includes acronyms, leave these, but also spell them out in parentheses if this is not already done elsewhere in the title.
 
Additional Usage Note:
If supplying title because one was not available from the vendor, generally avoid initial articles (such as The and A), acronyms, abbreviations, name of organization and dates and versions unless needed to differentiate between records. Acronyms, abbreviations, and other common
 
Additional Usage Note:
If a title is available in a second official language, put the second title into the Alternate Title field (alternateTitle). If the title is not already available in a second language, it will not typically be translated.
 
Example:
Car Pool Parking Lots (CPL)
 
Alternative Title: (Optional) Short name or other language name by which the cited information is known.
 
Example:
SWOOP (as an alternate title for Southwestern Ontario Orthophotography Project.)
 
Date: (Mandatory) Reference date for the cited resource.
Example:
2009-06-30 (follows the year, month, and day e.g. 2006-10-01)

Date Type:
(Mandatory) Identification of the event used for the temporal aspect in the resource. Usage Note: Select from Code List. Options include: creation, publication, revision, notAvailable, inForce, adopted, deprecated, superseded
 
Example:
creation

Edition:
(Optional) Version of the cited resource. Usage Note: Use information as supplied by vendor.
 
Example:
2008.3
 
Responsible Party:
Identification of a responsible party for the resource and the party’s role in the resource.

Organization Name:
(Mandatory) Name of the responsible organization.
Example: DMTI Spatial Inc.

City:
(Optional) City of the address.
Example:
Toronto

Administrative Area: (Optional) State or province of the address. Usage Note: Lists of states and provinces are available at: http://www.usps.com/ncsc/lookups/usps_abbreviatio
ns.htm (US) and http://www.canadapost.ca/common/tools/pg/manual/PGaddress-e.asp (Canada)
Example:
Ontario

Country:
(Optional) Country of the address. Usage Note: The country name shall be taken from the ISO 3166 code list available at http://www.iso.org/iso/en/prodsservices/ISO 3166ma/02iso-3166-code-lists/index.html. The full country name must be entered, not the code.
Example:
Canada

Role:
(Mandatory) Function performed by the responsible party. Usage Note: Select from Code List. Options include: resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author, collaborator, editor, mediator, rightsHolder
 
Additional Usage Note:
The following is an outline of how different role codes should generally be used in a SP metadata record.
·         distributor – the organization which distributed the dataset to Scholars Portal.
·         principalInvestigator – the primary authoring organization of the data. In some cases this is the same organization as the publisher – this is generally the case for Statistics Canada data.
·         publisher – the producer of the dataset (under Data Identification Information). A responsible party with this role code MUST be provided in all records. If the data producer also has another role, add the responsible party twice. For example, Statistics Canada is both the principalInvestigator and a publisher.
·         originator – this role code is typically used only in the Metadata Maintenance Information section, to describe the organization from which the source metadata originated.
·         pointOfContact – each record will include at least one organization as a general point of contact. Scholars Portal should be the point of contact for both metadata enquiries (Metadata Maintenance Information section) and data enquiries (Contact section).
 
Example:
resourceProvider (Could display in user interface as ‘Resource provider’)

Series:
(Optional) Name of the publication series or aggregate dataset of which the referenced dataset is a part.
Example:
CanMap RouteLogistics


Abstract: (Mandatory) Brief narrative summary of the dataset’s contents.Usage Note:
Ideally, an abstract should include information on general content, thematic features (e.g., geology, climatology; etc.), and features; dataset application: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date; and special data characteristics or limitations.
 
Additional Use Note:
In practice, abstract is typically taken as provided by the data producer. Revisions are made where additional relevant information is known.

Purpose:
(Optional) Summary of the intentions for which the dataset was developed. Purpose includes objectives for creating the dataset and what the dataset is to support
 
Example:
To provide a detailed overview of the surficial geology of southern Ontario and associated attributes available to the land-use planning, consulting, aggregate/industrial mineral industry and development community as well as government geoscientists, resource scientists, conservation authorities, land-use planners and academic researchers. Also, the data set will be of value to the broader scientific community, school teachers and general public who have an interest in Ontario's geological history and use of earth resources.

Status:
(Mandatory) Development phase of the dataset. Usage Note: Select from Code List. Options include: completed, historicalArchive, obsolete, onGoing, planned, required, underDevelopment, proposed
 
Example:
ongoing (Could be displayed in user interface as ‘Ongoing’)

Spatial Representation Type:
(Optional) Object(s) used to represent the geographic information. Usage Note: Select from Code List. Options include: vector, grid, textTable, tin, stereoModel, video
 
Example:
vector

Denominator:
(Optional, Conditional) Expressed as the numerical scale of a comparable hardcopy map or chart that the dataset describes (as either a reference or a digitized version (can include born digital data)). The number below the line in a proper fraction that the numerator is equal to 1.
Example:
30000 (expressed as 1:30000) *(can be used as a range, field is repeatable)


Distance: (Conditional) Ground sample distance. Usage Note: NAP describes data type Distance as: “A measure of length between two points.  A distance is made up of a value.
Additional Usage Note:
Distance is entered if and only if EquivalentScale (5.3.3.1) is not provided.
 
Example:        
30
1

Distance Unit of Measure:
(Optional, Conditional) Ground sample distance. Usage Note: NAP describes data type Distance as: “A measure of length between two points.  A distance is made up of a value AND a unit of measure.
Example:        
cm
m

Language: (Mandatory) Languages of the dataset using standard ISO three letter codes. Usage Note: Language code is given in lower case. Country code is given in uppercase. Language codes: http://www.loc.gov/standards/iso639-2/php/English_list.php Country codes: http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html.
 
Example:        
eng; CAN
fra; CAN 

Dataset Character Set:
(Optional) Character coding standard of the data.
Example:
utf8

Topic Category:
(Mandatory) The main theme(s) of the dataset. Usage Note: Select from Code List. Options include: 19 categories. More than one category may be selected. farming, biota, boundaries, climatologyMeterologyAtmosphere, economy, elevation, environment, geoscientificInformation, health, imageryBaseMapsEarthCover, intelligenceMilitary, inlandWater, location, oceans, planningCadastre, society, structure, transportation, utilitiesCommunication
 
Usage Note:
Topic Category is required when Hierarchy Level (5.2.5) type is set to dataset.
 
Example:
geoscientificInformation (displays in user interface as ‘Geoscientific Information’)

Supplemental Information:
(Optional) Other descriptive information about the dataset.
Example:
The aerial imagery, from which the orthophotography and contour data was derived, was collected during the spring and summer of 2006. Additions have been made in the spring of 2007 with flight lines being finished in Essex County.  


Environment Description: (Optional) Describes the dataset’s processing environment. Usage Note: Include information such as software, computer operating system, filename, and dataset size.
 
Example:
Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 8.3.0.800

Maintenance and Update Frequency:
(Mandatory) Frequency of changes and additions made to the resource after the initial completion. Usage Note: Select from Code List. Options include: continual, daily, weekly, fortnightly, monthly, quarterly, biannually, annually, asNeeded, irregular, notPlanned, unknown, semimonthly
 
Example:
quarterly

Graphic Overview:
The name, description and file type of an illustration of the resource.


File Name: (Mandatory) Name of the graphic file provided to illustrate the resource. Usage Note: The filename shall include path or URL to access the graphic file and the file type extension.
Example:
http://images.scholarsportal.info/gis/thumbnails/DMTI/DMTI_2010_CanMapRL_Canada_TZD.png

File Description:
(Optional) Text description of the graphic file’s content.
Example:
Thumbnail

File Type:
(Optional) Description of the graphic file format.
Example:
Png

Extent:
An element which describes inclusions or exclusions in a resource. It consists of approximation on the horizontal extent of the data represented by a rectangle-like shape.
 
West Bound Longitude:
(Mandatory) Western most coordinate of the dataset extent. Usage Note: Use decimal degrees.
Example:
-82.813464

East Bound Longitude: (Mandatory) Eastern most coordinate of the dataset extent. Usage Note: Use decimal degrees.
Example:
-75.241668

South Bound Longitude:
(Mandatory) Southern most coordinate of the dataset extent. Usage Note: Use decimal degrees.
Example:
42.095330

North Bound Longitude:
(Mandatory) Northern most coordinate of the dataset extent. Usage Note: Use decimal degrees.
Example:
46.489356

Extent Description:
Do not use

Temporal Extent:
Text which describes the temporal extent of the dataset.

Description:
(Optional) Text which describes the spatial and temporal extent of the dataset.
Example:
Coverage date


Begin Position: (Optional) Begin date as expressed in yyyy-mm-dd

End Position:
(Optional) End date as expressed in yyyy-mm-dd


Keywords (Free Text): (Optional) Commonly used words or phrases which describe the resource (subject, place and temporal). Usage Notes: Keywords may be added from more than one of the approved authoritative keyword lists. Note that keywords provided by data providers should not be removed. Additional keywords from the authoritative keyword lists should be added in addition where appropriate. At minimum there should be at least two or three theme keywords, and at least one place keyword, in a record.
 
Additional Usage Notes:
Theme keywords describe the thematic content or subject of a geospatial dataset.  Examples of theme keywords are: photograph, bathymetry, medical centres, population, and surficial geology.  Theme keywords that are applied to a particular dataset may include terms that are hierarchical (e.g., broader and narrower), equivalent or alternative, and perhaps also associative in order to provide for the best possible results in terms of retrieval by an end-user.  
 
At least one of the theme keywords are to be selected from one of two controlled vocabularies. The Keywords Task Group evaluated a number of thesauri as potential sources of thematic keywords for describing geospatial datasets; these are listed in Appendix B. Based on this evaluation, Scholars Portal has adopted the following two thesauri as authoritative sources for thematic keywords:
 
·         Government of Canada Core Subject Thesaurus (LAC),  and
·         LIO-MNR Thesaurus (Ontario Ministry of Natural Resources)
 
Example:        
Education

Keywords (LAC Thesaurus - bilingual):
(Mandatory, Conditional) Commonly used words or phrases, in both english and french, which describe the resource (subject, place and temporal). Usage Notes: Keywords may be added from more than one of the approved authoritative keyword lists.
 
Additional Usage Notes:
Theme keywords describe the thematic content or subject of a geospatial dataset.  Examples of theme keywords are: photograph, bathymetry, medical centres, population, and surficial geology.  Theme keywords that are applied to a particular dataset may include terms that are hierarchical (e.g., broader and narrower), equivalent or alternative, and perhaps also associative in order to provide for the best possible results in terms of retrieval by an end-user.  At least one of the theme keywords are to be selected from one of two controlled vocabularies.
 
Example:        
Education
Éducation *(where possible always include the french equivalent to the keyword you have choosen from the approved list)

Keywords (MNR Thesaurus):
(Mandatory, Conditional) Commonly used words or phrases which describe the resource (subject, place and temporal). Usage Notes: Keywords may be added from more than one of the approved authoritative keyword lists.
 
Additional Usage Notes:
Theme keywords describe the thematic content or subject of a geospatial dataset.  Examples of theme keywords are: photograph, bathymetry, medical centres, population, and surficial geology.  Theme keywords that are applied to a particular dataset may include terms that are hierarchical (e.g., broader and narrower), equivalent or alternative, and perhaps also associative in order to provide for the best possible results in terms of retrieval by an end-user.  At least one of the theme keywords are to be selected from one of two controlled vocabularies.
 
Example:        
Aerial Photography
 
Keywords (Place):
(Mandatory) Place keywords describe the geographical location of a geospatial dataset.  Examples of place keywords are: Canada, northern Ontario, Maritime provinces, Toronto, and Mimico. 
 
At least one of the place keywords are to be selected from the controlled vocabulary. The controlled place keywords should be sufficient for datasets with national or provincial coverage.  For county or municipal level datasets,  uncontrolled free-text keywords may also be added to describe local place names. 
 
The Keywords Task Group evaluated a number of Canadian and foreign authoritative sources for place names; these are listed in Appendix C. Based on this evaluation, Scholars Portal has adopted the following resource as our authoritative sources for place keywords:
 
·         Global Change Master Directory’s Location Keywords
 
Example:
Continent > North America > Canada > Ontario
 

Use Limitations:
(Optional, Conditional) Statement on the fitness for use or limitations on the use of the resource or metadata. Use Note: The attribute useLimitation is mandatory unless Legal Constraints (5.4.2) or Security Constraints (5.4.3) is provided.
 
Example:
Not for Legal Purposes.

Access Constraints:
(Optional) Limitations on access to the resource or metadata to protect privacy, intellectual property, or any special limitations. Usage Note: Select from Code List. Options include: copyright, patent, patentPending, trademark, license, intellectualPropertyRights, restricted, otherRestrictions, licenseUnrestricted, licenseEndUser, licenseDistributor, privacy, statutory, confidential, sensitivity
 
Example:
license

User Constraints:
(Optional) Restrictions or limitations or warnings to protect privacy, intellectual property, or other special restrictions on the resource or the metadata. Usage Note:
Select from Code List. Options include: copyright, patent, patentPending, trademark, license, intellectualPropertyRights, restricted, otherRestrictions, licenseUnrestricted, licenseEndUser, licenseDistributor, privacy, statutory, confidential, sensitivity
 
Example:
license

Other Constraints:
(Optional, Conditional) Other restrictions or legal prerequisites for accessing the resource or metadata. Usage Note: otherConstraints shall be provided if accessConstraints (5.4.2.2) or useConstraints (5.4.2.3) is set to "otherRestrictions".
 
Additional uasage notes: We at SP use this field to add free text statements that coincide with licensed products such as DMTI, OGDE, and other data products with specific wording for use.
 
Example:
The data is restricted to use by current students, faculty and staff at Ontario Universities who are members of the Ontario Geospatial Data Exchange (OGDE). See: http://mnr.gov.on.ca/en/Business/LIO/2ColumnSubPage/STEL02_167959.html

Linkage: (Mandatory) Internet location (address) for on-line access which uses a Uniform Resource Locator address or similar addressing scheme such as www.isotc211.org or ftp.isotc211.org. Usage notes: This field provides the link to the data resource found on either Scholars Portal’s servers, or another location.
 
Additional usage notes: All links are to be provided either as relative paths (i.e. in the case of map services hosted on SP servers) or as full paths to either ArcGIS services, or datasets in .zip file format (direct download, no visualization on the map). For the Direct Download option, all URLs must be structured accordingly,
http:__folder/filename.zip
 
For more information about naming files and folders for assigning authentication (i.e. collection or access information) please refer to guidelines found on the wiki space or e-mail gis@scholarsportal.info 
 
Example:
/ArcGIS/rest/services/OGDE/OGDE_WOODAREA/MapServer

Protocol: (Mandatory) The connection protocol to be used such as http, ftp, etc. The protocol should be taken from an official controlled list such as the Official Internet Protocol Standards published on the Web at http://www.rfc-editor.org/rfcxx00.html
Usage Notes: Always use the “http” protocol for map services published to the web. For direct download files (usually .zip file format) and tables use the “file” protocol.
 
Example:
http

Description: (Mandatory) Description of the utility that provides the resource sought.
 
Usage Note: There are certain standardized phrases which must be included in the metadata editor for all links to services, in order for the portal application to interpret them correctly. These are the standard phrases:
 
Eng:     Tiled map service (vector)
            Dynamic map service (vector)
Dynamic search map service (vector) "63 map sheet" - used for index maps linked to historical topo maps. this is acheived with the search text between the quotes and the cell bounds within the map layer.
Web tiled map service (raster) - used for historical topo maps  
            Image service (raster) {file format}
            External Dynamic map service (vector)
            Table
Fra:      Service de carte mis en cache (données vectorielles)
            Service de carte dynamique (données vectorielles)
            Service d’imagerie {file format]
            Table
           
It is still possible to put any other descriptive text needed into the field (but avoid using the word “tiled”, “dynamic”, “image” or “raster” unless that is the type of data being described).
           
Example:
Tiled map service (vector)

Transfer Options: The means and media by which the data/dataset is obtained from the distributor.

Transfer Size: TBD

Distribution Information: Information on party responsible for dataset distribution.

Organization Name: (Mandatory) Name of the responsible organization.
Example: DMTI Spatial Inc.

City: (Optional) City of the address.
Example:
Toronto

Administrative Area: (Optional) State or province of the address. Usage Note: Lists of states and provinces are available at: http://www.usps.com/ncsc/lookups/usps_abbreviatio
ns.htm (US) and http://www.canadapost.ca/common/tools/pg/manual/PGaddress-e.asp (Canada)
Example:
Ontario

Country: (Optional) Country of the address. Usage Note: The country name shall be taken from the ISO 3166 code list available at http://www.iso.org/iso/en/prodsservices/ISO 3166ma/02iso-3166-code-lists/index.html. The full country name must be entered, not the code.
Example:
Canada

Role: (Mandatory) Function performed by the responsible party. Usage Note: Select from Code List. Options include: resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author, collaborator, editor, mediator, rightsHolder
 
Additional Usage Note:
The following is an outline of how different role codes should generally be used in a SP metadata record.
·         distributor – the organization which distributed the dataset to Scholars Portal.
·         principalInvestigator – the primary authoring organization of the data. In some cases this is the same organization as the publisher – this is generally the case for Statistics Canada data.
·         publisher – the producer of the dataset (under Data Identification Information). A responsible party with this role code MUST be provided in all records. If the data producer also has another role, add the responsible party twice. For example, Statistics Canada is both the principalInvestigator and a publisher.
·         originator – this role code is typically used only in the Metadata Maintenance Information section, to describe the organization from which the source metadata originated.
·         pointOfContact – each record will include at least one organization as a general point of contact. Scholars Portal should be the point of contact for both metadata enquiries (Metadata Maintenance Information section) and data enquiries (Contact section).
 
Example:
distributor (displays in user interface as ‘Distributor’)
 
Scope Level: (Mandatory, Conditional) The data or application level for which data quality is described. Usage Note: Select from Code List. Options include: attribute, attributeType, collectionHardware, collectionSession, dataset, series, nonGeographicDataset, dimensionGroup, feature, featureType, propertyType, fieldSession, software, service, model, tile
 
Additional Usage Note:
NAP states that when level is not “dataset” or “series” then levelDescription must be entered. Note that this is not currently relevant at SP, currently all records have level of “dataset” or “series”.
 
Example:
dataset

Data Lineage Statement: (Optional) General explanation of the data producer’s knowledge of the dataset lineage.
 
Example:
“The geographic area boundaries, names, codes, and the relationships among the various geographic levels are found on Statistics Canada’s Spatial Data Infrastructure. These data for administrative areas are updated using information from provincial and territorial sources. These data for statistical areas are updated using the results of the previous census and input from users.”

Data Source Description: (Optional) Statement that describes the source data. Usage Note:
Any data source information provided by the producer / distributor.
 
Example:
The Spatial Data Infrastructure (SDI) is the source for all 2006 Digital Boundary File products.

Process Step Description: (Optional) Description of the processes performed on the data.=
Example:
DEM used to produce 1 metre contours.
 
Maintenance Note: (Optional) Used to describe any additional information about the maintenance or lineage of this metadata record. Usage Note: At SP we try to describe any transformations (i.e. FGDC to ISO 19115), or sources consulted (i.e. MNR, LIO) including any referencable IDs or catalogue numbers associated with the data product being described in this metadata record.
Example:
bf4edf9f-054e-4a92-89d0-f4c75e3bffa9 (taken from LIO metadata)

Organization Name: (Mandatory) Name of the responsible organization for the metadata maintenance.
Example: Scholars Portal

City: (Optional) City of the address.
Example:
Toronto

Administrative Area: (Optional) State or province of the address. Usage Note: Lists of states and provinces are available at: http://www.usps.com/ncsc/lookups/usps_abbreviatio
ns.htm (US) and http://www.canadapost.ca/common/tools/pg/manual/PGaddress-e.asp (Canada)
Example:
Ontario

Country: (Optional) Country of the address. Usage Note: The country name shall be taken from the ISO 3166 code list available at http://www.iso.org/iso/en/prodsservices/ISO 3166ma/02iso-3166-code-lists/index.html. The full country name must be entered, not the code.
Example:
Canada

Role: (Mandatory) Function performed by the responsible party. Usage Note: Select from Code List. Options include: resourceProvider, custodian, owner, user, distributor, originator, pointOfContact, principalInvestigator, processor, publisher, author, collaborator, editor, mediator, rightsHolder
 
Additional Usage Note:
The following is an outline of how different role codes should generally be used in a SP metadata record.
·         distributor – the organization which distributed the dataset to Scholars Portal.
·         principalInvestigator – the primary authoring organization of the data. In some cases this is the same organization as the publisher – this is generally the case for Statistics Canada data.
·         publisher – the producer of the dataset (under Data Identification Information). A responsible party with this role code MUST be provided in all records. If the data producer also has another role, add the responsible party twice. For example, Statistics Canada is both the principalInvestigator and a publisher.
·         originator – this role code is typically used only in the Metadata Maintenance Information section, to describe the organization from which the source metadata originated.
·         pointOfContact – each record will include at least one organization as a general point of contact. Scholars Portal should be the point of contact for both metadata enquiries (Metadata Maintenance Information section) and data enquiries (Contact section).
 
Example:
resourceProvider (Could display in user interface as ‘Resource provider’)
 
Data Holdings: This field is used to facilitate the delivery of the full download pre-packaged zip files available from the Portal. This field is useful for Scholars Portal and for datasets that exist fully in the Scholars Portal infrastructure for delivering data.
Example:
/zips/OGDE/OGDE_WOODAREA.zip

User Guide Links: These are stable URLs that link to resources, primarily PDFs but also other file formats that are hosted on Scholars Portal servers. If another server is being used to host the files the full URL is required along with an e-mail notice sent to gis@scholarsportal.info


Guide Label: The label or name/description of the file
Example:
Wooded Area – Data Description Report


Guide Link: The full URL to the resource with the convention: “http:__” used.
Example:
http:__maps1.scholarsportal.info/OGDE/filename.pdf


External Links: These are resource links to external sites such as the Ministry of Natural Resources site, other government departments etc. that specifically provide additional information about this dataset/product but the information ARE NOT available in a pdf or other static file format for download.


External Label: The label or name/description of the resource
Example:
Health Regions map


External Link: The full URL to the resource with the convention: “http:__” used.
Example:

http:__mnr.on.gov/HR/filename.html  




 












  • No labels