Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binarization creates 2 source files in target workspace #16

Closed
VolkerHartmann opened this issue Jun 19, 2018 · 3 comments
Closed

Binarization creates 2 source files in target workspace #16

VolkerHartmann opened this issue Jun 19, 2018 · 3 comments
Labels
bug Something isn't working

Comments

@VolkerHartmann
Copy link

VolkerHartmann commented Jun 19, 2018

While binarizing image to a new workspace two tifs will be created.
The filename of the image is not the filename of the given mets.xml!
It seems the filename of the METS file in the cache directory!?

(source) Files are stored in the root directory of the workspace and looks like this:
file.path.to.old.workspace.filename
and
file.path.to.new.workspace.file.path.to.old.workspace.filename

The original file (OCR-D-IMG/filename) is missing in the new workspace!
(Inside METS is a reference to the first file mentioned above!)
Steps:

ocrd workspace validate
ocrd workspace clone -a -m mets.xml
cd /tmp/pyocrd-'xyz'
ocrd-kraken-binarize -w /new/target/dir
@kba
Copy link
Member

kba commented Jun 19, 2018

These dot-separated files are the names come from the URL of the thing, e.g. file:///path/to/old/workspace/filename --> file.path.to.old.workspace.filename.

Nonetheless, things go wrong, need to debug this with a METS URL.

@kba
Copy link
Member

kba commented Jun 19, 2018

@kba
Copy link
Member

kba commented Dec 12, 2022

long out-of-date

@kba kba closed this as completed Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants