4 ms·
chart recognition and OCR in general would make UGC sites, in particular wikipedia, much more powerful. wikipedia is full of uploaded charts that should be data
by awinter-py 7y ago
chart recognition and OCR in general would make UGC sites, in particular wikipedia, much more powerful. wikipedia is full of uploaded charts that should be datasets.
in general chart sharing on the web is bad. If we can't have a <chart> element, maybe chart parsing is the next best thing to preserve some of the original information
- ygra 7y agoI think Wikipedia has macros that allow you to create a variety of charts with just textual information. I've seen at least timelines and family trees being created that way. The benefit is that it's text-editable, and the information is still accessible. In some cases, the markup is very, very unreadable, though and might actually be tool-generated. It still maintains the benefits in theory. For things that are trivial in SVG or even HTML, like bar or line charts, there should be little to no excuse not to use markup, agreed. In this case, we've concentrated on parsing graphs, though, as that's our main line of work (you could draw charts with yFiles, but it's not really that useful for it). We're still trying to find the time to clean up our code and publish it somewhere. This has been just a week-long effort by four people, but was definitely a fun learning experience.