Specification FOT 4.0.1 for NEW-capturing

Transcription

Specification
FOT 4.0.1
for
NEW-capturing
Version: FOT 4.0.1 20091022
Content.
1.0 Foreword............................................................................................................ 1
2.1. Geometric demands and rules.................................................................... 2.1.1
2.1.1 Coordinates and height system ................................................................ 2.1.1
2.1.2 3D set of coordinates ............................................................................... 2.1.1
2.1.3 Undefined height ..................................................................................... 2.1.1
2.1.4 Point density ........................................................................................... 2.1.1
2.1.5 Geometry types and their rules ................................................................ 2.1.1
2.1.6 Spline and circle ...................................................................................... 2.1.2
2.1.7 Types of points in lines and surfaces ....................................................... 2.1.2
2.1.8 Zero vector .............................................................................................. 2.1.3
2.1.9 Vertical vector ......................................................................................... 2.1.3
2.1.10 Backloop and spike ............................................................................... 2.1.3
2.1.11 Identical objects .................................................................................... 2.1.3
2.1.12 General geometric rules ......................................................................... 2.1.3
2.1.12.1 Snap-principles and snap-series .......................................................... 2.1.4
2.1.12.2 Intersecting lines ................................................................................ 2.1.5
2.1.12.3 Break of an object due to origin change .............................................. 2.1.8
2.1.12.4 Common geometry ............................................................................. 2.1.8
2.1.12.5 Points and lines within surfaces ........................................................ 2.1.10
2.1.12.6 The relationship of one surface to another......................................... 2.1.12
2.1.12.7 Network rules ................................................................................... 2.1.15
2.1.13 Secondary attributes ............................................................................ 2.1.18
2.1.14 Accuracy in relation to GSD ................................................................ 2.1.20
2.1.15 Accuracy and registration methods ...................................................... 2.1.20
2.1.16 Object sizes ......................................................................................... 2.1.21
2.1.17 Bisecting surfaces ................................................................................ 2.1.22
2.1.18 Nodes .................................................................................................. 2.1.22
2.1.19 Lifecycle rules ..................................................................................... 2.1.22
2.1.20 Metadata for object and geometry........................................................ 2.1.23
2.2. Quality ........................................................................................................ 2.2.1
2.2.1 Expectations ............................................................................................ 2.2.1
2.2.2 Accuracy types ........................................................................................ 2.2.1
2.2.3 Error counting methods ........................................................................... 2.2.1
2.2.4 Geometric accuracy ................................................................................. 2.2.2
2.2.5 Thematic accuracy................................................................................... 2.2.4
2.2.6 Logical accuracy ..................................................................................... 2.2.5
2.2.7 Completeness .......................................................................................... 2.2.6
3.0 Object catalogue .......................................................................................... 3.0.1
Object types ..................................................................................................... 3.0.1
Attribute types ................................................................................................. 3.0.3
3.1 BUILDINGS ................................................................................................ 3.1.1
Building ........................................................................................................ 3.1.1.1
3.2 BUILDING AREA ...................................................................................... 3.2.1
Town centre .................................................................................................. 3.2.1.1
Commercial area ........................................................................................... 3.2.2.1
Low building area ......................................................................................... 3.2.3.1
High building area ........................................................................................ 3.2.4.1
3.3 TRAFFIC ..................................................................................................... 3.3.1
Road centre line ............................................................................................ 3.3.1.1
Railway ........................................................................................................ 3.3.2.1
Road edge ..................................................................................................... 3.3.4.1
Traffic island ............................................................................................... .3.3.5.1
Speed bump .................................................................................................. 3.3.6.1
Crash barrier ................................................................................................. 3.3.7.1
Train halt ...................................................................................................... 3.3.8.1
3.4 TECHNICAL .............................................................................................. 3.4.1
Technical area ............................................................................................... 3.4.1.1
Runway ........................................................................................................ 3.4.2.1
Churchyard ................................................................................................... 3.4.3.1
Basin............................................................................................................. 3.4.4.1
Telemast base ............................................................................................... 3.4.5.1
Hign tension wire foundation ........................................................................ 3.4.6.1
High tension wire .......................................................................................... 3.4.7.1
Structure ....................................................................................................... 3.4.8.1
Other small structures ................................................................................... 3.4.9.1
Groyne ........................................................................................................ 3.4.10.1
Parking ....................................................................................................... 3.4.11.1
Chimney ..................................................................................................... 3.4.12.1
Telemast ..................................................................................................... 3.4.13.1
Wind turbine ............................................................................................... 3.4.14.1
Mast ............................................................................................................ 3.4.15.1
Gully........................................................................................................... 3.4.16.1
Manhole ...................................................................................................... 3.4.17.1
Statue Memorial Stone ................................................................................ 3.4.18.1
Installation cabinet ...................................................................................... 3.4.19.1
3.5 NATURE...................................................................................................... 3.5.1
Forest ............................................................................................................ 3.5.1.1
Heath ............................................................................................................ 3.5.2.1
Wetland ........................................................................................................ 3.5.3.1
Scrub vegetation ........................................................................................... 3.5.4.1
Sand_dune .................................................................................................... 3.5.5.1
Quarry .......................................................................................................... 3.5.6.1
Fence ............................................................................................................ 3.5.7.1
Boundary line ............................................................................................... 3.5.8.1
Slope............................................................................................................. 3.5.9.1
Dyke ........................................................................................................... 3.5.10.1
Tree ............................................................................................................ 3.5.11.1
Treegroup ................................................................................................... 3.5.12.1
3.6 HYDRO ....................................................................................................... 3.6.1
Lake .............................................................................................................. 3.6.1.1
Stream centre line ......................................................................................... 3.6.2.1
Drainage ditch............................................................................................... 3.6.3.1
Stream edge .................................................................................................. 3.6.4.1
Harbour ........................................................................................................ 3.6.5.1
Coastline ....................................................................................................... 3.6.6.1
Jetty_Bathingbridge ...................................................................................... 3.6.7.1
3.7 ADMINISTRATIVE ................................................................................... 3.7.1
Historical point ............................................................................................. 3.7.4.1
4.0 APPENDIX .................................................................................................. 4.0.1
4.3 Appendix C: METHOD_3D ....................................................................... 4.3.1
4.9 Appendix I: DSFL codes for FOT-4 objects and their properties ................ 4.9.1
4.12 Appendix L: Within ............................................................................... 4.12.1
4.13 Appendix M: Common Geometry .......................................................... 4.13.1
4.14 Appendix N: AttributCheck .................................................................... 4.14.1
1.0 Foreword
FOT stands for "FællesOffentligT geografisk administrationsgrundlag" (common public geographical
administration data), which refers to the geographical data that central government and municipalities
produce and maintain jointly.
The interests of the FOT parties are handled by the joint public association 'FOTdanmark'. FOTdanmark
is responsible for the FOT specification, a joint system structure and business model for the cooperation
between the state and the municipalities. According to the specification the practical provision of FOT
data is handled by local FOT collaboration. These consist of the municipalities in a given area, plus
Denmark's Kort & Matrikelstyrelsen (National Survey and Cadastre).
FOT version 4.0 is available in electronic form on FOTdanmark's website: www.fotdanmark.dk along
with other documents on aspects concerning the production and use of FOT-data.
FOT version 4.0 is an extension of all the major principles and visions from previous versions. FOT
version 3.0 was released on 20 March 2006, and revised by Revision 1.0 on 15 January 2007 and
Revision 2.0 on 28 March 2008, which along with other amendments are including in version 3.2.1,
dated 13 June 2008.
FOT version 4.0 can be seen as the result of the practical experience gained from production, quality
assurance and use of FOT data with version 3.0 and onwards. As such, it does not involve a broader
specification, but a series of measures for simplification and rationalisation of the specification with
regard to simplifying production and quality assurance of FOT data.
As such FOT version 4.0 is the result of:
General correction of errors and deficiencies in the specification.
Experience from the production of FOT data in local FOT collaboration, e.g. HRKS Midt, RAK
and HRKS Syd.
Experience from the practical implementation of the data model in joint system FOT2007.
KL's recommendations from the Open Standards for Geodata Areas Project, phase 1, report dated
30 October 2008.
Suggestions received.
Development of FOT version 3.0 was handled by the FOT specification group.
The ground sat from 17 August 2006 until 22 September 2008 and consisted of:
Rikke Folving (Kort & Matrikelstyrelsen) (Chair)
Mogens Skov (Kort & Matrikelstyrelsen) (former Chair)
Jette Hinrichs Christiansen (Herlev Kommune)
Inge Flensted (Herning Kommune)
Birthe Jacobsen (Høje-Taastrup Kommune)
Lorenz Lei (Banedanmark)
Michael Stjernholm (Danmarks Miljøundersøgelser)
Svend Elgaard (Vejdirektoratet)
Tine Skafte Nielsen (Skov- og Naturstyrelsen)
Paul Daugbjerg (Kort & Matrikelstyrelsen)
Mogens Skov (Kort & Matrikelstyrelsen)
Olaf Andersson (Kort & Matrikelstyrelsen)
Kurt Toft Forbech (Kort & Matrikelstyrelsen)
Søren Buch (Geoforum, BlomInfo A/S)
1
Stig Bervig (Dansk Ledningsejerforum)
Since then, its work was continued in the FOT specification forum (formed by FOTdanmark, and
convened on 12 November 2008), which consists of:
Inge Flensted (KL, Herning Kommune) (Chair)
Rikke Folving (leader of the FOT Specification Seeretariat, Kort & Matrikelstyrelsen)
Sara Bjerre (temp. coverage for Rikke, Kort & Matrikelstyrelsen)
Hanne Christensen (KL, Hillerød Kommune)
Brian Hansen Damsgaard (KL, Fåborg-Midtfyn Kommune)
Per Johansen (KL, Kolding Kommune)
Svend Elgaard (Vejdirektoratet)
Karen Skjelbo (Erhvervs & Byggestyrelsen)
Ian Berg Sonne (Kort & Matrikelstyrelsen, Miljøcenter Aalborg)
Kurt Toft (Kort & Matrikelstyrelsen)
Søren Buch (Geoforum, BlomInfo A/S)
Dorthe Krøyer (Geoforum, HNG – Hovedstadens Naturgas)
Significant contributions were also made by:
The local FOT collaboration: HRKS Midt, RAK and HRKS syd
Søren Riff Alexandersen (Kort & Matrikelstyrelsen)
Peter Højholt Sørensen (Kort & Matrikelstyrelsen)
Dorte Holm (FOT Secretariat)
Thomas W. Møller (FOT Secretariat)
28. March 2009
English translation: 20090618
2
2.1. Geometric demands and rules
2.1.1 Coordinates and height system
UTM zone 32/ETRS89 is used for level registration and DVR90 for height registration as setup and
storage system. Excerpts can be made in other coordinate systems.
However, ORTHOPHOTO data will always be defined as standard in UTM32/ETRS89, as this
coordinate system has been selected to form the basis of ORTHOPHOTO.
2.1.2 3D set of coordinates
All points in an object contain the 3D set of coordinates (X, Y, Z) in metres to two decimal points.
Undefined Z-coordinates are given a value of 999.00 metres. Points with undefined Z can be designated
for future revisions.
2.1.3 Undefined height
Data produced by photogrammetry or land survey cannot contain undefined heights.
2.1.4 Point density
Point distances in individual objects cannot be less than the registration accuracy for the respective
object types within a given AREA TYPE POLYGON. The exceptions are points registered to observe
the rules for point deviation in height and the numbers of points in a circle.
2.1.5 Geometry types and their rules
The geometry in an object must consist of one of the following three geometry types.
Point
A point must consist of a single set of coordinates.
Line
A line must consist of one or more related vectors.
The first vector's first set of coordinates (starting point) can be identical in 3D with the last
vector's last set of coordinates (end point), providing the line consists of >2 vectors.
A line cannot cross or bisect (have common 2D or 3D points) itself.
Surface
A surface must consist of three or more vectors.
The starting point must be identical (3D) with the end point.
The edge of a surface object cannot cross or bisect (have common 2D or 3D points) itself.
A surface must have an area of > 0
A surface consists of one outer limitation and can have either none or up to several inner
limitations. Such inner limitations are called cut-outs. A cut-out is an integrated part of the surface
and must have the same object type as the outer limitation.
FOT 4.0.1 20091022
2.1 Geometric requirements and rules
2.1.1
2.1.6 Spline and circle
Splines, circles and circular arcs must not occur. All objects are supplied as points or are composed of
vectors.
An arced object must however be registered as a circle but, before delivery, must also be vectorised with
a point deviation in height equivalent to the registration accuracy, although with minimum 13 set of
coordinates, regardless of the point density criterion.
If more than 13 points occur in a circular object, they must not be closer than the requirements set for
minimum point distance.
2.1.7 Types of points in lines and surfaces
Lines and surfaces contain four different point types: end point, common point, intermediate point and
branch point.
An end point is the start or end set of coordinates of an object. An object must always be registered from
end point to end point.
A common point is a convergent set of coordinates of two or more objects in both plan and height, if the
objects in the landscape lie at the same height (3D common point). If the objects lie at different heights,
convergence can only be in plan (2D common point). A point can be either a common point between to
or more objects, or an end point for one or more of those objects.
An intermediate point in an object is a point which is neither an end point nor a common point.
A branch point in an object is an end point in which three or more objects with the same object type
meet. This point type only occurs in object types in a network.
This is illustrated below using two object types, one purple, one red.
They have a common geometry over a distance (consisting of two points) and at a single point.
The common points (pink) are intermediate points in the respective objects, but also common
points between the two objects.
The blue point is the common point between the objects, but also the end point for the purple
object and intermediate point for the red object.
The red object has branches. The object ends in a branch, which is why the branch and end points
always appear together.
BLACK
LIGHT BLUE
PINK
BLUE
GREEN
FOT 4.0.1 20091022
End point
Intermediate point
Common and intermediate points
Common point Intermediate and end points
Branch and end points
2.1.2
2.1.8 Zero vector
Zero vectors must not occur. A zero vector is one which has an identical set of coordinates (3D) at both
ends.
2.1.9 Vertical vector
Vertical vectors must not occur. A vertical vector is one which has identical plan coordinates (2D) at
both ends but with different heights.
2.1.10 Backloop and spike
Backloops or spikes must not occur in line or surface objects, where the line doubles back on itself
before continuing. A return angle of less than 30 o is an error. Here are some examples:
2.1.11 Identical objects
Geometrically identical objects with the same object type and attribute values must not occur.
2.1.12 General geometric rules
There are a number of general geometric rules, which all geometric FOT objects must comply to. There
are no exceptions to these rules, unless explicitly defined in them.
The rules are explained below, starting with the philosophy applied and then the actual description.
FOT 4.0.1 20091022
2.1.3
2.1.12.1 Snap-principles and snap-series
Limitation
This description primarily concerns snaps between captured points for different objects. A situation in
which vectors in two objects cross each other is not covered here. Please see the section on crossed lines.
In principle, snap between objects is legal as long as:
the situation is realistic, and reflects reality
capture of the objects conforms to registration accuracy
Principles
All object types are broken down into a hierarchy of snap groups.
Snap grouping principles are as follows:
1. The groups consist of object types of varying degrees of hardness, where:
a. hard object types are well delimited, precisely defined object types, and certain networks.
b. soft object types are those with a limitation which cannot be defined precisely as a result of
the nature of the object type.
2. There is no hierarchy in the sequence in which object types are named within a snap group.
3. Some object types can only snap with those of the same type. This applies to:
a. HIGH TENSION WIRE
b. ORTHO POLYGON
c. NAME
Snap between snap groups
In the event of snap between points from different object types, it is the point in the object which belongs
to the lowest ranking group which snaps to the point in the object from the higher ranking group. The
point in the object from the higher ranking group will not move.
Snap internally within a snap group
In the event of snap between points from different object types in the same snap group:
the point will move from the object with the poorest degree of registration accuracy. E.g. if a point
registered with an object accuracy of 100 cm is moved to an object with a degree of object
registration accuracy of 10 cm.
the point moves from the newest object to the oldest object if the objects have the same degree of
object registration accuracy
if the objects have the same age and have the same degree of object registration accuracy, there are
no rules as to which object should move.
Snap methods
In the event of snap, snap to existing captured points in an object is prioritised higher than snap to
a vector in an object
In the event of snap to a vector, a common point is usually created, although there are exceptions,
see sect. 2.1.12.2 on intersceting lines
In the event of snap, objects are broken down according to the rules in the section on crossed lines
Where the height difference for two X, Y snap-linked points is greater than the height accuracy for
the area polygon, within which the objects are located, the snap-linked points are given the same X
and Y values, but different Z values (2D snap).
Where the height difference for two X and Y snap-linked points is less or equal to the degree of
height accuracy for the area type polygon that the objects are located in, the snap-linked points will
be given the same X, Y and Z values (3D snap)
Snap group hierarchy
FOT 4.0.1 20091022
2.1.4
According to these principles, the object types will be grouped into the following group hierarchy, where
group 1 is the highest and group 5 the lowest:
Group 1
Group 2
Group 3
Group 4
MUNICIPALITY ROAD EDGE
BUILDING
PARKING
RAILWAY
SPEED BUMP
STREAM EDGE
FOREST
DRAINAGE DITCH HEATH
LAKE
WETLAND
HARBOUR
TRAFFIC ISLAND
TRAIN HALT
COASTLINE
BOUNDARY LINE
STRUCTURE
SLOPE
WIND TURBINE
FENCE
OTHER SMALL
DYKE
STRUCTURES
CRASH BARRIER
TREE
INSTALLATION
CABINET
JETTY_BATHINGBRIDG
E
GROYNE
HIGH TENSION
FOUNDATION
TELEMAST BASE
MAST
MANHOLE
GULLY
STATUE_MEMORIAL_S
TONE
TELEMAST
Group 5
ROAD CENTRE LINE
SYSTEM LINE
STREAM CENTRE
LINE
SAND_DUNE
CHIMNEY
QUARRY
BUILDING_
BBRPOINT
SCRUB_VEGETATIO HISTORICAL AREA
N
TECHNICAL_AREA HISTORICAL POINT
CHURCHYARD
TOWN POLYGON
RUNWAY
TOWN CENTRE
TREEGROUP
AREA TYPE
POLYGON
HIGH BUILDING
AREA
LOW BUILDING
AREA
COMMERCIAL
AREA
2.1.12.2 Intersecting lines
Limitation
The rules for intersecting lines cover situations where vectors in line objects intersect each other, and
where vectors in line objects intersect vectors in surface objects.
Situations in which surface objects overlap each other are covered in the rules for surfaces (see sect.
2.1.12.6).
All intersection situations are described, in which vectors in a:
line object intersect a line object
line object intersect a surface object
surface object intersecting a surface object
Principles
There seven ways in which lines and/or surfaces can intersect each other:
1. Intersect with no common point
2. Intersect with common point without a break
a. 2D
b. 3D
c. 2D or 3D
FOT 4.0.1 20091022
2.1.5
3. Intersect with common point and with a break
a. 2D
b. 3D
c. 2D or 3 D
Plus:
4. Intersection forbidden
As a general rule, a common point must be created when two lines intersect each other in both 2D and
3D.
Rules
Key to rule description:
Term
Explanation
different height
The height difference at a common point between two objects is greater
than the nominal degree of registration accuracy for the area.
same height
The heights at a common point in the two objects are the same.
cross
An object continues unbroken (the same object) on the other side of the
intersection
broken
An object has its end point at the meeting point and continues as a new
object (with the same object type) on the other side of the point of
intersection.
branch
Meeting point for three or more objects. The objects all have their end point
here.
All line objects which intersect another line object
in 2D or 3D must have a common point at the intersection, but both objects are never broken.
Exceptions:
2D
Exception 1: An object of type SYSTEM LINE must always have a common point when it
intersects an object of the same type as itself in 2D. As a result of the 2D-intersection, it must not
have a common point with other line objects.
Exception 2: The line objects below must always have a common point 2D point when intersecting
objects of the same type as themselves, or one of the other objects in this group. As a result of
the 2D intersection, they must not have a common point with other line objects unless the rules for
common geometry between line and surface require it.
ROAD CENTRE LINE
RAILWAY
STREAM CENTRE LINE
Exception 3: An object of type HIGH TENSION WIRE must never have a common point at a 2D
intersection of other objects, regardless of their type.
FOT 4.0.1 20091022
2.1.6
3D
Exception 4: The line objects below must always have a common 3D point at an intersection
and break when they intersect an object of the same type as themselves. As a result of a 3D
intersection, they must not have a common point with other line objects unless the rules for
common geometry between line and surface require it.
ROAD CENTRE LINE
SYSTEM LINE
RAILWAY
HIGH TENSION WIRE
STREAM CENTRE LINE
Exception 5: The following line objects must, however, always have a common point without
break at a 3D intersection, when they cross each other:
ROAD CENTRE LINE
RAILWAY
All line objects which intersect a surface object
in 2D or 3D must have a common point at the intersection but are never broken.
Exceptions:
Exception 6: The line objects below must not have a common point with any 2D or 3D
intersection of a surface object:
ROAD CENTRE LINE
SYSTEM LINE
RAILWAY
HIGH TENSION WIRE
STREAM CENTRE LINE
Exception 7: ROAD CENTRE LINE will, however, have a common point and will always be
broken when intersecting MUNICIPALITY.
Exception 8: The surface objects below must not have a common point when intersecting a line
object:
HISTORICAL AREA
ORTHO POLYGON
All surface objects which intersect a surface object
in 2D or 3D, can – but do not have to – have common points when they intersect each other.
Exceptions:
Exception 9: The surface objects below, however, must never have common points when they
intersect another surface object:
TOWN POLYGON
MUNICIPALITY
HISTORICAL AREA
AREA TYPE POLYGON
ORTHO POLYGON
FOT 4.0.1 20091022
2.1.7
Which object types appear in the various exceptions?
1
ROAD CENTRE LINE
SYSTEM LINE
RAILWAY
HIGH TENSION WIRE
STREAM CENTRE LINE
TOWN POLYGON
MUNICIPALITY
HISTORICAL AREA
AREA TYPE POLYGON
ORTHO POLYGON
2
X
3
X
X
X
X
4
X
X
X
X
X
5
X
X
6
X
X
X
X
X
7
X
8
9
X
X
X
X
X
X
X
X
2.1.12.3 Break of an object due to origin change
Principles
Objects are not broken in the FOT database just because of a change in object metadata.
There are however exceptions:
Where necessary, objects can be broken during the production of FOT data.
FOT's tools for entering data in the FOT database collect point metadata as stated by the producer
for the objects supplied.
Thereafter, the tools can link objects which are only broken by a change in object metadata into
longer objects, in accordance with the rules for network topology (see sect. 2.1.12.7 Network
rules)
The producer's statement of differences in object metadata can be found for these linked objects by
studying the point metadata registered for their points.
2.1.12.4 Common geometry
Limitation
The rules for common geometry for situations line-line, line-surface and surface-surface. Under the rules
for surfaces, there are some basic aspects concerning common geometry between surface objects. These
rules are adhered to and coordinated in this section.
Principles
The rules for common geometry are based on the following principles:
1. Common geometry between FOT objects is generally illegal between all object types, unless
specifically permitted.
2. Every effort has been made to produce rules that govern logical and realistic situations.
3. For the sake of rational production and quality control, the rules have to be applied mechanically,
and therefore apply universally.
4. Due to this universal applicability, there can be rare instances in reality which cannot be expressed
as data. The need for maximum mechanical control therefore means that although it may be
desirable, a few special instances cannot be reproduced, as the rule will not be able to find this
type of error in all the other places where the situation is undesirable.
5. Common geometry can occur as 2D or 3D.
FOT 4.0.1 20091022
2.1.8
6. All registered points in common geometry in objects must be uniform (X, Y, Z) in 3D, and plan
coordinates (X, Y) must be uniform in 2D. For 2D,the height difference of common points in two
objects is greater than the nominal degree of registration accuracy for the area.
7. In common geometry where line objects are included, a given line object type can only appear
once.
8. In common geometry where surface objects are included, individual object types can only appear
more than once if they have different attribute values.
9. Unless otherwise stated specifically in the form, this applies to all objects belonging to an object
type regardless of their different attribute values.
Rules
The rules are stated on this form, an excerpt of which is shown here.
The full form can be found in appendix M.
FOT 4.0.1 20091022
2.1.9
2.1.12.5 Points and lines within surfaces
Limitation
FOT 4.0.1 20091022
2.1.10
The rules regarding "within" concern only the relationship of point and line objects with regards to their
location inside a surface object.
'Within' in this context is defined as all or part of an object's registered limitation lying within a given
surface area. It does not include parts of an object located on top of a surface, as this situation is
described by the rules for common geometry.
Principles
The rules are based on the principle that where a location is logically or physically impossible, it is
forbidden.
Rules
The rules are stated on this form, an excerpt of which is shown here.
The full form can be found in appendix L.
FOT 4.0.1 20091022
2.1.11
2.1.12.6 The relationship of one surface to another
Limitation
The rules only describe relationships applicable to surface objects.
Principles
All surface objects are broken down into groups.
There are rules concerning each group's objects and the relationship of groups to each other.
Terms
There is a list of terms and an explanation of their content in the following section.
Term
Explanation
overlap
Where objects lie wholly or partially cover each other.
cut-out
An object with a cut-out has an outer and one or more inner limitations.
totally enclosed
When an object is totally enclosed by another, no part of the inner object
can touch the outer contact, and there is no cut-out in the outer object
containing the inner object.
enclosed in cut-out
An object which cannot lie within or overlap another object can lie within
the object's cut-out area and fill it wholly or partially. Where the cut-out
boundary is followed, common geometry occurs.
FOT 4.0.1 20091022
2.1.12
common geometry
With common geometry, the objects concerned have exactly the same
geometry (in 2D or 3D) at the place where common geometry occurs.
Rules
Within each group
Surface objects must not overlap or be totally enclosed regardless of object type.
If there are situations in the landscape that show a surface object with one or more inner
limitations, they will always be registered as a cut-out (e.g. an island in a lake).
If there is a situation in the landscape showing a surface object lying totally enclosed within
another surface object from the group, then this can only occur by forming a cut-out in the
enclosing object, and placing the surface object within the cut-out.
Surface objects belonging to different object types can have common geometry according to the
rules for the same. See the rules for common geometry in sect. 2.1.12.4 Common Geometry.
Surface objects with the same object types can only have common geometry according to the rules
for the same. See the rules for common geometry in sect. 2.1.12.4 Common Geometry.
Between groups
Cut-out is never permitted if the whole created is completely filled by an object from another
group.
Rules for overlap (crossing lines) are found in sect. 2.1.12.2 Crossing Lines.
Rules for common geometry are found in sect. 2.1.12.4 Common Geometry.
Groups
Surface object types are broken down into the following groups:
Registered object types:
1. Man-made structures and lakes:
BASIN
RUNWAY
CHURCHYARD
HIGH TENSION FOUNDATION
TELEMAST BASE
BUILDING
LAKE
2. Areas with intense daily human activity:
TOWN CENTRE
LOW BUILDING AREA
HIGH BUILDING AREA
COMMERCIAL AREA
TECHNICAL_AREA
3. "Landscape" areas:
FOT 4.0.1 20091022
2.1.13
FOREST
HEATH
WETLAND
SAND_DUNE
QUARRY
SCRUB_VEGETATION
Object types of administrative character:
4. Historical areas:
HISTORICAL AREA
5. Town polygon:
TOWN POLYGON
6. Municipality:
MUNICIPALITY
7. Area type polygon:
AREA TYPE POLYGON
8. Ortho polygon:
ORTHO POLYGON
Illustration
Visual illustration of surface area grouping.
FOT 4.0.1 20091022
2.1.14
2.1.12.7 Network rules
Limitation
The rules only describe relationships applicable to linear networks.
Network types
FOT operates with two types of network:
Between objects with the same object type
Between objects with the different object types
Network between objects with the same object type
These object types each form a network with other objects of the same object type.
HIGH TENSION WIRE
ROAD CENTRE LINE
SYSTEM LINE
FOT 4.0.1 20091022
2.1.15
RAILWAY
HARBOUR: Harbour type = Sea
STREAM CENTRE LINE
STREAM EDGE
DRAINAGE DITCH
COASTLINE
SLOPE
Objects in these networks always snap 3D to other objects in the network.
All objects of an object type are included in the network, regardless of the value of the object type's
attributes.
However, only those objects with attribute Harbour type = Sea, are included in the network for object
type HARBOUR.
Network between objects with the different object types
FOT has a combined network consisting of the following object types:
COASTLINE and
HARBOUR (with Harbour type = Harbour)
Together, these two objects form a network with no branches, and therefore represent the border between
land and sea.
Objects in these networks snap 2D or 3D to other objects in the network.
General for all linear networks
Joins
As a rule, objects will always join to objects which are as long as possible in a network. However, they
can never join over a branch point or break point.
Break
A network must always (and only) be broken in three instances:
Branching
Attribute change
Meeting with an object of another type
FOT 4.0.1 20091022
2.1.16
LIGHT BLUE = Branching point
This is where a network forms a branch.
BLACK = Break point
The red network is broken when an attribute changes value.
GREEN = Break point
The red network will break when another object type is snapped in to the network.
Breaks are made in a network when there is a change of value for one of the following attributes:
Object type
Attribute
ROAD CENTRE LINE
RAILWAY
HIGH TENSION WIRE
SLOPE
STREAM CENTRE LINE
STREAM EDGE
Road centre type
Road authority
CVFadmnr
CPR municipality
CPR road code
Track type
Owner_Railway
Tension
Slope type
Stream type
Main stream
Owner_Stream centre line
Bank
Visible_stream edge
Breaks are created in a network if an object of another type snaps into the network, according to the
following rules.
The object causing the break is not affected by this network rule.
Objects not referred to below do not break a network if they snap into it.
Network
Break object type
ROAD CENTRE LINE
MUNICIPALITY
FOT 4.0.1 20091022
2.1.17
RAILWAY
STREAM CENTRE LINE
COASTLINE
TRAIN HALT
LAKE
COASTLINE
STREAM EDGE
STREAM CENTRE LINE
COASTLINE
STREAM EDGE
STREAM CENTRE LINE
2.1.13 Secondary attributes
It is important for some network object types that they can only be broken in nodes where three or more
objects meet (branch nodes) or where one of the primary attributes changes value (e.g. CPR municipality
at ROAD CENTRE LINE).
This applies to ROAD CENTRE LINE, SYSTEM LINE, RAILWAY and STREAM CENTRE LINE.
These objects have generally attached, primary attributes which apply to the whole object.
However, there are also a number of secondary attributes, which can also be linked to them. A change of
value for these attributes will not necessarily occur where a general object starts or ends. Secondary
attributes can therefore have a different length than the general object (the parent object).
Information about secondary attribute applicability range in relation to the parent object is stored in the
FOT2007 database by linking a stationing (intervals) to the spread of the attribute.
The graphical display below shows a STREAM CENTRE LINE with primary and secondary attributes.
The red figures refer to the comments below:
3: "Stream type" is a primary attribute, with the value "Ordinary" for the whole general object
4: "Visible" is a secondary attribute. "1" means visible, and the figures behind the 1 show the extent of
this attribute (the object is visible from station 0 to 236.79).
5: Similarly, the object is invisible from 236.79 to 390.13.
6: "Network" is a primary attribute, which applies for the whole general object
7: "Mid-bank" is a secondary attribute. With value "0-2.5" here, and applicable for the whole object (0390.13)
8 and 9: Statement of a further two primary attributes
Production of FOT
External producers of FOT data do not need to state this interval information, as they can use the simpler
method of bisected sub-objects, also referred to as the "rice grain model".
FOT 4.0.1 20091022
2.1.18
Network objects are broken according to this model:
As described above (under Break) by branching, break after attribute change and break after snap
to another object type.
Breaks also occur in the event of a change of attribute value for all types of attributes.
No differentiation is made between primary and secondary attributes in this respect
All objects must be fully attributed according to the rules on multiplicity for the individual
attributes
As a result of these extra break points:
pseudo-node points are accepted where there are changes to attribute values
no geometry duplication occurs (no continuous parent object)
no pseudo-node points can occur when there are no changes in attribute values
The figure below shows the principles for a ROAD CENTRE LINE in which there are changes to two
attributes between the real node points.
BLACK dot = Real node
BLUE dot = Pseudo-node
Both the attributes shown - Surface and Road width - have minimum multiplicity 1, and must therefore
figure on all sub-objects.
Other attributes have been left out of the example, and are indicated only by "…".
If there was a bridge on the stretch for example, it would be designated as "Level = Bridge" on the subobject where the bridge occurs.
Entering data in FOT2007
Data can be entered in the FOT2007 system either in the form of intervals, or as bisected sub-objects.
Both data types can be processed for entry in the FOT2007 database.
FOT 4.0.1 20091022
2.1.19
Extracting data from FOT2007
Network objects can be extracted from the database using the secondary attributes that a user may
require. Extraction supplies the secondary objects:
either as parent objects, with the user-defined interval secondary attributes attached (as shown in
the illustration above)
or as bisected sub-objects (referred to as the "rice grain model") in which the secondary attribute
values are constant throughout the whole length of the sub-object. The above example (with
stationing) will result in two sub-objects being cut out of the parent object according to this
method, and divided over into station 236.79. This creates several objects and bisections (pseudonodes), which are neither branch nodes nor nodes resulting from a change of primary attribute
values.
2.1.14 Accuracy in relation to GSD
FOT is normally based on aerial photographs taken with digital cameras. The traditional relationship
between image scale and expected accuracy using analogue cameras therefore does not exist.
The relationships between pixel sizes (Ground Sampling Distance) and accuracy are listed below instead.
Expected accuracy, depending on GSD:
GSD
Plan accuracy
10 cm
20 cm
40 cm
10 cm
20 cm
75 cm
Height accuracy Point deviation in plan
15 cm
30 cm
75 cm
20 cm
40 cm
125 cm
The degrees of accuracy stated only apply to photogrammetically well defined points, such as signalised
points, open gullies and the like.
A much lower degree of accuracy can be expected for poorly defined objects such as hedges, fences and
un-metalled roads.
Indefinite boundaries such as coastlines, lakes and boundary lines can only be related to in the situation
at the time the photo was taken.
Point deviation in plan is a definition of the difference in plan between a measured line or point and the
physical element in the landscape.
In general terms, objects included in GSD-10 images and which lie within a corresponding AREA
POLYGON will be registered with a degree of accuracy equivalent to that which can be captured in
GSD-10 images.
Registrations with twice the degree of accuracy can be expected from land surveys as those for GSD-10
images.
2.1.15 Accuracy and registration methods
The degree of accuracy of a registration is stated for the horizontal coordinates (X, Y) and height (Z)
separately. The degree of accuracy expresses estimated neighbouring accuracy. The following values are
legal:
FOT 4.0.1 20091022
2.1.20
0.03 m.
0.05 m.
0.10 m.
0.15 m.
0.20 m.
0.30 m.
0.50 m.
0.75 m.
1.00 m.
3.00 m.
10.00 m.
The method for coordinate capture is stated for the horizontal coordinates (X, Y) and height (Z)
separately. The following values are legal:
Method
Explanation
Direct from land survey
LL
Direct from photogrammetry
FF
Laser scanning
LS
Unspecified
UU
Calculation determined by an automatic process under
BR
administrative revision
Manually-defined under administrative revision
MA
2.1.16 Object sizes
Objects must be registered as large as possible in accordance with the requirements for the individual
object types.
The minimum sizes will usually apply. Any deviations are described in more detail in the section dealing
with individual object types.
Line objects which form a link in a network have a minimum size corresponding to the degree of
registration accuracy, unless otherwise stated under the individual object types.
In the course of upgrading the existing TK- and TOP10DK maps, existing surface objects in the data
collections may not be able to meet the minimum requirements for FOT.
However, there are special conditions for object types BUILDING and LAKE. These object types will be
upgraded for FOT, but supplied to the purchaser along with other data. Such data will be supplied in a
special "undersize" file instead. This file will be delivered concurrent with and in the same breakdown as
the other data for the mapping stage.
Undersized objects will thus be given FOT object type names, but retain their original details.
Other upgraded objects which are too small with no geometric and logical relationship to other objects
will be deleted.
FOT 4.0.1 20091022
2.1.21
2.1.17 Bisecting surfaces
Surface objects cannot be bisected by other objects. However, roads and streams with a width of > 12
metres will bisect NATURE surface objects.
Roads/streams will be exposed when bisecting surface objects. Roads or streams will be bordered by the
natural boundaries which would otherwise have been captured if there had only been a surface area on
one side of the object.. Such boundaries could be FENCE, BOUNDARY LINE, ROAD EDGE,
STREAM EDGE or the like.
Width is measured as the distance between these boundaries on each side of the bisected object.
Where a road is flanked for example by two different surface objects, and the road is not sufficiently
wide to be exposed, the two surface objects will have common geometry on that side of the road which
seems most natural. The same applies to streams.
Where the distance between boundaries fluctuates over and under the 12 metre limit, the entire
road/stream geometry has to be taken into account when deciding whether it should be bisected or not.
This is intended to prevent frequent confusion when changing between bisections and integration.
2.1.18 Nodes
The FOT system automatically creates a node at all end points for network objects ROAD CENTRE
LINE, SYSTEM LINE and RAILWAY. Where two objects have a common end point, their nodes at this
point always have the same number.
If an end point is moved, its node point remains the same. This also applies to the moving of a common
end point.
In the event of an end point being moved horizontally by more than 3 metres, the node will be deleted
and a new one created with a new number. This also applies to a node in a common end point.
A water authority can enter values for start and end nodes for network object STREAM CENTRE LINE.
Where two objects are part of the same order network and have a common end point, their nodes at this
point always have the same number. Where two objects are not part of the same order network and have
a common end point, their nodes at this point will never have the same number.
In the event of moving an end point horizontally by more than 5 metres (common/non-common) the
node value will remain the same. This also applies to moving a non-common end point by more than 5
metres.
In the event of moving a common end point horizontally by more than 5 metres (more than 2 objects
involved), the node will be deleted and a new one created with a new value for those objects included in
the same order network. Those objects included in a lower order network will retain the value of the
deleted node.
2.1.19 Lifecycle rules
Normally, an object will retain the same FOT ID as long as possible for the sake of users who refer to its
ID. This means that revising an object will not normally cause it to be deleted and a new one created.
FOT 4.0.1 20091022
2.1.22
However, this will occur in instances in which an object is divided into several individual objects, or
several objects combined into one in the course of a revision, applicable to line and surface objects.
Similarly, it will occur if just one of the object points for line network objects ROAD CENTRE LINE,
SYSTEM LINE and RAILWAY is moved horizontally by more than 3 metres. It will occur for
STREAM CENTRE LINE if one of the object's points is moved horizontally by more than 5 metres.
2.1.20 Metadata for object and geometry
With reference to the model for metadata (see app. G), metadata has been divided into object metadata
and geometry metadata. The latter is saved as point metadata.
Point_metadata is intended for production/quality assessment and for the use of FOT data for technical
purposes.
Object_metadata is partially derived from metadata for associated geometry. The registration standard
used should also be stated.
See app. G for a detailed description of FOT metadata.
FOT 4.0.1 20091022
2.1.23
2.2. Quality
2.2.1 Expectations
This chapter describes the quality of FOT data a user can expect according to the FOT-4 specification.
The geometric data stems from very different sources and will be maintained by many different bodies,
which is why it is vital that a conscientious provision of metadata is a requisite for other map users to be
able to determine whether a map has sufficient quality for its intended use.
Controlling a map's geometric quality must therefore fulfil various data requirements depending on
which AREA POLYGON it refers to and takes into account metadata for a given object.
2.2.2 Accuracy types
The concept of quality in this specification is broken down into 4 sub-groups:
Geometric accuracy
The geometric accuracy is defined as the coordinate accuracy at an individual point in the data set. This
applies to accuracy both in plan and height.
Thematic accuracy
Thematic accuracy is defined as an expression of whether objects are captured with the correct object
types, attributes and attribute values.
Logical accuracy
Logical accuracy is defined as an expression of whether data fulfils the requirements for topology and
structure.
Completeness
Completeness is defined as an expression of the difference between the number of captured objects in
relation to those detected in the images (photogrammetric capture) or those detected in reality at the time
of survey (terrestrial registration).
In the event of a total revision, the margins of error for the total data will be used for the entire revised
area.
In the event of a selective revision the same will apply as for a total revision, although only for those
areas selected.
2.2.3 Error counting methods
A number of error counting methods have been devised to calculate the number of errors.
Name
Method
A
Total number of errors found in relation to the number of coordinates in the data for
the area.
FOT 4.0.1 20091022
2.2 Quality
2.2.1
B
C
D
E
F
G
H
J
Total number of surface errors found in relation to the number of surface objects in the
data for the area.
Total number of network errors in relation to network objects in the data for the area.
Counted for surface and network errors individually.
Total number of network errors found in relation to the number of the relevant object
types in the data for the area.
Counted for each of the named object types individually.
This error must not occur.
Total number of errors found in relation to the number of line and surface objects in
the data for the area.
Total number of errors found in relation to the number of the objects of the relevant
types in the data for the area.
Total number of missing objects in relation to those captured in a random square.
1 km square within AREA POLYGON with TYPE=3
For at least 100 objects (image objects) in the area, otherwise the area will have to be
expanded until there are at least 100.
Point-designated revision places: Total number of missing revisions in relation to the
designated number.
Up to 5 of these errors can occur per stage.
2.2.4 Geometric accuracy
Geometric accuracy is defined as the coordinate accuracy at an individual point on the map. This applies
to accuracy in both plan and height.
An object's geometric accuracy has a vital influence on its metadata. Individual registrations must
therefore be saved as either "certain" or "uncertain" registrations, or as "a missing height registration".
Certain registration
Certain registrations will fall within the accuracy limitations given in the table under sect. 2.1.15
"Geometric requirements and rules" for well defined points. For poorly defined object types such as
FOREST, COASTLINE and other indefinite boundaries, the degree of registration accuracy will be the
same, but the uncertainty of the object's location will mean that the accuracy of localisation will not be
the same as the degree of accuracy of registration. In the metadata, these objects will still have a degree
of accuracy equivalent to "certain registration" as the registration method has not deteriorated, only the
definition of the object's uncertain localisation.
Uncertain registration
Uncertain registration will occur when a given combination of registration methods and circumstances
make it impossible to register an object with the accuracy that the method of registration can otherwise
attain. This can be caused by e.g. shading from trees or buildings. The accuracy of uncertain registration
is set to 3.00 metres.
No height registration
Height registration is not recorded when the registration method used does not supply a usable Z
coordinate, e.g. from screen digitalisation or registration in 2D-GIS. If a Z coordinate is missing, plan
and height accuracy will correspond to that the registration method would otherwise be able to supply for
the area in question. The actual Z coordinate will, on the other hand, always be set to the prescribed
value for undefined Z coordinates as described in sect. 2.1.2 "Geometric requirements and rules".
FOT 4.0.1 20091022
2.2 Quality
2.2.2
There will be a logical relationship between registration method, object type and accuracy.
Legal values
Please refer to sect. 2.1.15 "Geometric requirements and rules" for a table listing the required degrees of
accuracy.
Checking point average errors
Checking plan point average errors is performed as a relative or absolute check. Checking height average
errors is performed as an absolute.
The requirements for average errors in both plan and height must be observed, for a FOT data set to be
able to pass the point average error test.
Checking relative point average errors in plan
Normally, the relative point average error is near to the absolute average error.
The relative point average error is checked by performing a series of distance measurements.
To obtain a satisfactory basis for assessing the plan point average error at least 25 independent distance
measurements must be performed, distributed evenly over the FOT data set to be checked.
Calculation of the relative point average error:
Am Distance measured in the field
Af Distance calculated from corresponding points in FOT data
n
Number of measurements
Note:
Serious errors (max. 5%) can occur. These are not included in average error calculation.
Determining the distance in the field must be performed with an average error on checkpoints, which are
at least 3 times less than the expected average error on the checkpoints in FOT data.
Checking absolute point average errors in plan
Normally, the relative point average error is close to the absolute average error.
The absolute point average error is established by checking a series of defined control point localisations.
To obtain a satisfactory basis for assessing point average error in plan, at least 25 independent check
measurements must be performed, distributed evenly throughout the FOT data set to be checked.
The measurements must be performed with a high degree of accuracy. Calculated local coordinates are
transformed in conformity (only parallel offset and rotation) over the database coordinates. The
transformation average errors will correspond to the relative point average error.
Note:
Determining a coordinate in the field must be performed with an average error on the checkpoints, which
is at least 3 times smaller than the expected average error on the checkpoints in FOT data.
Checking absolute average errors in height
Average errors in height are checked by surveying the height of at least 25 independent and well defined
height checkpoints, which have also been surveyed in the database.
FOT 4.0.1 20091022
2.2 Quality
2.2.3
Calculating height average error:
Km Height measured in the field
Kf Height from FOT data
n Number of measurements
Note:
Determining the height in the field must be performed with an average error on the checkpoints, which is
at least 3 times smaller than the expected average error on the checkpoints in FOT data.
2.2.5 Thematic accuracy
Thematic accuracy is defined as an expression of whether objects are captured with the correct object
types, attributes and attribute values or not.
Thematic accuracy is shown in the following table.
Object type plus their major
Permissible errors %
Calculation
attributes
method
BUILDING
ROAD CENTRE LINE,
RAILWAYS, STREAM CENTRE
LINE
LANDSCAPE group surfaces
Coastline (COASTLINE and
HARBOUR)
All other object types, individually
Attributes included in the count:
Object type
BUILDING
ROAD CENTRE LINE
RAILWAY
STREAM CENTRE LINE
HARBOUR
AREA TYPE
POLYGON
AREA TYPE
POLYGON
AREA TYPE
POLYGON
TYPE=1
TYPE=2
TYPE=3
3
3
2
2
1
1
F
F
3
3
2
2
1
1
F
F
5
4
3
F
Attributes
All
All, except: Surface and Road Width
All
All
All
Checking attributes and their values.
This includes a check that all object type names, attributes and attribute values are spelt correctly.
Further checks are performed to ensure the attributes:
are present for the proscribed objects
possess a legal value
are correctly combined with any other attributes on the same object
FOT 4.0.1 20091022
2.2 Quality
2.2.4
The spelling of all object types and attributes plus the combination rules for attributes are listed in a
spreadsheet (see app. N).
This check can run fully automatically, and as spellings and attribute combinations are vital for the
database, no errors will be accepted in this test.
Here is an excerpt of an example of a form from FOT3. When there is a form for FOT4, the graphic and
appendix will be replaced. The form is dynamic, and can change several times during a survey.
2.2.6 Logical accuracy
Logical accuracy is defined as an expression of how well the data fulfils the requirements listed below
for internal structure.
Item
Definition
Permissible
Calculation
errors %
method
Geometry type
Correct geometry type (point, line,
0
D
surface) and observance of the rules
stated for them.
Splines and circles
Observance of the rules.
0
D
Zero vector and
Are requirements for zero vectors and
J
backloop
backloops fulfilled?
Statement of accuracy Only the proscribed values can be
0
D
used.
Height statements
Undefined height statements cannot
J
occur for photogrammetric work, such
as setting up, upgrading or revision.
Snap
Error snap= snap missing or wrong.
0,20
A
Minimum sizes
Failure to observe minimum size for
Per geometry
J
points: distance to other objects
type
lines: Minimum length + registration
density (internally and in relation to all
other objects)
surfaces: Minimum area + registration
density (internally and in relation to all
other objects)
Topology
Same geometry, object type and
0
D
Identical objects
attributes.
Topology
Illegal overlap of surfaces wholly or
1
B
Object overlap
partial, no cut-out, illegal cut-out and
no common geometry between
surfaces.
Topology
Common geometry
Topology
Break-Join
FOT 4.0.1 20091022
Network objects (ROAD CENTRE
LINE, RAILWAY and STREAM
CENTRE LINE) cutting with the
bordering objects.
Illegal or no common geometry
between objects.
Full network topology as proscribed
for: ROAD CENTRE LINE,
2.2 Quality
0.2
E
0.1
C
2.2.5
SYSTEM LINE, RAILWAY,
STREAM CENTRE LINE plus
COASTLINE/HARBOUR
2.2.7 Completeness
Completeness is defined as the percentage of registered objects in relation to those which can be
identified in the images. Terrestrial registrations: in relation to those detected in the landscape.
The selection of object types must correspond to the proscribed selected relevant AREA POLYGON
(providing they really exist in the area).
The area must appear homogenous, and any missing objects (which must also be clearly visible in the
images) must be randomly distributed.
Item
Permissible errors
Calculation
%
method*
BUILDING
1
G/H
ROAD CENTRE LINE (only those with CPR
1
G/H
code)
ROAD CENTRE LINE (only those without CPR
3
G/H
code)
Other point objects (each object type individually)
5
G/H
Other line objects (each object type individually)
3
G/H
Other surface objects (each object type
3
G/H
individually)
*
Method G is used for total revision
Method H is used for point designated revision
FOT 4.0.1 20091022
2.2 Quality
2.2.6
3.0 Object catalogue
The object catalogue is divided into eight main sections, each concerning a group of objects.
Group object types are described in each group.
Each object type description is based on the same format, with the following main sections:
Main section
Content
Object definition
A very brief description of the occurrence in the landscape which the
object type describes.
Attributes and references
A list of the primary and secondary attributes which can be linked to
the object.
Representation
A brief explanation of what a data user can expect to be represented
by the object type.
New mapping
A detailed guide to photogrammetric registration of the object type.
There is also a corresponding terrestrial registration guide for some
object types.
If not all the attributes or their values are to be processed
photogrammetrically, a description can also be found here.
Examples
Examples of how object types are correctly captured in typical
situations.
Object types
Object group
BUILDINGS
Object type
BUILDING
Geometry Minimum size Area
Surface
1.2=25 m2
1 2 3
2
3=10 m
BUILDING_BBRPOINT
BUILDING AREA
TRAFFIC
TECHNICAL
FOT 4.0.1 20091022
Point
2
TOWN CENTRE
Surface
2,500 m
COMMERCIAL AREA
Surface
2,500 m2
LOW BUILDING AREA
Surface
2,500 m2
HIGH BUILDING AREA
Surface
2,500 m2
ROAD CENTRE LINE
Line
1 m.
RAILWAY
Line
1 m.
SYSTEM LINE
Line
1 m.
ROAD EDGE
Line
-
TRAFFIC ISLAND
Line
-
SPEED BUMP
Line
CRASH BARRIER
Line
TRAIN HALT
Point
-
TECHNICAL_AREA
Surface
500 m2
RUNWAY
Surface
1000 m2
3.0 Object catalouge
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
3
3
3
3
3
3
3
3
3
3
3
3
1 2 3
1 2 3
1 2 3
3.0.1
Surface
500 m2
BASIN
Surface
25 m
2
TELEMAST BASE
Surface
1 m.
Surface
1 m.
HIGH TENSION WIRE
Line
-
STRUCTURE
Line
OTHER SMALL STRUCTURES
Line
1=25 m2
2.3=10 m2
-
GROYNE
Line
25 m.
PARKING
Line
50 m.
CHIMNEY
Point
Height 10 m.
TELEMAST
Point
Height 10 m.
WIND TURBINE
Point
Height 10 m.
MAST
Point
Height 3 m.
GULLY
Point
MANHOLE
Point
STATUE_MEMORIAL_STONE
Point
INSTALLATION CABINET
Point
60 cm.
FOREST
Surface
2,500 m2
HEATH
Surface
2,500 m2
WETLAND
Surface
2,500 m2
SCRUB_VEGETATION
Surface
50 m2
SAND_DUNE
Surface
10,000 m2
QUARRY
Surface
2,500 m2
FENCE
Line
1.2=25 m. 3=2 m.
BOUNDARY LINE
Line
-
SLOPE
Line
50 m.
DYKE
Line
50 m.
TREE
Point
-
TREEGROUP
Point
CHURCHYARD
NATURE
HYDRO
Surface
50 m /100 m2
STREAM CENTRE LINE
Line
50 m.
DRAINAGE DITCH
Line
50 m.
STREAM EDGE
Line
50 m.
HARBOUR
Line
50 m.
COASTLINE
Line
50 m.
LAKE
JETTY_BATHINGBRIDGE
ADMINISTRATIVE
Line
1.2=50m 3=10 m
TOWN POLYGON
Surface
2,500 m2
MUNICIPALITY
Surface
2,500 m2
Point
-
HISTORICAL AREA
Surface
2500 m2
HISTORICAL POINT
Point
-
AREA TYPE POLYGON
Surface
10,000 m2
ORTHO POLYGON
Surface
ORTHO PHOTO
Image
PLACE NAME
MISCELLANEOUS
FOT 4.0.1 20091022
2
0.25 km2
1 2 3
1 2 3
3
3
123
123
3
123
23
123
123
123
3
3
3
3
3
1 2 3
1 2 3
1 2 3
3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
3
1 2 3
1 2 3
1 2 3
3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
1 2 3
3.0.2
Attribute types
Object group
Object type
Attribute
BUILDINGS
BUILDING
Building type
Tank/Silo_Type
Measurement point_Building
Method_3D
Under_Minimum_Building
BBR_Reference
Building_ID
Area qualtity
BUILDING_BBRPOINT
Building_ID
Placing_BBRpoint
BUILDING AREA
TOWN CENTRE
COMMERCIAL AREA
LOW BUILDING AREA
HIGH BUILDING AREA
TRAFFIC
ROAD CENTRE LINE
Road center type
Start node_Road
End node_Road
Road authority
CVFadmnr
CPR municipality
CPR road code
Road class
Traffic type
Level
Surface
Road width
Place
Fictive
Access way
Roundabout
Parent FOTID
Parent FOTversion
Start
End
RAILWAY
Track type
Owner_Railway
Start node_Railway
End node_Railway
Level_Railway
Visible_Railway
Parent FOTID
Parent FOTversion
Start
End
FOT 4.0.1 20091022
3.0.3
SYSTEM LINE
Start node_System
End node_System
Road authority_System
CVFadmnr
CPR municipality
CPR road code
ROAD EDGE
Type
Surface_Road edge
Visible_Road edge
TRAFFIC ISLAND
SPEED BUMP
CRASH BARRIER
Barrier type
TRAIN HALT
Name
Owner_Train halt
TECHNICAL
TECHNICAL_AREA
Area type
RUNWAY
Runway type
CHURCHYARD
BASIN
Basin type
TELEMAST BASE
HIGH TENSION WIRE
TENSION
STRUCTURE
GROYNE
PARKING
CHIMNEY
TELEMAST
Medium type
WIND TURBINE
Building_ID
MAST
GULLY
MANHOLE
Manhole type
NATURE
FOREST
Owner_Forest
Under_Minimum_Forest
HEATH
Heath type
Under_Minimum_Heath
WETLAND
Under_Minimum_Wetland
SCRUB_VEGETATION
SAND_DUNE
QUARRY
Mineral type
Quarry type
FOT 4.0.1 20091022
FENCE
Fence type
BOUNDARY LINE
Boundary line type
SLOPE
Slope type
DYKE
Dyke type
TREE
Tree species
3.0.4
TREEGROUP
HYDRO
LAKE
Lake type
Salt_Lake
Temporary
Lake_Under_Minimum
Island_Under_Minimum
STREAM CENTRE LINE
Stream type
Start node_Stream centre line
End node_Stream centre line
Direction
Network
Main stream
HR_VL_Code
HR_VL_Start
HR_VL_End
Centre width
Visible_Stream centre
ParentFOTID
ParentFOTversion
Start
End
DRAINAGE DITCH
STREAM EDGE
Bank
Visible_stream edge
HARBOUR
Harbour type
COASTLINE
JETTY_BATHINGBRIDGE
Pier type
Location
ADMINISTRATIVE TOWN POLYGON
Town type
Building area code
MUNICIPALITY
CPR municipality
HISTORICAL AREA
Memorial type_FFO
Under_Minimum_FFO
Paragraph 4_FFO
Paragraph 4_Ref_FFO
HISTORICAL POINT
Memorial type_FFP
Paragraph 4_FFP
Paragraph 4_Ref_FFP
PLACE NAME
Place name
SNSOR_Code
MISCELLANEOUS
AREA TYPE POLYGON
Area type
ORTHO POLYGON
Ortho type
ORTHO PHOTO
FOT 4.0.1 20091022
3.0.5
3.1 BUILDINGS
Building
FOT 4.0.1 20091022
3.1 BUILDINGS
3.1.1
BUILDING
Object group
BUILDING
Object type
BUILDING
Geometry type
Surface
Minmum size
25 m2
Area
1 and 2
10 m2
3
Object definition
Representation of a building object's developed and covered area in a BBR registered building object.
Apart from the general attributes, the following special attributes have been defined:
Name
Multiplicity
Type
Legal values
BUILDING TYPE
[1..1]
Text
TANK/SILO_TYPE
[0..1]
Text
MEASUREMENT POINT_ [1..1]
BUILDING
Text
Building
Houseboat
Greenhouse
Tank/Silo
Slurry, open
Slurry, covered
Slurry, unknown
Unknown
Roof
METHOD_3D
[1..1]
Text
TK/FOT-roof
UNDER_
MINIMUM_
BUILDING
[1..1]
BBR_REFERENCE
[1..1]
Change ResponOrigin
triggers
sible
history
No
KOM
Explicitly stated
when entered.
No
KOM
Explicitly stated
when entered.
No
KOM
No
KOM
Boolean 0
No
KOM
Survey method stated
in object origin
details, or explicitly
stated when entered.
Stated according to
which method Z
coordinate is
registered.
Explicitly stated
when
administratively
entered.
Boolean 0
No
KOM
KMS
BUILDING TYPE
States type of building using one of the stated values.
TANK/SILO_TYPE
Only stated for BUILDING with BUILDING TYPE=Tank/Silo, with one of the stated values.
MEASUREMENT POINT_BUILDING
States the method the object was captured with.
METHOD_3D
Stated according to which method the Z coordinate is registered, including specification. See app. C for
further details.
UNDER_MINIMUM_BUILDING
0 = BUILDING's area >= minimum for area
FOT 4.0.1 20091022
3.1.1 BUILDINGS-BUILDING
3.1.1.1
BBR_REFERENCE
0 = BUILDING has no BBR reference
Representation
As the establishment of BUILDINGs for an initial FOT setup is partially based on existing, older data,
they can be produced according to different specifications. As such, no unambiguous representation of
BUILDING can be given which describes all the aspects that can apply for the individual objects in
relation to those specifications they have been based on. A detailed description of these aspects can be
found in the respective specifications.
The following description applies only to BUILDINGs registered in accordance with the FOT-4
specification.
BUILDING represents a permanent building, including garage, car port, tank/silo, conservatory, sun
lounge, shed, lean-to, covered area, fixed canopy on a building, platform roof, houseboat and the likebut not mobile homes, caravans, tents or the like.
Furthermore, projected buildings can also be represented.
Depending on the MEASUREMENT POINT_BUILDING, BUILDINGs with BBR reference have a
similar geometric shape to a corresponding building in BBR.
A BUILDING without BBR reference represents one or more buildings which have no reference to a
building object in BBR, either because no geocoding has yet been performed, or because of no
registration in BBR.
Within AREA POLYGON with AREA TYPE = 1 and 2 there are no buildings with an area of < 25 m2
unless the municipality has separately designated them for registration.
Within AREA POLYGON with AREA TYPE = 3 there are no buildings with an area of < 10 m2 unless
the municipality has separately designated them for registration.
BUILDINGs with BUILDING TYPE =Tank/Silo will only appear if they are on land and can be
registered on the periphery of several small silos.
For the purpose of calculation, BUILDING has right angled corners where the corners of the physical
building are deemed to be.
New mapping
Photogrammetric registration instruction
These registration instructions apply only to new photogrammetrical mapping. These can be performed
using several methods. The following description only applies to BUILDINGs captured in accordance
with FOT4 specification using METHOD_3D = TK/FOT roof
Data capture is on the extreme edge of the roof, although not for apex points when they lie in a line
between two roof edges in 2D. The height is captured on the roof edge. There are rules for roof elevation
differences, but the captured height must be as high as the lowest building element.
BUILDING must be divided when BUILDING TYPE changes and for geocoded buildings, where
different building parts have separate BBR references.
FOT 4.0.1 20091022
3.1.1.2
Where a building stands entirely or partly on pillars or a building part links two buildings without contact
with the ground the roof edge is captured.
BUILDING represents a permanent building, including garage, car port, tank/silo, conservatory, sun
lounge, shed, lean-to, covered area, fixed canopy on a building, platform roof, houseboat and the like but not mobile homes, caravans, tents or the like.
Access stairs, shelter walls, balconies (with no connection to the ground) and textile awnings should not
be included.
Buildings under construction are included when there is enough of the walls and/or roof that it can be
deemed possible to register the dimensions of the final building. When registering walls the height must
be captured at ground level.
For the purpose of calculation, BUILDING has right angled corners where the corners of the physical
building are deemed to be.
BUILDINGs with an area smaller than that shown in the table below are included if each one is
explicitly designated for revision/capture in advance:
AREA
AREA
Requirement for minimum size
POLYGON
POLYGON
3
1 and 2
2
Building registered if its area >=
10 m
25 m2
Horizontal difference in roof structures included if they are >=
30 cm.
1 m.
Angle correction must be performed on building corners
deemed to be right-angled. However, the points surveyed
during this process cannot be moved more than:
30 cm.
1 m.
Holes in the roof surface (e.g. atrium courtyards) where the
hole extends down to the ground, appear as cut-outs in the
BUILDING with the same value as for BUILDING TYPE, if
the hole area >=
10 m2
25 m2
BUILDINGs with less area than shown in the table are included if each one is explicitly designated for
revision in advance:
Similarly, customers are encouraged to designate special, notable, small buildings (e.g. Lighthouses or
Transformer Buildings) within AREA POLYGON Type=1, if they are to be registered.
Special aspects:
Building with BUILDING TYPE =Houseboat must not have any internal limitation (cut-out).
Building with BUILDING TYPE =Houseboat will be captured (X, Y, Z) when the hull is deemed to
have the largest area. Bridge superstructures, bowsprits and the like will not be included.
Building with BUILDING TYPE =Houseboat should not be corrected with right-angles but symmetry
along its own longitudinal axis should be attempted.
Building with BUILDING TYPE =Houseboat will only be captured if designated in advance by the
municipality.
FOT 4.0.1 20091022
3.1.1.3
Building with BUILDING TYPE=Greenhouse, will only be registered if it is on a commercial scale
(market gardening, nurseri, flower park, public access etc.) with roof and walls mainly of glass. Glass
building (wholly or partially of glass) belonging to private houses, stations, stadiums, swimming pools,
shopping centres, company offices or the like are not Greenhouse, but Building.
When a BUILDING with BUILDING TYPE=Tank/Silo is partially located in a BUILDING with
another value for BUILDING TYPE, the other BUILDING will be registered first as normal, followed
by the remaining part of the silo as BUILDING with BUILDING TYPE= Tank/Silo with 2D snap to the
shared side with BUILDING.
When a BUILDING with BUILDING TYPE=Tank/Silo does not fulfil the requirement for minimum
measurement, the surrounding silos (if there are several which are all too small, are too close together or
a silo over the minimum size lies just beside) will be captured instead (see examples).
Examples
RED=BUILDING-Building
LIGHT BLUE=BUILDING-Greenhouse
YELLOW=BUILDING-Tank/Silo_Type-Slurry, open
PINK=BUILDING-Tank/Silo_Type-Slurry, closed
GREEN=BUILDING-Houseboat
FOT 4.0.1 20091022
3.1.1.4
FOT 4.0.1 20091022
3.1.1.5
LIGHT BLUE=BUILDING-Tank/Silo_Type-Unknown
FOT 4.0.1 20091022
3.1.1.6
FOT 4.0.1 20091022
3.1.1.7
3.2 BUILDING AREA
TOWN CENTRE
COMMERCIAL AREA
LOW BUILDING AREA
HIGH BUILDING AREA
FOT 4.0.1 20091022
3.2 BUILDING AREA
3.2.1
TOWN CENTRE
Object group
BUILDING AREA
Object type
TOWN CENTRE
Geometry type
Surface
Minimum size
2,500 m2
Area
1 2 3
Object definition
Limitation of an area with interrelated building types in the centre of a town.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
TOWN CENTREs are represented by the area's boundary line bordering on another line- and/or surface
object. The height is at terrain level.
TOWN CENTRE delimits the built-up area in a town centre, consisting of housing blocks, apartment
blocks, squares and building complexes and the areas behind them, such as car parks, backyards and
playgrounds.
TOWN CENTRE is only registered for areas >= 2,500 m2
New mapping
TOWN CENTRE registration is based on the limitation of the built-up area in a town centre, consisting
of housing blocks, apartment blocks, squares and terraced buildings and the areas behind them, such as
car parks, backyards and playgrounds.
Limitation occurs at ROAD CENTRE LINEs or on other BUILDING AREA surfaces. Where these
object types are not found, ROAD EDGE, FENCE, BOUNDARY LINE, HARBOUR or other object
types are used, which form the border of the surface's area.
TOWN CENTRE is registered with as few points as possible. However, the difference between the
actual line and registered line will not exceed the following values in plan and height.
AREA TYPE POLYGON,
Area type=
Discrepancy in metres
1
2
3
2
1
1
TOWN CENTRE is registered for areas >= 2,500 m2 only.
Examples
PINK=TOWN CENTRE
BLUE=LOW BUILDING AREA
YELLOW=HIGH BUILDING AREA
FOT 4.0.1 20091022
3.2.1 BUILDING AREA-TOWN CENTRE
3.2.1.1
GREEN=TECHNICAL_AREA-Train station
GREY=COMMERCIAL AREA
FOT 4.0.1 20091022
3.2.1 BUILDING AREA-TOWN CENTRE
3.2.1.2
COMMERCIAL AREA
Object group
BUILDING AREA
Object type
COMMERCIAL AREA
Geometry type
Surface
Minimum size
2,500 m2
Area
1 2 3
Object definition
The limitation of an area with commercial buildings in the form of industry, trades, shopping centres or
industrial harbour areas.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
COMMERCIAL AREA is represented by the area's boundaries bordering up to another line- and/or
surface object. The height is at terrain level.
COMMERCIAL AREA delimits areas which are primarily built-up with factories, trade premises,
shopping centres and industrial harbour areas. The area contains all the buildings, technical facilities,
storage areas, grassed areas, parking areas and the like, which primarily belong to COMMERCIAL
AREAS.
COMMERCIAL AREA only appears for areas >= 2,500 m2
New mapping
COMMERCIAL AREA is registered based on the limitation of the building area, consisting of factories,
trade premises, shopping centres and industrial harbour areas. The area contains all the buildings,
technical facilities, storage areas, grassed areas, parking areas and the like, which primarily belong to
COMMERCIAL AREAS.
Within AREA TYPE POLYGON with AREA TYPE=3: The delimitation is made at ROAD CENTRE
LINE. Where this is not found, another BUILDING AREA object type, TECHNICAL AREA, ROAD
EDGE, FENCE, BOUNDARY LINE, HARBOUR or other object types are used, which form the border
of the surface's area. Where TECHNICAL AREA and one of the BUILDING AREA object types are
coterminous on each side of a ROAD CENTRE LINE, the BUILDING AREA object type is not
bounded by ROAD CENTRE LINE but it is extended in such a way that it is bounded by TECHNICAL
AREA.
Outside AREA TYPE POLYGON with AREA TYPE=3: The delimitation is made at ROAD EDGE.
Where this is not found, another BUILDING AREA object type, TECHNICAL AREA, FENCE,
BOUNDARY LINE, HARBOUR or other object types are used, which form the border of the surface's
area.
COMMERCIAL AREA is registered with as few points as possible. However, the difference between
the actual line and registered line must not exceed the following values in plan and height.
FOT 4.0.1 20091022
3.2.2 BUILDING AREA-COMMERCIAL AREA
3.2.2.1
AREA TYPE POLYGON,
Area type=
1
2
3
2
1
1
COMMERCIAL AREA is registered for areas >= 2,500 m2 only.
Areas which are clearly designated for building and which border COMMERCIAL AREAS or are totally
enclosed within, but not yet developed, are also COMMERCIAL AREAS.
Examples
BLACK=ROAD CENTRE LINE
YELLOW-surface=COMMERCIAL AREA
GREEN-surface=LOW BUILDING AREA
FOT 4.0.1 20091022
3.2.2 BUILDING AREA-COMMERCIAL AREA
3.2.2.2
LOW BUILDING AREA
Object group
BUILDING AREA
Object type
LOW BUILDING AREA
Geometry type
Surface
Minimum size
2,500 m2
Area
1 2 3
Object definition
Limitation of a building area with 1 and 2 storey buildings.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
LOW BUILDING is represented by the area's boundaries bordering up to another line- and/or surface
object. The height is at terrain level.
LOW BUILDING AREA delimits areas which are primarily developed with 1 and 2 storey buildings,
such as detached buildings, farms, terraced housing, housing estates, housing blocks, service industry,
schools or institutions.
These areas can contain playgrounds, gardens, lawns, vegetation, public areas and car parks, plus
backyards, tanks, silos, compost heaps, and areas for agricultural machinery, if the area is of permanent
character as well as gardens and parks linked to castles or manor houses.
LOW BUILDING AREA only appears for areas >= 2,500 m2
However, isolated farms can be registered as LOW BUILDING AREA if the developed area is > 500 m2.
New mapping
LOW BUILDING AREA is registered based on limitation of the building area, primarily developed with
1 and 2 storey buildings, such as detached buildings, farms, terraced housing, housing estates, housing
blocks, service industry, schools or institutions.
These areas can contain playgrounds, gardens, lawns, vegetation, public areas and car parks, plus
backyards, tanks, silos, compost heaps, and areas for agricultural machinery, if the area is of permanent
character as well as gardens and parks linked to castles or manor houses.
AREA.
FOT 4.0.1 20091022
3.2.3 BUILDING AREA-LOW BUILDING AREA
3.2.3.1
area.
LOW BUILDING AREA is registered with as few points as possible. However, the difference between
the actual line and registered line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
Area type=
1
2
3
2
1
1
LOW BUILDING AREA is registered for areas >= 2,500 m2 only.
However, isolated farms can be registered as LOW BUILDING AREA if the developed area is > 500 m2.
Areas which are clearly designated for building and which border LOW BUILDING AREAS or are
totally enclosed within, but not yet developed, are also LOW BUILDING AREAS.
Examples
RED-surface=HIGH BUILDING AREA
GREEN-dashed=FENCE
YELLOW-dashed=BOUNDARY LINE
YELLOW-surface=FOREST
FOT 4.0.1 20091022
3.2.3.2
FOT 4.0.1 20091022
3.2.3.3
FOT 4.0.1 20091022
3.2.3.4
HIGH BUILDING AREA
Object group
BUILDING AREA
Object type
HIGH BUILDING AREA
Geometry type
Surface
Minimum size
2,500 m2
Area
1 2 3
Object definition
The limitation of an area with buildings of two or more storeys.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
HIGH BUILDING AREA is represented the area's boundaries bordering up to another line- and/or
surface object. The height is registered at terrain level.
HIGH BUILDING AREA delimits an area primarily developed with buildings of two or more storeys,
such as housing blocks, apartment blocks, service industries schools or institutions.
The area can contain playgrounds, gardens, lawns, vegetation, public areas, car parks and backyards.
HIGH BUILDING AREA only appears for areas >= 2,500 m2
New mapping
HIGH BUILDING AREA is registered based on limitation of the building area, primarily developed
with buildings of more than two storeys, such as housing blocks, apartment blocks, service industries
schools or institutions.
The area can contain playgrounds, gardens, lawns, vegetation, public areas and car parks, plus
backyards.
AREA.
area.
FOT 4.0.1 20091022
3.2.4 BUILDING AREA-HIGH BUILDING AREA
3.2.4.1
HIGH BUILDING AREA is registered with as few points as possible. However, the difference between
the actual line and registered line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
Area type=
1
2
3
2
1
1
HIGH BUILDING AREA is registered for areas >= 2,500 m2 only.
Areas which are clearly designated for building and which border HIGH BUILDING AREA or are
totally enclosed within, but not yet developed, are also HIGH BUILDING AREA.
Examples
RED-surface=HIGH BUILDING AREA
FOT 4.0.1 20091022
3.2.4 BUILDING AREA-HIGH BUILDING AREA
3.2.4.2
3.3 TRAFFIC
ROAD CENTRE LINE
RAILWAY
ROAD EDGE
TRAFFIC ISLAND
SPEED BUMP
CRASH BARRIER
TRAIN HALT
FOT 4.0.1 20091022
3.3 TRAFFIC
3.3.1
ROAD CENTRE LINE
Object class
TRAFFIC
Object type
ROAD CENTRE LINE
Geometry type
Line
Min. size
1m
Area
1 2 3
Object definition
The centre of a way used for motorised, pedestrian, bicycle or mounted thoroughfare.
Primary attributes and references
Apart from the general attributes, the following special, primary attributes have been defined:
Name
Multiplicity
Type
Legal values
Change ResponsOrigin
triggers
ible
history
No
VM
Allocated by
KMS
photogrammetric or
administrative
registration.
No
VD
KOM
KMS
No
KOM
CPR road register
ROAD CENTRE TYPE
[1..1]
Text
Road
Path
Path link
ROAD AUTHORITY
[1..1]
Text
Not allocated
CPR MUNICIPALITY
[1..n]
Integer
100-999
CPR ROAD CODE
[0..n]
Integer
0001-9899
No
Always 4 digits precisely
KOM
CPR road register
ROAD CENTRE TYPE:
Type of ROAD CENTRE is described by one of the following values:
VALUE
MEANING
Road intended for ordinary motorised traffic.
Road
Paths intended for pedestrian, bicycle and/or mounted traffic.
Path
"Extra" road centre objects registered to ensure a logically related network
Path link
for planning travel by public transport.
If TRAIN HALT does not have a connection with a node in a ROAD
CENTRE, a PATH LINK will have to be registered to ensure the necessary
relationship between them.
PATH LINK is also used for registering "footpaths" where paths are not
usually perceived as such. E.g. passage between buildings, in tunnels, on
stairs, on platforms over squares and the like.
Such footpaths are registered to enable a "realistic" calculation of walking
distances and times.
These are often not visible in an aerial photo.
ROAD AUTHORITY:
The name of the authority responsible in accordance with the ”Lov om offentlige veje” or ”Lov om
private fællesveje”.
Links:
http://www.retsinfo.dk/_GETDOCI_/ACCN/A19990067129-REGL
http://www.retsinfo.dk/_GETDOCI_/ACCN/A19990067029-REGL
FOT 4.0.1 20091022
3.3.1 TRAFFIC-ROAD CENTRE LINE
3.3.1.1
CPR MUNICIPALITY:
All objects are allocated a value which corresponds to the number of the municipality in which they lie.
CPR ROAD CODE:
All objects representing a road or path registered in CPR’s road name register are allocated a number in
accordance with the register, ref. the Erhvervs- og Boligstyrelsen (Danish Enterprise and Construction
Authority) circular on addresses.
Secondary attributes
Name
Multiplicity
Type
ROAD CLASS
[1..1]
Text
TRAFFIC TYPE
[0..1]
Text
SURFACE
[1..1]
Text
ROAD WIDTH
[1..1]
Legal values
Local road
Driveway
Other road
Main path
Bicycle path alongside a road
Path, misc.
Not allocated
Motorway
Expressway
Path
Bus filter
Not allocated
Metalled
Unmetalled
triggers
ible
history
No
VM
Allocated by
KMS
photogrammetric
or administrative
registration.
No
KMS
Allocated when
entered
No
KMS
ROAD EDGE
attribute
SURFACE
No
KMS
Corresponds to
de facto
standard in TK
mapworks,
No
VM
Allocated when
entered
PLACE
[1..1]
0-3
3-4.5
4.5-6
6-7.5
7.5-9
9Unknown
Boolean 0
FICTIVE
[1..1]
Boolean 0
No
VM
ACCESS WAY
[1..1]
No
KMS
ROUNDABOUT
[1..1]
Boolean 0
1
Boolean 0
1
No
KMS
Text
ROAD CLASS:
Classification of ROAD CENTRE is described by one of the following values:
The value Local road can only be used if the sub-categories of local road, e.g. Local road-Primary are
not used.
VALUE
Local road
MEANING
Local roads are those which provide good accessibility for all
vehicle types. This means low speed restrictions for safety and
many junctions to increase accessibility.
Local roads or sub-divisions of local roads have a CPR ROAD
CODE and serve several addresses.
Driveway
Usually only serving a single address and not part of one of the
FOT 4.0.1 20091022
3.3.1.2
higher classes. Have the same CPR ROAD CODE as the road
they branch off.
Other road
Roads which are not covered by one of the higher classes. I.e.
small forest tracks, farm tracks and roads which do not serve as
access to separate addresses.
Do not have a CPR ROAD CODE.
Main path
Paths intended for pedestrian, cycling and/or mounted traffic.
Bike path alongside a road
Areas primarily for bicycle traffic alongside roads. Bicycle paths
are given the same CPR MUNICIPALITY and CPR ROAD
CODE as the road they run alongside.
Path, misc.
Internal path (laid-out path or path with lighting in the shape of
MAST) in a green area, park and access from road to building is
registered. Furthermore is registered similar significant path,
which makes the connection to Main path. Path, misc. is not
captured on housing estate plots.
Not allocated
Non-allocated road class.
Used during new registrations for all other ROAD CENTRE
LINES which do not fall under one of the other classes.
TRAFFIC TYPE
The value of TRAFFIC TYPE is allocated in accordance with the limitations in traffic types according to
the Road Traffic Act.
VALUE
MEANING
ROAD CENTRE LINE represents a motorway.
Motorway
Expressway
ROAD CENTRE LINE represents an expressway.
Path
ROAD CENTRE LINE represents a path (pedestrian, bicycle and mounted).
Bus filter
ROAD CENTRE LINE represents a road for buses only.
Not allocated
Non-allocated traffic class.
SURFACE
VALUE
Metalled
Unmetalled
MEANING
Metalled, i.e. the surface is covered with a hard material in the form of asphalt,
concrete, paving stones, slabs or the like.
Unmetalled, i.e. the surface is gravel, sand, earth or the like.
ROAD WIDTH
VALUE
MEANING
Range for traffic area's estimated width
0-3
FOT 4.0.1 20091022
3.3.1.3
3-4.5
4.5-6
6-7.5
7.5-9
9-
Unknown
Unknown road width.
PLACE
VALUE
0
MEANING
ROAD CENTRE LINE is NOT a place.
FICTIVE
VALUE
0
MEANING
ROAD CENTRE LINE is real.
ACCESS WAY
VALUE
MEANING
ROAD CENTRE LINE is NOT an ACCESS WAY.
0
1
ROAD CENTRE LINE is an ACCESS WAY.
An ACCESS WAY is a road intended for one-way access to/from between two
ROAD CENTRE LINES with ROAD CENTRE TYPE=Road. Occurs only where
motorways and expressways merge with another smaller road. Only ACCESS
WAYs with a length of > 50 metres are included.
ROUNDABOUT
VALUE
MEANING
ROAD CENTRE LINE is NOT part of a roundabout.
0
1
ROAD CENTRE LINE is part of a roundabout.
Representation
The estimated centre of permanent roads and paths. Height measured at ground level.
ROAD CENTRE LINE usually lies within the limitations of the road in the form of ROAD EDGE or
other objects on the map.
ROAD CENTRE LINE runs continuously under/over bridges, through tunnels, through buildings and the
like where the road or path runs.
FOT 4.0.1 20091022
3.3.1.4
ROAD CENTRE LINE objects run from node point to node point.
New mapping
ROAD CENTRE LINE is registered at ground level as the estimated centre between the road area's
longitudinal delimitation lines.
ROAD CENTRE LINE is registered with as few points as possible, so that the difference between the
actual route and the registered route is < 2 metres in plan and 1 metre in height at any point.
ROAD CENTRE LINE objects with a length of < 1 metre are not captured.
As a rule, all ROAD CENTRE LINES of a permanent character are captured.
Object types ROAD CENTRE LINE and ROAD EDGE work in such a way that the values for ROAD
CENTRE LINE Road Class and ROAD EDGE-Type influence each other, as can be seen in the table
below:
ROAD CENTRE LINE
ROAD EDGE
Road class
Type
Local road
Thoroughfare
Driveway
Driveway
Other road
Other road
Internal road
Road, misc.
Main path
Main path or Bicycle Path
Bicycle path alongside a road
Bicycle path
Path, misc.
Path, misc.
Not allocated for both object types has no influence on the other object type's attribute values.
Definitions:
Central reservation
A physical longitudinal division of a road in which the reservation
separates the traffic allowing it to run in both directions. The actual
reservation can be covered with grass, gravel, asphalt or slabs.
If the reservation is longer than > 300 metres, each lane is regarded as an
independent road. Central reservations that have breaks, e.g. for
pedestrian crossings, are treated as one continuous reservation.
Traffic island
A physical division of a road that directs traffic around the obstacle. The
actual island can be covered with grass, gravel, asphalt or slabs.
Traffic island that have breaks, e.g. for pedestrian crossings, are treated
as one continuous island.
ROAD CENTRE LINE is registered through an island as if it was not
there.
Road loop
A road principally intended for motorised traffic around a physical
obstacle (an inner area) intended to direct the traffic along the diversion
to avoid the obstacle.
FOT 4.0.1 20091022
3.3.1.5
Where a Road loop has a length of > 100 metres or an area of > 100 m2,
the road is considered to be in two lanes, each of which are treated
independently. ROAD CENTRE LINE is registered around a road loop
outside its inner area.
If the area is < 100 m2 the ROAD CENTRE LINES is registered through
the loop.
Roundabout
A crossroads with an area principally intended for motorised traffic
around a central physical obstacle (an inner area) intended to direct the
traffic around the roundabout to avoid the obstacle.
The road is comprised of lanes in a continuous circular course.
Each lane is regarded as an independent road, regardless of the size of
the inner area.
Road closure
A permanent obstruction for vehicles across a road area or at the end of a
road. Can be curb stones, an earth bank, posts, boulders, flower boxes,
railings, steps etc. permitting passage for pedestrians, cyclists or
mounted traffic.
This is not a traffic restriction indicated by signs or in the form of
booms, gates or chains across the carriageway.
Passage through a road closure is registered as ROAD CENTRE LINE
with ROAD CENTRE TYPE=Path.
Road Path
Path
link
x
Nature
A road area of permanent character mainly used for motorised, bicycle or
mounted traffic.
x
A road area of permanent character mainly used for pedestrian, bicycle or
mounted traffic.
x
A road area of permanent character reserved for pedestrian, bicycle or
mounted traffic, running through a tunnel or building, e.g. a station, over a
square or place, on platform steps and along a platform. In an aerial photo,
this area may be difficult or impossible to identify.
The logical network link between ROAD CENTRE LINE objects internally
and between ROAD CENTRE LINE and RAILWAY.
x
x
x
Where ROAD CENTRE LINE runs over or under a bridge, or in a tunnel, its
course is estimated accordingly.
x
x
x
Riding tracks on open fields are not registered.
FOT 4.0.1 20091022
3.3.1.6
x
x
x
Places and squares are not registered.
x
Only continuous and clearly defined ROAD CENTRE LINES are registered
in harbour areas. ACCESS WAY to ferry docks are show in such a way that
the estimated ROAD CENTRE LINE runs through the assembly area and is
snapped 3D to HARBOUR in the middle of the dock.
x
The course of ROAD CENTRE LINE changes for crawler lanes, passing
bays, bus stop bays, turning bays, speed restriction measures and the like
along roads if a deviation from the normal route continues > 300 metres.
x
Where ROAD CENTRE LINE leads into a courtyard, the endpoint will be in
the centre of the courtyard.
x
Where ROAD CENTRE LINE runs through a courtyard, the line will also
continue through the courtyard.
x
ROAD CENTRE LINE are registered in all parking spaces with a metalled
covering and at gravel covering parking space with a surface >2.500 m2. The
road class depends on the local conditions but will typical be Local roadxx
or Other road.
x
ROAD CENTRE LINE-Driveway (which only serves one address) must
have a length of > 20 metres to be registered.
ROAD CENTRE LINE-Driveways are never registered within a TOWN
POLYGON internally on housing estates or in a cul-de-sac.
ROAD CENTRE LINE-Local road (with or without sub-division) which
serve more than one address must have a length of > 20 metres and
preferably lie in a cul-de-sac if it serves more than one address.
(See illustrations below table).
x
x
At the end of a road area, snap is made to an object which represents the
end, e.g. ROAD EDGE, BUILDING AREA, BUILDING, FOREST,
FENCE, BOUNDARY LINE etc.
x
x
ROAD CENTRE LINE along a road is only registered if it has its own route.
x
x
Where two or more paths run in parallel and are divided by a central
reservation, two ROAD CENTRE LINEs are registered. If there is no
division, only one ROAD CENTRE LINE is registered.
x
Main path routes are registered internally in churchyards if they link roads,
buildings, monuments and exits to and from the churchyard.
x
Footbridges over roads or railways incl. steps which do not lead to a
platform.
x
FOT 4.0.1 20091022
ROAD CENTRE LINE registered on the basis of source material from
traffic operators and others. When selecting a ROAD CENTRE LINE for
3.3.1.7
registration, allowance must be made for the significance of the object for
the logical network relationship. I.e. if an object has a significant, regarding
accessibility from one point to another, e.g. over a square or place.
x
ROAD CENTRE LINES which are internal on industrial sites is registered
for a road which is access road leading from a public road to an address
point while the length is of > 20 metres.
x
Dead-end farm and forest tracks with Road class =Local roadxx or Other
road are registered if:
the object has a length of > 50 metres and
leads to a FOT object (e.g. LAKE, FOREST, STREAM CENTRE
LINE, WIND TURBINE etc.).
x
Dead-end farm and forest tracks with Road class =Local roadxxor Other
road are registered if:
the object has a length of > 300 metres and
is deemed to be permanent and
can be used by ordinary vehicles.
ROAD WIDTH
During new mapping the ROAD WIDTH is determined from the existing TK data set. Where no TK da
ta is available or the TK data does not state a width: Unknown is used.
CPR ROAD CODE
During new mapping the CPR ROAD CODE is determined from the existing TK and TOP10DK data
sets. Where there are discrepancies in material supplied which cannot be resolved by the supplier, the
latter should contact the client. (value range 0001-9899)
Examples
ROAD CENTRE LINE in a crossroad
ORANGE=ROAD CENTRE LINE-Road
PINK=ROAD CENTRELINE-Path
FOT 4.0.1 20091022
3.3.1.8
PATH LINK and nodes.
FOT 4.0.1 20091022
3.3.1.9
Path link is used to form the topological links to show where passengers can walk, for public transport
users in particular.
LIGHT BLUE-line=ROAD CENTRE LINE-Path link
BLACK-line=ROAD CENTRE LINE-Road
GREEN-line=ROAD CENTRE LINE-Path
RED-line=RAILWAY
BLACK-circle=node
RED-circle=TRAIN HALT and node
A bridge is shown here linking another road via steps or paths. A bus bay can be clearly seen that a "Path
link" snaps to and breaks with ROAD CENTRE LINE-Road (black) and ROAD CENTRE LINE-Path
(green)
FOT 4.0.1 20091022
3.3.1.10
ROAD CENTRE LINE-Local road, ROAD CENTRE LINE-Main path and ROAD CENTRE
LINE-Path, miscellaneous
BLUE=ROAD CENTRE LINE-Road-Local road
RED=ROAD CENTRE LINE-Path-Main path
GREEN=ROAD CENTRE LINE-Path-Path, miscellaneous
FOT 4.0.1 20091022
3.3.1.11
Internal ROAD CENTRE LINE in industrial estates
FOT 4.0.1 20091022
3.3.1.12
The capture of ROAD CENTRE LINE-Access road and ROAD CENTRE LINE-Local road:
A ROAD CENTRE LINE (in the green oval) leads to two addresses, and is therefore a Local road. As
the road is > 20 metres, it is captured as shown with object type=ROAD CENTRE LINE and with Road
class=Local road.
A ROAD CENTRE LINE (in the green oval) here leads to only one address, and is therefore an Access
road. As the road is > 20 metres, it has object type=ROAD CENTRE LINE with road class=Driveway.
However, the road is not captured, because ROAD CENTRE LINE-Driveway is not captured internally
in housing estate plots or cul-de-sacs.
FOT 4.0.1 20091022
3.3.1.13
ROAD CENTRE LINE-Path close to another ROAD CENTRE LINE
RED=ROAD CENTRE LINE-Path
BLUE=ROAD CENTRE LINE-Road
BLACK=node
FOT 4.0.1 20091022
3.3.1.14
BLACK=ROAD EDGE-Road
RED=ROAD EDGE-Path
GREEN=ROAD CENTRE LINE-Road
BLUE=ROAD CENTRE LINE-Path
BLACK-circle=node
ROAD CENTRE LINE and double paths.
PINK=ROAD EDGE-Path
Where a double path is divided by a central reservation, a double ROAD EDGE-Path and double ROAD
CENTRE LINE>-Path are captured.
FOT 4.0.1 20091022
3.3.1.15
But not in the next two situations, as the paths are not divided by a central reservation.
FOT 4.0.1 20091022
3.3.1.16
RED=RUNWAY-Takeoff_Landing
GREEN=RUNWAY-Taxi Runway
BLUE=RUNWAY-Place
ORANGE=ROAD CENTRE LINE
FOT 4.0.1 20091022
3.3.1.17
RAILWAY
Object group
TRAFFIC
Object type
RAILWAY
Geometry type
Line
Min. size
1 m.
Area
1 2 3
Object definition
A centre line between a set of rails for rail-borne traffic.
Apart from the general attributes, the following special, primary attributes have been defined:
Name
Multiplicity
Type
TRACK TYPE
[1..1]
Text
OWNER_RAILWAY
[1..1]
Text
Legal values
Main track
Continuous track
Other two-way tracks
Siding
"Owner name"
triggers
ible
history
No
KMS
Explicitly stated
BDK
when
administratively
registered.
No
KMS
Explicitly stated by
BDK
Trafikstyrelsen
(Public Transport
Authority) when
administratively
entered.
TRACK TYPE
Track type can indicate one of the following values:
VALUE
MEANING
Railway track outside station areas
Main track
Railway track for through traffic in station areas
Continuous track
Other railway tracks for rail traffic within station areas
Other two-way tracks
Other railway tracks
Siding
OWNER_RAILWAY
The owner of the railway the object represents.
Name
Multiplicity
LEVEL_RAILWAY
[0..1]
VISIBLE_RAILWAY
[1..1]
LEVEL_RAILWAY
VALUE
Bridge
FOT 4.0.1 20091022
Type
Legal values
Text
Bridge
Tunnel
Boolean 0
1
triggers
ible
history
No
KOM
LEVEL from
TOP10DK
No
KOM
KMS
MEANING
RAILWAY lies on a bridge.
A bridge is a link over land and/or water. The link consists of a bridge
deck, e.g. of concrete, supported by pillars and/or suspended from
cables. A bridge transfers a RAILWAY. BRIDGE starts and stops at
the ends of the estimated span of the bridge deck. BRIDGE has
3.3.2 TRAFFIC-RAILWAY
3.3.2.1
Tunnel
VISIBLE_RAILWAY
VALUE
0
1
common geometry with the relevant RAILWAY on the bridge. Only
BRIDGEs with a length of > 100 metres are included.
RAILWAY lies in a tunnel.
A tunnel is an underpass under land and/or water. There is an entrance
at both ends between which the tunnel is covered by soil and/or water.
A tunnel carries a RAILWAY underground. TUNNEL starts and stops
at the ends of the underpass itself (entrances). TUNNEL has common
geometry with the relevant RAILWAY in the tunnel. Only TUNNELs
with a length of > 200 metres are included.
MEANING
RAILWAY cannot be identified photogrammetrically as it runs
beneath buildings, bridge or lies in a tunnel.
RAILWAY can only be identified photogrammetrically.
Representation
The estimated centre of a pair of rails which bear rail traffic.
A RAILWAY's course is estimated under bridges, through tunnels, under buildings etc.
RAILWAY objects run from node point to node point.
New mapping
RAILWAY is captured at ground level as a line estimated in the centre of the 2 rails which comprise a
set of rails in a longitudinal direction.
RAILWAY is captured with as few points as possible, although such that the difference between the
actual route and the captured route is <1 metre in both plan and height at any point.
RAILWAY 3D snaps to HARBOUR at ferry ports in the centre of the ferry dock.
An undefined Z is given for RAILWAY in a tunnel unless height details are available from
Banestyrelsen (Rail Net Denmark).
Data from Banedanmark as described under upgrading is used as basic info.
Examples
YELLOW=TECHNICAL_AREA-Train station/sidings
BLUE=RAILWAY-Main track
RED=RAILWAY-Continuous track
GREEN=RAILWAY-Other train track
PINK=RAILWAY-Sidings
FOT 4.0.1 20091022
3.3.2.2
FOT 4.0.1 20091022
3.3.2.3
ROAD EDGE
Object group
TRAFFIC
Object type
ROAD EDGE
Geometry type
Line
Min. size
-
Area
1 2 3
Object definition
Delimitation of a way used for motorised, pedestrian, cycling or mounted thoroughfare.
Name
Multiplicity
TYPE
[1..1]
SURFACE_ROAD EDGE
[1..1]
VISIBLE_ROAD EDGE
[1..1]
Type
Legal values
Text
Thoroughfare
Driveway
Internal road
Other road
Road, misc.
Bicycle path
Main path
Path, misc.
Text
Metalled
Unmetalled
Boolean 1
triggers
ible
history
No
Road
TK99
authority
No
No
Road
TK99
authority
KOM
TK99 + road
authority
TYPE
Definition of road edge type. Type should be the same for the two edges which define the road's width.
VALUE
MEANING
Thoroughfare
The area of a road, bridge, path or place deemed to be open to general traffic
and access road to more than one property.
The edge of a road which is the access road to a single address.
A road area within a property.
Very small roads which do not serve addresses, e.g. farm or forest tracks.
Supplementary delimitations for roads.
A road area used by bicycles. Borders up to Road/internal road.
A road area in the form of a continuous path, including general paths which
serve as distribution networks for smaller side paths.
Internal, small paths.
Driveway
Internal road
Other road
Road, misc.
Bicycle path
Main path
Path, misc.
SURFACE_ROAD EDGE
Definition of the surface of road's surface:
VALUE
MEANING
Metalled
Metalled, i.e. the surface is covered with a hard material in the form of asphalt,
concrete, paving stones, slabs etc.
Unmetalled, i.e. the surface is gravel, sand, earth etc.
Unmetalled
VISIBLE_ROAD EDGE
Definition of visibility from the air.
VALUE
MEANING
FOT 4.0.1 20091022
3.3.4 TRAFFIC-ROAD EDGE
3.3.4.1
1
Visible from the air.
Representation
Delimitation of road areas road, place and path in the form of surface edge, curb stone, gravel etc. Height
at ground level.
New mapping
Captured on the line of limitation in the form of surface edge, curb stone, gravel etc. Height at ground
level.
ROAD EDGE is registered within all AREA POLYGONs regardless of value of AREA TYPE. Within
AREA POLYGON with AREA TYPE=1 however, ROAD EDGE is only captured as follows:
ROAD EDGE along roads according to the following rules:
1. TYPE=Thoroughfare
2. SURFACE_ROAD EDGE=Metalled or Unmetalled
3. ROAD CENTRE LINE for the road has a CPR CODE
4. ROAD CENTRE LINE for the road has a ROAD CENTRE TYPE=Road
5. ROAD CENTRE LINE for the road has a value for ROAD CLASS= Local road or a higherranking class
6. A new road (=road not yet on the map) will also be captured if it is deemed to fulfil the
aforementioned criteria according to its size and relationship to other roads
Plus ROAD EDGE along main paths according to the following rules:
1. TYPE=Main path
2. SURFACE_ROAD EDGE=Metalled
3. ROAD CENTRE LINE for the road has a ROAD CENTRE TYPE=Path
Registered as an unbroken continuous line despite being concealed in places due to gravel on roadsides
and curves for driveways etc.
ROAD EDGE falls within the areas and is prioritised in relation to other TRAFFIC-objects as follows:
OBJECT TYPE
TYPE
SURFACE
VISIBLE
ROAD EDGE
ROAD EDGE
PARKING
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
ROAD EDGE
Thoroughfare
Thoroughfare
Metalled
Unmetalled
Visible
Visible
Driveway
Driveway
Internal road
Internal road
Bike path
Main path
Main path
Other road
Road, misc.
Path, misc.
All types
Metalled
Unmetalled
Metalled
Unmetalled
Metalled
Metalled
Unmetalled
All surfaces
All surfaces
All surfaces
All surfaces
Visible
Visible
Visible
Visible
Visible
Visible
Visible
Visible
Visible
Visible
Invisible
FOT 4.0.1 20091022
AREA
1 2 3
1 2 3
2 3
2 3
2 3
2 3
2 3
3
1 2 3
2 3
3
3
3
2 3
3.3.4.2
Registration rules:
A When roads, car parks and paths in the above priority order adjoin each other or cross each
other, the main rule applies that - the highest prioritised object will continue unbroken. I.e.
that objects from the highest-prioritised object are captured continuously without break.
Similarly, lower-prioritised objects stop when they join a higher-prioritised object.
However, CAR PARK and ROAD EDGE-Thoroughfare are prioritised equally when their
surface metalling is the same.
See also rule C.
B Where equally prioritised objects adjoin, they are captured on the physical edge.
C A higher-prioritised object is not registered through, if:
an adjoining object to a higher-prioritised object has the same value for
SURFACE_ROAD EDGE
and that it is not a physical edge.
The aim is that for cartographic reasons e.g. adjoining asphalted roads can appear as unbroken
and related.
D A lower-prioritised object is also registered through, if:
An object with SURFACE_ROAD EDGE=Metalled runs over an object in plan with
SURFACE_ROAD EDGE=Unmetalled
The unmetalled object has a higher priority than the metalled one
The delimiting lines of the two roads/paths will thus cross each other.
The aim is to show prominent surface differences, e.g. where an asphalted bicycle path passes
an unmetalled road. In this instance, the unmetalled road and the metalled bicycle path will be
captured through.
E An adjoining road/path will always continue right out to the highest-prioritised road/path,
including any corner curve, i.e. right out to the tangential point.
F ROAD EDGE capture is not performed photogrammetrically under other objects, e.g. when
passing under bridges, in tunnels, under hedges, under roof overhangs or similar locations
invisible from the air. Roads/paths occurring such locations can be registered administratively
with the attribute VISIBLE_ROAD EDGE=0
The following applies to objects with
TYPE= Thoroughfare and SURFACE_ROAD EDGE=Metalled:
ROAD EDGE is registered at the surface edge, i.e. typically the curb stone in urban areas and asphalt
edge in rural areas. Painted carriageway edges are not used for delimitation.
Bus bays, car parks, bicycle paths and emergency lanes are included in the road area providing they
alone are delimited from the carriageway by painted road stripes.
FOT 4.0.1 20091022
3.3.4.3
TRAFFIC ISLAND with a length of > 100 metres, central reservation and inner circle in a roundabout is
captured.
Short central reservation can however also be captured as ROAD EDGE if they as a whole include other
central reservations in the road. Dedicated pedestrian TRAFFIC ISLAND in crossroads will however
always be TRAFFIC ISLAND.
If bicycle/pedestrian paths cross "through" a central reservation, the objects will be captured along the
bicycle/pedestrian path edges.
If bicycle/pedestrian paths cross "over" a central reservation, the object is captured without a break.
Where there are speed BUMPS, the object is always captured as an unbroken line through the road's
envisaged or actual extension beyond the bump.
A line can be captured without any visible delimitation in the field. This applies for example in the
following situations:
Where an adjoining road is registered over a pavement/bicycle path to close a larger road.
Where a road area is closed over a bicycle path or at the end of the same
Where a road area is closed over a surfaced crossing (on a main road)
Where a central reservation is broken by a pedestrian crossing/bicycle path.
Gaps for emergency vehicle access in the central reservation of a motorway are registered as part of the
carriageway edge.
Surfaced access roads with a length of > 20 metres leading to CAR PARK.
Car park bays running alongside a road are not CAR PARKS, but ROAD EDGE.
TYPE= Thoroughfare and SURFACE_ROAD EDGE=Unmetalled:
ROAD EDGEs with these attributes are usually used to capture:
Gravel roads in summerhouse areas
Farm tracks serving as access roads to more than one property
Farm tracks serving as link roads between farms or public roads
Unmetalled access roads with a length of > 20 metres leading to CAR PARK.
Unmetalled FOREST roads are not captured as TYPE=Thoroughfare.
TYPE=Driveway
ROAD EDGE is captured on the extreme surface edge on metalled or unmetalled roads deemed to serve
as the access road to a single property.
For farm properties, the primary access road is captured as ROAD EDGE with TYPE=Driveway to the
farmyard/buildings. The primary access road is that which links the property with the road to which its
address belongs.
Only roads with a length of > 20 metres are included.
FOT 4.0.1 20091022
3.3.4.4
TYPE= Internal road and SURFACE_ROAD EDGE=Metalled:
ROAD EDGE is captured at the extreme surface edge on metalled roads which are an internal road on a
property.
The following occurrences are captured:
Roads with a length > 20 metres in internal areas with housing blocks, institutions, industrial
estates, airports, farms, churchyards etc.
Places reserved for public transport.
Metalled roads in allotment garden areas
Internal on industrial sites.only internal roads which fulfil the following conditions can be
captured:
access roads to/from public roads
car parking for employees and guests
large, clearly marked roads for internal transport within the site
not storage areas for materials etc.
But not:
Access roads with a length of < 20 metres to a car park. These are included in CAR PARK.
Roads to housing estate plots in urban areas.
Roads in allotment garden areas where the metalled area of the road coincides with FENCE.
TYPE= Internal road and SURFACE_ROAD EDGE=Unmetalled:
ROAD EDGE is captured at the extreme surface edge on unmetalled roads which are an internal road on
a property.
Captured only if they are of a permanent character. Dirt roads on building sites are therefore not
captured.
ROAD EDGE is captured at:
Unmetalled roads with a length of > 20 metres on internal areas, e.g. farms, parks, churchyards,
allotment garden areas and industrial estates.
Internal on industrial sites.only internal roads which fulfil the following conditions can be
captured:
access roads to/from public roads
car parking for employees and guests
large, clearly marked roads for internal transport within the site
not storage areas for materials etc.
But not:
Access roads with a length of < 20 metres to a car park. These are registered as CAR PARK.
Roads on housing estates.
Roads in allotment garden areas where the road edge coincides with FENCE.
Farm and forest tracks
TYPE= Other road:
FOT 4.0.1 20091022
3.3.4.5
ROAD EDGE is registered at the extreme surface edge on metalled or unmetalled roads which comprise
very small permanent roads, e.g. farm and forest tracks or the like, which are not the only access road to
an address.
Only roads with a length of > 20 metres are captured.
Dead end roads with a length of > 300 metres and roads with a length of > 50 metres which lead to
another FOT object.
For farm properties, the primary access road is registered as ROAD EDGE with TYPE=Driveway to the
farmyard/buildings. The primary access road is that which links the property with the road to which its
address belongs.
Road running further on a property or other access road is captured as Other road.
Tractor tracks or other wheel tracks which can only be used for seasonal work a few times a year are not
captured.
TYPE= Bicycle path and SURFACE_ROAD EDGE=Metyalled:
ROAD EDGE TYPE= Bicycle pathcan not have SURFACE_ROAD EDGE=Unmetalled.
ROAD EDGE is registered for metalled bicycle paths along roads.
Only bicycle paths/verges and bicycle paths/pavements are registered as this object.
The carriageway/bicycle path edge is captured as TYPE=Carriageway or TYPE =Internal road, as
CARRIAGEWAY and INTERNAL ROAD have higher priority. Most bicycle paths in urban areas will
thus be registered by a single line, unless there is a dividing reservation between the carriageway and
bicycle path.
BICYCLE PATHS are not captured if they are solely delimited by painted stripes.
BICYCLE PATHS only run over side roads if there is a surface change or there is a physical bicycle path
edge.
TYPE=Main path:
ROAD EDGE is registered in the form of a continuous path within its own route, including general paths
which serve as distribution networks for smaller side paths.
ROAD EDGE is registered at the extreme edge lines of multifunctional paths.
Where a path is divided by a central reservation, the edges of the reservation are also captured.
ROAD EDGE is always captured by 2 lines, unless one or both sides are replaced by ROAD EDGE of
TYPE=Carriageway.
Internal paths in green areas, parks and the like are captured as Paths, misc.
FOT 4.0.1 20091022
3.3.4.6
They are captured unbroken over objects with TYPE= Path, misc., regardless of whether there are
visible edges or not.
Paths running from a car park, turning area or a cut-through to the surrounding or adjacent building area
are not Main paths, but Paths, misc.
Paths running in and out of CHURCHYARDS and large paths in very large churchyards are Main
paths. Paths around individual graves within a CHURCHYARD are not captured.
Where there is doubt whether a path should be captured as Bicycle path or Main path, it will help to
determine which TYPE is to be considered.
If one criterion has not resolved the doubt, move on to the next criterion:
1. The rest of the path
Click on the rest of the path.
The same object type as the general line is used where only a short stretch of the path deviates from the
path's general line, If the deviation is sustained, the path is given another object type, starting at the point
where the deviation starts.
2. One-way
Main path are normally two-way, whilst Bicycle path are one-way.
3. Route line
Main path usually have is own independent route, whilst Bicycle path usually follow the same route as
a road.
Path running over or under a road will often be Main path.
4. Distance to carriageway
Main path does not run alongside a road, whilst Cycle paths can run alongside a road with up to a 2
metres distance from the roadside.
Main path will normally also be used as bicycle path.
TYPE= Road, misc.:
Supplementary lines in connection with road structures and places such as pavements and field access
crossings are captured for ROAD EDGE with TYPE=Road, misc.
In areas between buildings/fences and the carriageway, a single line is captured when: (see next figure)
FOT 4.0.1 20091022
3.3.4.7
Where there are 2 or more pavement lines to choose from, only that furthest away from the carriageway
is captured.
TYPE= Path misc.:
Internal path (laid-out path or path with lighting in the shape of MAST) in a green area, park and access
from road to building is registered. Furthermore is registered similar significant path, which makes the
connection to Main path. Path, misc. is not captured on housing estate plots.
Paths in and out of green areas, parks and the like are not Path, misc. but Main path.
Objects closer to FENCE than 1 metre are not captured.
Paths with a width < 1 metre not captured withROAD EDGE.
Relationship between ROAD EDGE and ROAD CENTRE LINE
Object types ROAD CENTRE LINE and ROAD EDGE work together such that the values for ROAD
CENTRE LINE-Road class and ROAD EDGE-Type influence each other when they both occur in areas
that can be seen in the table below:
ROAD CENTRE LINE
ROAD EDGE
Road class
Through road
Road-Branch
Local road
Local road-Primary
Local road-Secondary
Local road-Tertiary
Driveway
Other road
Type
Thoroughfare
Thoroughfare
Thoroughfare
Thoroughfare
Thoroughfare
Thoroughfare
Driveway
Other road
Internal road
Road, misc.
Main path
Main path or Bicycle Path
Bicycle path along road
Bicycle path
Path, misc.
Path, misc.
Not allocated for both object types has no influence on the other object type's attribute values.
Examples
ROAD EDGE and double paths.
Where a double path is divided by a central reservation, a double ROAD EDGE-Path and double ROAD
CENTRE LINE-Path are made.
FOT 4.0.1 20091022
3.3.4.8
BLACK=ROAD EDGE-Main path
LIGHT BLUE=ROAD CENTRE LINE-Path
FOT 4.0.1 20091022
3.3.4.9
But not in the next two situations, as the paths are not divided by a central reservation.
FOT 4.0.1 20091022
3.3.4.10
BLACK=ROAD EDGE-Thoroughfare
RED=ROAD EDGE-Main path
LIGHT BLUE=ROAD EDGE-Path, misc.
PINK=CAR PARK and TRAFFIC ISLAND
YELLOW=ROAD EDGE-Bicycle path
GREEN=Boundary line
Where there is a physical edge, ROAD EDGE is captured on it.
FOT 4.0.1 20091022
3.3.4.11
GREEN=CHURCHYARD
ORANGE= ROAD CENTRE LINE -Road-Local road
LIGHT BLUE=ROAD CENTRE LINE-Path-Main path
PINK=CAR PARK
FOT 4.0.1 20091022
3.3.4.12
LIGHT BLUE=ROAD EDGE-Path, misc.
PINK=CAR PARK
FOT 4.0.1 20091022
3.3.4.13
FOT 4.0.1 20091022
3.3.4.14
TRAFFIC ISLAND
Object group
TRAFFIC
Object type
TRAFFIC ISLAND
Geometry type
Line
Min. size
-
Area
3
Object definition
Delimitation of an area free from moving traffic.
Name
Multiplicity
Type
Legal values
Change Responstriggers
ible
history
Origin
Representation
The outline of traffic ISLANDS at junctions, pedestrian crossings and the like.
Height at ground level.
New mapping
Captured on the objects boundaries. Height at ground level.
TRAFFIC ISLAND is only captured if there is a different type of surface or physical edge.
They are only captured on roads delimited by a ROAD EDGE.
If there are bicycle paths/pedestrian crossings running across traffic ISLANDS, several TRAFFIC
ISLANDS will be captured.
If there are bicycle paths/pedestrian crossings running across a traffic island, one TRAFFIC ISLAND
will be registered.
The inner circles of roundabouts are registered as ROAD EDGE or SPEED BUMP.
TRAFFIC ISLAND has 4-wheeled moving vehicles on both sides.
If 2-wheeled vehicles have passage on one side of a traffic island, then this will be captured as SPEED
BUMP not as TRAFFIC ISLAND.
TRAFFIC ISLAND with a length of > 100 metres is not captured as TRAFFIC ISLAND, but as ROAD
EDGE.
However, where there is a stretch where traffic separation switches between TRAFFIC ISLAND and
ROAD EDGE, the same object type should be selected to maintain a homogenous description for the
road.
FOT 4.0.1 20091022
3.3.5 TRAFFIC-TRAFFIC ISLAND
3.3.5.1
INCORRECT
Where the same occurrence in nature continuously
switches object type only due to a very small difference
in length.
CORRECT
Note the small TRAFFIC ISLAND at the top of the
photo. This is still a TRAFFIC ISLAND, as it is not
deemed to be part of the alternation between ROAD
CENTRE LINE and TRAFFIC ISLAND.
Examples
PURPLE=TRAFFIC ISLAND
LIGHT BLUE=ROAD EDGE-Main path
FOT 4.0.1 20091022
3.3.5.2
FOT 4.0.1 20091022
3.3.5.3
SPEED BUMP
Object group
TRAFFIC
Object type
SPEED BUMP
Geometry type
Line
Min. size
-
Area
3
Object definition
Delimitation of speed-reducing installations for moving traffic.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
The outline of speed-reducing installations lying wholly or partially within the road's delimitation lines.
Height at ground level.
New mapping
The outline of speed-reducing installations lying wholly or partially within the road's delimitation lines
in the form of ROAD EDGE. Height at ground level.
All captured as individual parts of traffic-calming measures, e.g. flower boxes, flower beds, chicanes,
bus bays "town gates", road level bumps and ramps etc.
Captured at road edge, delimitation of "BUMPS" or the like which delimit the road area.
Inner circle of roundabouts, which are solely marked by a change in the surface are captured as SPEED
BUMP.
Where there are SPEED BUMPS, ROAD EDGE is always captured unbroken as a continuation of the
road's envisaged or actual extension beyond the bump.
SPEED BUMP is not captured for paving stones/slabs placed at the ‘mouth’ of roads or barriers that
prevent cars from driving onto paths.
Installation which solely consist of acoustic or visual warnings (painted road surface) is not SPEED
BUMP.
Not captured internally in industrial estates.
Examples
PINK-STIPPLED LINE=SPEED BUMP
BLACK=ROAD EDGE
BLACK-STIPPLED LINE=ROAD CENTRE LINE
FOT 4.0.1 20091022
3.3.6 TRAFFIC-SPEED BUMP
3.3.6.1
FOT 4.0.1 20091022
3.3.6 TRAFFIC-SPEED BUMP
3.3.6.2
CRASH BARRIER
Object group
TRAFFIC
Object type
CRASH BARRIER
Geometry type
Line
Min. size
-
Area
3
Object definition
BARRIERS to prevent traffic accidents.
Name
Multiplicity
BARRIER TYPE
[1..1]
Type
Text
Legal values
Steel
Concrete
Cable
Wire mesh
ible
history
No
Road
authority
Origin
BARRIERTYPE
is shown using one of the following values:
VALUE
MEANING
Steel
BARRIERS in the form of horizontal steel beams.
Concrete
BARRIERS in the form of horizontally laid concrete beams.
Cable
Heavy duty cable barrier in the form of horizontally-tensioned steel wires.
Wire mesh
Steel wire mesh.
Representation
Crash barrier or wire barrier on roads.
New mapping
Crash BARRIERS are captured at the front edge of the actual barrier facing the road. Height captured on
the top of the object.
Wire BARRIERS are captured at the middle. Height captured on the top of the object.
Wire BARRIERS are defined as BARRIERS installed in the central reservation or alongside a road to
prevent pedestrians crossing.
Wire mesh fences for the retention of animals are captured as FENCES.
Examples
RED=CRASH BARRIER
BLACK=ROAD CENTRE LINE-Road
LIGHT BLUE=ROAD CENTRE LINE-Path
FOT 4.0.1 20091022
3.3.7 TRAFFIC-CRASH BARRIER
3.3.7.1
FOT 4.0.1 20091022
3.3.7 TRAFFIC-CRASH BARRIER
3.3.7.2
TRAIN HALT
Object group
TRAFFIC
Object type
TRAIN HALT
Geometry type
Point
Min. size
-
Area
1 2 3
Object definition
A place where passengers board and alight from rail passenger transport.
Name
Multiplicity
Type
NAME
[1:1]
Text
OWNER-TRAIN HALT
[1:1]
Text
Legal values
ible
history
Name of station or step. No
BDK
KMS
Name of owner of
No
Trafikstation or step.
styrelsen
(Public
Transport
Authority)
Origin
NAME
Stated as the name given in Banedanmark's data, or where this is not available, based on TOP10DK. If
no value can be found: Not allocated is to be used.
OWNER
Stated as the owner in Banedanmark's data. If not available: Not allocated is to be used.
Representation
Marking of where boarding and alighting for rail passenger transport is possible. Height capture at
ground level.
New mapping
Captured as a point on RAILWAY on the lowest track number at the centre of the nearest platform.
Height captured at ground level.
Examples
BLACK-LINE=ROAD CENTRE LINE-Road
BLACK-POINT=Node
LIGHT BLUE=ROAD CENTRE LINE-Path link
GREEN=ROAD CENTRE LINE-Path
RED-LINE=RAILWAY
RED-POINT=TRAIN HALT
FOT 4.0.1 20091022
3.3.8 TRAFFIC-TRAIN HALT
3.3.8.1
FOT 4.0.1 20091022
3.3.8 TRAFFIC-TRAIN HALT
3.3.8.2
3.4 TECHNICAL
TECHNICAL_AREA
RUNWAY
CHURCHYARD
BASIN
TELEMAST BASE
HIGH TENSION WIRE FOUNDATION
HIGH TENSION WIRE
STRUCTURE
GROYNE
PARKING
CHIMNEY
TELEMAST
WIND TURBINE
MAST
GULLY
MANHOLE
FOT 4.0.1 20091022
3.4 TECHNICAL
3.4.1
TECHNICAL AREA
Object group
TECHNICAL
Object type
TECHNICAL_AREA
Geometry type
Surface
Min. size
500 m2
Area
1 2 3
Object definition
An area with a technical function and/or installations such as a military facility, sewage works, wind
farm or airport.
Name
AREA TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Military facility
Sports facility
Power distribution facility
Wind farm
Train station/sidings
Airport
Car park
Unknown
ible
history
No
KOM
Origin
AREA TYPE
TECHNICAL AREA type is shown using one of the listed values.
Representation
The outline of an area's outer limitations in which there are technical facilities. Height is at ground level.
New mapping
The outline of the outer delimitation of an area in which there are technical facilities. Height measured at
ground level.
The area can be delimited by a fence, dyke, vegetation, building area, boundary line etc.
All relevant topography within the area, such as the buildings, technical facilities, storage areas, parking
and other areas which naturally belong to the area are to be captured.
The following special aspects apply:
Military facilities:
The outline of buildings, lawns, parade grounds, garages, storage areas, parking areas, training grounds
etc. which are part of a barracks, including the outline of exercise grounds, radar stations, aerial masts
etc.
Sports facilities:
The outline of sports facilities which can contain stadiums, buildings, spectator facilities, pitches and
miscellaneous sports areas (football, throwing, shooting, swimming, golf, riding, motor sport etc.)
Sport facilities include
School sports facilities
FOT 4.0.1 20091022
3.4.1 TECHNICAL-TECHNICAL AREA
3.4.1.1
Freestanding sports halls at schools
Halls attached to other school buildings are not included in the area.
Associated parking areas are not included
Individual facilities within the area are not registered as TECHNICAL_AREAs.
Minimum size for capture is 2,500 m2, for race tracks 10,000 m2.
Power distribution facility:
The outline of areas with power stations, transformer plants, gas regulator stations or solar power stations
incl. their buildings, coal depots, ash depots, oil tanks, garages, storage and parking areas etc.
Wind farm:
TECHNICAL AREA is registered for a group of 10 WIND TURBINES or more. If there is no physical
boundary for the area, TECHNICAL AREA will snap to the outermost turbine. If the turbines stand in a
straight line, a line snapped on the first and last turbine will be captured and then an estimated line at a
distance of minimum 1 metre from the original line will be captured to create a long thin 1 m-wide area.
Train station/sidings:
The outline intended for railway traffic in relation to a station or sidings. Buildings, storage areas and
private parking areas are included in the area.
Airport:
The outline of an airport, incl. terminals, buildings, fuel tanks, runways, rolling pavements, aircraft
docking stations, aircraft service areas, hangers, control towers, freight sheds, private parking areas and
other relevant facilities are included in the area.
Parking:
NB: Only occur within AREA POLYGON with AREA TYPE=1.
Outline of parking areas for cars, buses, heavy goods vehicles, trailers, storage for boats etc.
Minimum size 2,500 m2. Several smaller areas adjacent parking areas bisected by ROAD CENTRE
LINE will however be included if they exceed the minimum size.
The minimum size for parking areas within TECHNICAL AREA (with another value for AREA TYPE
than Parking facility) is however 10,000 m2.
Unknown:
Used when AREA TYPE is unknown.
Examples
Military facility
YELLOW=TECHNICAL AREA_Military facility
FOT 4.0.1 20091022
3.4.1.2
Sports facility
YELLOW=TECHNICAL AREA-Sports facility
RED=BUILDING
GREEN-DASHED=FENCE-Not allocated
GREEN=FOREST
BLACK=ROAD CENTRE LINE-Path
FOT 4.0.1 20091022
3.4.1.3
Power distribution facility
YELLOW=TECHNICAL AREA-Power distribution facility
RED=BUILDING
GREEN-DASHED=FENCE-Hedge
PINK=FENCE-Wire
RED-DASHED=HIGH TENSION WIRE
LIGHT GREEN=BUILDING-Tank/silo
GREEN=FOREST
FOT 4.0.1 20091022
3.4.1.4
PINK=STRUCTURE
BLACK=ROAD EDGE
BLUE-CIRCLE=CHIMNEY
RED-DASHED=FENCE-Wire
RED-CROSS=TELEMAST
BLUE=STREAM CENTRE LINE 0-2.5
GREEN-LINE=FENCE-Hedge
GREEN SURFACE=FOREST
PINK=STRUCTURE
FOT 4.0.1 20091022
3.4.1.5
Wind farm
YELLOW=TECHNICAL AREA-Wind farm
Train station/sidings
YELLOW=TECHNICAL AREA-Train station/sidings
Airport
YELLOW=TECHNICAL AREA-Airport
FOT 4.0.1 20091022
3.4.1.6
Car park
YELLOW=TECHNICAL AREA-Parking
RED=BUILDING
GREEN=FENCE-Hedge
FOT 4.0.1 20091022
3.4.1.7
Unknown
YELLOW=TECHNICAL AREA-Unknown
FOT 4.0.1 20091022
3.4.1.8
PURPLE=BUILDING-Tank/Silo
BLACK=ROAD EDGE
BLACK-STIPPLED LINE=ROAD CENTRE LINE-Driveway
GREEN=STRUCTURE
BLUE=BASIN
FOT 4.0.1 20091022
3.4.1.9
RUNWAY
Object group
TECHNICAL
Object type
RUNWAY
Geometry type
Surface
Min. size
1000 m2
Area
1 2 3
Object definition
A marked area specifically designed for aircraft takeoff and landing.
Name
Multiplicity
RUNWAY TYPE
RUNWAY TYPE
VALUE
Takeoff_Landing
Taxi runway
Place
[1..1]
Type
Text
Legal values
Takeoff_Landing
Taxi runway
Place
triggers
ible
history
No
KMS
Photogrammetric
registration
MEANING
Airport area where aircraft take off and land.
Airport area primarily used for aircraft taxiing.
Airport area where aircraft embark/disembark passengers or goods, aircraft
parking area and aircraft service areas of any type.
Representation
The boundary line of an area intended for aircraft traffic. The height is captured at ground level.
New mapping
Outline of the extreme delimitation of an area intended for manoeuvring aircraft. The height is captured
at ground level.
Captured as the outline of a traffic area of gravel, grass or metalled surface for use by aircraft - fixedwing or helicopter. The area includes runways, taxi runways for aircraft within the airport area and
aircraft service areas of various types.
The outline is captured where the metalled surface stops, or where attribute value for runway type
changes.
Unmetalled surfaces: the transition from gravel to grass or white stone markings on grassed areas.
Examples
RED=RUNWAY-Takeoff_Landing
GREEN=RUNWAY-Taxi runway
BLUE=RUNWAY-Place
FOT 4.0.1 20091022
3.4.2 TECHNICAL-RUNWAY
3.4.2.1
FOT 4.0.1 20091022
3.4.2.2
ORANGE=Road centre line
FOT 4.0.1 20091022
3.4.2.3
FOT 4.0.1 20091022
3.4.2.4
CHURCHYARD
Object group
TECHNICAL
Object type
Geometry type
CHURCHYARD
Min. size
Surface
500 m
2
Area
1 2 3
Object definition
An area used or intended for burial.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
The boundary line of the area. The height is captured at ground level.
New mapping
The boundary line of an area intended or used for burial. The height is captured at ground level.
Captured on the outer extremes of the area, primarily on churchyard walls but dykes, hedges, boundary
lines and so on can be included. The surface encloses an area irrespective of entrance gates and/or
similar access breaks in the boundary.
The area contains actual burial plots and areas of park or garden-like character which are clearly part of
the area. All relevant topography within the areas, such as church, chapel, office, toilets, sheds, trees,
hedges, avenues, major roads and paths are captured.
Car parking areas for a vicarage, parish buildings or churchgoers located immediately adjacent to but not
within the churchyard wall are not included in the area.
Roads and major paths can only be included if they lead in or out of the area. See also under ROAD
CENTRE LINE and ROAD EDGE.
Examples
GREEN=CHURCHYARD
PINK=CAR PARK
FOT 4.0.1 20091022
3.4.3 TECHNICAL-CHURCHYARD
3.4.3.1
FOT 4.0.1 20091022
3.4.3.2
FOT 4.0.1 20091022
3.4.3.3
FOT 4.0.1 20091022
3.4.3.4
FOT 4.0.1 20091022
3.4.3.5
BASIN
Object group
TECHNICAL
Object type
BASIN
Geometry type
Surface
Min. size
25 m2
Area
1 2 3
Object definition
Open containers sunk into or above the ground for the storage of liquids.
Name
BASIN TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Sewage works
Swimming pool
Other
Unknown
ible
history
No
KOM
Origin
BASIN TYPE
Type is shown using one of the listed values.
Representation
The outer edge of a basin in a sewage works, a swimming pool or a sports facility/amusement park etc.
Height is on the top edge.
New mapping
The outer edge of a basin in a sewage works, an overflow basin for the collection of waste water, an
open air swimming pool at a sports facility/amusement park or the like. Height is captured on the top
edge.
Not captured in private gardens.
The following rules also apply within areas covered by AREA POLYGON with AREA TYPE=1:
If there are several BASINs with a distance < 1 m from each other, they are captured as one BASIN. If
there are several BASINs under the minimum size with a distance < 1 m from each other, they are
captured as one BASIN
Examples
BLUE=BASIN-Sewage works
BLACK=ROAD EDGE
GREEN=STRUCTURE
FOT 4.0.1 20091022
3.3.4.1
BLUE=BASIN-Swimming pool
RED=BUILDING
BLACK=ROAD EDGE
BLACK-STIPPLED=ROAD CENTRE LINE
PINK=CAR PARK
FOT 4.0.1 20091022
3.3.4.2
TELEMAST BASE
Object group
TECHNICAL
Object type
TELEMAST BASE
Geometry type
Surface
Min. size
1 m.
Area
3
Object definition
Concrete base for a TELEMAST.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
The outline of an individual telemast base. The height is at ground level.
New mapping
Captured on the outer limit of each base structure supporting or reinforcing a TELEMAST. The height is
captured at ground level.
Only bases with a diagonal distance > 1 metre are captured.
Examples
RED=TELEMAST BASE
FOT 4.0.1 20091022
3.4.5 TECHNICAL-TELEMAST BASE
3.4.5.1
HIGN TENSION WIRE FOUNDATION
Object group
TECHNICAL
Object type
HIGH TENSION WIRE
FOUNDATION
Geometry type
Surface
Min. size
1 m.
Area
3
Object definition
Concrete base for a HIGH TENSION WIRE pylon.
Name
Multiplicity
Type
Legal values
Change Respontriggers
sible
history
Origin
Representation
The outline of individual HIGH TENSION WIRE FOUNDATIONs. The height is at ground level.
New mapping
Captured on the outline of each foundation supporting or reinforcing a HIGH TENSION WIRE
FOUNDATION. The height is captured at ground level.
Only foundations with a diagonal distance > 1 metre are captured.
Examples
RED=HIGH TENSION WIRE FOUNDATION
FOT 4.0.1 20091022
3.4.6 TECHNICAL-HIGH TENSION WIRE FOUNDATION
3.4.6.1
HIGH TENSION WIRE
Object group
TECHNICAL
Object type
HIGH TENSION WIRE
Geometry type
Line
Min. size
-
Area
123
Object definition
Route of a HIGH TENSION WIRE suspended from steel pylons or paired wooden masts.
Name
VOLTAGE
Multiplicity
[1..1]
Type
Text
Legal values
50 kV
Not allocated
triggers
ible
history
No
KMS
The high voltage
maps of the
electricity providers.
VOLTAGE:
As stated by the electricity providers:
50 kV: > 50 kV
Not allocated: Voltages not allocated
Representation
The middle of the corridor line of HIGH TENSION WIREs.
Captured on the middle of the mast or pylon. Height is at the top.
Can also occur if the wire terminates at e.g. a power supply sub-station or a building.
New registration
Captured at the middle of the wire corridor line. Height captured on the top of the mast or pylon.
Where several masts support a hanger: estimation is made at the middle of the hanger.
Captured with intermediate points on each mast or pylon, and at the end points.
Captured into a power supply sub-station to/from the outer mast/building. Other wires inside the substation area are not captured.
The attribute for VOLTAGE is stated by:
50 kV: > 50 kV. Set in accordance with TOP10DK's data.
Not allocated: Non-allocated voltage. Applied to all newly-captured objects.
Examples
RED=BUILDING
YELLOW=TECHNICAL AREA-Power supply sub-station
FOT 4.0.1 20091022
3.4.7 TECHNICAL-HIGH TENSION WIRE
3.4.7.1
PINK=FENCE-Wire
GREEN-DASHED=FENCE-Hedge
FOT 4.0.1 20091022
3.4.7 TECHNICAL-HIGH TENSION WIRE
3.4.7.2
STRUCTURE
Object group
TECHNICAL
Object type
STRUCTURE
Geometry type
Line
Min. size
1=25 m2 2,3= 10 m2
Area
123
Object definition
Large structures which cannot be characterised as buildings.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
The edge of bridges, pump stations, supporting walls, statue pedestals, large installation cabinets,
(transformers, gas regulator stations) fountains, ruins and the like.
Registered at the centre or on the outer edge. Height is on the upper edge.
New mapping
The edge of bridges, pump stations, supporting walls, statue pedestals, large installation cabinets,
fountains, ruins, foundations for buildings under construction and the like.
Captured at the centre or on the outer edge (if width is > 2m.). Height captured on the upper edge.
Concrete structures with no water contact in harbour areas.
Hard borders (=concrete, stone, iron or wood) of streams where the structure cannot be classed as
HARBOUR with harbour type=Stream.
Supporting wall > 2 metres high is captured as STRUCTURE.
Supporting wall is captured as a single line on the top edge.
Lower supporting wall is captured as FENCE.
Wall with a width >1 meter is captured as STRUCTURE at the centre. Height captured on the top.
Narrower wall is captured as FENCE.
Building under construction is captured as STRUCTURE if the foundations only are visible.
Large installation cabinets, pump cabinets and statue pedestals with an area > 2 m2 are captured when
they lie inside an AREA POLYGON with AREA TYPE=3.
Table with general minimum measurements:
AREA POLYGON
Area type=1
Area
25 m2
FOT 4.0.1 20091022
3.4.8 STRUCTURE
AREA POLYGON
Area type=2
10 m2
AREA POLYGON
Ares type=3
10 m2
3.4.8.1
Line
At road bridge
25 m
5m
10 m
5m
5m
5m
Examples
PINK=STRUCTURE
BLUE=STREAM EDGE-Visible
RED=STREAM EDGE-Invisible
PINK=STRUCTURE
RED-DASHED=FENCE-Wire
RED-CROSS=TELEMAST
BLUE=STREAM CENTRE LINE
GREEN-LINE=FENCE-Hedge
FOT 4.0.1 20091022
3.4.8 STRUCTURE
3.4.8.2
GREEN=STRUCTURE
BLACK=ROAD EDGE
BLUE=BASIN
GREEN=STREAM CENTRE LINE-Visible
RED-STIPPLED=STREAM CENTRE LINE-Invisible
FOT 4.0.1 20091022
3.4.8 STRUCTURE
3.4.8.3
Object group
TECHNICAL
Object type
Geometry type
Line
Min. size
-
Area
3
Object definition
Less significant structures and constructions.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Minor walls, covers, weirs, freestanding stairs, small bridges and similar structures.
Foundations for aerial crane gantries.
The outer edge, height is on the top of the object.
Only occur within AREA POLYGON with AREA TYPE=3.
New registration
Minor walls, covers, weirs, freestanding stairs, small bridges and similar structures.
Foundations for aerial crane gantries.
Captured on the outer edge, height captured on the top of the object.
Aerial structures must only be shown by their foundations on the ground.
No data capture on farm properties or in private gardens.
Examples
YELLOW=OTHER SMALL STRUCTURES
RED=STRUCTURE
BLACK=ROAD EDGE-Path, misc.
BLUE=LAKE
FOT 4.0.1 20091022
3.4.9 TECHNICAL-OTHER SMALL STRUCTURES
3.4.9.1
FOT 4.0.1 20091022
3.4.9 TECHNICAL-OTHER SMALL STRUCTURES
3.4.9.2
GROYNE
Object group
TECHNICAL
Object type
GROYNE
Geometry type
Line
Min. size
25 m.
Area
123
Object definition
Wave-breaking structure off or parallel to COAST.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Barriers in the form of fences, piles, stones, concrete blocks or the like which break the destructive force
of waves on the coast. Located off or parallel to the coastline.
Wave-breakers linked to harbours are captured as HARBOUR.
Captured in the middle. Height is on the top.
GROYNE > 2 metres wide at the water surface is captured on the outline else at the middle.
New mapping
Barrier in the form of stones, concrete blocks or the like which break the destructive force of waves on
the coast. Placed off or parallel to the coast.
GROYNE linked to harbour is captured as HARBOUR.
Boundary fences etc. around sand traps to retain sand deposits in marshes and tidal flats are captured as
GROYNE.
Captured at the middle. Height captured on the top.
GROYNE > 2 metres wide at the water surface is captured on the outline. Smaller GROYNE is captured
at the estimated middle.
GROYNE starting on land and running into the sea is captured along the full length as GROYNE.
Examples
RED-STIPPLED=GROYNE
RED=HARBOUR-Sea
GREEN=COAST
FOT 4.0.1 20091022
3.4.10 TECHNICAL-GROYNE
3.4.10.1
FOT 4.0.1 20091022
3.4.10.2
FOT 4.0.1 20091022
3.4.10.3
PARKING
Object group
TECHNICAL
Object type
PARKING
Geometry type
Line
Min. size
50 m.
Area
2 3
Object definition
Outline of an independent car parking area.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Surface edge around an independent car parking area.
Internal distribution roads and access roads shorter than 20 m. to or from a car park are included in the
area.
New mapping
Data capture on the surface edge. The height is captured at ground level.
Capture of PARKING is a question of assessment using the points listed below as a guide:
PARKING is captured in connection with ROAD EDGE of TYPE=Carriageway, but never in
connections with ROAD EDGE=Internal road.
ACCESS WAYs shorter than 20 metres to and from car park areas are captured as PARKING.
The following are captured as PARKING in connection with ROAD EDGE of TYPE=Carriageway:
Car park areas linked to a larger unit: institution, shopping centre, sports facility, railway station,
sightseeing attraction etc.
Car parking areas in squares or in town centres
Car parking on the roofs of buildings
Common car parking areas on housing estates, terraced houses or the like
Independent parking areas with their own road access to ROAD EDGE of TYPE=Carriageway
But not:
Car parking on industrial sites, private houses or farms
Car parking alongside roads
Bus bays
Traffic islands, bay markers and similar objects in car parks are captured as PARKING if they have the
form of a curb stones or areas of vegetation etc.. Painted stripes and change of level are not considered to
be sufficient delimitation to warrant independent capture.
FOT 4.0.1 20091022
3.4.11 TEKNIK-PARKERING
3.4.11.1
Examples
PINK=TRAFFIC ISLAND
YELLOW=PARKING
BLACK=ROAD EDGE-Carriageway
GREEN=CHURCHYARD
PINK=CAR PARK
FOT 4.0.1 20091022
3.4.11.2
YELLOW=PARKING
RED=BUILDING
GREEN=ROAD EDGE
FOT 4.0.1 20091022
3.4.11.3
CHIMNEY
Object group
TECHNICAL
Object type
CHIMNEY
Geometry type
Point
Min. size
Height=10 m
Area
123
Object definition
Structure in the form of a pipe or tube designed to disperse smoke or gas.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Freestanding chimney or chimney on a building.
Registered in the middle. Height is on the top edge.
New mapping
Middle of large chimneys. Freestanding or on top of large buildings. Height is captured on the top edge.
Freestanding chimney is captured if it is >= 20 metres over ground level.
Chimney located on the roof of a building (e.g. a power station) is captured if it is >= 10 metres over the
roof level of the building.
Examples
Please note:
CHIMNEY is here in the pictures shown at the chimney-top to show, that it is digitised at the TOP.
If CHIMNEY is viewed on top of an orthophoto, it will always be shown at the bottom regardless of its
height.
BLUE-CIRCLE=CHIMNEY
LIGHT GREEN=BUILDING-Tank/silo-Other
GREEN=FOREST
PINK=STRUCTURE
BLACK=ROAD EDGE
FOT 4.0.1 20091022
3.4.12 TECHNICAL-CHIMNEY
3.4.12.1
FOT 4.0.1 20091022
3.4.12.2
LIGHT BLUE=BUILDING-Tank/Silo-Other
FOT 4.0.1 20091022
3.4.12.3
FOT 4.0.1 20091022
3.4.12.4
TELEMAST
Object group
TECHNICAL
Object type
TELEMAST
Geometry type
Point
Min. size
Height 10 m.
Area
123
Object definition
Mast/tower bearing aerials.
Name
MEDIUM TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Not allocated
Change ResponOrigin
triggers
sible
history
No
KMS
Explicitly stated
KOM
when entered.
MEDIUM TYPE
Only one value can be stated.
Representation
Construction in the form of a tower, trellis mast or a combination of both to support antennas for
communication purposes, e.g. radio-TV broadcast, telephony, shared antennas, warning sirens etc.
Captured in the middle. Height is on the top (without top antenna if mounted).
Only TELEMAST standing on the ground can be captured.
Building-like antennas and masts for radar and/or military purposes are captured as BUILDING.
New mapping
Construction in the form of a mast or tower or a combination of both to support antennas for
communication purposes, e.g. radio-TV broadcast, telephony, shared antennas, warning sirens etc.
All forms of towers and masts whether concrete column, single leg or multi-leg steel trellis structures are
captured as a single central point.
Height captured on the top (without top antenna if mounted).
Only TELEMAST standing on the ground can be captured.
Building-like antenna and mast for radar and/or military purpose is captured as BUILDING.
TELEMAST in private gardens is not captured.
Examples
FOT 4.0.1 20091022
3.4.13 TECHNICAL-TELEMAST
3.4.13.1
FOT 4.0.1 20091022
3.4.13 TECHNICAL-TELEMAST
3.4.13.2
WIND TURBINE
Object group
TECHNICAL
Object type
WIND TURBINE
Geometry type
Point
Min. size
Height 10 m.
Area
123
Object definition
Tower with 3-bladed wind turbine or nacelle.
Name
BUILDING_ID
Multiplicity
[0..1]
Type
Text
Legal values
000000000000000999999999999999
triggers
ible
history
Yes
KOM
Corresponds to the
related
BUILDING_ID in
BBR's core data
BUILDING_ID:
Identical with the corresponding building ID stated for a building in BBR
Representation
Construction in the form of a steel or concrete tower with a 3-bladed rotary wind turbine on the top.
Captured in the middle of the mast. Height is on top of the tower.
WIND TURBINES standing either on the ground or at sea and with a tower height > 10 m are captured.
New mapping
Construction in the form of a steel or concrete tower with a 3-bladed rotary wind turbine on top.
Captured in the middle of the mast. Height captured on top of the tower.
WIND TURBINE standing either on the ground or at sea and with a tower height > 10 m is captured.
10 or more WIND TURBINES standing together form a wind farm. An area surrounding all the WIND
TURBINES is captured as TECHNICAL AREA with AREA TYPE=Wind farm.
All individual WIND TURBINEs in a wind farm must be captured
Examples
FOT 4.0.1 20091022
3.4.14 TECHNICAL-WIND TURBINE
3.4.14.1
FOT 4.0.1 20091022
3.4.14 TECHNICAL-WIND TURBINE
3.4.14.2
MAST
Object group
TECHNICAL
Object type
MAST
Geometry type
Point
Min. size
Height 3 m.
Area
3
Object definition
Mast for the suspension of wires and/or light fittings.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Mast for suspension of wires for low tension electricity supply and/or light fittings.
Captured in the middle. The height is at ground level.
New mapping
Captured in the middle. The height is captured at ground level.
MASTs in private gardens, industrial and railway areas are not captured.
Only masts > 3 metres high for street lighting and electricity supply are captured.
Examples
FOT 4.0.1 20091022
3.4.15 TECHNICAL-MAST
3.4.15.1
FOT 4.0.1 20091022
3.4.15 TECHNICAL-MAST
3.4.15.2
GULLY
Object group
TECHNICAL
Object type
GULLY
Geometry type
Point
Min. size
-
Area
3
Object definition
Grid covering a drain intended for surface water dispersal.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
GULLY is captured in the centre og the grid cover. The height is at ground level.
New mapping
GULLY is captured in the centre of the grid cover. The height is captured at ground level.
GULLY in private garden, farm plot, industrial and railway area is not captured.
Examples
RED=GULLY
GREEN=MANHOLE COVER
FOT 4.0.1 20091022
3.4.16 TECHNICAL-GULLY
3.4.16.1
FOT 4.0.1 20091022
3.4.16 TECHNICAL-GULLY
3.4.16.2
MANHOLE
Object group
TECHNICAL
Object type
MANHOLE
Geometry type
Point
Min. size
-
Area
3
Object definition
Cover over access to an underground installation.
Name
MANHOLE TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Rainwater
Wastewater
Sewage water
Water supply
District heating
Gas
Tele
Electricity
Not allocated
Other
ible
history
No
KOM
Origin
MANHOLE TYPE
Type is shown using one of the listed values.
Representation
All forms of covers (round or square) that cover the accesses to sewers, district heating installations,
telephone cables, water supply etc.
Captured in the centre. The height is captured at ground level.
New mapping
Captured in the centre. The height is captured at ground level.
All MANHOLEs are captured.
However, manholes located in private properties, industrial sites, farms and railway areas are not
captured.
Photogrammetric limitations
The above describes the general aspects for this object type. Photogrammetric data capture from aerial
imagery, however, does not always completely comply with all these requirements. The following is a
description of the criteria photogrammetric work has to fulfil.
Only the following attributes and values are captured:
If there are details in TK data regarding manhole types, they should be transferred to attribute
MANHOLE TYPE.
Otherwise, for newly- captured MANHOLE "Not allocated" will always be used.
FOT 4.0.1 20091022
3.4.17 TECHNICAL-MANHOLE
3.4.17.1
Examples
GREEN=MANHOLE
RED=GULLY
FOT 4.0.1 20091022
3.4.17 TECHNICAL-MANHOLE
3.4.17.2
STATUE MEMORIAL STONE
Object group
TECHNICAL
Object type
Geometry type
Point
Min. size
-
Area
3
Object definition
Statue or memorial stone.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Statue with or without pedestal, memorial stone, stones on ancient burial mounds or unusually large
boulders on land or in water.
STATUE_MEMORIAL_STONEs are captured at the middle. The height is at ground level.
New mapping
Statues with or without pedestals, memorial stones, stones on ancient burial mounds or unusually large
boulders on land or in water. Large foundations serving as bases for the aforementioned are captured as
STRUCTURE.
Captured at the middle. The height is captured at ground level.
STATUE_MEMORIAL_STONE in private gardens, industrial and railway areas is not captured.
These objects are only captured after designation from the municipality or KMS.
Examples
RED=STATUE_MEMORIAL_STONE
GREEN=STRUCTURE
FOT 4.0.1 20091022
STONE
3.4.18 TECHNICAL-STATUE_MEMORIAL
3.4.18.1
FOT 4.0.1 20091022
STONE
3.4.18 TECHNICAL-STATUE_MEMORIAL
3.4.18.2
Object group
TECHNICAL
Object type
Geometry type
Point
Min. size
60 cm.
Area
3
Object definition
Freestanding cabinet for technical devices.
Name
Multiplicity
Type
Legal values
ible
history
Origin
Representation
Freestanding cabinet for technical devices such as telephone box, electrical cabinet, transformer, traffic
control, gas regulation etc...
Minimum measurement diagonal = > 0.6 m. Max. area = < 2 m2.
Captured at the centre. The height is at ground level.
New mapping
Freestanding cabinet for technical devices such as telephone box, electrical cabinet, transformer, traffic
control, gas regulation etc.
Minimum measurement diagonal = > 0.6 m. Max. area = < 2 m2.
Captured at the centre. The height is captured at ground level.
Where these objects stand close together, each is captured individually.
Objects larger than the specified max. size are captured as STRUCTUREs.
Not captured in private properties, industrial or railway areas.
Examples
Missing
FOT 4.0.1 20091022
CABINET
3.4.19 TECHNICAL-INSTALLATION
3.4.19.1
3.5 NATURE
FOREST
HEATH
WETLAND
SCRUB_VEGETATION
SAND_DUNE
QUARRY
FENCE
BOUNDARY LINE
SLOPE
DYKE
TREE
TREEGROUP
FOT 4.0.1 20091022
3.5 NATURE
3.5.1
FOREST
Object group
NATURE
Object type
FOREST
Geometry type
Surface
Min. size
2,500 m2
Area
1 2 3
Object definition
An area covered in trees.
Name
OWNER_FOREST
Multiplicity
[1..1]
UNDER_MINIMUM_FOREST [1..1]
Type
Text
Legal values
Not allocated
Boolean 0
sible
history
No
SNS,
KOM,
BANEDK
No
KOM,
SNS
Origin
Stated explicitly
when entered
administratively.
Stated explicitly
when entered
administratively.
OWNER_FOREST
Owner is stated using one of the listed values.
UNDER_MINIMUM_FOREST
0 = FOREST > 2,500 m2
Representation
FOREST is represented by the boundary of the tree coverage at the edge of the area and/or up to another
object. Height is captured at tree crown level.
Only FOREST > 2,500 m2 is captured as a rule. However, FOREST < 2,500 m2 can be included if
designated by an environmental administrative body.
New mapping
FOREST is captured on the boundary line of the tree coverage up to another object (e.g. lake, dyke,
meadow, stream bank etc.) or where this does not occur: captured on an assessed transition line between
forest undergrowth and e.g. a fire break, a boundary line along a road, a field etc. Height is captured at
tree crown level.
FOREST is captured with as few points as possible. However, the difference between the actual line and
captured line should not exceed the following values in both plan and height.
AREA TYPE POLYGON
1
2
3
Area type=
3
2
1
FOREST with an area >= 2,500 m2 is captured.
FOREST with an area < 2,500 m2 is captured as either TREE GROUP or FENCE.
FOT 4.0.1 20091022
3.5.1 NATURE-FOREST
3.5.1.1
FOREST with an area < 2,500 m2 lying within an object of type HEATH, WETLAND or SAND_DUNE
with a total area for both objects >= 2,500 m2, will be included in the surrounding object.
FOREST with an area < 2,500 m2 adjacent to objects of type HEATH, WETLAND of SAND_DUNE
with a total area for both adjacent objects >= 2,500 m2, will be included in the surrounding areas.
FOREST with an area < 2,500 m2, designated for registration by an environmental administrative body
is also captured photogrammetrically.
Small, separate areas with forest are captured as one FOREST if the distance between them is < 10
metres and the total area > 2,500 m2.
Clearings and fire breaks in forest are not included in FOREST if they have a width of > 10 metres and a
length of > 250 metres.
Only clearings and/or fire breaks with the character of permanent unplanted areas (no trees or bushes)
are considered to be clearings and/or fire breaks. Open areas due to felling, storm damage or re-planting
are not clearings and will therefore be included in FOREST.
The width of roads or streams in a fire break should not be not included when calculating the width of a
fire break.
Examples
PINK-HATCHING=FOREST
GREEN=FENCE-Hedge
BLUE=LAKE
YELLOW-STIPPLED=HEATH
GREEN=FOREST
FOT 4.0.1 20091022
3.5.1 NATURE-FOREST
3.5.1.2
ORANGE=FENCE-Hedge
PINK=TREE GROUP
FOT 4.0.1 20091022
3.5.1 NATURE-FOREST
3.5.1.3
FOT 4.0.1 20091022
3.5.1 NATURE-FOREST
3.5.1.4
HEATH
Object group
NATURE
Object type
HEATH
Geometry type
Surface
Min. size
2,500 m2
Area
1 2 3
Object definition
Areas with a dry, sparse undergrowth often covered with heather, grass, moss and other dwarf
vegetation.
Name
HEATH TYPE
Multiplicity
[1..1]
UNDER_MINIMUM_HEATH [1..1]
Type
Text
Legal values
Not allocated
Boolean 0
Change ResponOrigin
triggers
sible
history
No
KOM,
Stated explicitly
SNS
when entered
administratively.
No
KOM,
Stated explicitly
SNS
when entered
administratively.
HEATH TYPE
Sub-classification of HEATH depending on the dominant plant life.
Sub-classification makes it possible to classify HEATH with the stated values for HEATH TYPE and
from these, search for specific heath types.
HEATH TYPE can indicate one of the following values:
VALUE
MEANING
Non-allocated heath type.
Not allocated
UNDER_MINIMUM_HEATH
0 = HEATH >= 2,500 m2
Representation
HEATH is represented by the area's plant-covered border line and/or a border line up to another object.
Height is at ground level.
Only HEATH >= 2,500 m2 is represented as a rule. However, HEATH < 2,500 m2 can be included
designated by an administrative authority.
New mapping
HEATH is captured based on a visible and/or an estimated boundary of an area. Visible delimitation is
defined as delimitation up to other objects. Height is captured at ground level.
HEATH is captured with as few points as possible. However, the difference between the actual line and
captured line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
1
2
3
Area type=
FOT 4.0.1 20091022
3.5.2 NATURE-HEATH
3.5.2.1
3
2
1
Where there are other more well-defined objects closer than or equal to the stated discrepancy in metres
for HEATH, all common geometry is captured where HEATH snaps to another object.
It can be difficult to identify HEATH from aerial imagery but the landscape will usually have uneven
plant coverage and will look almost bare, dry, withered and untidy. TOP10DK data can be used as a
guide to where HEATH has previously been observed, but the physical conditions can have changed
since the object type was classified in TOP10DK.
HEATH is only captured for areas >= 2,500 m2.
HEATH with an area < 2,500 m2 lying within an object of type FOREST, WETLAND or SAND_DUNE
with a total area for both objects >= 2,500 m2, will be included as part of the surrounding object.
HEATH with an area < 2,500 m2 adjacent to objects of type FOREST, WETLAND or SAND_DUNE
with a total area for both adjacent objects >= 2,500 m2, will be included as part of the surrounding area.
HEATH with an area < 2,500 m2, designated for natural or administrative reasons is also captured
photogrammetrically.
Small, separate areas of heath are captured as one HEATH if the distance between them is < 10 metres
and the total area > 2,500 m2.
HEATHs narrower than < 10 metres are not captured unless part of a larger cohesive area of HEATH.
All relevant topography on the boundary and within HEATH is captured.
Where only one side of a road is HEATH, whilst the other side is captured as a surface object (apart from
BUILDING, BASIN, TELEMAST BASE and HIGH TENSION WIRE FOUNDATION) and the road is
not so wide that its area can be exposed, the two surface objects will have common geometry on that side
of the road which seems the most natural. The same applies to streams.
Examples
GREEN=FOREST
ORANGE=FENCE-Hedge
PINK=TREE GROUP
FOT 4.0.1 20091022
3.5.2 NATURE-HEATH
3.5.2.2
FOT 4.0.1 20091022
3.5.2 NATURE-HEATH
3.5.2.3
WETLAND
Object group
NATURE
Object type
WETLAND
Geometry type
Surface
Min. size
2,500 m2
Area
1 2 3
Object definition
Flat, relatively low-lying wet areas of water-meadow, marsh or bog.
Name
Multiplicity
UNDER_MINIMUM_WETLAND [1..1]
Type
Legal values
Boolean 0
Change ResponOrigin
triggers
sible
history
No
KOM, Stated explicitly
SNS
when entered
administratively.
UNDER_MINIMUM_WETLAND
0 = WETLAND >= 2,500 m2
Representation
WETLAND is represented at the visible and/or estimated boundary line of the area. Visible delimitation
is defined as delimitation up to other well-defined objects. Height at ground level.
WETLANDS with an area >= 2,500 m2 are only captured as a rule. However, WETLAND < 2,500 m2
can be included if designated by an environmental administrative authority.
New mapping
WETLAND is capture is on the visible and/or estimated boundary of an area. Visible delimitation is
defined as delimitation up to other objects. Height is captured at ground level.
WETLAND is captured with as few points as possible. However, the difference between the actual line
and captured line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
1
2
3
Area type=
5
3
1
Where there are other more well-defined objects closer than or equal to the stated discrepancy in metres
for WETLAND, all common geometry is captured where WETLAND snaps to another object.
It can be difficult to identify WETLAND from aerial imagery but the landscape will usually be unevenly
planted, darker than the surroundings due to the wet surface and lie close to STREAM CENTRE LINE
or LAKE. TOP10DK can be used as a guide, but the physical conditions can have changed since the
object type was classified in TOP10DK.
WETLAND is captured only for areas >= 2,500 m2.
FOT 4.0.1 20091022
3.5.3 NATURE-WETLAND
3.5.3.1
WETLAND with an area < 2,500 m2 lying within an object of type FOREST, HEATH or SAND_DUNE
with a combined area for both objects >= 2,500 m2, will be included as part of the surrounding object.
WETLAND with an area < 2,500 m2 adjacent to an area of type FOREST, HEATH or SAND_DUNE
with a combined area for both adjacent objects >= 2,500 m2, will be included as part of the surrounding
area.
WETLAND with an area < 2,500 m2, designated for natural or administrative reasons is also captured
Small, separate areas of heath are captured as one WETLAND if the distance between them is < 10
metres and the total combined area > 2,500 m2.
WETLAND areas narrower than < 10 metres are not captured unless they are part of a larger cohesive
WETLAND.
All relevant topography on the border and within WETLAND is captured.
Where only one side of a road is WETLAND and the other side is captured as a surface object (apart
from BUILDING, BASIN, TELEMAST BASE and HIGH VOLTAGE WIRE BASE) and the road is not
so wide that its area can be exposed, the two surface objects will have common geometry on that side of
the road which seems the most natural. The same applies to streams.
Examples
YELLOW-STIPPLED=WETLAND
GREEN-STIPPLED=BOUNDARY LINE
GREEN SYMBOL=TREE GROUP
FOT 4.0.1 20091022
3.5.3.2
PINK-HATCHED=WETLAND
BLUE=LAKE
ORANGE=FENCE-Hedge
GREEN-STIPPLED=FOREST
LIGHT BLUE=STREAM CENTRE LINE
FOT 4.0.1 20091022
3.5.3.3
SCRUB VEGETATION
Object group
NATURE
Object type
SCRUB_VEGETATION
Geometry type
Surface
Min. size
50 m2
Area
3
Object definition
Area covered with low vegetation.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
SCRUB_VEGETATION is represented by the area's plant-cover and/or the boundary line up to another
object. Height at ground level.
Area primarily covered with cultivated bushes and trees which don't have the character of forest.
Occurs most often alongside roads, technical areas on sports grounds and similar urban and road-related
areas.
SCRUB_VEGETATION with an area >= 50 m2 is captured.
New mapping
SCRUB_VEGETATION is captured on the area's boundary line and/or delimitation up to another object.
Height is captured at ground level.
SCRUB_VEGETATION will normally be delimited by BUILDING, ROAD EDGE, PARKING or
FENCE.
SCRUB_VEGETATION is captured with as few points as possible, though in such a way that the
difference between the actual line and the captured line is <1 metre in both plan and height at any point.
SCRUB_VEGETATION only with an area >= 50 m2 is captured as a rule.
Small separate areas of SCRUB_VEGETATION can be captured as a single combined
SCRUB_VEGETATION area if the distance between them is < 1 metre.
SCRUB_VEGETATION should not be captured in private gardens, camping sites, parks, green areas,
industrial sites and churchyards.
Examples
FOT 4.0.1 20091022
3.5.4 NATURE-SCRUB VEGETATION
3.5.4.1
PURPLE=TREE
BLACK=ROAD EDGE
GREEN=FENCE-Not allocated
GREEN-Surface=SCRUB_VEGETATION
LIGHT BLUE=PARKING
FOT 4.0.1 20091022
3.5.4.2
GREEN-STIPPLED=SCRUB_VEGETATION
FOT 4.0.1 20091022
3.5.4.3
SAND_DUNE
Object group
NATURE
Object type
SAND_DUNE
Geometry type
Surface
Min. size
10,000 m2
Area
1 2 3
Object definition
Areas of beach, drifting sand or dunes.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
SAND_DUNE is represented by the area's boundary line and/or delimitation up to another object.
Areas of beach, drifting sand or dunes. Dunes with both dispersed and dense vegetation coverage in the
form of lyme grass, dune grass and the like.
It will often be difficult to define a precise boundary between SAND_DUNE and other landscape types
such as HEATH. The boundary lines between SAND_DUNE and e.g. HEATH will therefore often have
to be estimated.
SAND_DUNE with an area >= 10,000 m2 is captured. Height at ground level.
New mapping
Captured on an area's boundary line or estimated boundary line up to another object. Height is captured
at ground level.
SAND_DUNE is captured with as few points as possible. However, the difference between the actual
line and captured line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
1
2
3
Area type=
5
3
1
SAND_DUNE only with areas >= 10,000 m2 are captured as a rule.
All relevant topography on the border and within the area is captured.
SAND_DUNE narrower than < 10 metres are not captured unless part of a larger cohesive
SAND_DUNE area.
SAND_DUNE with an area < 2,500 m2, designated for natural or administrative reasons are also
captured photogrammetrically.
FOT 4.0.1 20091022
3.5.5 NATURE-SAND_DUNE
3.5.5.1
Small, separate areas of SAND_DUNE are captured as one SAND_DUNE area if the distance between
them is < 10 metres and the total area > 10,000 m2.
Examples
YELLOW-STIPPLED=SAND_DUNE
BLUE=COAST
ORANGE-surface=HEATH
FOT 4.0.1 20091022
3.5.5 NATURE-SAND_DUNE
3.5.5.2
QUARRY
Object group
NATURE
Object type
QUARRY
Geometry type
Surface
Min. size
2,500 m2
Area
1 2 3
Object definition
An area where the excavation of raw materials takes place.
Name
Multiplicity
Type
Legal values
RAW MATERIAL TYPE
[1..1]
Text
Not allocated
sible
history
No
KOM
QUARRY TYPE
[1..1]
Text
Active area
No
KOM
Origin
Stated explicitly
when entered
administratively.
RAW MATERIAL TYPE
Statement of the possible values the raw material can have.
QUARRY TYPE
QUARRY TYPE can indicate one of the following values:
VALUE
MEANING
Quarry area in which excavation has started. An active quarry will ALWAYS
Active area
be considered to be an approved area.
Representation
QUARRY AREA is represented by the area's boundary line at ground level and/or delimitation up to
another object.
The excavation of e.g. chalk, lime, marl, clay, sand, stone, gravel or peat.
QUARRYs with an area >= 2,500 m2 are represented.
Both active and approved QUARRYs are represented.
New mapping
QUARRYs are captured on the area's boundary line. Height is captured at ground level.
Areas directly linked with the quarry area that are used for sorting and storage of raw materials are
included in the area.
QUARRY is captured with as few points as possible. However, the difference between the actual line
and captured line will not exceed the following values in both plan and height.
AREA TYPE POLYGON,
1
2
3
Area type=
5
3
1
QUARRY with an area >= 2,500 m2 is captured.
FOT 4.0.1 20091022
3.5.6 NATURE-QUARRY
3.5.6.1
Only QUARRYs which are active can be captured.
QUARRYs narrower than < 10 metres are not captured unless part of a larger cohesive QUARRY area.
Small, separate areas of QUARRY are captured as one combined QUARRY area if the distance between
them is < 10 metres and the total area > 2,500 m2.
Where only one side of a road is a QUARRY and the other side is to be captured as a surface object
(except BUILDING, BASIN, TELEMAST BASE and HIGH TENSION WIRE FOUNDATION) and the
road is not so wide that its area can be exposed, the two surface objects will have common geometry on
the side of the road which is deemed the most natural. The same applies to streams.
All relevant topography on the border and within the area is captured. (With the exception of SLOPE)
Examples
YELLOW=QUARRY AREA
GREEN-STIPPLED=FENCE-Hedge
GREEN-CROSS=WOOD GROUP
LIGHT BLUE=LAKE
FOT 4.0.1 20091022
3.5.6 NATURE-QUARRY
3.5.6.2
FENCE
Object class
Object type
NATURE
FENCE
Geometry type
Min. size
Area
Line
1,2=25 m. 3=2 m.
1 2 3
Object definition
A line in the terrain consisting of a hedge, row of trees, wire fence, embankment, wall or the like which
is a moderate to major obstacle to physical passage on foot.
Name
FENCE TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Hedge
Wire
Other
Not allocated
sible
history
No
KMS
KOM
Origin
FENCE TYPE:
Type of fence is described by one of the following values:
VALUE
MEANING
All types of linear obstacle in the form of vegetation: Hedges, bushes, rows
Hedge
of densely-planted trees, shelter belts and the like.
Permanent linear obstacle in the form of chain link wire fence.
Wire
Other forms of linear obstacle, e.g. plank fences or walls.
Other
Type of fence not allocated.
Not allocated
Representation
FENCE is represented at the middle of the fence. Height at ground level.
New mapping
FENCE is captured at its estimated CENTRE LINE. Height is captured at ground level.
All forms of linear obstacle representing a certain physical type are included: hedges, avenues, plank
fences, narrow boundary walls and permanent wire fences.
Fence type=Wire is captured only when it occurs:
At the edge of and within TECHNICAL_AREA of any type
Around prisons and secure institutions
Around harbour areas and airports
Animal fences around deer farms or alongside motorways.
Fences of woven wire located in other places are captured as Fence type=Not allocated.
FENCE is captured with as few points as possible, though in such a way that the difference between the
actual line and the captured line does not exceed the following values in both plan and height at any
point.
AREA TYPE POLYGON,
1
2
3
FOT 4.0.1 20091022
3.5.7 NATURE-FENCE
3.5.7.1
Area type=
Minimum length
3
25
2
25
1
2
Supporting walls > 2 metres high are captured as STRUCTURE and not FENCE.
Supporting walls with a width >1 metre are captured as STRUCTURE and not FENCE.
Stone dykes and earth embankments > 2 metres wide are captured as DYKEs. If the dyke is also a hedge,
it will also be captured as FENCE with fence type=Hedge in areas where this attribute value can be
captured, otherwise as Fence type=Not allocated.
Trees and bushes in rows are captured as FENCE in one line if the width is < 10 metres.
FENCE with a width > 10 metres and which describe a wood of >= 2,500 m2 are captured as FOREST.
FENCE with a width of > 10 metres which are not FOREST should be flanked on both sides by
BOUNDARY LINE to show the limitation of the hedge.
FENCE cannot be captured over a driveway unless it is a wire fence.
FENCE cannot be captured internally in private gardens, camping sites, parks, green areas, industrial
sites, churchyards and metalled surfaces in housing areas.
Within AREA TYPE POLYGON with AREA TYPE=3:
FENCE with Fence type= Not allocated is captured where a row of at least 10 trees are standing
so close to each that one is unable to walk through them .
For all other rows of trees or single trees TREE is captured on each individual tree.
For FENCE within objects from the BUILDING AREA group in particular:
All forms of FENCE are captured
Without using attribute values Fence type=Hedge or Other however. These types of FENCE are
captured with Fence type=Not allocated instead.
Only Fence type=Wire or Not allocated are used.
FENCE lines are not broken for accesses or entrances to houses.
FENCEs outside and on the edge of objects from the BUILDING AREA group in particular:
Holes in FENCE with Fence type=Hedge caused by missing vegetation over a stretch < 30 metres
does not mean that the object should be broken, unless the hole has been man-made or used for the
passage of 4-wheeled vehicles.
Only Fence type=Hedge, Wire or Other are captured.
Examples
FOT 4.0.1 20091022
3.5.7 NATURE-FENCE
3.5.7.2
RED-STIPPLED=FENCE-Wire
GREEN=FOREST
ORANGE=FENCE-Hedge
GREEN=FOREST
PINK=TREE GROUP
FOT 4.0.1 20091022
3.5.7 NATURE-FENCE
3.5.7.3
RED=FENCE-Not allocated
This section is from an area with Area type=3.
It can be seen here that regardless of the fence type: hedge, wall or plank, the same attribute value is
used, i.e. Not allocated.
FOT 4.0.1 20091022
3.5.7 NATURE-FENCE
3.5.7.4
GREEN SOLID=FENCE-Not allocated
YELLOW=BOUNDARY LINE
RED-STIPPLED=LOW_BUILDING AREA
FOT 4.0.1 20091022
3.5.7 NATURE-FENCE
3.5.7.5
BOUNDARY LINE
Object group
NATURE
Object type
BOUNDARY LINE
Geometry type
Line
Min. size
-
Area
1 2 3
Object definition
Terrain line for the delimitation of an area's usage.
Name
Multiplicity
BOUNDARY LINE TYPE [1..1]
Type
Text
Legal values
Other
sible
history
No
KOM
Origin
BOUNDARY LINE TYPE
Some values for BOUNDARY LINE TYPE are not obligatory. This applies to the value Forest line,
There has to be specific reference in the relevant mapping agreement to have objects of this type
captured in a given area.
BOUNDARY LINE types can have the following values:
BOUNDARY LINE TYPE
Other
Mandatory /
Optional
Mandatory
Description
Delimitation of fields or vegetation with
capture of farm tracks.
Boundary type in open country - only
boundary lines of permanent character.
Support line for wide fence or the like.
Representation
Terrain lines supplemented by FENCE constitute the boundary line of the area's usage, e.g. field,
railway, road, path and the like.
BOUNDARY LINE is represented in the middle. Height at ground level.
New mapping
BOUNDARY LINE is captured on boundary line of an area's specific usage e.g. field, railway, road,
path and the like. Height is captured at ground level.
BOUNDARY LINE is not captured along or using the same route on the edge of NATURE-surfaces to
show the extent of the area.
BOUNDARY LINE is captured with as few points as possible, in such a way that the difference between
the actual line and the captured line does not exceed the following values in both plan and height at any
point.
AREA TYPE POLYGON,
1
2
3
FOT 4.0.1 20091022
3.5.8 NATURE-BOUNDARY LINE
3.5.8.1
Area type=
3
2
1
Boundaries to traffic arteries are captured so that any verges and slopes will be included in the road area.
Where the distance between BOUNDARY LINE and the top of a slope is < 1 metre, only SLOPE with
SLOPE TYPE=TOP is captured within AREA TYPE POLYGON with AREA TYPE=1 or 2. For
AREA TYPE=3 the limit is 0.5 metres.
BOUNDARY LINE in open country between cultivated areas:
Boundaries between cultivated areas are only captured when they are deemed to have permanent
character. There should be a clear indication of grass and/or tree growth or a level difference in the form
of a slope, dyke, excavated ditch etc. in the boundary line
Field boundaries between different crops are not captured as these are considered as temporary.
BOUNDARY LINES between cultivated areas are captured with two lines but where the width is < 10
metres a single line is captured in the middle.
BOUNDARY LINES alongside roads and streams are only captured on the boundaries to areas that are
cultivated or used in some other way.
BOUNDARY LINES to other objects are captured on the cultivation/vegetation line.
BOUNDARY LINES are broken by driveways, but not by field accesses crossing DRAINAGE
DITCHes.
BOUNDARY LINES are not broken at the entrances or accesses to houses or at ROAD CENTRE LINE
with ROAD CLASS=Path, misc.
BOUNDARY LINES are not captured internally in private properties, industrial sites, farm building
areas, temporary garden areas on farms, camping sites and metalled areas in housing estates.
Internal BOUNDARY LINES in FORESTS are not captured just to differentiate between tree species
and/or their height, unless there is a specific agreement. For this option, BOUNDARY LINE
(BOUNDARY LINE TYPE=Forest line) is captured on distinct vegetation boundaries which separate
deciduous and evergreen, and/or where there is a distinct change in vegetation height (> 5 metres).
Height is captured to the top of the highest vegetation.
Inside FOREST, BOUNDARY LINE (BOUNDARY LINE TYPE=Other) is only registered along
ROAD CENTRE LINE.
FENCES with a width > 10 metres, which are not FOREST, are flanked on both sides by BOUNDARY
LINEs to show the limits of the hedge.
In coastal areas, BOUNDARY LINE is captured at the transition from beach to dune at the foot of the
dune, or at the change from beach or dune to clearly defined areas, such as garden, park, forest, field,
road, heath, path etc.
BOUNDARY LINES with a length < 50 metres without any relationship to other objects are not
captured within AREA TYPE POLYGON with AREA TYPE= 1 and 2.
FOT 4.0.1 20091022
3.5.8.2
BOUNDARY LINE is captured around a TREE GROUP or continuous vegetation area which is not
FOREST or FENCE, with a width of > 10 metres and lies within AREA TYPE POLYGON with AREA
TYPE 1 or 2.
Within AREA TYPE POLYGON with AREA TYPE=3, DYKES are flanked by DYKE TYPE=Earth
bank or Stone dyke, with a height and breadth that does not allow access across them on both sides of a
BOUNDARY LINE and shows the extent of the dyke to the sides.
Examples
RED=BOUNDARY LINE-Other
GREEN=FENCE-Hedge
FOT 4.0.1 20091022
3.5.8.3
SLOPE
Object group
NATURE
Object type
SLOPE
Geometry type
Line
Min. size
50 m.
Area
1 2 3
Object definition
Terrain line which delimits steeply sloping terrain at the top or bottom of a sloping area.
Name
SLOPE TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Top
Bottom
Change Respontriggers sible
history
No
KOM
KMS
Origin
SLOPE TYPE:
Statement of an object indicating the top or bottom of the slope.
VALUE
MEANING
The whole object is shown at the top.
Top
The whole object is shown at the bottom.
Bottom
Representation
SLOPE delimits a slope area at the top or bottom.
SLOPE represents the transition between slope and the surrounding terrain. Height at ground level.
New mapping
SLOPE is captured where the terrain angle changes sharply. Height is captured at ground level.
Slopes located outside AREA TYPE POLYGON with AREA TYPE =3.
All SLOPES in the form of man-made cuttings alongside roads, paths and railways or in the form of
man-made sharp drops in the terrain.
SLOPE is given the value Top for attribute SLOPE TYPE if the object represents the top of a slope or
the value Bottom for attribute SLOPE TYPE if the object represents the bottom of a slope. End points in
SLOPE must always snap 3D with another SLOPE.
SLOPE is captured as two open polygons with an end point at each end where top and bottom meet. One
polygon constitutes the bottom of the slope and the other the top.
All slopes with a total length >100 metres and a height difference of 1.5 metres at the highest point along
ROAD CENTRE LINE and RAILWAY are captured.
SLOPE is captured with as few points as possible, in such a way that the difference between the actual
line and the captured line is no greater than 1 metre in both plan and height at any point.
SLOPEs are not captured in QUARRY areas.
FOT 4.0.1 20091022
3.5.9 NATURE-SLOPE
3.5.9.1
Natural slopes are only captured if they are significantly large, i.e. with a height of >=5 metres and so
steep that they cannot be traversed on foot, e.g. coastal slopes.
Where the distance between BOUNDARY LINE and the top of a slope is < 1 metre, SLOPE is only
captured by SLOPE TYPE=Top.
Slopes within or on the edge of AREA TYPE POLYGON with AREA TYPE =3.
Prominent slopes in relation to the surrounding terrain and those which separate laid surfaces in sports
grounds, parks, industrial estates, and apartment block areas etc.
An object of type SLOPE can only depict the top or bottom of a slope.
SLOPE is given the value Top for attribute SLOPE TYPE if the object describes the top of a slope or the
value Bottom for attribute SLOPE TYPE if the object describes the bottom.
Sloping ditch sides with a height difference of > 2 metres are captured at the top. The bottom of the ditch
is not captured as SLOPE.
Natural slopes are only captured if they are significant, – i.e. with a height of >=5 metres and so steep
that they cannot be traversed on foot, e.g. coastal slopes.
Where the distance between BOUNDARY LINE and the top of a slope is < 0.5 metre, SLOPE is only
captured by SLOPE TYPE=Top.
Rainwater basins are captured with SLOPE TYPE=Top at the top of the basin and SLOPE
TYPE=Bottom at the bottom/water surface.
SLOPES are not captured in private gardens unless they are part of a longer slope.
For SLOPES lying in all types of AREA TYPE POLYGON, the general rule is that they cannot occur as
invisible, which is why they cannot be captured under a bridge (or any other non-visible place) but
instead are ended fictively. This is done by extending SLOPE with SLOPE TYPE=Top down to SLOPE
TYPE=Bottomwhere they meet at a bridge edge, as shown in the following illustration (note that
SLOPE TYPE=Top is marked in red and SLOPE TYPE=Bottom is marked in green):
FOT 4.0.1 20091022
3.5.9 NATURE-SLOPE
3.5.9.2
Examples
RED=SLOPE-Top
RED-STIPPLED=SLOPE-Bottom
PINK=STRUCTURE
FOT 4.0.1 20091022
3.5.9 NATURE-SLOPE
3.5.9.3
DYKE
Object group
NATURE
Object type
DYKE
Geometry type
Line
Min. size
50 m.
Area
1 2 3
Object definition
Earth or stone embankment in the terrain.
Name
DYKE TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Not allocated
Change Respontriggers sible
history
No
KOM
Origin
DYKE TYPE
Type is stated using one of the listed values.
Representation
DYKE represented the estimated mid-line of the dyke. Height on the top.
New mapping
DYKE is captured at its estimated mid-line. Height is captured on the top.
DYKE is captured with as few points as possible, in such a way that the difference between the actual
line and the captured line does not exceed the following values in both plan and height at any point.
AREA TYPE POLYGON,
1
2
3
Area type=
3
2
1
Only DYKES with a total length of > 50 metres are captured as a rule.
DYKES are not captured internally in private property, industrial sites and farm building areas.
New DYKEs are not captured photogrammetrically. TOP10DK-DYKEs and the environmental
authority's dykes are used as the basis for how and to what extent DYKES should be captured. Only
TOP10DK-DYKES and the environmental authority's dykes which clearly no longer exist are not
captured. If a dyke cannot be seen due to vegetation, it does not mean that it does not exist.
Examples
To follow.
FOT 4.0.1 20091022
3.5.10 NATURE-DYKE
3.5.10.1
TREE
Object class
Object type
NATURE
TREE
Geometry type
Min. size
Area
Point
-
3
Object definition
A prominent, individual tree.
Name
TREE SPECIES
Multiplicity
[1..1]
Type
Text
Legal values
Deciduous
Evergreen
sible
history
No
KOM
Origin
TREE SPECIES
Representation
TREE occurs as a point in the estimated middle of the tree trunk. Height at ground level.
New mapping
TREE is captured at a point in the estimated middle of the tree trunk. Height is captured at ground level.
Where a tree trunk is not visible, a point at the estimated middle of the tree crown is captured but with
the height captured at ground level.
Only large trees are captured (trunk diameter > 20 cm or when the tree is supported by poles).
TREE must have a distance of > 1 metre to another TREE.
Where at least 10 trees standing in a row are so dense that one cannot easily pass through tem, they are
captured as FENCE.
TREES are captured alongside roads, main paths, paths, on public squares and the like. All individual
prominent trees are also captured.
TREES are however not captured in private gardens or on industrial sites or railway areas.
Examples
PURPLE=TREE
BLACK=ROAD EDGE
GREEN=FENCE-Not allocated
GREEN-Surface=SCRUB_VEGETATION
RED=BUILDING
LIGHT BLUE=PARKING
FOT 4.0.1 20091022
3.5.11 NATURE-TREE
3.5.11.1
GREEN-CIRCLE=TREE
FOT 4.0.1 20091022
3.5.11 NATURE-TREE
3.5.11.2
TREEGROUP
Object group
NATURE
Object type
TREEGROUP
Geometry type
Point
Min. size
-
Area
1 2 3
Object definition
A group of trees.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
TREEGROUP represents the estimated middle of a tree group and within AREA TYPE POLYGON with
AREA TYPE=1 and 2 plus prominent individual trees.
Height on the top.
New mapping
TREEGROUP is captured as a point in the estimated middle of a tree group. Height is captured on the
top.
Within AREA TYPE POLYGON with AREA TYPE = 3, TREEGROUPS are captured alongside roads,
main paths, paths, in public squares and the like, and for groups of trees which are not considered as
either TREE, FENCE or FOREST.
In other AREA TYPE POLYGONS with AREA TYPE = 1 or 2, capture of:
TREEGROUP for a prominent, individual tree or group of trees which are not FENCE or
FOREST
Individual trees with a crown diameter < 10 metres must not be captured
Groups of trees with a total crown diameter < 10 metres must not be captured
Description of vegetation type in a BOUNDARY LINE (with a length of > 10 metres) with a
hedge which is shorter than the minimum measurement for FENCE.
TREEGROUP must have a distance > 25 metres to another TREEGROUP.
TREEGROUP is not captured internally in private properties, industrial sites, railway areas and farm
building areas.
Within objects of object type HEATH, QUARRY AREA and SAND_DUNE, there can be extensive
vegetation to such an extent that the area can be on the verge of being classified as FOREST. In these
circumstances TREEGROUPs are captured in the areas where the vegetation is most dense. These
objects are placed with a distance of > 100 metres to each other.
Examples
GREEN=FENCE-Hedge
FOT 4.0.1 20091022
3.5.12 NATURE-TREE GROUP
3.5.12.1
RED=TREEGROUP
FOT 4.0.1 20091022
3.5.12 NATURE-TREE GROUP
3.5.12.2
3.6 HYDRO
LAKE
STREAM CENTRE LINE
DRAINAGE DITCH
STREAM EDGE
HARBOUR
COASTLINE
JETTY_BATHINGBRIDGE
FOT 4.0.1 20091022
3.6 HYDRO
3.6.1
LAKE
Object group
HYDRO
Object type
LAKE
Geometry type
Surface
Min. size
50 m2/ 100m2
Area
1 2 3
Object definition
Water-filled depression on land.
Name
Multiplicity
Type
Legal values
LAKE TYPE
[1..1]
Text
SALT_LAKE
[1..1]
Boolean
Fish pond
Lake
0
TEMPORARY
[1..1]
Boolean
0
LAKE_UNDER_MINIMUM
[1..1]
Boolean
0
ISLAND_UNDER_MINIMUM
[1..1]
Boolean
0
Change ResponOrigin
triggers
sible
history
No
KOM
Explicitly stated
KMS
when entered.
No
KOM
Explicitly stated
when
administratively
entered.
No
KOM
Explicitly stated
when
administratively
entered.
No
KOM
Explicitly stated
when
administratively
entered.
No
KOM
Explicitly stated
when
administratively
entered.
LAKE TYPE
Type of LAKE is described by one of the following values:
VALUE
MEANING
Basin or dammed pond for breeding freshwater fish on a fish farm.
Fish pond
Natural or man-made lake.
Lake
SALT_LAKE
Salt lakes can be included by administrative designation if they have natural or administrative
significance.
0 = LAKE is not salt.
TEMPORARY
Used when LAKE is deemed to be of a temporary nature, i.e. seasonal or as a result of construction work
etc. Same applies to lakes created by quarrying. These lakes can be included by administrative
designation if they have natural or administrative significance.
0 = LAKE is permanent.
LAKE_UNDER_MINIMUM
FOT 4.0.1 20091022
3.6.1 HYDRO-LAKE
3.6.1.1
LAKE with an area < 100 m2, can be included for administration if designated, if it has a natural or
administrative significance.
0 = LAKE is >= 100 m2.
ISLAND_UNDER_MINIMUM
ISLAND with an area < 100 m2, can be included for administration if designated, if it has a natural or
administrative significance.
0 = ISLAND is >= 100 m2.
Representation
LAKE is represented as the boundary between water and land.
Only permanent freshwater lakes with an area >= 100 m2 are represented as a rule.
ISLANDS in LAKES are usually only found if the island's area is >= 100 m2.
New mapping
LAKES are captured as a surface along the estimated bank at water level. Height captured at water level.
Reed beds along lake banks are included in LAKE. The lake's waterline through these is estimated.
LAKE is captured with as few points as possible, in such a way that the difference between the actual
line and the captured line is no greater than 1 metre in both plan and height at any point.
AREA TYPE POLYGON,
Area type=
1
2
3
2
2
1
In intensively used areas within AREA TYPE POLYGON with AREA TYPE=3, 0.5 metres.
The height must remain constant within LAKE, incl. any cut-outs for islands.
LAKEs must be of permanent character, e.g. temporary lakes which may result from seasonal conditions
are not captured, unless designated due to natural or administrative significance.
Moats, blind rivers and the like which are not part of a flowing water system are captured as LAKE.
A LAKE can be captured in a stream network where the width on a stretch of > 50 metres more than
trebles and where the minimum area requirement for LAKE can be met.
Dams and the like, e.g. for roads or railways which cross a LAKE, divide it into separate lakes. Bridges
on piles etc, which do not significantly restrict water flow, do not divide a LAKE.
LAKE is usually captured if its area >= 100 m2.
LAKES with an area < 100 m2, designated for natural or administrative reasons are also captured.
ISLAND in a LAKE is captured as a cut-out in LAKE.
ISLANDS with an area of < 100 m2 are not captured.
FOT 4.0.1 20091022
3.6.1 HYDRO-LAKE
3.6.1.2
Areas deemed to be salt lakes or salt water areas, wholly or partially dammed but still connected to the
sea, are not LAKES.
Basins which are part of technical facilities, swimming pool complexes etc. are not LAKES.
Special conditions for LAKE TYPE=Fish pond
Fish farms are captured at the outer edge of the dams or basins water surface.
Empty basins on fish farms that are in use are captured on the estimated water edge.
Only fish pond basins with an area >= 50 m2 are captured.
If several fish pond basins lie < 1 metre from each other and they are not separated by other captured
objects, then they should be captured as one large fish pond basin. Basins with an areas < 50 m2 are
included if the total and combined area is > 50 m2.
If data is available, a completeness check is performed against TOP10DK (LAKE) data, TK99 (LAKE)
and the environmental administration authority’s LAKE data (§3 data)
Examples
FOT 4.0.1 20091022
3.6.1 HYDRO-LAKE
3.6.1.3
LIGHT BLUE=LAKE
BLUE=STREAM CENTRE LINE-General
RED=STREAM CENTRE LINE-Through lake
FOT 4.0.1 20091022
3.6.1 HYDRO-LAKE
3.6.1.4
STREAM CENTRE LINE
Object group
HYDRO
Object type
STREAM CENTRE LINE
Geometry type
Line
Min. size
50 m
Area
1 2 3
Object definition
The centre of a natural or excavated, open or piped water channel.
Name
Multiplicity
Type
Legal values
STREAM TYPE
[1..1]
Text
NETWORK
[1..1]
MAIN STREAM
[1..1]
General
Through lake
Piped
Boolean 0
1
Boolean 1
OWNER_STREAM
CENTRE LINE
[1..1]
Text
Not allocated
Change ResponOrigin
triggers
sible
history
No
KOM
Explicitly stated
KMS
when entered.
No
KOM
No
KOM
No
KOM
Explicitly stated
when
administratively
entered.
STREAM TYPE
Type of STREAM CENTRE LINE is described by one of the following values:
VALUE
MEANING
Open stream
General
Fictive STREAM CENTRE LINE through a LAKE
Through lake
Administrative registration of piped stream. Can be registered when the
Piped
authority believes that registration has functional significance for the stream
network.
NETWORK
0: STREAM CENTRE LINE is not part of a network which flows into the sea or a lake.
1 : STREAM CENTRE LINE is part of a network which flows into the sea or a lake.
MAIN STREAM
Where there is a minor tributary to a STREAM CENTRE LINE which returns to the main stream, it must
be captured separately.
1 :STREAM CENTRE LINE is part of the main stream
OWNER_STREAM CENTRE LINE
States possible values for ownership of STREAM CENTRE LINE.
Name
CENTRE LINE WIDTH
FOT 4.0.1 20091022
Multiplicity
[1..1]
Type
Text
Legal values
0-2.5
Change ResponOrigin
triggers
sible
history
No
KOM
Determined
3.6.2 HYDRO-STREAM CENTRE LINE
3.6.2.1
2.5-12
12Unknown
VISIBLE_STREAM
CENTRE LINE
[1..1]
KMS
Boolean 0
1
No
photogrammetrically
or administratively
using water
regulative.
KOM
KMS
CENTRE LINE WIDTH
Statement of stream width for one of the listed intervals.
However, Unknown is always used when STREAM TYPE=Piped or Through lake are captured.
VISIBLE_STREAM CENTRE LINE
A stream which cannot be seen photogrammetrically because it runs under a structure, bridge or through
a tunnel.
0 = STREAM CENTRE LINE is not visible.
1 = STREAM CENTRE LINE is visible.
STREAM CENTRE LINE with STREAM TYPE=Through lake or Piped always has value 0
throughout the length of the object.
Representation
STREAM CENTRE LINE represents the estimated centre line between the sides of a stream.
If a LAKE has more than one STREAM CENTRE LINE object linked to it, then they are linked out in
the lake by STREAM CENTRE LINE with STREAM TYPE=Through lake.
New mapping
STREAM CENTRE LINE represents the estimated centre between the sides of a stream.
STREAM CENTRE LINE is registered with as few points as possible, in such a way that the difference
between the actual line and the captured line are no greater than the following values in both plan and
height at any point.
AREA TYPE POLYGON,
Area type=
1
2
3
2
2
1
Height is captured at water level or in the bottom if the stream is dry.
The heights should show a subsequent fall or rise to the course of a STREAM CENTRE LINE.
A small pocket or bulge on one river bank will not cause STREAM CENTRE LINE to reflect a
corresponding divergence.
STREAM CENTRE LINE should be part of the largest possible network.
STREAM CENTRE LINE has different rules, depending on the value of STREAM TYPE:
VALUE
MEANING
General
Cannot occur in objects BASIN, TELEMAST BASE, HIGH TENSION WIRE
FOUNDATION or LAKE
FOT 4.0.1 20091022
3.6.2.2
Can contribute to exposure of surface objects.
Through lake
Can only occur in object LAKE
Always allocated width Not allocated
Cannot contribute to exposure of surface objects.
Piped
Can occur in all surface objects
Always allocated width Not allocated
Cannot contribute to exposure of surface objects.
Only STREAM CENTRE LINE with STREAM TYPE=General or Through lakeare captured
Administratively entered STREAM CENTRE LINE with STREAM TYPE =Piped are edited together
with other STREAM CENTRE LINES.
The largest possible cohesive network of objects should be created.
If LAKE is deemed to have an inlet and outlet, STREAM CENTRE LINE must be captured through the
lake. The object is captured with the shortest possible distance between inlet and outlet, without touching
the lake bank or any islands. If there is more than one inlet/outlet, STREAM CENTRE LINE is linked by
an estimated line out in the lake.
If an open stream runs over a piped stream, only the open stream is included. This only applies if the
streams belong to the same network. However, if the streams belong to two different networks, it is
treated as an exception, in which case objects out of level can cross each other without a break.
Moats, blind rivers etc. which are not part of a flowing water system are captured as LAKE.
Examples
GREEN=STREAM CENTRE LINE
BLUE=STREAM EDGE
YELLOW=STREAM CENTRE LINE-Invisible
ORANGE=STREAM EDGE
LIGHT BLUE=LAKE-Fish pond
FOT 4.0.1 20091022
3.6.2.3
BLUE=STREAM EDGE
RED=HARBOUR-Stream
PINK-STIPPLED=STRUCTURE
BLACK-STIPPLED=ROAD CENTRE LINE-Invisible
GREEN=STREAM CENTRE LINE
GREEN with RED-stippled line=STREAM CENTRE LINE-Invisible
LIGHT BLUE=STREAM CENTRE LINE-Through lake
BLUE=STREAM EDGE
ORANGE=STREAM EDGE-Invisible
PURPLE=STRUCTURE
RED=BUILDING
RED-STIPPLED=HARBOUR-Lake
YELLOW=LAKE
BLACK-THICK=ROAD CENTRE LINE-Road
FOT 4.0.1 20091022
3.6.2.4
BLACK-THIN=ROAD CENTRE LINE-Path
BLACK-THICK-STIPPLED=ROAD CENTRE LINE-Path-invisible
FOT 4.0.1 20091022
3.6.2.5
DRAINAGE DITCH
Object group
HYDRO
Object type
DRAINAGE DITCH
Geometry type
Line
Min. size
50 m.
Area
3
Object definition
The middle of an open, artificial channel for water.
Name
Multiplicity
Type
Legal values
Change
triggers
history
Responsible
Origin
Representation
DRAINAGE DITCH represents the estimated middle of an artificial channel for draining roads, railways
etc.
Only isolated ditches with no link to a network are included. Ditches which are part of a network are
captured as STREAM CENTRE LINE.
DRAINAGE DITCHes with lengths < 50 metres are not captured.
New mapping
DRAINAGE DITCH is captured at the estimated mid-line of an artificial channel for draining roads,
railways etc. Height is captured at water level or at the bottom if the ditch is dry.
DRAINAGE DITCH is captured with as few points as possible. However, the difference between the
actual line and captured line should not exceed 0.5 metres in both plan and height.
Only DRAINAGE DITCHES within AREA TYPE POLYGON with TYPE=3 should be captured.
Only isolated ditches with no link to a STREAM CENTRE LINE are captured.
DRAINAGE DITCH cannot be captured internally in private gardens, camping sites, parks, green areas,
industrial sites, churchyards and metalled areas on housing estates.
DRAINAGE DITCH can be broken where it runs under a farm track, in a culvert under a road or the
like.
DRAINAGE DITCHes < 50 metres long are not captured.
Objects are captured from one node point to another.
DRAINAGE DITCHES have a node point where:
The object starts or ends.
DRAINAGE DITCH joins another DRAINAGE DITCH.
FOT 4.0.1 20091022
3.6.3 HYDRO-DRAINAGE DITCH
3.6.3.1
The object flows out into COASTLINE, HARBOUR or LAKE (with no connection to STREAM
CENTRE LINE)
Examples
LIGHT BLUE=DRAINAGE DITCHLIGHT BLUE=DRAINAGE DITCH
THICK BLUE=STREAM CENTRE LINE-Centre width 2.5-12
THIN BLUE=STREAM CENTRE LINE-Centre width 0-2.5
FOT 4.0.1 20091022
3.6.3 HYDRO-DRAINAGE DITCH
3.6.3.2
STREAM EDGE
Object group
HYDRO
Object type
STREAM EDGE
Geometry type
Line
Min. size
50 m.
Area
1 2 3
Object definition
The side delimitations of a stream.
Name
Multiplicity
Type
Legal values
WIDTH
[1..1]
Text
2.5-12
12-
VISIBLE_STREAM EDGE [1..1]
Boolean 0
1
Change
triggers
history
No
Responsible
Origin
KOM
KMS
Photogrammetric
capture or
administratively
entered.
No
KOM
KMS
WIDTH
Statement of stream width for one of the listed intervals.
VISIBLE_STREAM EDGE
A stream which cannot be seen photogrammetrically because it runs under a road bridge.
0 = STREAM EDGE is not visible.
1 = STREAM EDGE is visible.
Representation
STREAM EDGE is the side delimitation of a stream. Side delimitation is on the crown edge. Where
there is no crown edge, side delimitation is defined as the point at which the water surface meets the
land.
STREAM EDGE is found for all streams with a width of >= 2.5 metres. Stream width is determined by
the distance between the two stream edges.
STREAM EDGE has a length of > 50 metres.
New mapping
STREAM EDGE is captured on the crown edge if found, or on the water surface.
FOT 4.0.1 20091022
3.6.4 HYDRO-STREAM EDGE
3.6.4.1
Height is captured the same place as the plan location, i.e. on the crown edge or water surface
respectively.
STREAM EDGE is captured with as few points as possible, in such a way that the difference between
the actual line and the captured line does not exceed the following values:
AREA TYPE POLYGON,
Area type=
1
2
3
2
2
1
STREAM EDGE is captured down to a stream width of 2.5 metres, although capture should continue if
there is only a limited piece of a longer STREAM EDGE under the minimum width.
Statement of stream width for one of the listed intervals applicable for the full length of the object.
Guidance for width can be read here or by measuring the actual width.
Where STREAM CENTRE LINE runs through a LAKE, STREAM EDGE is not captured.
Where STREAM EDGE represents a stream which runs under a road or railway bridge, it is captured
under these objects using VISIBLE_STREAM EDGE=0 without snapping to them. A traffic artery in
this context is where traffic passes (captured on ROAD CENTRE LINE, SYSTEM LINE, RAILWAY or
STREAM CENTRE LINE).
STREAM EDGE for STREAM CENTRE LINE with a length < 50 metres and width < 2.5 metres and
which is isolated in relation to STREAM CENTRE LINE, LAKE, HARBOUR and COASTLINE are not
captured, unless designated administratively.
Where an open stream, delimited by STREAM EDGE, runs into a LAKE, HARBOUR or COASTLINE,
it is delimited from these by the object the stream runs into which is captured across the mouth of the
stream.
Where a narrow stream with no STREAM EDGE widens to a degree that it warrants STREAM EDGEs,
the STREAM EDGEs are captured as Invisible over the stream at that point.
Where a narrow stream with no STREAM EDGE runs into a larger stream with STREAM EDGE,
STREAM EDGE-Invisible is registered over the mouth of the narrow stream.
Where a stream with STREAM EDGE runs into a LAKE, HARBOUR or COASTLINE, STREAM
EDGE-Invisible has a common route with those objects in accordance with the common route form in
app. M.
Examples
GREEN=STREAM CENTRE LINE-Visible
PURPLE=STRUCTURE
FOT 4.0.1 20091022
3.6.4.2
FOT 4.0.1 20091022
3.6.4.3
There is no bridge here, and STREAM EDGE is therefore not plotted under the road
There is a bridge here and STREAM EDGE is plotted under the road as INVISIBLE.
FOT 4.0.1 20091022
3.6.4.4
PINK-STIPPLED=STRUCTURE
BLACK-STIPPLED=ROAD CENTRE LINE-Invisible
FOT 4.0.1 20091022
3.6.4.5
HARBOUR
Object group
HYDRO
Object type
HARBOUR
Geometry type
Line
Min. size
50 m
Area
1 2 3
Object definition
Structure on the boundary between land and water or isolated in the water.
Name
HARBOUR TYPE
Multiplicity
[1..1]
Type
Text
Legal values
Lake
Sea
Stream
Docking jetty
sible
history
No
KOM
KMS
Origin
Explicitly stated
when entered.
HARBOUR TYPE
Statement of harbour location using one of the listed values.
VALUE
MEANING
For HARBOURS located on the bank of a LAKE.
Lake
For HARBOURS located on the coast.
Sea
For HARBOURS located on the bank of a stream.
Stream
For HARBOURS which represent a large docking jetty in a harbour.
Docking jetty
Representation
HARBOUR represents a structure in the form of a quay, wharf, wave-breaking installation linked to a
harbour, mole, bedding, floating dock or the like, plus docking jetty within a harbour area.
HARBOUR < 50 metres are not represented.
New mapping
HARBOUR is captured on the boundary between land and water at the outer boundary to the water.
Height is captured on the land surface for vertical structures (e.g. quay edge or wharf). Height is captured
at water level for angled structures (e.g. groynes or concrete blocks).
HARBOUR is captured with as few points as possible, in such a way that the difference between the
actual line and the captured line does not exceed the degree of capture accuracy for the actual AREA
TYPE POLYGON.
Freestanding structures in water (for breaking waves in a harbour) are captured as structures at water
level, and at the middle of the object if wider than < 2 metres. Width is measured at water's edge.
All wave-breaking installations lying wholly or partially out of the water linked to a harbour are
included.
FOT 4.0.1 20091022
3.6.5 HYDRO-HARBOUR
3.6.5.1
Where a structure with a length along the water's edge is < 50 metres but is part of an overall
HARBOUR/STREAM EDGE or HARBOUR/COASTLINE route, STREAM EDGE or COASTLINE
should be captured respectively.
Several HARBOUR objects (min. 2) and COASTLINE objects which each have a length of < 50 metres
but which together have a combined length of > 50 metres are jointly captured as HARBOUR. If
COASTLINE in this instance represents the termination of a stream delimited by HARBOUR EDGE, the
route is captured as COASTLINE.
HARBOUR is captured unbroken under a bridge.
HARBOUR of HARBOUR TYPE=Sea must be snapped together with COASTLINE to represent
the collective boundary between sea and land.
Structures on the coastline are captured as HARBOUR (HARBOUR TYPE=Sea) with 2D/3D common
geography with COASTLINE.
Where there is a docking jetty or bathing bridge within a harbour with a width > 2 metres and a length >
50 metres, it is captured as HARBOUR with HARBOUR TYPE=Docking jetty. Objects which do not
fulfil minimum measurements are not captured.
Floating docks are captured as HARBOUR with HARBOUR TYPE=Docking jetty.
Structures on the edge of a LAKE which can be characterised as HARBOUR are captured as
HARBOUR (HARBOUR TYPE=Lake) with 2D common geometry with LAKE.
Structures on the edge of a stream which can be characterised as HARBOUR are captured as
HARBOUR (HARBOUR TYPE=Stream) with no common geometry with STREAM EDGE but with
2D/3D common end points.
Objects are captured from one node point to another.
HARBOUR has points where:
HARBOUR has node point where it meets COASTLINE, STREAM CENTRE LINE or STREAM
EDGE
Where a HARBOUR is not broken by COASTLINE, STREAM CENTRE LINE or STREAM
EDGE on an island, it is captured as an object with common start and end node points.
If the height difference between HARBOUR and COASTLINE is < 1 metre, a 3D node point is
created. In all other situations, a 2D node point is created.
Where STREAM CENTRE LINE flows into a HARBOUR, a 2D node point is created in both
objects
Where STREAM EDGE flows into a HARBOUR, a 3D node point is created in both objects
A 2D common point exists with an object from group BUILDINGS where it intersects
HARBOUR and stands on piles in the water as described in the table for intersecting lines.
HARBOUR continues unbroken under BUILDING and does not follow the overlying building
outline.
Examples
PURPLE=HARBOUR-Docking jetty
RED=HARBOUR-Sea
BLUE=COAST
FOT 4.0.1 20091022
3.6.5 HYDRO-HARBOUR
3.6.5.2
YELLOW=STREAM CENTRE LINE
ORANGE=STREAM EDGE
RED-STIPPLED=GROYNE
PURPLE-STIPPLED=HARBOUR-Stream
FOT 4.0.1 20091022
3.6.5 HYDRO-HARBOUR
3.6.5.3
FOT 4.0.1 20091022
3.6.5 HYDRO-HARBOUR
3.6.5.4
FOT 4.0.1 20091022
3.6.5 HYDRO-HARBOUR
3.6.5.5
COASTLINE
Object group
HYDRO
Object type
COASTLINE
Geometry type
Line
Min. size
50 m.
Area
1 2 3
Object definition
The boundary between the sea and land.
Name
Multiplicity
Type
Legal values
sible
history
Origin
Representation
COASTLINE represents the boundary line between sea and land whether natural or artificial with the
exception of that part of a harbour boundary which is classed as HARBOUR.
COASTLINE sections < 50 metres are not normally represented.
Permanent islands surrounded by the sea with an area > 100 m2 are also COASTLINE.
New mapping
COASTLINE is captured at the estimated naturally occurring boundary between sea and land as seen in
the photograph.
COASTLINE is captured with as few points as possible, in such a way that the difference between the
actual line and the captured line does not exceed 10 m in plan and 2 m in height.
COASTLINE is captured where the sea meets the land on beaches, cliffs, salt marshes or sea dykes
(dykes at the water's edge to prevent coastal erosion).
COASTLINE is captured across the mouths of streams where they flow into the sea.
COASTLINE is captured unbroken under bridges.
COASTLINE along with HARBOUR of HARBOUR TYPE=Sea represents the collective
boundary between sea and land.
COASTLINE sections < 50 metres are not captured unless COASTLINE represents the end of a stream
delimited by STREAM EDGE.
Several HARBOUR objects (min. 2) and COASTLINE objects which each have a length < 50 metres
but which collectively have a length of > 50 metres are jointly captured as HARBOUR, unless
COASTLINE represents the end of a stream delimited by STREAM EDGE.
FOT 4.0.1 20091022
3.6.6 HYDRO-COASTLINE
3.6.6.1
ISLANDS deemed to be permanent, (and not just consisting of reeds) and with an area of >= 100 m2, are
captured as COASTLINE.
Objects are captured from node point to node point HARBOUR where:
COASTLINE has points where:
COASTLINE has a node point where it meets HARBOUR, STREAM CENTRE LINE or
STREAM EDGE
COASTLINE is not broken by HARBOUR, STREAM CENTRE LINE or STREAM EDGE on
islands where it is captured as an object with common start and end node point.
If the height difference between COASTLINE and HARBOUR is < 1 metre, a 3D node point is
created. In all other situations, a 2D node point is created.
Where STREAM CENTRE LINE flows out to a COASTLINE, a 3D node point is created in both
objects
Where STREAM EDGE flows out to a COASTLINE, a 3D node point is created in both objects
A 2D common point exists with an object from group BUILDINGS where it intersects
COASTLINE and stands on piles in the water as described in the table for intersecting lines.
COASTLINE continues unbroken under BUILDING and does not follow the overlying building
outline.
Examples
BLUE=COASTLINE
RED-STIPPLED=GROYNES
RED=HARBOUR-Sea
FOT 4.0.1 20091022
3.6.6.2
FOT 4.0.1 20091022
3.6.6.3
JETTY_BATHINGBRIDGE
Object group
HYDRO
Object type
JETTY_BATHINGBRIDGE
Geometry type
Line
Min. size
1,2=25 m; 3=10 m
Area
1 2 3
Object definition
Structure built on piles in or out from the edge of a lake, stream or the coastline.
Name
Multiplicity
Type
Legal values
JETTY TYPE
[1..1]
Text
Bathing jetty
Boat jetty
LOCATION
[1..1]
Text
Lake
Stream
Sea
Change ResponOrigin
triggers
sible
history
No
KOM
Photogrammetric
KMS
captured or
administrative entry.
No
KOM
Photogrammetric
KMS
captured or
administrative entry.
JETTY TYPE
VALUE
MEANING
JETTY_BATHINGBRIDGE intended for bathing.
Bathing jetty
JETTY-BATHINGBRIDGE intended for mooring boats.
Boat jetty
LOCATION
VALUE
Lake
Stream
Sea
MEANING
JETTY-BATHINGBRIDGE located at the edge of or in a LAKE.
JETTY-BATHINGBRIDGE located at the edge of or in a stream.
JETTY-BATHINGBRIDGE located at the edge of or in the sea.
Representation
Minor isolated boat or bathing jetty.
New mapping
JETTY_BATHINGBRIDGE is captured on the estimate mid-line or outline. Height is captured on the
top.
JETTY_BATHINGBRIDGE is captured with as few points as possible, in such a way that the difference
between the actual data and the captured data does not exceed the following values in either plan or
height at any point.
AREA TYPE POLYGON,
Area type=
1
2
3
2
2
1
A bathing jetty is built on piles in a lake, stream or the sea and is primarily intended for bathing.
FOT 4.0.1 20091022
3.6.7 HYDRO-JETTY_BATHINGBRIDGE
3.6.7.1
A boat jetty is built on piles in a lake, stream or the sea and is primarily intended for mooring and for
embarking and disembarking to and from boats.
JETTY_BATHINGBRIDGE has the following minimum sizes which must be fulfilled before capture:
AREA TYPE POLYGON,
Area type=
Width in metres
Length in metres
1
2
3
1
25
1
25
1
10
JETTY_BATHINGBRIDGE less than the minimum size should not be captured.
Branches at a narrow JETTY_BATHINGBRIDGE must also abide the rules for minimum size in order
to be captured.
Branches at a wide JETTY_BATHINGBRIDGE are included in the registration regardless of their
length.
JETTY_BATHINGBRIDGES < 2 metres wide are captured along the mid-line otherwise around the
edge.
JETTY_BATHINGBRIDGES are not captured in a harbour areas.
Examples
BLUE=COASTLINE
PINK=JETTY_BATHINGBRIDGE
RED-STIPPLED=GROYNE
FOT 4.0.1 20091022
3.6.7 HYDRO-JETTY_BATHINGBRIDGE
3.6.7.2
3.7 ADMINISTRATIVE
HISTORICAL POINT
FOT 4.0.1 20091022
3.7 ADMINISTRATIVE
3.7.1
HISTORICAL POINT
Object group
ADMINISTRATIVE
Object type
HISTORICAL POINT
Geometry type
Point
Min. size
-
Area
1 2 3
Object definition
Visible historical structure.
Name
Multiplicity
HISTORICAL TYPE_FFP [1..1]
PARAGRAPH 4_FFP
[1..1]
PARAGRAPH 4_REF_FFP [0..1]
Type
Text
Legal values
Burial mound
Cairn
Passage grave
Rune stone
Ramparts
Settlement
Viking fort
Holy spring
Ruin
Not allocated
Unknown
Boolean 0
1
Text
Measurement board
sheet no. + serial no.
Change ResponOrigin
triggers
sible
history
No
KAS
Explicitly stated by
Kulturarvsstyrelsen
(KAS)-(National
Heritage) at
administrative entry
No
KAS
No
KAS
HISTORICAL TYPE_FFP
Stated using one of the show values.
PARAGRAPH 4_FFP
HISTORICAL POINT listed in the Kulturarvsstyrelsen's (KAS) register of preservation orders. The
environmental administration authority will handle the administrative designation in the course of
continuous administrative revision.
0 = HISTORICAL POINT not listed in the preservation order register.
1 = HISTORICAL POINT listed in the preservation order register.
PARAGRAPH 4_REF_FFP
A HISTORICAL POINT covered by the Nature Conservation Act has a link to a reference in the KAS
(National Heritage) preservation order register. The reference corresponds to the unique preservation
number allocated to each object in connection with its entry in the registered and consists of a
measurement board sheet number of 4 digits and a serial number.
Representation
HISTORICAL POINT listed in the KAS preservation order register.
HISTORICAL POINT is represented as a point in the centre of the structure. Height at ground level.
As a rule of thumb only historical structures < 2,500 m2 occur.
FOT 4.0.1 20091022
3.7.4 ADMINISTRATIVE-HISTORICAL POINT
3.7.4.1
New mapping
HISTORICAL POINT is captured as a point at the estimated centre of the structure. Height is captured at
ground level.
HISTORICAL POINTS are only captured for historical structures with an area < 2,500 m2.
Larger areas are captured as HISTORICAL AREAS.
Photogrammetric limitations
The above describes the general aspects of object type. Photogrammetric data capture from aerial
imagery, however, does not always completely comply with all these requirements. The following is a
description of the criteria photogrammetric work has to fulfil.
Only the following attributes and values are captured:
HISTORICAL TYPE. Where data from KAS states a HISTORICAL type, this is used.
Otherwise the value: Not allocated is allocated.
HISTORICAL POINT will in most cases have details of a §4 reference attached to the data received.
This data can be found in data field %D8000 (if the file is supplied in DSFL format)
When an object has a §4 references, it should be reused and saved under the correct attributes as follows:
PARAGRAPH 4 must be set to "1"
PARAGRAPH 4_REF must be set to the reference supplied for the object.
When the point does not have a reference, set:
PARAGRAPH 4 to "0"
PARAGRAPH 4_REF is not stated.
HISTORICAL TYPE is always set to Not allocated
The points are given the following origin:
%ND1 UU
%ND11 10
%ND12 10
%ND23 060101
%ND41 KMS 2006
Examples
To follow.
FOT 4.0.1 20091022
3.7.4 ADMINISTRATIVE-HISTORICAL POINT
3.7.4.2
4.0 APPENDIX
C Method_3D
I DSFL codes
L Within
M Common Geometry
N Attribute Check
FOT 4.0.1 20091022
4.0 APPENDIX
4.0.1
4.3 Appendix C: METHOD_3D
Method TK/FOT-roof
FOT 4.0.1 20091022
4.3 APPENDIX C
4.3.1
4.9 Appendix I: DSFL codes for FOT-4 objects and their properties
Object codes and D-fields in this list are not retrospectively compatible with data transfers from FOT-3
or earlier FOT specifications.
Object type
Property
BUILDINGS
BUILDING
Object code D-field
%KG4 %U91
Building type
D9111
D9112
D9113
D9114
D9151
D9115
D115
D9116
Tank/Silo_Type
Measurement point_Building
Method_3D
Under_Minimum_Building
BBR_Reference
Building_ID
Area quality
%KG4 %U92
BUILDING_BBRPOINT
Building_ID
D115
D9138
Placing_BBRpoint
BUILDING JUMP
BUILDING-SEPARATION
%KG4 %U481
%KG4 %U48
BUILDING AREA
TOWN CENTRE
COMMERCIAL AREA
LOW BUILDING AREA
HIGH BUILDING AREA
%KG6 %U53
%KG6 %U54
%KG6 %U51
%KG6 %U52
TRAFFIC
ROAD CENTRE LINE
%KG3 %U91
Road centre type
Startnode_Road
Endnode_Road
Road authority
CVF admnr
CPR municipality
CPR road code
Road class
Traffic type
Level
Surface
Road width
Place
Fictive
FOT 4.0.1 20091022
4.9 APPENDIX I
D9120
D9200
D9201
D9121
D1121
D111
D112
D9122
D9123
D9124
D9125
D9126
D9127
D9128
4.9.1
Access way
D9129
D9130
D9210
D9211
D9212
D9213
Roundabout
ParentFOTID
ParentFOTversion
Start
End
%KT5 %U11
SYSTEM LINE
Startnode_System
D9202
D9203
D9137
D1121
D111
D112
Endnode_System
Roadauthority_System
CVF admnr
CPR municipality
CPR road code
%KG3 %U611
RAILWAY
Track type
D9131
D9132
D9204
D9205
D9139
D9133
D9210
D9211
D9212
D9213
Owner_Railway
Startnode_Railway
Endnode_Railway
Level_Railway
Visible_Railway
ParentFOTID
ParentFOTversion
Start
End
%KG3 %U1
ROAD EDGE
Type
D9134
D9145
D9146
Surface_Roadedge
Visible_Roadedge
%KG3 %U17
%KG3 %U561
%KG3 %U51
TRAFFIC ISLAND
SPEED BUMP
CRASH BARRIER
Barrier type
D9135
%KG3 %U6
TRAIN HALT
Name
D9136
D9149
Owner_Train halt
TECHNICAL
TECHNICAL_AREA
%KG6 %U45
Area type
D9140
%KG3 %U71
RUNWAY
Runway type
D9187
%KG6 %U41
%KG4 %U54
CHURCHYARD
BASIN
Basin type
%KG8 %U37
%KG8 %U33
TELEMAST BASE
HIGH TENSION WIRE
FOUNDATION
FOT 4.0.1 20091022
D9141
4.9 APPENDIX I
4.9.2
%KG8 %U32
HIGH TENSION WIRE
Voltage
D9142
%KG4 %U7
%KG4 %U75
STRUCTURE
OTHER SMALL
STRUCTURES
GROYNE
PARKING
CHIMNEY
TELEMAST
%KG4 %U63
%KG3 %U24
%KG4 %U51
%KG8 %U363
Medium type
D9143
%KG8 %U74
WIND TURBINE
Building_ID
D115
%KG8 %U34
%KG8 %U12
%KG8 %U11
MAST
GULLY
MANHOLE
Hole type
D9144
%KG8 %U6
STATUE_HISTORICAL_ST
ONE
%KG8 %U2
NATURE
FOREST
%KG6 %U17
Owner_Forest
D9150
D9163
Under_Minimum_Forest
%KG6 %U14
HEATH
Heath type
D9152
D9164
Under_Minimum_Heath
%KG6 %U2
WETLAND
Under_Minimum_Wetland
D9165
%KG6 %U13
%KG6 %U31
%KG6 %U34
SCRUB_VEGETATION
SAND_DUNE
QUARRY
Quarry type
D9153
D9154
Quarry type
%KG5 %U1
FENCE
Fence type
D9188
%KG5 %U32
BOUNDARY LINE
Boundary line type
D9159
%KG5 %U7
SLOPE
Slope type
D9160
%KG5 %U17
DYKE
Dyke type
D9161
%KG8 %U551
TREE
Tree species
D9162
TREEGROUP
%KG8 %U55
HYDRO
LAKE
%KG5 %U51
FOT 4.0.1 20091022
4.9 APPENDIX I
4.9.3
Lake type
D9170
D9171
D9172
D9173
D9174
Salt_Lake
Temporary
Lake_Under_Minimum
Island_Under_Minimum
%KG5 %U44
STREAM CENTRE LINE
Stream type
D9175
D9206
D9207
D9189
D9176
D9177
D9178
D9179
D9180
D9181
D9182
D9147
D9210
D9211
D9212
D9213
Start node_Stream centre line
End node_Stream centre line
Direction
Network
Main stream
HR_VL_Code
HR_VL_Start
HR_VL_End
Centre width
Visible_Stream centre line
ParentFOTID
ParentFOTversion
Start
End
%KG5 %U46
%KG5 %U42
DRAINAGE DITCH
STREAM EDGE
Bank
D9183
D9148
Visible_stream edge
%KG5 %U93
HARBOUR
Harbour type
D9184
%KG5 %U61
%KG4 %U621
COASTLINE
JETTY_BATHINGBRIDGE
Jetty type
D9185
D9186
Location
ADMINISTRATIVE
TOWN POLYGON
%KG2 %U91
Town type
D9190
D9191
Building area code
%KG2 %U93
MUNICIPALITY
CPR municipality
D111
%KG8 %U601
HISTORICAL AREA
Memorial type_FFO
D9155
D9166
D9156
D9157
Under_Minimum_FFO
Paragraph 4_FFO
Paragraph 4_Ref_FFO
%KG8 %U602
HISTORICAL POINT
Memorial type_FFP
Paragraph 4_FFP
FOT 4.0.1 20091022
4.9 APPENDIX I
D9167
D9169
4.9.4
Paragraph 4_Ref_FFP
D9168
%KG2 %U92
PLACE NAME
Place name
D121
D9192
SNSOR_Code
MISCELLANEOUS
AREA TYPE POLYGON
%KA2 %U1
Area type
D9193
%KA2 %U2
ORTHO POLYGON
Ortho type
METAPOLYGON
CHANGE DESIGNATION,
point
CHANGE DESIGNATION,
line
CHANGE DESIGNATION,
surface
FOT 4.0.1 20091022
4.9 APPENDIX I
D9194
%KA2 %U3
%KA2 %U51
%KA2 %U52
%KA2 %U53
4.9.5
4.12 Appendix L: Within
This appendix is also found as an excel-file: 4-12 APPENDIX L Within_20091022
FOT 4.0.1 20091022
4.12 APPENDIX L
4.12.1
4.13 Appendix M: Common Geometry
This appendix is also found as an excel-file: 4-13 APPENDIX M Common_geometry_20091022
FOT 4.0.1 20091022
4.13 APPENDIX M
4.13.1
4.14 Appendix N: AttributCheck
This appendix is also found as an excel-file: 4-14 APP N FraProducent_SpecInfoSkema_FOT4v1.02
Here is an example:
FOT 4.0.1 20091022
4.14 APPENDIX N
4.14.1

Specification FOT 4.0.1 for NEW-capturing

Transcription

Similar documents

Welcome Visitors - Highlands Church of Christ

Fall 2015 - Friends of Tanzania

2 5 th anniversary edition

Defining Waterbodies: Davidsonville Wildlife Sanctuary

t-rmb er - Eel River Recovery Project

Systemic service value stream mapping. Application to a healthcare

Creekway Park is an opportunity to construct the

IQMediaMonitor - Video over IP Remote Monitoring Probe

IX. Basic specification

Gulf Stream Dwarf Nandina