It doesn't seem to do all that well on blueprint type line art.[1] It seems to do a lot better when it has areas to separate. Which is not surprising, considering the approach.
This is about as well as I was doing on scanned engineering drawings in 1983. I wrote Autodesk's CAD/Camera. 20 minutes of compute to process a drawing on an IBM PC/AT.
You can be too early. By now, a product in that space should be recognizing not just lines, but dimensions, and generating a properly dimensioned CAD model.
I can sympathize. In the early/mid-90s when Apple released QuickTimeVR, a buddy of mine and I tried to start an early VR real estate virtual tour company. Realtors of the time had no idea, and the internet was still too new for people to really grok the concept. Early DSLR writing to floppy disks just put that little cherry on top
Yes, yes you can. I worked on a project than included hardware are related workflow for digitizing analog input to essentially a digital image processing workflow, just because the digital sensors weren't quite there yet. A few years later, they were.
For the generation of simplified Bézier paths, I hope they consider the new methods in kurbo[1]. These have some fairly fancy math behind them and result in pretty close to a global optimum in terms of the minimal number of segments needed to hit an error target. They don't do implicit low-pass filtering, rather treat the input as a source of truth, but perhaps options could be added for that.
This is the best I've found as well. They also have a new offering (different internal model, similar quality evidently) that I've used back when it was in a free unlimited trial. Not sure the status right now:
https://vectorizer.ai/
There's a lot of handwritten texts out there. I spent a few months transcribing my great-great grandmother's journals as a military wife in the late 19the century. It was an enormous task - I'd spend an hour or two a week and got though a few dozen pages.
I used potrace and autotrace to darken the faded text strokes - I should give this a try and see if it can do a better job.
I had a similar idea the other day after fighting with inkscape tracing!
The problem with auto tracing is lack of content awareness so it's just shapes and colors leading to strange objects that require lots of tinkering.
I'm going to try it:
Use segment anything to get object masks, Trace each object separately and combine from there!
> Comparing to Potrace which only accept binarized inputs (Black & White pixmap), VTracer has an image processing pipeline which can handle colored high resolution scans. tl;dr: Potrace uses a O(n^2) fitting algorithm, whereas vtracer is entirely O(n).
What is the Big-O of the algorithm with Segment Anything or other segmentation approaches?
This is about as well as I was doing on scanned engineering drawings in 1983. I wrote Autodesk's CAD/Camera. 20 minutes of compute to process a drawing on an IBM PC/AT. You can be too early. By now, a product in that space should be recognizing not just lines, but dimensions, and generating a properly dimensioned CAD model.
[1] https://github.com/visioncortex/vtracer/blob/master/docs/ima...