Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Setup your Forum photo and profile here.
While exporting locations works fine as is, I really would like it also to include the Latitude and Longitude that I have entered for each location. As now implemented, when I export the locations to another database, I can no longer map sightings.
Bert Frenz
Hi Bert,
I did implement this back in v5.2.44.
However, I now see that a bug prevents the lat/lng from getting imported properly.
This is fixed in Build 19 of v5.3.
Thanks for reporting this.
With the fixed version, if I export from one database and import into another database that already has the location names but not the lat/long will it update those locations with lat/long?
if I export from one database and import into another database that already has the location names but not the lat/long will it update those locations with lat/long?
No, it does not. I find myself sitting here puzzling over whether that would be the correct thing to do. It could have unintended consequences.
I understand your need, I am just trying to figure out if that makes sense for the other 99.9% of BD users that do not have multiple databases.
Your thoughts?
If someone does not have multiple databases, why would they import locations from a file created by BD? If they are giving their export file to another user who wants the location data, why would that user not want the lat/lon as well? Also, importing the lat/lon only would effect the locations, not any sightings.
Agreed. Fixing.
Does that go for Description, Habitat and Comments. Update all of these on import?
Latest Post: Error Message 3420 Our newest member: jenreddington Recent Posts Unread Posts
