{"id":1187,"date":"2016-10-30T18:22:06","date_gmt":"2016-10-30T22:22:06","guid":{"rendered":"http:\/\/www.craigperler.com\/blog\/?p=1187"},"modified":"2024-06-06T23:25:25","modified_gmt":"2024-06-07T03:25:25","slug":"web-scraping-part-2-parsing","status":"publish","type":"post","link":"https:\/\/www.craigperler.com\/blog\/2016\/10\/30\/web-scraping-part-2-parsing\/","title":{"rendered":"Web Scraping, Part 2: Parsing"},"content":{"rendered":"
\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

In the last post<\/a>, we saw that many times the web page you request is not the page you receive. Similarly, often the page you’ve downloaded looks nothing like the page you end up viewing. When you download a web page, your browser executes scripts that transform the raw content into something entirely different. Consequently, the task of parsing web content from a received HTTP response is often not as straightforward as splitting strings.<\/p>\n\n\n\n

A Quick Demo<\/h2>\n\n\n\n

Open up a new tab and head to Google<\/a>. Click in your browser’s URL box, enter the following line, and press Enter.  (Note that some browsers might not let you copy\/paste this as-is, so double-check that your pasted version actually includes the “javascript:” part.)
javascript: (function() {document.getElementById('hplogo').srcset = 'https:\/\/upload.wikimedia.org\/wikipedia\/commons\/2\/24\/Yahoo%21_logo.svg';})();<\/code><\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Hopefully this isn’t too surprising, but let’s recap: we downloaded a page from Google, we ran a script, and now we have Google search with a Yahoo logo.  The point is that your browser can and will run all sorts of scripts that change what you see, making the simple task of parsing HTML into one that can be much more complex.<\/p>\n\n\n\n

As the browser reads web pages and evaluates styles and scripts, it builds up a hierarchical representation of all the elements on the page known as the Document Object Model<\/a> (the DOM).  The DOM is dynamic, and holds a lot more detail than what’s actually visible in your browser.  This is important to understand, because when you are scraping a web page, sometimes you need to parse the raw HTML from your request, aka the source; but sometimes, you need to parse the DOM.<\/p>\n\n\n\n

Browser Diagnostics<\/h2>\n\n\n\n

By far, the best tools for exploring the source and DOM are your browser’s own developer diagnostics.  Each major browser comes packaged with or offers a developer panel, a way for folks who are building websites to debug them.  Chrome has Developer Tools<\/a>; Firefox has Toolbox<\/a>; IE\/Edge has F12 Tools<\/a>; Safari has an Inspector<\/a>.  For this post (and all future posts on the subject), I’ll be referring to Chrome’s toolbox.<\/p>\n\n\n\n

In Chrome, open up a new tab, and head again to Google<\/a>. \u00a0Now, right-click on the page (anywhere except the Google logo image) and select View Page Source (also available from the View -> Developer -> View Source menu). \u00a0You now see the raw HTML your browser retrieves when accessing http:\\\\www.google.com – there’s a bit of HTML, and a lot of JavaScript, all of which your browser has executed.<\/p>\n\n\n\n

Search the page for hplogo<\/em> – you should see one occurrence, as (at the time of this writing) this is the id for the main logo’s image element:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Inspecting the Source<\/span><\/h3>\n\n\n\n

We can see that Google is using an image srcset<\/a> to determine which image to show, picking, at least in my case, https:\/\/www.google.com\/images\/branding\/googlelogo\/2x\/googlelogo_color_272x92dp.png<\/a>.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

 Now, head back to the logo image, right-click on it, and select Inspect, which will bring up Chrome’s view of the DOM, highlighting the logo image we just found in the source page.  No surprises here – the detail matches exactly what we saw in the source.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

So far, so good.  Now, go ahead and re-run the bit of code from earlier in the post, converting the Google logo into a Yahoo one.  The DOM should now show your new image src – the DOM always reflects the current state of the page.  If, however, you re-view the page source, that will remain unchanged, as that simply shows the initial content your browser downloaded.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

I’m belaboring the point because it’s important: the Python libraries we used in the prior post to retrieve the web page only give us access to the source; they do not construct a document object model, they do not retrieve linked styles or scripts, and they do not execute any JavaScript.  In many cases, the data you want is in the DOM, and in those cases you need to do more work to get at it.<\/p>\n\n\n\n

We’ll be covering parsing the DOM in future posts; for the remainder of this one, let’s dig a bit into parsing the source, the raw HTML.<\/p>\n\n\n\n

Parsing HTML<\/h2>\n\n\n\n

An HTML document is really just some text that usually conforms to the HTML standard<\/a>. \u00a0Many web pages loosely conform to the HTML standard, and many others don’t conform at all. \u00a0Most browsers are smart enough to deal with poorly written HTML. \u00a0As HTML is just structured text, regular expressions<\/a> in many cases can extract the content of interest. \u00a0For example, even\u00a0on the shittiest of web pages, anchor elements<\/a> still contain links.<\/p>\n\n\n\n

Let’s again use the exercise of figuring out the titles of the posts on my blog’s landing page.  Python makes regex very easy – the hard part is constructing the right expression.<\/p>\n\n\n

\nimport urllib2\nimport re\n\nhtml = urllib2.urlopen('http:\/\/www.craigperler.com').read()\n\nre.findall(r'<a.*www.craigperler.com\/blog\/2.*>([A-Za-z]+[A-Za-z1-9 ]+)<\/a>', html)\n'''['On Web Scraping',\n'Tracking Personal Finances',\n'Better Babies',\n'I Type Faster Than You',\n'Side Projects',\n'Plumbing and Coding',\n'On Web Scraping',\n'Tracking Personal Finances',\n'Better Babies',\n'I Type Faster Than You']'''\n<\/pre><\/div>\n\n\n
Deconstructing that regex, it says to:<\/p>\n\n\n\n
  1. Find any text that starts with “<a”<\/li>
  2. That is followed by any characters which must be followed by the text “www.craigperler.com\/blog\/2”<\/li>
  3. Which is then followed by any characters which must then be followed by “>”<\/li>
  4. Thereafter, we capture a group, where the captured text must start with a letter [A-Za-z], but can be followed by a letter, number or space [A-Za-z1-9 ]<\/li>
  5. And the group must be followed by “<\/a>”<\/li><\/ol>\n\n\n\n
    Regex does the job… in this very simple case. What if we wanted to grab any blog post title on the landing page that’s tagged with “python” or “development”? Figuring out the regex for this would be a tremendous task. Of course, there are better ways for parsing data from HTML or HTML-like content.<\/p>\n\n\n\n
    Parsing Libraries<\/h2>\n\n\n\n
    There are two main libraries when it comes to HTML parsing: lxml<\/a>\u00a0and\u00a0BeautifulSoup<\/a>. \u00a0There’s a lot of overlap across the libraries, and in general, each provides an API that wraps the others. \u00a0There are differences in performance<\/a> and probably in some edge case behaviors<\/a>, but in general the choice in package is a matter of preference (IMO). With all of these libraries, there are a couple ways of accomplishing the same goal. A few highlights are below.<\/p>\n\n\n\n
    LXML<\/h3>\n\n\n\n
    One approach with LXML is using XPath to traverse the document. XPath<\/a> is a language for querying an XML document, and as well-structured HTML follows an XML-defined schema, we can often use XPath as a way of parsing HTML. With XPath, we use the HTML tags and attributes to move throughout the document and pull out the fields of interest. In the following example, we use the XPath string, “\/\/a[@itemprop=’mainEntityOfPage’]\/text()<\/em>“.  This means, starting from the root of the document, find all anchor tags that have an itemprop attribute that contains only the value “mainEntityOfPage”, and from each of those tags, pull out the contained text.  This XPath relies on the fact that each of the landing page blog post links have that itemprop attribute, something we can only know from looking at the page source or inspecting the blog.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    <\/p>\n\n\n
    \nimport urllib2\nresponse = urllib2.urlopen('http:\/\/www.craigperler.com')\n\n# Build a document tree representation of the HTML content:\nfrom lxml import etree\ntree = etree.parse(response, etree.HTMLParser())\n\n# Use xpath to find the \"nodes\" of interest:\ntree.xpath(\"\/\/a[@itemprop='mainEntityOfPage']\/text()\")\n'''['Web Scraping, Part 1',\n 'On Web Scraping',\n 'Tracking Personal Finances',\n 'ProjectSHERPA: a startup retrospective',\n 'Better Babies',\n 'Can Yelp Reviews Predict Real Estate Prices?',\n 'I Type Faster Than You',\n u'Don\\u2019t Look at My Baby',\n 'Side Projects',\n 'Plumbing and Coding']'''\n<\/pre><\/div>\n\n\n
    One thing to note here is that we get more posts back than the regex method.  This is because our regex pattern was not accounting for unicode characters, so it didn’t find the “Don’t Look at My Baby” link, which has the unicode apostrophe (\\u2019<\/a>).  The XPath doesn’t care what characters are in the text – it’s just more forgiving than our very specific regex pattern.<\/p>\n\n\n\n
    CSS Selector<\/h4>\n\n\n\n
    Another option with LXML is to use a CSS selector.  CSS defines how to apply styling to HTML content; CSS selectors<\/a> are a way of identifying the elements to which a given styling rule should apply.  So, just like XPath can find the part of the document that has the content we want, CSS selectors can do the same.  We can use the same itemprop with CSS selectors by querying for “a[itemprop=’mainEntityOfPage’]<\/em>“.  This means the same thing as it did earlier, but uses a different syntax.  The code looks like:<\/p>\n\n\n
    \nimport urllib2\nresponse = urllib2.urlopen('http:\/\/www.craigperler.com')\n\n# Build a document tree representation of the HTML content:\nfrom lxml import etree\ntree = etree.parse(response, etree.HTMLParser()) \n\n# Use CSS to select the tags of interest:\nfrom lxml.cssselect import CSSSelector\nselector = CSSSelector('a[itemprop=\"mainEntityOfPage\"]')\n\n# Print out the text attribute of each selected HTML tag:\n[element.text for element in selector(tree)]\n<\/pre><\/div>\n\n\n
    BeautifulSoup<\/h3>\n\n\n\n
    BeautifulSoup doesn’t offer an XPath option, but does support a subset of CSS selection in addition to its own API.<\/p>\n\n\n
    \nimport urllib2\nresponse = urllib2.urlopen('http:\/\/www.craigperler.com').read()\n\n# Make the soup (wrap the HTML response in a BeautifulSoup instance):\nfrom bs4 import BeautifulSoup\nsoup = BeautifulSoup(response)\n\n# Pull out the links using CSS selection:\nlinks = soup.select('a[itemprop=\"mainEntityOfPage\"]')\n[link.text for link in links]\n<\/pre><\/div>\n\n\n
    It also offers its own API that may or may not be more intuitive depending on your tastes:<\/p>\n\n\n
    \nimport urllib2\nresponse = urllib2.urlopen('http:\/\/www.craigperler.com').read()\n\n# Make the soup (wrap the HTML response in a BeautifulSoup instance):\nfrom bs4 import BeautifulSoup\nsoup = BeautifulSoup(response)\n\n# Use the soup's findAll call to retrieve the links:\nlinks = soup.findAll('a', itemprop='mainEntityOfPage')\n[link.text for link in links]\n<\/pre><\/div>\n\n\n
    Using XPath, CSS, and regex, it’s possible to identify and extract most elements in a well-structured web page. There are of course cases where the authors obfuscate pages, which require more involved approaches.<\/p>\n\n\n\n
    That said, simply knowing how to retrieve and parse web pages, you can get stuff done with web scraping. We can build a very rudimentary web crawler that will analyze a page for links, and then traverse those related pages for more links, until an entire site has been exhaustively searched. This is a recursive or iterative process – as each page is scraped, we need to re-run the scraping process on all of the related links of interest.<\/p>\n\n\n\n
    A Complete Parsing Example<\/h2>\n\n\n\n
    The following bit of code will crawl through my entire blog site, starting with the landing page. With each scraped page, it will identify all other links that point to places on my blog, and will build a dictionary that holds link relationships (which page points to which other pages).<\/p>\n\n\n
    \nimport urllib2\nfrom lxml import etree\n\n# The starting URL for the crawler:\nstart_url = 'http:\/\/craigperler.com'\n\n# Given a URL, return a list of all the links that point to other pages on my blog.\n# Uses XPath to filter only links on craigperler.com\/blog.\ndef get_links(url):\n    try:\n        response = urllib2.urlopen(url)\n        tree = etree.parse(response, etree.HTMLParser())\n        return tree.xpath(\"\/\/a[contains(@href, 'craigperler.com\/blog')]\/@href\")\n    except Exception as e:\n        # Some linked pages on my site such as MIDI files aren't retrievable or parse-able in this\n        # way.  Rather than account for those, this simply ignores attempts to pull them down.\n        return []\n\n# Run the crawler, starting with the start_url, and using the link_retriever function\n# for extracting links from the scraped pages.\ndef crawl(start_url, link_retriever=get_links):\n    links = {} # Holds the dictionary of links to return at the end.\n    stack = [] # A (fake) stack structure to track what pages to crawl next.\n\n    # Start the crawler by retrieving the start_url:\n    stack.append(start_url)\n\n    # While there are pages to crawl:\n    while len(stack) > 0:\n        # Get the next URL to crawl, \"popping\" it from the stack:\n        next_url = stack[0]\n        del stack[0]\n\n        # Add the URL about-to-be scraped to our list of scraped URLs:\n        links[next_url] = []\n\n        # Get the links on the URL:\n        for link in link_retriever(next_url):\n            links[next_url].append(link)\n\n            # Clean each retrieved link - this is just to speed up the process:\n            if '#' in link:\n                link = link.split('#')[0]\n            if '?' in link:\n                link = link.split('?')[0]\n            if not link.endswith('\/'):\n                link += '\/'\n\n            # Add each link not yet seen to the stack, so that it will in turn be crawled:\n            if link not in links:\n                stack.append(link)\n                links[link] = []\n\n    return links\n<\/pre><\/div>","protected":false},"excerpt":{"rendered":"
    In the last post, we saw that many times the web page you request is not the page you receive. Similarly, often the page you’ve downloaded looks nothing like the…<\/p>\n","protected":false},"author":1,"featured_media":1215,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[64],"tags":[],"powerkit_post_featured":[],"class_list":{"0":"post-1187","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-application-development"},"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.craigperler.com\/blog\/wp-content\/uploads\/2016\/10\/img_5816705ca5bf8.png?fit=890%2C593&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p1SwZ6-j9","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/posts\/1187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/comments?post=1187"}],"version-history":[{"count":4,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/posts\/1187\/revisions"}],"predecessor-version":[{"id":1579,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/posts\/1187\/revisions\/1579"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/media\/1215"}],"wp:attachment":[{"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/media?parent=1187"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/categories?post=1187"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/tags?post=1187"},{"taxonomy":"powerkit_post_featured","embeddable":true,"href":"https:\/\/www.craigperler.com\/blog\/wp-json\/wp\/v2\/powerkit_post_featured?post=1187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}