You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Specify Data Exporter exports the Lat1Text and Long1Text values instead of using the decimal format in the Latitude1 and Longitude1 fields. For example, when exporting catalog number 000068515, the Lat1Text field displays the latitude in decimal degree format as '38.503253° N', which is correctly represented in the exported data as decimalLongitude: 38.503253. However, when exporting catalog number 000086813, where the Lat1Text field is in degrees, minutes, and seconds (DMS) format like 20° 50' 00.0" N, the exported decimalLongitude erroneously shows 205000.0.
Specify is incorrectly exporting the text coordinate values instead of exporting the decimal coordinate values. It assumes that the value is a decimal value when it, in fact, can be DMS or other supported entry formats. If you put the decimal lat and long values into the lat1text and long1text fields, the issue is resolved.
Reported By: PRI Paleo
The text was updated successfully, but these errors were encountered:
The Specify Data Exporter exports the
Lat1Text
andLong1Text
values instead of using the decimal format in theLatitude1
andLongitude1
fields. For example, when exporting catalog number000068515
, theLat1Text
field displays the latitude in decimal degree format as '38.503253° N', which is correctly represented in the exported data asdecimalLongitude: 38.503253
. However, when exporting catalog number000086813
, where theLat1Text
field is in degrees, minutes, and seconds (DMS) format like20° 50' 00.0" N
, the exporteddecimalLongitude
erroneously shows205000.0
.Specify is incorrectly exporting the text coordinate values instead of exporting the decimal coordinate values. It assumes that the value is a decimal value when it, in fact, can be DMS or other supported entry formats. If you put the decimal lat and long values into the lat1text and long1text fields, the issue is resolved.
Reported By: PRI Paleo
The text was updated successfully, but these errors were encountered: