Free GIS Book: Metadata - Revision history

Neteler: Reverted edits by Ptère (talk) to last revision by Neteler

2012-04-10T12:53:11Z

Reverted edits by Ptère (talk) to last revision by Neteler

Wiki-Ptère: /* Cooking Up Your Own Metadata Standard */

2012-04-10T12:47:58Z

Cooking Up Your Own Metadata Standard

Neteler: better title

2011-08-21T19:37:15Z

better title

Neteler: /* See also */

2010-08-25T17:41:45Z

Neteler: link Metadata software

2009-01-30T12:37:15Z

link Metadata software

Wiki-Sunburned Surveyor: Metadata moved to Free GIS Book: Metadata

2008-10-22T23:23:51Z

Metadata moved to Free GIS Book: Metadata

Wiki-Sunburned Surveyor at 23:23, 22 October 2008

2008-10-22T23:23:30Z

Wiki-Sunburned Surveyor at 23:21, 22 October 2008

2008-10-22T23:21:36Z

Show changes

Wiki-Sunburned Surveyor at 23:15, 22 October 2008

2008-10-22T23:15:56Z

Show changes

Neteler: + DCLite4G

2008-09-04T20:10:11Z

+ DCLite4G

@@ Line 107: / Line 107: @@
 Still, there may be situations in which it makes sense to track custom metadata. In this case it would be prudent to develop a standard of your own that governs how this metadata is created, stored, and used.
-What are some things you need to consider when <span class="plainlinks">[http://blog.le-petit-cuisto.fr<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">cooking</span>] up your own metadata standard? Here is a short list:
+What are some things you need to consider when cooking up your own metadata standard? Here is a short list:
 *What metadata elements will I want to capture that are not part of an existing standard? How will this information be represented in my metadata?

@@ Line 107: / Line 107: @@
 Still, there may be situations in which it makes sense to track custom metadata. In this case it would be prudent to develop a standard of your own that governs how this metadata is created, stored, and used.
-What are some things you need to consider when cooking up your own metadata standard? Here is a short list:
+What are some things you need to consider when <span class="plainlinks">[http://blog.le-petit-cuisto.fr<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">cooking</span>] up your own metadata standard? Here is a short list:
 *What metadata elements will I want to capture that are not part of an existing standard? How will this information be represented in my metadata?

@@ Line 247: / Line 247: @@
 * The Parcel Map shows a Pacific Telegraph Company easement across Parcel 1 and Parcel 4. The width of the easement is not shown on the Parcel Map. The Parcel Map contains a surveyor’s note indicating that the width of the easement was not listed in the deed granting the easement. As a result this easement was not added to the Easement layer of the DXF as required by the drafting procedures.
-=See also=
+=Metadata software=
 * [[Metadata software]]
 [[Category: Public Geospatial Data Committee]]

@@ Line 247: / Line 247: @@
 * The Parcel Map shows a Pacific Telegraph Company easement across Parcel 1 and Parcel 4. The width of the easement is not shown on the Parcel Map. The Parcel Map contains a surveyor’s note indicating that the width of the easement was not listed in the deed granting the easement. As a result this easement was not added to the Easement layer of the DXF as required by the drafting procedures.
-==See also==
+=See also=
 * [[Metadata software]]
 [[Category: Public Geospatial Data Committee]]

← Older revision		Revision as of 12:37, 30 January 2009
Line 247:		Line 247:
	* The Parcel Map shows a Pacific Telegraph Company easement across Parcel 1 and Parcel 4. The width of the easement is not shown on the Parcel Map. The Parcel Map contains a surveyor’s note indicating that the width of the easement was not listed in the deed granting the easement. As a result this easement was not added to the Easement layer of the DXF as required by the drafting procedures.		* The Parcel Map shows a Pacific Telegraph Company easement across Parcel 1 and Parcel 4. The width of the easement is not shown on the Parcel Map. The Parcel Map contains a surveyor’s note indicating that the width of the easement was not listed in the deed granting the easement. As a result this easement was not added to the Easement layer of the DXF as required by the drafting procedures.

		+	==See also==
		+
		+	* [[Metadata software]]
	[[Category: Public Geospatial Data Committee]]		[[Category: Public Geospatial Data Committee]]

← Older revision	Revision as of 23:23, 22 October 2008
(No difference)

@@ Line 204: / Line 204: @@
-==Automated Metadata Management
+==Automated Metadata Management==
 What Is Automated Metadata Management?
 Automated metadata is generated with a minimum of human interaction using a computer program. An example would be a computer program that automatically generated a list of image files and their corresponding world files in a particular folder of the computer filesystem. Such a tool could be set-up to scan the folder on a regular basis to keep a current inventory of the images in the folder. Another example would be a program that parses, or reads through a ESRI Shapefile to determine the geometry type of the features and that creates a list of the feature attributes.
 Why Would You Want To Use Automated Metadata Management?
 Despite its importance in any GIS, metadata creation and maintenance is often neglected because of the time and energy it requires. Creating and maintaining the metadata for your GIS is like changing the oil in your car. You don’t really notice you’ve neglected to do it until you ruin an expensive engine. Imagine for a moment that your automotive maintenance was performed for you automatically when you pulled into your garage at home. That is the type of benefit that automated metadata management can bring to your GIS.
 What Are The Limitations Of Automated Metadata Management?
 One obstacle to widespread use of automated metadata management is the cost of acquiring or developing the computer programs that produce it. Off-the-shelf or out-of-the-box solutions can be expensive. They may not capture all the metadata elements that you need, as metadata needs are often unique to each organization. Software development is not a simple task, and developing custom metadata tools is not always practical.
 Another limitation of automated metadata management is the lack of the human element. (This is also, ironically, one of its advantages.) This lack of human interaction causes two challenges for automated metadata management.
 [1] Automated metadata management tools typically need some type of event to trigger this execution. Connecting these tools to the other components of a GIS so they can be properly triggered can be a challenge. (Each stage of the metadata lifecycle should be considered when determining how to trigger the execution of automated metadata management tools.)
 [2] The content of metadata generated by an automated process is often limited to two types of information:
 (1)  Information that is already present, but not clearly evident from or separated in, existing geospatial data. (An example would be the number of layers in a DXF file, or the color type of a georeferenced JPEG image.)
 (2)  Information that is set-up prior to the execution of a tool and that applies to more than one geospatial dataset or more than one part of a geospatial dataset. (An example of this would be the organization identity and contact information for geospatial dataset. If an organization created multiple datasets then this information could be reused by an automated metadata tool during metadata creation.
+==A Simple Metadata Example==
 Below is a simple example of geospatial metadata. This metadata was generated for DXF files of survey maps creating subdivisions of land. This is the type of DXF file that might be used within an organization.
 Survey Map Name: Parcel Map 05-062
@@ Line 278: / Line 243: @@
 Notes:
--     The west line of Parcel 3 as shown on the Parcel Map is shown with a length of 536.85 feet. If this length is corrected to 563.85 feet the closure error for Parcel 3 is reduced by 27.00 feet. This correction was made in the DXF file representing this parcel map.
+* The Parcel Map shows a Pacific Telegraph Company easement across Parcel 1 and Parcel 4. The width of the easement is not shown on the Parcel Map. The Parcel Map contains a surveyor’s note indicating that the width of the easement was not listed in the deed granting the easement. As a result this easement was not added to the Easement layer of the DXF as required by the drafting procedures.
 [[Category: Public Geospatial Data Committee]]

← Older revision		Revision as of 20:10, 4 September 2008
Line 54:		Line 54:

	* [http://www.crepad.rcanaria.es/metadata/en/index_en.htm ISO Metadata Editor (IME)]		* [http://www.crepad.rcanaria.es/metadata/en/index_en.htm ISO Metadata Editor (IME)]
		+
		+	* [http://dclite4g.xmlns.com/ DCLite4G]: simple method of representing some properties of geographic data sets. The vocabulary is defined in RDF and OWL. [http://genesi-dr.terradue.com/news/_news.asp?title=Core+Metadata Example]
		+
	-----		-----