Bug #1309: Registry: Changes in Spatial Coverage - Metacat - Ecoinformatics Redmine

Actions

Copy link

Bug #1309

closed

Registry: Changes in Spatial Coverage

Added by Saurabh Garg about 20 years ago. Updated almost 20 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Saurabh Garg

Category:

registry

Target version:

Postpone

Start date:

02/02/2004

Due date:

% Done:

Estimated time:

Bugzilla-Id:

1309

Description

1> Is the lat/long precision calculated correctly

2> Validate Lat/Long fields
1. 0-59 for minutes and seconds
2. No Negatives
3. 0-90 for Latitudes & 0-180 for Longitudes

Actions

Copy link

Updated by Saurabh Garg about 20 years ago

Fom Rick's comments in NceasReposSoftwareNotesFinal.doc

3) Within the ‘Spatial Coverage of Data’ section, Coordinates entry fields, it
is possible to enter numbers which are not valid for Latitude and Longitude:
For example, 0, -1, numbers < -90 and > 90 (for latitude) and numbers < -180 or

360 (for longitude). Suggest having these entry fields filter the inputs for

valid Latitude/Longitude.

Actions

Copy link

Updated by Saurabh Garg about 20 years ago

4) Fom Andrea's comments in NceasReposSoftwareNotesFinal.doc
Coordinate values were displayed with too many decimal places (see example
below):
Geographic Description: Flakaliden experimental site, Sweden
Bounding Coordinates:
West: 19.45 degrees
East: 19.45 degrees
North: 64.1166666666667 degrees
South: 64.1166666666667 degrees

Actions

Copy link