NJGIN Metadata Tips

Transcription

1 NJGIN Metadata Tips Last updated 27 March 2008 P. 1 of 18 NJGIN Metadata Tips Standard-compliant metadata records are the lifeblood of the New Jersey Geographic Information Network Explorer, the online geospatial catalog for New Jersey. This document contains summary tips on writing geospatial metadata that will function correctly as part of NJGIN Explorer, and that will comply (minimally) with the Federal Geographic Data Committee-Content Standard for Geospatial Metadata (FGDC-CSDGM). The Tips focus on avoiding common mistakes and on highlighting special requirements for NJGIN Explorer. If you need an introduction to geospatial metadata or to the FGDC-CSDGM, please look at other parts of the NJGIN metadata help page, first. If further help is needed, please do not hesitate to contact NJGIN staff at njgin@oit.state.nj.us. We will be happy to answer questions about metadata authoring and about NJGIN Explorer. Many contributors to NJGIN Explorer use ESRI software products, so the Tips are written with the ArcCatalog FGDC metadata editor in mind. However there is no requirement to use this editor; as long as the required structured XML elements are completed, any geospatial metadata editor, an xml editor, or even a simple text editor, can be used. Word processors such as MS Word are not recommended. Change history of this document: March 2008: corrected formation errors and blank page, added element instructions for Map Service metadata Entity Type section, minor edits to Map Service metadata checklist. January 2008: software and URL updates, simplification and rewording of some information, including checklists. December 6, 2005: removed info on ArcCatalog 8.3 attribute handling. Added explanations to some checklist items. September 8, 2005: added URL. March 29, 2005: revised Part II Step A; added notation to highlight, on checklists, elements essential to NJGIN Explorer intake. Please read pages 1-4 carefully. The balance of the document consists of pick lists and other reference information. Part I Avoiding format and character errors (FGDC-CSDGM and XML) A. Date format for all dates: YYYYMMDD. The year digits are required. For most dates, month and day are optional. If used, each must include leading zeros where appropriate (e.g. January 5, 2004 would be ). B. XML (Extensible Markup Language) reserved characters must not be used in the bodies of entries (i.e. outside of the tags). Characters that are not recognized by XML v. 1.0 must also be avoided, as must some characters that have special uses by ESRI products that handle metadata. Thus, do NOT use the following: < > & " ' -- (double dash) { } (curly brackets) and non-ascii characters such as bullets, symbol characters, curly quotes. If copying and pasting from a Word document, be sure to review your text after pasting to make sure it meets these requirements. If < > & " ' are needed, use escape characters as follows: &lt &gt &amp &quot &apos.

2 NJGIN Metadata Tips Last updated 27 March 2008 P. 2 of 18 If you are using ArcCatalog 9.2, the metadata editor itself will enforce most of these restrictions. Part II Steps to geospatial cataloging on NJGIN Explorer: A. Construct a metadata record in FGDC-CSDGM format. Use one of the element checklists below in Part IV to make sure you are capturing at least the essential elements for cataloging. Elements are pieces of structured information. Use pick lists for selected elements for NJGIN Explorer that are different from the FGDC-CSDGM. These pick lists are included below, in Part V, for Theme Keyword Thesaurus, Theme Keyword, Resource Description, and (optional) Security Classification elements. They also are noted in the element checklists. Optional: Fill out additional FGDC-CSDGM elements that are applicable to your data set (or other geospatial item). Documenting the development process of a data set, the quality checks done on it, and/or detailed information about the attributes included in the table, will assist you greatly in the long-term management of the data set, as well as providing more information in the catalog. If the metadata will be submitted as part of a deliverable to a State of New Jersey agency, additional elements will be required in order to create a record that is fullycompliant with the FGDC-CSDGM. B. Check the metadata record for grammar, spelling, and general understandability, preferably by having a colleague proofread it. C. Export/save your metadata file from any geospatial metadata editing software as FGDC-compliant xml. D. Optional: Do other checks for XML and FGDC-CSDGM compliance, such as running MP (Metadata Parser); this can be done most easily by using the online Metadata Validation Service at E. Optional: Construct a standalone Thumbnail. Construct a small.jpg file of dimension 200 pixels wide by 133 pixels high, that illustrates your data set, map, or map service. Put it on your local computer drive (usually C). F. Register at NJGIN Portal as a publisher. Wait for approval (you ll receive an ). G. Find the NJGIN Publishing page and submit your xml metadata and (optional) thumbnail.

3 NJGIN Metadata Tips Last updated 27 March 2008 P. 3 of 18 H. Wait for metadata approval or request for edits, from NJGIN metadata administrator. If changes are needed, edit your local copy of the metadata record, then log into NJGIN Explorer, go to My Metadata page and Update the appropriate record. I. After record is approved (you ll receive an ), search for it on NJGIN Explorer and check spatial extent (button at bottom of details page), in order to make sure it is functioning as it should. J. As an added bonus, your record will be harvested to Geospatial One Stop, usually within two weeks. No separate action on your part is required.

4 NJGIN Metadata Tips Last updated 27 March 2008 P. 4 of 18 Part III Additional helpful notes A. ArcCatalog 9.2 Metadata Editor tips: -Set up your ArcCatalog preferences to NOT automatically create or update metadata (Tools>Options>Metadata). Don t forget to reset if you reinstall the software. -For data sets, be sure to assign the coordinate system to your data set before starting to write metadata. (For shapefiles,.prj file; for ArcSDE feature classes, spatial reference: for both, set via ArcCatalog in data set properties (rt-cl on data set in Catalog tree window>fields>shape geometry>spatial reference). -Set ArcCatalog metadata stylesheet to FGDC. Check to see if the data set already has metadata because it was captured by ArcCatalog/ArcToolbox during geoprocessing; if so, be sure to save a copy of it by exporting it as plain xml. It can provide information for Process Step entries. It also can be re-incorporated into the metadata record. Call the NJGIN metadata adminstrator for help if needed. -Import your customized.xml template, if you have one, with box checked for Enable automatic update of metadata. -After import, edit the Metadata Properties for the data set and check box for do not automatically update metadata. -If the data set or map service is in NJ State Plane coordinates NAD83, at the end of every edit session, before saving, go to Spatial Reference>Horizontal Coordinate System>Encoding Information, Encoding Type: State Plane Coordinate System and manually add "1983" to the end of the entry so it reads State Plane Coordinate System At the end of each metadata edit session, before saving, look at Identification>Citation>Detail>Online linkage. Make sure the entry is what you want it to be. -It is possible to turn off the ISO synchronizer, so that your metadata records don t have extraneous elements that you don t see in the FGDC editor. This is done by adding the Set Working Synchronizers tool to the metadata toolbar, then using the tool. (Menu Tools>Customize>Commands tab, Categories>Metadata, drag command to toolbar). Don t turn off the Geography Network synchronizer. B. Additional resources for metadata authors: -Content Standard for Digital Geospatial Metadata Workbook Version 2.0 (aka the Green Book ) -Hugh Phillips page on metadata tools -Add on for viewing metadata within ArcMap -Enumerated Domain Helper from the USGS (requires workaround involving.txt form of metadata, but possibly worthwhile if you have a LOT of enumerated domain info to deal with)

5 NJGIN Metadata Tips Last updated 27 March 2008 P. 5 of 18 Part IV Cataloging-element checklists Geospatial metadata records intended for cataloging (publishing) on NJGIN Explorer, the statewide geospatial portal for New Jersey, need to include the elements (structured information) that enable searches on NJGIN Explorer and harvesting to Geospatial One Stop (the Federal Government unified catalog). The checklists below list and explain these essential elements. Double-checking the listed elements will ensure that the metadata record will load to NJGIN Explorer properly, will be discoverable once loaded (search functions will work properly on the record), and the record will be harvestable by Geospatial One Stop. Please note that Minimal metadata for cataloging are minimally useful for internal and external documentation; efforts to write full FGDC CSDGM compliant metadata will return your investment many times over in the future. So don t stop with the elements on these checklists if you can include more information. The crucial cataloging elements are listed below, by their element names and by their xml tags (= FGDC CSDGM short name). There are two separate lists, one for data sets (and most other items), and a separate one for map services. *Checklist for data sets (also mostly applicable to maps, documents, and applications (computer programs). Symbol marks five elements to check first if an attempt fails to submit metadata to NJGIN Explorer. Symbol! marks other needed elements that commonly cause errors in how the record functions. Italicized material gives navigation hints for ArcCatalog 9.2 FGDC editor: Identification section (General tab) A. Abstract <abstract> : Write at least a paragraph, describing the data set or other item; include content, features, form (GIS, CAD, image, Access table, etc), geographic coverage in words, time period of content, special characteristics or limitations. B. Purpose <purpose> : Describe the specific use(s) that was anticipated when the data set was created. Was it intended for cartographic display (at what scale)? Planning? Site engineering? Legal descriptions? Was it created for a specialized use, or was wide distribution the intention from the start? C. Access Constraints <accconst> : Are there any legal restrictions or prerequisites on viewing or on obtaining the data set? None is a legal entry, if true. D. Use Constraints <useconst> : Are there any legal restrictions or prerequisites on using the data set once access has been granted? None is a legal entry, but use only if known to be true. Check with the legal department of your organization. If you do not have anything written, enter call metadata contact.

6 NJGIN Metadata Tips Last updated 27 March 2008 P. 6 of 18 (Citation tab, Details button, General subtab) E. Title <title> : Use a meaningful title, not just the filename of the data set. When the title is returned from a search, the potential user should get a reasonable idea about the data set from the title. Make it accurate and descriptive, including enough information to distinguish this data set from similar data sets. Consider including (in decreasing order of importance) where, what, when, who, why, resolution, filename, source. F. Originator <origin> : Name of the party responsible for the data set (not necessarily the metadata). Fully qualify any organization name, and include any commonly-used abbreviations, e.g. State of New Jersey Department of Environmental Protection (NJDEP), Office of Information Resources Management (OIRM), Bureau of Geographic Information Systems (BGIS) John Tyrawski. G.!Publication Date <pubdate> : Format YYYYMMDD. The year digits are required, month and day are optional. Refers to the date when the data set was first made available. H.!Online Linkage <onlink> : In the Identification section, the first Online Linkage provides information for important functions in NJGIN Explorer and Geospatial One Stop. Its contents should be a fully-qualified URL to the data set download, if available. (Any additional URL for a general information page can be put in a second Online Linkage element, and/or in Distribution Information, Network Resource Address. If no direct download address is available, the general information URL can go here in the first Online Linkage element.) For Application metadata, enter the fully-qualified URL of the application front page, if it is on-line. For map service metadata, a specific format is required for Online Linkage. See the separate checklist for map service metadata. If no URL is appropriate for the data set, enter None. The element can be omitted, but if using the ArcCatalog FGDC editor, you will have to remove the element (by using the x button) each time the metadata record is edited. Otherwise, the editor fills it with the internal file path. The internal file path probably is something you don t want to publish. (Series/Publication Information subtab) I.!Publication Place <pubplace> : City, State. J. Publisher <publish> : Name of the party making the data set available. Please fullyqualify the name in the same manner as for Originator.

7 NJGIN Metadata Tips Last updated 27 March 2008 P. 7 of 18 (Time Period tab) K. Time Period of Content <timeperd> and Currentness Reference <current> : Make sure these relate correctly to each other. If you know the date (to at least the year) or dates when the data set and the real world matched, use that date, and ground condition. If you don t know the date for ground condition, use publication date. The date reference for either can be a Single Date <sngdate>, a Range of Dates <rngdates>, or Multiple Dates <mdattim>. For ongoing work, a range end date can be Present. (Status tab) L. Progress <progress> : complete in work or planned. The latter is used for publicizing future data acquisition projects, especially if you are looking for funding partners. M. Maintenance and Update Frequency <update> : see Green Book or editor list. Unknown and None planned are both legal entries. Use as needed only if there is a specific plan in place for updating whenever the information on the ground changes. (Spatial Domain tab, Bounding Coordinates and G-Polygon subtab) N. Bounding Coordinates <bounding> (parent of 4 children): Expressed in decimal degrees, with negatives for S of Equator and W of the Prime Meridian (Greenwich, England). In New Jersey, all longitudes (East and West bounding coordinates) are negative. Usually read by the software from the data set. If not, must be determined by you and entered. (Keywords tab)!keyword Thesaurus and Keyword entries should be thought of as paragraphs, with the Keyword Thesaurus as the header and each Keyword (or phrase) as a separate sentence in the paragraph. Don t string all the keywords together in one entry. Make sure each of your keywords is entered in the list for the correct Thesaurus. O.!Theme Keyword Thesaurus <themekt>: At least one entry, ISO Topic Category. This should be the first entry. P. Theme Keyword <themekey> : From ISO pick list (See Part V. A., below). Entry is used for any Content Theme search done on NJGIN Explorer. Q. If NJSDI Framework data, add Theme Keyword Thesaurus NJGIN and a framework keyword (see Part V.B., below). R. Add another Theme Keyword Thesaurus (can be None ) and more Theme Keywords. S. Place Keyword Thesaurus <placekt> : At least one entry, can be None.

8 NJGIN Metadata Tips Last updated 27 March 2008 P. 8 of 18 T.!Place Keyword <placekey> : First one should express the geographic coverage area of the data set in words (e.g. New Jersey or Margate City, Atlantic County, New Jersey ). Spatial Reference section (Horizontal Coordinate System tab, Encoding Information subtab) U.!Grid Coordinate System Name <gridsysn> this is labeled Horizontal Coordinate System Encoding Type by the ArcCatalog FGDC metadata editor: If the data set is in NAD83 State Plane Coordinates, check to make sure the entry is as follows: State Plane Coordinate System ArcCatalog FGDC editor bug chops off the 1983 when the editor is opened. The other required elements for this section need to be present for data sets. They are usually auto-read from the data set spatial reference by ArcCatalog, and need no further attention. Distribution section V. Resource Description <resdesc> (in Distribution Information): One from the list below, exactly as shown (omit parenthetical notes): Downloadable Data Offline Data Map Files Static Map Images Other Documents Applications Geographic Services Clearinghouses Geographic Activities (generally via http or ftp site) (interactive maps:.pmf,.mxd, etc.) (such as.jpg,.gif, or.pdf maps) (geospatial functionality available as a web service, callable by other applications) (such as NJGIN Explorer) (planned data acquisition projects) The entry will be used in any Content Type search done by NJGIN Explorer. Please note that this requirement is a flat-out departure from the FGDC-CSDGM definition for this element. Metadata Reference section W. Metadata Date <metd> : YYYYMMDD format, full date when you finished writing the metadata is required. Should be changed whenever significant updates are performed. (General tab, Details button) X. Metadata Contact Organization Primary <cntorgp> or Metadata Contact Person Primary <cntperp> : If the metadata contact left for a comfortable retirement in Tahiti, should a person with questions about the metadata track him/her down, or ask someone else in the organization? Depending on this choice of element, one of the next two elements is required; both are recommended.

9 NJGIN Metadata Tips Last updated 27 March 2008 P. 9 of 18 Y. Metadata Contact Person <cntper>: this is the person responsible for maintaining the metadata record and for answering questions about it. Z. Metadata Contact Organization <cntorg>: If this organization is the same as the Originator or the Publisher, any abbreviation specified in Originator or Publisher can be used here. Otherwise, specify the organizational unit as completely as possible. AA. Metadata Contact Voice Telephone <cntvoice> : Include Area Code. If at all possible, use a phone number that will persist. Provide any additional help needed for callers in Metadata Contact Instructions. (Address subtab) BB. Metadata Contact Address Type <addrtype> Metadata Contact City <city> Metadata Contact State or Province <state> Metadata Contact Postal Code <postal> All of the above are required. *Checklist for map services. Symbol marks five elements that must be present and correct for successful NJGIN Explorer initial intake. Symbol! marks other needed elements that commonly cause fatal errors. Italicized material gives navigation hints for ArcCatalog 9.2 FGDC editor: Identification section (General tab) A. Abstract <abstract> : Write at least a paragraph, describing the map service; include content, features, type of service, geographic coverage, time period of content, special characteristics or limitations. B. Purpose <purpose> : Describe the specific use(s) that was anticipated when the map service was created. C. Access Constraints <accconst> : Are there any legal restrictions or prerequisites on viewing the map service? None is a legal entry, if true. D. Use Constraints <useconst> : Are there any legal restrictions or prerequisites on using the map service once access has been granted? None is a legal entry, but use only if known to be true. Check with the legal department of your organization. If you do not have anything written, enter call metadata contact. (Citation tab, Details button, General subtab) E. Title <title> : Use a meaningful title, not just the servicename. When the title is returned from a search, the potential user should get a reasonable idea about the map service from the title. Make it accurate and descriptive, including enough information to distinguish this

10 NJGIN Metadata Tips Last updated 27 March 2008 P. 10 of 18 map service from others. Consider including (in decreasing order of importance) where, what, service type, when, who, why, resolution, filename, source. F. Originator <origin> : Name of the party responsible for the map service (not necessarily the metadata). Fully qualify any organization name, and include any commonly-used abbreviations, e.g. State of New Jersey Department of Environmental Protection (NJDEP), Office of Information Resources Management (OIRM), Bureau of Geographic Information Systems (BGIS) John Tyrawski. G.!Publication Date <pubdate> : Format YYYYMMDD. The year digits are required, month and day are optional. Refers to the date when the map service was first made available. H.!Online Linkage <onlink> : In the Identification section, the first Online Linkage provides information for important functions in NJGIN Explorer and Geospatial One Stop. Its contents should be map service connection information that will be parsed by the NJGIN Explorer intake tool (italicized information is what you fill in with the appropriate entries for your service; they should be in plain text): Server= Service=Parcels_Feature; ServiceType=feature For ServiceType, the legal entry is one of the following: image feature wms wfs metadata Requirements are still evolving as OGC standards for web map services come out. If you have difficulty, contact NJGIN staff for help. (Series/Publication Information subtab) I.!Publication Place <pubplace> : City, State. J. Publisher <publish> : Name of the party making the map service available. Please fullyqualify the name in the same manner as for Originator. (Time period tab) K. Time Period of Content <timeperd> and Currentness Reference <current> : Make sure these relate correctly to each other. If you know the date (to at least the year) or dates when the data in your map service and the real world matched, use that date, and ground condition. If you don t know the date(s) for ground condition, use publication date. The date reference for either can be a Single Date <sngdate>, a Range of Dates <rngdates>, or Multiple Dates <mdattim>. (Status tab) L. Progress <progress> : complete or in work. M. Maintenance and Update Frequency <update> : see Green Book or editor list. Unknown and None planned are both legal entries. Use as needed only if there is a specific plan in place for updating whenever the information on the ground changes.

11 NJGIN Metadata Tips Last updated 27 March 2008 P. 11 of 18 (Spatial Domain tab, Bounding Coordinates and G-Polygon subtab) N. Bounding Coordinates <bounding> (parent of 4 children): Expressed in decimal degrees, with negatives for S of Equator and W of the Prime Meridian (Greenwich, England). In New Jersey, all longitudes (East and West bounding coordinates) are negative. Can be read by ArcCatalog from an ArcIMS map service, IF you have configured your ArcIMS server to allow you to author metadata for the service and save it to the ArcIMS server. If not, must be determined by you and entered. (Keywords tab)!keyword Thesaurus and Keyword entries should be thought of as paragraphs, with the Keyword Thesaurus as the header and each Keyword (or phrase) as a separate sentence in the paragraph. Don t string all the keywords together in one entry. Make sure each of your keywords is entered in the list for the correct Thesaurus. O.!Theme Keyword Thesaurus <themekt>: At least one entry, ISO Topic Category. This should be the first entry. P. Theme Keyword <themekey> : From ISO pick list (See Part V.A., below). Entry is used for any Content Theme search done on NJGIN Explorer. Q. If NJSDI Framework data, add Theme Keyword Thesaurus NJGIN and a framework keyword (See Part V. B., below). R. Add another Theme Keyword Thesaurus (can be None ) and more Theme Keywords. S. Place Keyword Thesaurus <placekt> : At least one entry, can be None. T.!Place Keyword <placekey> : First one should express the geographic coverage area of the map service, in words (e.g. New Jersey or Margate City, Atlantic County, New Jersey ). Spatial Reference section (Horizontal Coordinate System tab, Encoding Information subtab) U.!Grid Coordinate System Name <gridsysn> this is labeled Horizontal Coordinate System Encoding Type by the ArcCatalog FGDC metadata editor (in Spatial Reference): If the map service is in NAD83 State Plane Coordinates, check to make sure the entry is as follows: State Plane Coordinate System ArcCatalog FGDC editor bug chops off the 1983 when the editor is opened. All required elements for Spatial Reference are required for map services. In the case of ArcIMS services, your ArcIMS server may be configured so as to allow metadata authoring for the map service; if so, when you open up the ArcCatalog metadata editor, ArcCatalog can read the Spatial Reference information directly from a properlyconfigured map service.

12 NJGIN Metadata Tips Last updated 27 March 2008 P. 12 of 18 If the ArcIMS server is configured for metadata authoring, but the information is not read, the map service is missing some important tags in the map configuration (AXL) file; the latter should be edited, and the map service restarted. Help documents are available both for metadata authoring configuration and for AXL file coordinate system tags. Contact NJGIN staff for a copy of either one. If you have to write metadata for a map service and the server cannot be configured to allow metadata authoring, the easiest way to acquire the Spatial Reference elements is to copy them from data set metadata for a data set in the same coordinate system as the map service. Distribution section V. Resource Description <resdesc> (in Distribution Information): Enter Live Data and Maps and NOTHING ELSE. The entry will be used in any Content Type search done by NJGIN Explorer. Please note that this requirement is a flat-out departure from the FGDC- CSDGM definition for this element. Metadata Reference section W. Metadata Date <metd> : YYYYMMDD format, full date when you finished writing the metadata is required. Should be changed whenever significant updates are performed. (General tab, Details button) X. Metadata Contact Organization Primary <cntorgp> or Metadata Contact Person Primary <cntperp> : If the metadata contact left for a comfortable retirement in Tahiti, should a person with questions about the metadata track down him/her, or ask someone else in the organization? Depending on this choice of element, one of the next two elements is required; both are recommended. Y. Metadata Contact Person <cntper>: this is the person responsible for maintaining the metadata record and for answering questions about it. Z. Metadata Contact Organization <cntorg>: If this organization is the same as the Originator or the Publisher, any abbreviation specified in Originator or Publisher can be used here. Otherwise, specify the organizational unit as completely as possible. AA. Metadata Contact Voice Telephone <cntvoice> : Include Area Code. If at all possible, use a phone number that will persist. Provide any additional help needed for callers in Metadata Contact Instructions.

13 NJGIN Metadata Tips Last updated 27 March 2008 P. 13 of 18 (Address subtab) BB. Metadata Contact Address Type <addrtype> Metadata Contact City <city> Metadata Contact State or Province <state> Metadata Contact Postal Code <postal> All of the above are required. Strongly recommended, but not actually required by NJGIN Explorer: CC. Document the data sets included in the map service as follows: In Entity and Attribute section, use a separate Entity Type entry to describe briefly each included data set. 1. Entity Type Label <enttypl>: Enter layer name. 2. Entity Type Definition <enttypd>: Enter a full descriptive Title, from the data set metadata if it exists. 3. Entity Type Definition Source <enttypds>: Enter the data set Originator. If the included data sets are fully documented elsewhere, detailed attribute information can be omitted.

14 NJGIN Metadata Tips Last updated 27 March 2008 P. 14 of 18 Part V Non-FGDC Pick lists A. ISO Topic Category codes 1 : For all metadata records, include one of the following ISO Topic Category codes, which expresses the Primary Theme of the data set, map, service, or application. Enter the thesaurus entry and keyword entry exactly as shown (case sensitive). Theme Keyword Thesaurus: ISO Topic Category Theme Keywords: biota for naturally-occurring flora and fauna, such as wildlife, biological sciences, ecology, wilderness, sea life, wetlands, habitats boundaries for administrative and political boundaries, i.e. legal land descriptions climatologymeteorologyatmosphere for atmospheric processes and phenomena, such as cloud cover, weather, atmospheric conditions, climate change, precipitation economy for economic activities or employment, such as labor, revenue, commerce, industry, tourism, ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of minerals, oil, gas elevation for height above or below sea level, such as altitude, bathymetry, digital elevation models, slope, and products derived from the preceding environment for environmental resources, protection, and conservation, such as pollution, waste storage and treatment, environmental impact assessment, environmental risk, and nature reserves farming for agriculture and farming, including the rearing of animals or cultivation of plants. For example, irrigation, aquaculture, herding, pests and diseases affecting crops and livestock geoscientificinformation for geological, geophysical, and other earth science information, such as minerals, rock structure, rock composition, rock origin, earthquakes, volcanic activity, landslides, gravity, soils, permafrost, hydrogeology, erosion health for human health and disease, health services, human ecology, and safety, such as human disease, human illness, factors affecting health, hygiene, mental and physical health, substance abuse imagerybasemapsearthcover classified and unclassified images. for base maps, such as land cover, topographic maps, 1 Derived from ISO Draft International Standard: Geographic information -- Metadata (ISO/DIS 19115), 2001, Section B.5.27 MD_TopicCategoryCode<<CodeList>> (pp ) and Creating and Using Metadata Services, 2002, ESRI, Chapter 4 Publishing metadata in ArcCatalog.

15 NJGIN Metadata Tips Last updated 27 March 2008 P. 15 of 18 intelligencemilitary for military bases, structures, and activities, such as barracks, training grounds, military transportation, military information collection inlandwaters for inland water features and drainage systems, such as rivers, glaciers, salt lakes, water use plans, dams, currents, floods, water quality, hydrographic charts location for positional information and services, such as addresses, geodetic networks, postal zones and services, control points, place names oceans for features and characteristics of salt water bodies excluding inland waters, such as tides, tidal waves, coastal information, reefs planningcadastre for land use, such as zoning maps, cadastral surveys, land ownership society for characteristics of societies and cultures, such as natural settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, crime and justice, recreational areas and activities, social impact assessments, census information structure for man-made construction, such as buildings, museums, churches, factories, housing, monuments, and towers transportation for transportation networks, the means and aids for conveying people and goods, such as roads, airports, airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways utilitiescommunication for energy, water, and waste systems, and communications infrastructure and services, such as hydroelectricity, geothermal, solar, and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, and communication networks. B. NJ Framework data layers: Use one of these Framework keywords if the data set, map, service, or application deals mainly with the subject of the keyword. Theme Keyword Thesaurus: NJGIN Theme Keywords: njfw_geocontrol Geodetic control provides a highly accurate common reference system for establishing coordinates for all geographic data. njfw_orthophoto Geo-referenced images of the Earth's surface, collected by a sensor. Digital orthoimages have the geometric characteristics of a map and image qualities of a photograph. njfw_boundaries Describes, by a consistent set of rules and semantic definitions, the boundaries of federal, state, local, and tribal governments as reported/certified to the U.S. Census Bureau by responsible officials of each government for purposes of reporting the nation's official statistics.

16 NJGIN Metadata Tips Last updated 27 March 2008 P. 16 of 18 njfw_cadastral Describes the geographic extent of past, current, and future right, title, and interest in real property and the framework to support the description of that geographic extent. njfw_hydro Surface water features such as lakes, ponds, streams, rivers, canals, oceans, and coastlines. njfw_elevation Geo-referenced digital representations of terrestrial and bathymetric surfaces, natural or manmade, which describe vertical position above or below a datum surface. njfw_transport Geographic locations, interconnectedness, and characteristics of the transportation system. The transportation system includes both physical and non-physical components representing all modes of travel that allow the movement of goods and people between locations. njfw_critical Locations of the following: Emergency Operations Centers Police Stations Fire Stations Emergency Medical Services Stations Coverage Areas for the above Hospitals Schools Colleges and Universities Day Care Facilities Government Buildings Power Generating Plants Power Substations Armories Military Sites Communication Towers Telecommunication Sites Utility Transmission Lines Sports Arenas / Stadiums TCPA Sites SARA Sites Utility Transmission Lines Ingestion Zones Prisons Evacuation Routes Drinking Water Intakes Sewage Pumps njfw_lulc conditions. Spatially accurate, detailed vector dataset describing land use and land cover C. Online Thesauri: There are an increasing number of high-quality thesauri available online. A few with the most general usefulness are listed below; however this is not a very well researched list, nor an exhaustive list.

17 NJGIN Metadata Tips Last updated 27 March 2008 P. 17 of 18 If you use a thesaurus, be sure to fill in the element(s) for Theme Keyword Thesaurus <themekt> and/or Place Keyword Thesaurus <placekt> with the recognized title by which the thesaurus is known. Then each Theme Keyword associated with that Theme Keyword Thesaurus MUST be picked from that Thesaurus. If you do not want to look up entries in a thesaurus, just use Theme Keyword Thesaurus none and your own head as the source for keywords. For Theme Keywords: Library of Congress For photography, maps, architecture, etc: Thesaurus for Graphic Materials For general-level of any subject involved in legislation: Legislative Indexing Vocabulary For any feature type found on USGS topographic quadrangle maps, plus others: Alexandria Digital Library Feature Type Thesaurus For environmental subjects: GEneral Multilingual Environmental Thesaurus (GEMET) started by the European Environment Agency California Environmental Resources Evaluation System (CERES) Thesaurus (choose CERES Thematic Directory) For Place Keywords: Alexandria Digital Library Gazetteer (choose ADL Gazetteer server) Getty Thesaurus of Geographic Names (TGN) Geographic Names Information System (GNIS) The GNIS is our Nation's official repository of domestic geographic names information Peter Schweitzer s Place-picker (U.S. Geological Survey)

18 NJGIN Metadata Tips Last updated 27 March 2008 P. 18 of 18 D. Content Type codes for Resource Description <resdesc> Use EXACTLY ONE of the following entries, exactly as shown (case sensitive): Live Data and Maps Downloadable Data Offline Data Static Map Images Other Documents Applications Geographic Services Clearinghouses Geographic Activities E. Security Classification Entries Optional NJGIN system includes the following: Security Classification System: NJGIN Security Classification: Public Secure Classified Personal Data readable by anyone Data available to state and other government workers as needed for official purposes Data of a sensitive nature, available only to designated employees, supercedes above categories Personnally-identifiable information about individuals, protected by federal or state law, supercedes other categories Security Handling Description is also required if the above elements are used. It is a free text element. The above entries may be used both for Security Information in Section 1, and for Metadata Security Information, in section 7. The data and the metadata may have different Security Classifications; for example a Secure data set may have Public metadata If you have comments or questions about this document, please contact: Edith H. Konopka, GIS Specialist edith.konopka@oit.state.nj.us Mail: Office of GIS, NJ Office of Information Technology P.O. Box 212, Trenton, NJ Location: 200 Riverview (Route 29 & Cass Street) Voice: Fax: