Google2Csv is a simple Google scraper that saves the results on a CSV file
github.com
github.com
For my thesis which required millions of datapoints, I used this tool: http://www.scrapebox.com/
Unless the file uses the actual ASCII record separator you'll end up with a CSV file which can only be read by a handful of software, after telling it explicitly what the separator and quoting rules are. And even then it's hit or miss. And likely it does not use the RS because even though the chances it's unambiguous greatly increase and the RS was actually meant for that, software doesn't typically use it because when CSV was invented it's existence was unknown or ignored beacue it's not human readable (I guess, don't really know actually) and so the sad story began.
As you can see: I'm not a fan of CSV :) Just today I again had to waste time because at one point in the development of this otherwise fine piece of software I'm working on - even though I knew I'd regret it - I allowed it to export CSV files. Customer moved software to another machine, forgot that they once told the CSV exporter part to use the system settings, and now has CSV files with a comma separator (you know, the C in CSV). Oh the irony, that's not what they wanted.
The existence of software that produces braindead CSVs is beside the point. Don't use that software. Just do the above and everything will work.
If you're writing an (en|de)coder for a specific or limited target, then sure it's fine. Otherwise I would steer clear of it.
This exactly is part of the problem: how many people do you think would come up with this specific specification? You do realize in real life CSV gets used for anything which is plain text and separated and perhaps even quoted? Also 'should be' UTF-8? By what authority?
The existence of software that produces braindead CSVs is beside the point.
No, it is not. Especially not because there's so much software. And because it's not braindead, it's just doing something else. Which is bascially fine since there's no standard.
Just do the above and everything will work.
Yes, in your personal bubble. Beyond that it's totally insufficient.
It would be easy to use CSV if you never did any data interchange with it.
IANAL, can someone please elaborate? This sounds wrong in several ways, one of which being that Google results are almost exclusively scraped from somewhere else already.
(Isn’t it weird they don’t offer this already? Makes you think.)
Based on the LinkedIn case my guess is no, because it could be considered "generally public". But that ruling is highly suspect and likely to go to the supreme court, imo.
Have you run into issues with getting blocked by Google / issued captchas?
My work around is to run in on the cloud with multiple IPs, so I just switch between. Mine's a one time thing so this is workable.
If you're querying for news, Reddit might be a wise choice, they have quite a bit of free APIs afaik.