Database Reference
In-Depth Information
TABLE 7.1
Table Describing the Data Structure of Merea Maps' Administrative
Geographical Information
Field Name
Field Full Name
Example
Comments for the RDFS Ontology
F_ID
Feature ID
000123
A unique ID that can be used to generate the URI.
DEF_NAME
Definitive name
Ash Fleet
Parish
“Definitive” is not an appropriate description in a
decentralized Web world. Merea Maps will just
use “Name” as the namespace will demonstrate
that it is they who have coined the name.
DEG_LAT
Degrees of Latitude
54
Merea Maps decides to reuse the Basic Geo
(WGS84) vocabulary
a
that defines latitude and
longitude and is used by many other Linked
Data sets, so these fields will be combined.
MIN_LAT
Minutes of Latitude
2.7
DEG_LONG
Degrees of Longitude
0
These fields will be combined.
MIN_LONG
Minutes of Longitude
13.2
X
Local X coordinate
462500
Outside scope
Y
Local Y coordinate
516500
Outside scope
Type
Type
Parish
This is actually the class to which the instance
in this row belongs.
F_NAME
Filename
Medina
County
This refers to the name of the file in which the
polygon information is stored. In Merea Maps'
case, the files are named according to the
administrative area that contains the instance.
PID
Polygon ID
12345
A reference to the polygon in the file.
Merea Maps
could
use this unique ID to
form the URI; however, it identifies the
spatial footprint, not the object itself, so it
would be misleading to do so.
MAP_NO
Map number
647
Corresponds to Merea Maps' paper products.
Outside scope.
TILE_NO
Tile number
839
Corresponds to Merea Maps' raster data product.
Outside scope.
M_CODE
Merea Feature code
C
An internal code that is not needed.
E_DATE
Edit date
13-06-2001
When the data was collected and input to the
system. This is useful but should be metadata,
which we will discuss elsewhere.
UPDATE_CO
Update code
P
An internal code for Merea Maps indicating
when the data should next be checked for
accuracy. We could choose to include an
“expiry date” on our data, but instead follow
the convention of assuming it is in date unless
deprecation is specifically noted. So, this is
out of scope.
