{"id":375,"date":"2009-09-16T08:51:20","date_gmt":"2009-09-16T13:51:20","guid":{"rendered":"http:\/\/www.kralidis.ca\/blog\/?p=375"},"modified":"2009-09-16T09:37:31","modified_gmt":"2009-09-16T14:37:31","slug":"python-kml-and-parishes","status":"publish","type":"post","link":"https:\/\/www.kralidis.ca\/blog\/2009\/09\/16\/python-kml-and-parishes\/","title":{"rendered":"Python, KML and Parishes"},"content":{"rendered":"

When looking for phone numbers for various churches<\/a>, I thought wouldn’t it be neat to put the locations on a map?<\/p>\n

Python to the rescue.\u00a0 After some scraping to generate a CSV listing, I geocoded the addresses, then I used the OGR to convert into a KML document, using the same approach I previously blogged<\/a> about.\u00a0 Nice!<\/p>\n

Looking deeper, I wanted to have more exhaustive content within the <description> element.\u00a0 Turns out ogr2ogr has a -dsco DescriptionField=fieldname option, but I wanted more than that.\u00a0 So I decided to hack the original CSV:<\/p>\n

#!\/usr\/bin\/python\r\n\r\nimport csv\r\nimport urllib2\r\nimport urllib\r\nfrom lxml import etree\r\n\r\nr = csv.reader(open('greek_churches_canada.csv'))\r\n\r\nnode = etree.Element('kml', nsmap={None: 'http:\/\/www.opengis.net\/kml\/2.2'})\r\n\r\nr.next()\r\n\r\nfor row in r:\r\n    params = '%s,%s,%s,%s' % (row[1], row[2], row[3], row[4])\r\n    url = 'http:\/\/maps.google.com\/maps\/geo?output=csv&q=%s' % urllib.quote_plus(params)\r\n    #print url\r\n    content = urllib2.urlopen(url)\r\n    status, accuracy, lat, lon = content.read().split(',')\r\n    #print status, accuracy, lat, lon\r\n    if status == '200':\r\n        row.append(lat)\r\n        row.append(lon)\r\n        subnode = etree.Element('Placemark')\r\n        subsubnode = etree.Element('name')\r\n        subsubnode.text = row[0]\r\n        subsubnode2 = etree.Element('description')\r\n        description = '<p>'\r\n        description += '%s<br\/>' % row[1]\r\n        description += '%s, %s<br\/>' % (row[2], row[3])\r\n        description += '%s<br\/>' % row[4]\r\n        if row[5] != 'none':\r\n            description += '%s<br\/>' % row[5]\r\n        if row[6] != 'none':\r\n            description += '%s<br\/>' % row[6]\r\n        if row[7] != 'none':\r\n            description += '<a href=\"%s\">Website<\/a><br\/>' % row[7]\r\n        if row[8] != 'none':\r\n            description += '<a href=\"mailto:%s\">Email<\/a><br\/>' % row[8]\r\n        description += '%s<br\/>' % row[9]\r\n        description += '<\/p>'\r\n        subsubnode2.text = etree.CDATA(description)\r\n        subsubnode3 = etree.Element('Point')\r\n        subsubsubnode = etree.Element('coordinates')\r\n        subsubsubnode.text = '%s, %s' %(lon, lat)\r\n        subsubnode3.append(subsubsubnode)\r\n        subnode.append(subsubnode)\r\n        subnode.append(subsubnode2)\r\n        subnode.append(subsubnode3)\r\n        node.append(subnode)\r\nprint etree.tostring(node, xml_declaration=True, encoding='UTF-8', pretty_print=True)<\/pre>\n
I wonder whether an OGR -dsco DescriptionTemplate=foo.txt, where foo.txt would look like:<\/p>\n
<table><\/pre>\n
\u00a0<tr><\/pre>\n
\u00a0 <th>City<\/th><\/pre>\n
\u00a0 <td>[city]<\/td><\/pre>\n
\u00a0 <th>Province<\/th><\/pre>\n
\u00a0 <td>[province]<\/td><\/pre>\n
\u00a0<\/tr><\/pre>\n
<\/table><\/pre>\n
Or anything the user specified, for that matter.\u00a0 Then OGR would then use for each feature’s <description> element.<\/p>\n
Anyways, here’s the resulting map<\/a>.\u00a0 Cool!<\/p>\n\n\n