42 lines
1.0 KiB
Plaintext
42 lines
1.0 KiB
Plaintext
head 1.1;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
expand @o@;
|
|
|
|
|
|
1.1
|
|
date 2006.07.10.15.29.15; author SteveKelling; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="SteveKelling" date="1152545355" format="1.1" version="1.1"}%
|
|
%META:TOPICPARENT{name="WebHome"}%
|
|
|
|
|
|
|
|
|
|
-- Main.SteveKelling - 10 Jul 2006
|
|
|
|
From Lynn Kutner's Document:
|
|
|
|
Location:
|
|
|
|
Ideally, at least geocoordinates plus an accuracy term. Since there is a considerable amount of historical / legacy data that does not presently have a georeference yet has valuable information that should be included in observation databases and shared, we cannot at this time require data to be in a GIS format.
|
|
|
|
Suggest:
|
|
a) Location information be required, preferably geocoordinates and mapping precision, but if not available then a text description and the finest level of geolocation using the Darwin Core attributes.
|
|
b) Location data include the representation of observations as point, line, or polygon data (with the necessary spatial metadata).@
|