Project

General

Profile

Bug #1309

Registry: Changes in Spatial Coverage

Added by Saurabh Garg almost 16 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
registry
Target version:
Start date:
02/02/2004
Due date:
% Done:

0%

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

History

#1 Updated by Saurabh Garg almost 16 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.

#2 Updated by Saurabh Garg almost 16 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

#3 Updated by Saurabh Garg over 15 years ago

Fixed.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 1309

Also available in: Atom PDF