The World's Premier Listing Software
for Birders and Naturalists!
Celebrating 22 Years Serving Birders
and Naturalists around the World!
At present I enter latitude & longitude in the comments field of the location table however this risks formatting errors, particularly if it is necessary to enter other comments.
Entering this data in user defined fields on the sightings table has the disadvantage that it must be entered with each observation.
This data is logically linked to the location but should not be a mandatory field.
Thanks for posting this.
The problem with assigning a Lat/Long to a location is that it is not a good definition. A location requires a polygon to define it typically; e.g. city, park, county, etc.
Whereas a sighting is a specific lat/long.
Not the answer you were looking for just a bit of history as to why it is this way currently.
Where do you need this data displayed and output? View/Edit window; reports?
The new fields should go on the Add/Edit Locations window, preferably in the top half. Fields should be optional with degrees in the range 0 - 180, Minutes & seconds in the range 0 - 59. If degrees = 180 then minutes & seconds must be 0. Direction must be 'E', 'W' for longitude, 'N', 'S' for latitude.
The reports to display the fields on are Sightings Report and Trip Report. Include these fields in the selection of output columns for the report. Both these reports already display 'Location'.
Above you mention formatting for Lat/Long. My plan is just to make it a free-format text field; you pick the format you want to use instead of me forcing one on the users. Do you see a problem with that?
This new feature will be in Build 36 and later of v5.0.
I will get this released this weekend sometime.
Thanks for the input.