Geographic coverage
Type in here the exact geographic names/places that are covered by the data. Add Countries names only if the data displayed is really about the entire country. Example of locations/places are lakes, rivers, cities, marine areas, glaciers, bioregions like alpine region etc.
Exclude from Table of Contents
Type id of what do you want to exclude.
Contact person(s) for EEA
Outside person to be contacted by EEA if questions regarding the data resource arise at a later date, responsible project manager at EEA.
Data type is a named collection of data that contains individual data units organized (formatted) in a specific way. It contains one or more data files in different formats like mdb, csv/tsv, shape files, geotiff, xml etc.
Data
Scale of the dataset
Gives a rough value of accuracy for the GIS dataset. Example: 1:1000
EEA Management Plan
EEA Management plan code.
PDF Maximum depth
Maximum depth to recursively include children items while generating PDF. Leave it empty to use the portal global defined value.
The WGS84 latitude of a SpatialThing (decimal degrees).
A point, typically described using a coordinate system relative to Earth, such as WGS84.
Uniquely identified by lat/long/alt. i.e. spaciallyIntersects(P1, P2) :- lat(P1, LAT), long(P1, LONG), alt(P1, ALT), lat(P2, LAT), long(P2, LONG), alt(P2, ALT). sameThing(P1, P2) :- type(P1, Point), type(P2, Point), spaciallyIntersects(P1, P2).
PDF cover main image
Main cover image that will show up on the pdf cover page
Geographic accuracy
It is applicable to GIS datasets. It indicates the geographic accuracy of location, ground distance as a value in meters.
Themes
Choose max 3 themes
PDF Maximum items
Total maximum children items to be includedwhile generating PDF. Leave it empty to use the portal global defined value.
The relation between something and the point, or other geometrical thing in space, where it is. For example, the realtionship between a radio tower and a Point with a given lat and long. Or a relationship between a park and its outline as a closed arc of points, or a road and its location as a arc (a sequence of points). Clearly in practice there will be limit to the accuracy of any such statement, but one would expect an accuracy appropriate for the size of the object and uses such as mapping
Processor
The technical producer or processor of the resource.
External links, non EEA websites
External links, non EEA websites. Please write http:// in front of the links.
Source
A reference to a resource from which the present resource is derived. Details such exact body or department, date of delivery, original database, table or GIS layer, scientific literature..
Short ID
Short ID description.
PDF Maximum breadth
Maximum breadth to include children items while generating PDF. Leave it empty to use the portal global defined value.
Owner
An entity or set of entities that owns the resource. The owner is responsible for the reliability of the resource.
The WGS84 longitude of a SpatialThing (decimal degrees).
Environmental reporting obligations (ROD)
The environmental reporting obligations used to optain the data. Reporting obligations are requirements to provide information agreed between countries and international bodies such as the EEA or international conventions.
Hide Workflow Steps Trail Viewlet
Hide Workflow Steps Trail viewlet for this context/page
PDF Theme
Disable PDF export or override theme used to export this content as PDF.
Last upload
Date when the data resource was last uploaded in EEA data service. If not manually provided it will coincide with publishing date. It can later be used when a dataset is re-uploaded due to corrections and when a whole new version is not necessary.
The WGS84 altitude of a SpatialThing (decimal meters above the local reference ellipsoid).
WGS84 Geo Positioning: an RDF vocabulary
A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. Version $Id: wgs84_pos.rdf,v 1.22 2009/04/20 15:00:30 timbl Exp $. See http://www.w3.org/2003/01/geo/ for more details.
Recent changes to this namespace: $Log: wgs84_pos.rdf,v $ Revision 1.22 2009/04/20 15:00:30 timbl Remove the time bits which have been deal with elsewhere eg in iCal. Revision 1.21 2009/04/20 12:52:47 timbl try again Revision 1.20 2009/04/20 12:42:11 timbl Add Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09) Revision 1.19 2009/04/20 12:36:31 timbl Add Event (edited ages ago and never checked in), and location (following discussion http://chatlogs.planetrdf.com/swig/2009-04-20#T12-36-09) Revision 1.18 2006/02/01 22:01:04 danbri Clarified that lat and long are decimal degrees, and that alt is decimal metres about local reference ellipsoid Revision 1.17 2004/02/06 17:38:12 danbri Fixed a bad commit screwup Revision 1.15 2003/04/19 11:24:08 danbri Fixed the typo even more. Revision 1.14 2003/04/19 11:16:56 danbri fixed a typo Revision 1.13 2003/02/19 22:27:27 connolly relaxed domain constraints on lat/long/alt from Point to SpatialThing Revision 1.12 2003/01/12 01:41:41 danbri Trying local copy of XSLT doc. Revision 1.11 2003/01/12 01:20:18 danbri added a link to morten's xslt rdfs viewer. Revision 1.10 2003/01/11 18:56:49 danbri Removed datatype range from lat and long properties, since they would have required each occurance of the property to mention the datatype. Revision 1.9 2003/01/11 11:41:31 danbri Another typo; repaired rdfs:Property to rdf:Property x4 Revision 1.8 2003/01/11 11:05:02 danbri Added an rdfs:range for each lat/long/alt property, http://www.w3.org/2001/XMLSchema#float Revision 1.7 2003/01/10 20:25:16 danbri Longer rdfs:comment for Point, trying to be Earth-centric and neutral about coordinate system(s) at the same time. Feedback welcomed. Revision 1.6 2003/01/10 20:18:30 danbri Added CVS log comments into the RDF/XML as an rdfs:comment property of the vocabulary. Note that this is not common practice (but seems both harmless and potentially useful). revision 1.5 date: 2003/01/10 20:14:31; author: danbri; state: Exp; lines: +16 -5 Updated schema: Added a dc:date, added url for more info. Changed the rdfs:label of the namespace from gp to geo. Added a class Point, set as the rdfs:domain of each property. Added XML comment on the lat_long property suggesting that we might not need it (based on #rdfig commentary from implementors). revision 1.4 date: 2003/01/10 20:01:07; author: danbri; state: Exp; lines: +6 -5 Fixed typo; several rdfs:about attributes are now rdf:about. Thanks to MortenF in #rdfig for catching this error. revision 1.3 date: 2003/01/10 11:59:03; author: danbri; state: Exp; lines: +4 -3 fixed buglet in vocab, added more wgs links revision 1.2 date: 2003/01/10 11:01:11; author: danbri; state: Exp; lines: +4 -4 Removed alt from the as-a-flat-string property, and switched from space separated to comma separated. revision 1.1 date: 2003/01/10 10:53:23; author: danbri; state: Exp; basic geo vocab
Anything with spatial extent, i.e. size, shape, or position. e.g. people, places, bowling balls, as well as abstract areas like cubes.
label_description
help_description
Table of contents depth level
Which header tags should be taken into consideration for the table of contents.
Force Disable Autolinks
Disable Autolinks for this context/page
Unit
Describes the unit(s) taken in account for the measurement values(s) of the data resource.
Related items
Specify relations to other content within Plone.
Coordinate reference system
Coordinate reference system used for the GIS dataset. Example: Lambert Azimutal
Additional information
Other relevant information.
Temporal coverage
The temporal scope of the content of the data resource. Temporal coverage will typically include a set of years or time ranges.
label_short_name
help_shortname
Title
A comma-separated representation of a latitude, longitude coordinate.
Disclaimer
Disclaimer description.
Methodology
Description of how the resource was compiled: used tools, applied procedures, additional information to understand the data, further references to used methodologies.