2.4.34 Other constraints
From Geostandards
- 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.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.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
This element ‘Other constraints’ contains all the other constraints (including restrictions to accessibility security restrictions) and requirements for access to, and use of, the dataset.
When there are no constraints, one should adopt the text “no limitation on public access”. Adopting at least one of the three elements is mandatory Legal restrictions to accessibility, other constraints, security restrictions.
Geonovum recommends the use of geo shared license based on creative commons, to indicate the terms of license. The geo shared license is included in the element ‘Other constraints’.
Example;
No limitation to public access
| ← previous | 2 Metadata | next → |
