Reverse geocoding fails

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Reverse geocoding fails

cool.chris65

Hi,

 

I just tried to tag some hundreds of pics in several folders with places by using reverse geocoding, but in some cases it fails with a message like this in the terminal:

----------------------- 8-< -----------------------

digikam.geoiface: ----
digikam.geoiface: ----
digikam.geoiface: "created cluster 0: 20 tiles"
digikam.geoiface: "level 5: 20 non empty tiles sorted into 1 clusters (20 searched)"
digikam.geoiface: "created cluster 0: 20 tiles"
digikam.geoiface: "level 5: 20 non empty tiles sorted into 1 clusters (20 searched)"
digikam.geoiface: ----
digikam.geoiface: ----
digikam.dbengine: Failure executing query:
"INSERT INTO Tags(name, pid, lft, rgt) VALUES(?, ?, @myLeft + 1, @myLeft + 2);"  
Error messages: "QMYSQL3: Der Befehl konnte nicht ausgeführt werden" "Duplicate entry '342-Landkreis Aurich' for key 'pid'" 1062 2  
Bound values:  (QVariant(QString, "Landkreis Aurich"), QVariant(int, 342))
digikam.dbengine: Error while executing DBAction [ "InsertTag" ] Statement [ "INSERT INTO Tags(name, pid, lft, rgt) VALUES(:tagname, :tagPID, @myLeft + 1, @myLeft + 2);" ]

----------------------- 8-< -----------------------
I saw this problem since today only if I tried to tag all pics in a folder - if I just mark and tag just one or two lines (about 15 to 20 pics) there where no problem.

 

Greets, Christoph
--

GPG-Fingerabdruck: B578 8557 B9B1 354B 3A91 1CC0 5E3C 7538 7C91 0837

GPG-Kennung: 7C910837

Reply | Threaded
Open this post in threaded view
|

Re: Reverse geocoding fails

cool.chris65

Sorry,

 

I forgot some system-infos:

 

Using DK 5.3.0 from 64bits ApppImage under (K)Ubuntu 16.04 with all fixes; parallel there is a DK 5.2.0-installation on my hdd from ppa.

 

Using a system with iCore3, 16 gb Ram, 500gb SSD (system) and

Database is stored on a Openmediavault-NAS (v3) with mysql-server, also the pics are stored there on a 12TB-Raid5. All metadata allways stored in xmp-sidecar-files, too.

 

Now I got a different error by reverse geotagging just about 15 pic where it looks just that dk is doing nothing anymore ... in terminal it looks like this:

----------------------- 8-< -----------------------

digikam.metaengine: Metadata for file "IMG_1262_20161023_T120329.JPG" written to file.
digikam.metaengine: Will write XMP sidecar for file "IMG_1262_20161023_T120329.JPG"
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: wroteComment:  false
digikam.metaengine: wroteEXIF:  true
digikam.metaengine: wroteIPTC:  true
digikam.metaengine: wroteXMP:  true
digikam.metaengine: Metadata for file "IMG_1260_20161023_T120214.JPG" written to XMP sidecar.
digikam.metaengine: Metadata for file "IMG_1261_20161023_T120319.JPG" written to XMP sidecar.
digikam.metaengine: Metadata for file "IMG_1262_20161023_T120329.JPG" written to XMP sidecar.

----------------------- 8-< -----------------------

 

Greets, Christoph

 

Am Montag, 31. Oktober 2016, 20:05:37 CET schrieb [hidden email]:

> Hi,

>

> I just tried to tag some hundreds of pics in several folders with places by

> using reverse geocoding, but in some cases it fails with a message like

> this in the terminal: ----------------------- 8-< -----------------------

> digikam.geoiface: ----

>

> ----------------------- 8-< -----------------------

>

>

> Greets, Christoph--

> */GPG-Fingerabdruck: B578 8557 B9B1 354B 3A91 1CC0 5E3C 7538 7C91 0837/*

> */GPG-Kennung: 7C910837/*

 


--

GPG-Fingerabdruck: B578 8557 B9B1 354B 3A91 1CC0 5E3C 7538 7C91 0837

GPG-Kennung: 7C910837