Re:Show HN: Parsing horse racing charts with Apache PDFBox
by jahewson on Saturday July 08, 2017 @01:05AM
(#14724169)
PDFBox committer here, if you want even lower-level access to the page content stream, without anything 'clever' at all, check out the PDFGraphicsStreamEngine class, which is a superclass of the text extraction and rendering classes. Gives you access to the raw glyphs. You can override PageRenderer too, for visual debugging, e.g. render glyph bounding boxes. We have an interactive Swing PDFDebugger which does just that.
https://github.com/apache/pdfbox/blob/6f18d7c4bef4d23a22d/ex...
Re:Show HN: Parsing horse racing charts with Apache PDFBox
by joosters on Saturday July 08, 2017 @02:43PM
(#14726639)
Thanks for the guidance, I'll take a look.
Re:Show HN: Parsing horse racing charts with Apache PDFBox
by robinhowlett on Saturday July 08, 2017 @12:09AM
(#14724030)
Yes I encountered similar issues but many of them were able to be solved.
With PDFBox I was able to deal with the content at a very low level (on a per-character basis), so that when for instance building a String, I would insert a pipe character when the distance between adjacent characters was greater than the width of the space character and then detect that when translating to a certain field.
See the convertToText() method for an example: https://github.com/robinhowlett/chart-parser/blob/master/src...
and https://github.com/robinhowlett/chart-parser/blob/f8d651e9a1... for when I used this technique
Re:Show HN: Parsing horse racing charts with Apache PDFBox
by tcho on Saturday July 08, 2017 @12:23AM
(#14724071)
Very cool, good to see the level of control this package allows.
Re:Show HN: Parsing horse racing charts with Apache PDFBox
by bpicolo on Friday July 07, 2017 @06:48PM
(#14722823)
Huh, interesting. I was looking around for PDF libs previously and PDFBox didn't show up in google results. pdftk was the only one that showed up in Google results anywhere useful.
Edit: Looks like it's on the second page of results and I never made it that far, heh. Goes to show how biasing the first page of results is.
All PDF parsers that I have tried cope very badly with these kind of situations, and often try to be 'too clever' in that they value the final layout of the text over and above the individual strings.
Have you experienced similar problems with PDFBox, or does it handle formatting and layout fairly reliably?