2.6.6 Object and attribute information

From Geostandards

Jump to: navigation, search

2.1 Introduction to Metadata

2.1.1 What is metadata?
2.1.2 Why metadata?
2.1.3 What can you do with it?
2.1.4 Where can you find metadata?
2.1.5 Applications
2.1.6 Discovery discovery

2.2 Metadata standards

2.2.1 What is a standard for?
2.2.2 Standards for geo-information
2.2.3 Metadata standards
2.2.4 INSPIRE
2.2.5 Discovery standards

2.3 Metadata in the working process

2.3.1 How do you make metadata?
2.3.2 How do you make metadata from services?
2.3.3 Where in the working process?
2.3.4 Tips for gathering metadata
2.3.5 Publishing metadata
2.3.6 Harvesting
2.3.7 Validating
2.3.8 Discovery working process

2.4 Metadata elements

2.4.0 Overview of metadata elements
2.4.1 Title of the resource
2.4.2 Summary
2.4.3 Status
2.4.4 Level of hierarchy
2.4.5 URL
2.4.6 Protocol
2.4.7 Name
2.4.8 Unique Identifier of the resource
2.4.9 Language of the resource
2.4.10 Subject
2.4.11 Keyword
2.4.12 Thesaurus
2.4.13 Thesaurus date
2.4.14 Thesaurus date type
2.4.15 Minimum x-coordinate
2.4.16 Maximum x-coordinate
2.4.17 Minimum y-coordinate
2.4.18 Maximum y-coordinate
2.4.19 Temporal cover
2.4.20 Date of the resource
2.4.21 Date type of the resource
2.4.22 Grade of the description of quality
2.4.23 General description of origin
2.4.24 Scale of application
2.4.25 Resolution
2.4.26 Code Reference system
2.4.27 Responsible organisation for namespace reference system
2.4.28 Conformity indication with the specification
2.4.29 Clarification
2.4.30 Specification
2.4.31 Specification date
2.4.32 Specification date type
2.4.33 Legal restrictions to accessibility
2.4.34 Other constraints
2.4.35 Security restrictions
2.4.36 User constraints
2.4.37 Responsible organisation resource
2.4.38 Responsible organisation resource: email
2.4.39 Responsible organisation resource: role
2.4.40 Metadata unique identifier
2.4.41 Parent unique identifier
2.4.42 Responsible organisation metadata
2.4.43 Responsible organisation metadata: role
2.4.44 Responsible organisation metadata: email
2.4.45 Metadata date
2.4.46 Language of the metadata
2.4.47 Metadata standard name
2.4.48 Metadata Standard version
2.4.49 Discovery metadata for data

2.5 Metadata elements for services

2.5.0 Metadata elements for services overview
2.5.1 Resource Title
2.5.2 Resource abstract
2.5.3 Resource type
2.5.4 Resource locator
2.5.5 Connect Point Linkage
2.5.6 Coupled resource
2.5.7 Scoped Name
2.5.8 Coupling Type
2.5.9 Spatial data service type
2.5.10 Service Type Version
2.5.11 Operation Name
2.5.12 DCP
2.5.13 Keyword value
2.5.14 Originating controlled vocabulary
2.5.15 Geographic location
2.5.16 Temporal Reference
2.5.17 Spatial resolution
2.5.18 Degree
2.5.19 Specification
2.5.20 Constraints
2.5.21 Conditions applying to access and use
2.5.22 Responsible party
2.5.23 Responsible party role
2.5.24 Metadata point of contact
2.5.25 Metadata language
2.5.26 Metadata date
2.5.27 The link to the metadata of the dataset and dataset series from the service
2.5.28 Discovery metadata for services

2.6 What you should also know

2.6.1 Bordering rectangle
2.6.2 Reference system
2.6.3 Geo shared licence
2.6.4 Optional set metadata of data
2.6.5 Multilingual metadata
2.6.6 Object and attribute information
2.6.7 Guidelines for sectors
2.6.8 Exchanging metadata


It is not possible to store object and attribute information in ISO 19115. Because the Dutch working field has requested this explicitly, the following solution is offered to enable the storing of this information. ISO offers a standard concerning the object catalogue in ISO 19110 FeatureCatalogue. Per continent, country or sector, a profile can then be defined on this ISO 19110. An example is ISO 19126, the American profile on ISO 19110. Because defining the object catalogue is not included in the scope of the project, Geonovum only focuses on storage of the object and attribute information. This means that not all mandatory elements of ISO 19110 are stored. The elements that can be stored are per object, (featureType); o the name of the object; o the definition of the object;  per object the attribute names (featureAttribute);  per attribute name the definition of the attribute name. 


ISO 19110 provides the user needs of the forum. It is possible to indicate mutual relationships and, for example, domains of the attributes, in ISO 19110. If this extra information is being stored, the terms of ISO 19110 have to be observed.



This method is in accordance with NEN3610. If a dataset was coded according to a sector model of NEN3610 then an object catalogue can be generated, because the object and attribute information (inclusive of name and definition) is also stored in the sector models. An object catalogue is a part of NEN3610.


← previous 2 Metadata next →
Retrieved from "http://geostandards.geonovum.nl/index.php/2.6.6_Object_and_attribute_information"
Personal tools