This was reported by Dave Watts (Dave.Watts AT aad.gov.au).
We have a number of problems with the consistency of the formatting of
coordinate values.
On the tabular views we format the interpreted values from the
OccurrenceRecord and frequently end up with ridiculous values as a result
of rounding in the float values.
On the occurrence detail page we show whatever the original data provider
supplied (from the RawOccurrenceRecord).
The use of the different values in the different contexts is probably
sensible and appropriate, but we should make sure that we do not suggest
ridiculous precision in the tabular view.
Dave has suggested that we use the associated precision value, where
present, to determine how many decimal places are appropriate. We should
presumably select a configurable default precision (e.g. 1km) for use in
cases where none is supplied.
From Dave's e-mail:
Since many of the records should have a coordinate precision in metres,
then that could give a better sense of the number of decimals place to
display the latitude or longitude.
One degree in latitude is about 120km implies then at 5 decimals places (eg
-67.67896) you have a position to 1.2 metres. So for 500 metres in a
position error then a display of 3 decimals places would suffice.
Original issue reported on code.google.com by josecua...@gmail.com on 31 Jul 2009 at 1:18
Original issue reported on code.google.com by
josecua...@gmail.comon 31 Jul 2009 at 1:18