alt Hacker NewsOCR for construction documents does not work, we fixed it
So we've built an API and trained models that detects fixtures, extracts schedules, and analyzes construction documents. Check us out!
More examples: - https://www.getanchorgrid.com/developer/docs/endpoints/drawi...
Main website: - https://www.getanchorgrid.com/developer
Why we did it: https://www.getanchorgrid.com/developer/docs/changelog/const...
Comments
We’re taking a different path, building a parsing engine that converts CAD (DWG/DXF) into fully structured JSON with preserved semantics (no ML in the critical path).We also have a separate GIS parser that extracts vector data (features, layers, geometries) independently, Like to know how you handle consistency and reproducibility across runs using models and how you make it affordable, especially at scale. because as far as i know CAD and GIS need precision and accuracy.
I ran the example doors given and it missed 9 swinging doors, some that were in double swing pairs, and a few that were just out on their own not clustered. Not bad overall though
OCR accuracy on technical documents is one of those problems that looks 95% solved until you hit the edge cases. Construction docs are especially tricky because of mixed handwriting, stamps, revision clouds, and poor scan quality. Curious how you handle multi-language documents — a lot of international construction projects have specs in two or three languages on the same page.
Looks cool! Where are you getting the data to finetune the cv models for element extraction? I'm worried there isn't a robust enough dataset to be able to build a detection model that will generalize to all of the slightly different standards each discipline (and each firm for that matter) use.
What do you foresee being the end use case for this (or most valuable use case)?
When will this be available for 30000x8000px electrical diagrams?
I have to make a BOM and oh boy I hate my job
Great points raised!
Love it! Starbucks Vente Machiato sip
Love to give it to an arc client, not sure who the right person to implement this would be? Hmm…
Of course it is not working. PDF and images are supposed to be tamper resistant. OCR tries to reverse engineer them.
Your smart features looks like a game changer? Nice job!
> OCR for construction documents does not work
I'm reminded of the Xerox JBIG2 bug back in ~2013, where certain scan settings could silently replace numbers inside documents, and bad construction-plans were one of the cases that led to it being discovered. [0]
It wasn't overt OCR per se, end-user users weren't intending to convert pixels to characters or vice-versa.
[0] https://www.youtube.com/watch?v=c0O6UXrOZJo&t=6m03s