<?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 &#187; web</title>
	<atom:link href="http://www.kralidis.ca/blog/category/web/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, 25 Jun 2010 18:23:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Geoprocessing with OGR and PyWPS</title>
		<link>http://www.kralidis.ca/blog/2010/06/25/geoprocessing-with-ogr-and-pywps/</link>
		<comments>http://www.kralidis.ca/blog/2010/06/25/geoprocessing-with-ogr-and-pywps/#comments</comments>
		<pubDate>Fri, 25 Jun 2010 18:14:23 +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=497</guid>
		<description><![CDATA[PyWPS is a neat Python package supporting the OGC Web Processing Service standard.  Basic setup and configuration can be found in the documentation, or Tim&#8217;s useful post. I&#8217;ve been working on a demo to expose the OGR Python bindings for geoprocessing (buffer, centroid, etc.). Here&#8217;s an example process to buffer a geometry (input as WKT), [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/06/25/geoprocessing-with-ogr-and-pywps/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>Tips on Finding a Job</title>
		<link>http://www.kralidis.ca/blog/2010/06/18/tips-on-finding-a-job/</link>
		<comments>http://www.kralidis.ca/blog/2010/06/18/tips-on-finding-a-job/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 17:27:30 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[personal]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=494</guid>
		<description><![CDATA[Great post by Dave here on his experience and suggestions / ideas on finding a job.  Upbeat, positive and encouraging.  Congratulations and good post Dave! Written from Starbucks in Laval: window.onload=function() { var point494 = new GLatLng(45.568007, -73.727295); var map494 = new GMap2(document.getElementById("map494")); map494.addControl(new GSmallMapControl()); map494.setCenter(point494, 10); var icon494 = new GIcon(); icon494.image = "http://labs.google.com/ridefinder/images/mm_20_red.png"; [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/06/18/tips-on-finding-a-job/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>45.568007 -73.727295</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>Displaying GRIB data with MapServer</title>
		<link>http://www.kralidis.ca/blog/2010/06/04/displaying-grib-data-with-mapserver/</link>
		<comments>http://www.kralidis.ca/blog/2010/06/04/displaying-grib-data-with-mapserver/#comments</comments>
		<pubDate>Fri, 04 Jun 2010 23:02: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=485</guid>
		<description><![CDATA[I recently had the opportunity to prototype WMS visualization of meteorological data.  MapServer, GDAL and Python to the rescue!  Here are the steps I took to make it happen. The data, (GRIB), is a GDAL supported format, so MapServer can handle processing as a result.  The goal here was to create a LAYER object.  First [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/06/04/displaying-grib-data-with-mapserver/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
			<georss:where>
			<gml:Point>
				<gml:pos>43.663194 -79.575653</gml:pos>
			</gml:Point>
		</georss:where>	</item>
		<item>
		<title>OWSLib CSW Updates and Implementation Thoughts</title>
		<link>http://www.kralidis.ca/blog/2010/05/07/owslib-csw-updates-and-implementation-thoughts/</link>
		<comments>http://www.kralidis.ca/blog/2010/05/07/owslib-csw-updates-and-implementation-thoughts/#comments</comments>
		<pubDate>Sat, 08 May 2010 01:34:28 +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=477</guid>
		<description><![CDATA[I&#8217;ve had some time to work on CSW support in OWSLib in the last few days.  Some thoughts and updates: FGDC Support Added Some CSW endpoints out there serve up GetRecords responses in FGDC CSDGM format.  This has now been added to trunk (mandatory elements + eainfo).  Note that csw:Record (DMCI + ows:BoundingBox) and ISO [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/05/07/owslib-csw-updates-and-implementation-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>easy CSW with eXcat</title>
		<link>http://www.kralidis.ca/blog/2010/03/14/easy-csw-with-excat/</link>
		<comments>http://www.kralidis.ca/blog/2010/03/14/easy-csw-with-excat/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 01:52:54 +0000</pubDate>
		<dc:creator>tomkralidis</dc:creator>
				<category><![CDATA[geospatial]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.kralidis.ca/blog/?p=444</guid>
		<description><![CDATA[If you have existing metadata and simply want a CSW interface as a means to search and discover your geospatial metadata, eXcat provides a simple solution.  Following the installation steps, it&#8217;s quite simple to populate your CSW: $ cd excat/csw/WEB-INF/harvest $ tar zxf my_metadata_files.tgz $ for i in *.xml &#62; do &#62; lwp-download "http://localhost/excat/csw?request=Harvest&#38;service=CSW&#38;\ &#62; [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/03/14/easy-csw-with-excat/feed/</wfw:commentRss>
		<slash:comments>3</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() { var point439 = new GLatLng(43.663194, -79.575653); [...]]]></description>
		<wfw:commentRss>http://www.kralidis.ca/blog/2010/02/19/geoscript/feed/</wfw:commentRss>
		<slash:comments>4</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 [...]]]></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 [...]]]></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; [...]]]></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")); map322.addControl(new GSmallMapControl()); map322.setCenter(point322, 10); var icon322 = new GIcon(); icon322.image = "http://labs.google.com/ridefinder/images/mm_20_red.png"; icon322.shadow = "http://labs.google.com/ridefinder/images/mm_20_shadow.png"; icon322.iconSize = new GSize(12, 20); icon322.shadowSize = new [...]]]></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>
	</channel>
</rss>
