<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml">

<channel>
	<title>tommy&#039;s scratchpad</title>
	<atom:link href="http://www.kralidis.ca/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kralidis.ca/blog</link>
	<description>I use this blog to post my thoughts and random stuff from time to time.  See my About page for more info about me.  Note that my views and opinions expressed here are my own and do not reflect the views of my employer</description>
	<lastBuildDate>Fri, 19 Feb 2010 20:28:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>NYC Sprint is Upon Us</title>
		<link>http://www.kralidis.ca/blog/2010/02/19/nyc-sprint-is-upon-us/</link>
		<comments>http://www.kralidis.ca/blog/2010/02/19/nyc-sprint-is-upon-us/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 20:28:07 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=441</guid>
		<description><![CDATA[Building on the Toronto Code Sprint 2009 (I had the honour of helping Paul set this up), this year MapServer, GDAL, PostGIS, etc. devs are headed to to the Big Apple for the New York Code Sprint 2010.  Having participated in last year&#8217;s event, I can say that it is a fun, spirited and productive [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/02/19/nyc-sprint-is-upon-us/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>GeoScript</title>
		<link>http://www.kralidis.ca/blog/2010/02/19/geoscript/</link>
		<comments>http://www.kralidis.ca/blog/2010/02/19/geoscript/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 20:01:07 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=439</guid>
		<description><![CDATA[GeoScript looks like a neat effort to leverage GeoTools into Python (an increasingly widely used language for GIS scripting) and JavaScript.
I love this for JavaScript, and I wonder how this relates to the other Python work out there (like Shapely and WorldMill); Sean?

		Written from home:


      window.onload=function() {
    [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/02/19/geoscript/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Why XML Libraries Rock</title>
		<link>http://www.kralidis.ca/blog/2010/02/03/why-xml-libraries-rock/</link>
		<comments>http://www.kralidis.ca/blog/2010/02/03/why-xml-libraries-rock/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 23:46:44 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=433</guid>
		<description><![CDATA[msautotest is MapServer&#8217;s way of unit testing and sanity checking various features and bug fixes.
When testing the addition of AuthorityURL and Identifier support in WMS Capabilities XML, I found an issue with the output being invalid XML, which was tested and fixed.  Another fix was then added to ensure valid XML (isn&#8217;t open source [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/02/03/why-xml-libraries-rock/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>45.545823 -73.738539</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Why I Love Linux</title>
		<link>http://www.kralidis.ca/blog/2009/12/11/why-i-love-linux/</link>
		<comments>http://www.kralidis.ca/blog/2009/12/11/why-i-love-linux/#comments</comments>
		<pubDate>Sat, 12 Dec 2009 02:48:09 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=409</guid>
		<description><![CDATA[$ uptime
 21:20:01 up 112 days,  9:06,  1 user,  load average: 0.05, 0.09, 0.18

		Written from home:


      window.onload=function() {
        var point409 = new GLatLng(43.663194, -79.575653);

        var map409 = new GMap2(document.getElementById("map409"));
        [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/12/11/why-i-love-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Python, KML and Parishes</title>
		<link>http://www.kralidis.ca/blog/2009/09/16/python-kml-and-parishes/</link>
		<comments>http://www.kralidis.ca/blog/2009/09/16/python-kml-and-parishes/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 13:51:20 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=375</guid>
		<description><![CDATA[When looking for phone numbers for various churches, I thought wouldn&#8217;t it be neat to put the locations on a map?
Python to the rescue.  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 about.  [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/09/16/python-kml-and-parishes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Friday Metadata Thoughts</title>
		<link>http://www.kralidis.ca/blog/2009/06/12/friday-metadata-thoughts/</link>
		<comments>http://www.kralidis.ca/blog/2009/06/12/friday-metadata-thoughts/#comments</comments>
		<pubDate>Fri, 12 Jun 2009 19:00:38 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=340</guid>
		<description><![CDATA[Not the most exciting topic, but I&#8217;ve found myself knee deep in metadata standards as they pertain to CSW in the last couple of weeks.
I&#8217;ve made some recommendations in the past for OWS metadata, which have helped in established publishing requirements for cataloguing.
Starting to look at ISO metadata (data, service) makes you quickly realize the [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/06/12/friday-metadata-thoughts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>new stuff in OWSLib</title>
		<link>http://www.kralidis.ca/blog/2009/06/03/new-stuff-in-owslib/</link>
		<comments>http://www.kralidis.ca/blog/2009/06/03/new-stuff-in-owslib/#comments</comments>
		<pubDate>Wed, 03 Jun 2009 23:29:25 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=330</guid>
		<description><![CDATA[I&#8217;ve been spending alot of time lately doing a CSW client library in python, which was committed today to OWSLib.  CSW requests can be tricky to construct correctly, so this contribution attempts to provide an easy enough entry point to querying OGC Catalogues.
At this point, you can query your favourite CSW server with:
&#62;&#62;&#62; from owslib [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/06/03/new-stuff-in-owslib/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>MapServer 5.4.0 released</title>
		<link>http://www.kralidis.ca/blog/2009/04/23/mapserver-540-released/</link>
		<comments>http://www.kralidis.ca/blog/2009/04/23/mapserver-540-released/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 11:26:08 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=322</guid>
		<description><![CDATA[Announced yesterday, this release closes 92 bugs, and adds some new goodies.
Next stop: MapServer 6.0

		Written from home:


      window.onload=function() {
        var point322 = new GLatLng(43.663194, -79.575653);

        var map322 = new GMap2(document.getElementById("map322"));
       [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/04/23/mapserver-540-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Sun, Oracle and MySQL</title>
		<link>http://www.kralidis.ca/blog/2009/04/20/sun-oracle-and-mysql/</link>
		<comments>http://www.kralidis.ca/blog/2009/04/20/sun-oracle-and-mysql/#comments</comments>
		<pubDate>Mon, 20 Apr 2009 13:32:56 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=314</guid>
		<description><![CDATA[http://www.sun.com/third-party/global/oracle/.  I wonder what this will mean for MySQL?

		Written from home:


      window.onload=function() {
        var point314 = new GLatLng(43.663194, -79.575653);

        var map314 = new GMap2(document.getElementById("map314"));
        map314.addControl(new GSmallMapControl());
    [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/04/20/sun-oracle-and-mysql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Creating sitemap files for GeoNetwork</title>
		<link>http://www.kralidis.ca/blog/2009/04/15/creating-sitemap-files-for-geonetwork/</link>
		<comments>http://www.kralidis.ca/blog/2009/04/15/creating-sitemap-files-for-geonetwork/#comments</comments>
		<pubDate>Wed, 15 Apr 2009 23:44:56 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=309</guid>
		<description><![CDATA[Sitemaps are a valuable way to index your content for web crawlers.  GeoNetwork is a great tool for metadata management and a portal environment for discovery.  I wanted to push out all metadata resources out as a sitemap so that content can be found by web crawlers.  Python to the rescue:
#!/usr/bin/python

import MySQLdb

# connect to db
db=MySQLdb.connection(host='127.0.0.1', [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2009/04/15/creating-sitemap-files-for-geonetwork/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
	</channel>
</rss>
