<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
	>
<channel>
	<title>Comments on: GeoWeb Standards &#8211; Where we are</title>
	<atom:link href="http://highearthorbit.com/geoweb-standards-where-we-are/feed/" rel="self" type="application/rss+xml" />
	<link>http://highearthorbit.com/geoweb-standards-where-we-are/</link>
	<description>Transmitting ideas, observations, and images from 42,000 km.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:15:16 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gertie</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-406292</link>
		<dc:creator>Gertie</dc:creator>
		<pubDate>Sun, 02 Oct 2011 16:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-406292</guid>
		<description>Your story was really inofrmvatie, thanks!</description>
		<content:encoded><![CDATA[<p>Your story was really inofrmvatie, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe wolter</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-293691</link>
		<dc:creator>joe wolter</dc:creator>
		<pubDate>Thu, 11 Feb 2010 13:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-293691</guid>
		<description>Andrew,

Can you address the lack of tools for importing GeoRSS/KML/GML to spatiaLite? GML specifically GML.

....  /geoserver/wfs?REQUEST=GetFeature&amp;T ....

Thanks,
Joe</description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>Can you address the lack of tools for importing GeoRSS/KML/GML to spatiaLite? GML specifically GML.</p>
<p>&#8230;.  /geoserver/wfs?REQUEST=GetFeature&amp;T &#8230;.</p>
<p>Thanks,<br />
Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Turner</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-270873</link>
		<dc:creator>Andrew Turner</dc:creator>
		<pubDate>Fri, 28 Aug 2009 17:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-270873</guid>
		<description>Thanks for your feedback truthman. Actually my path to current work has nothing to do with shapefiles - except to find them and open them up.

My point is that Shapefiles definitely served a necessary purpose, but they have clear shortcomings and so we need to move onto better formats. And these better formats cannot be proprietary. 

These issues are entirely removed from the security and integrity issue. And not even about homogenized databases. It&#039;s about usability and interoperability. 

You do have a valid point on data and information size. There are definite use cases for people needing to share and utilize large, topologically or relationally connected, features. (something that Shapefiles don&#039;t support either). 

I agree that GeoRSS/KML/GML don&#039;t address that. However, Spatialite does (will be talking more about that in a future post).</description>
		<content:encoded><![CDATA[<p>Thanks for your feedback truthman. Actually my path to current work has nothing to do with shapefiles &#8211; except to find them and open them up.</p>
<p>My point is that Shapefiles definitely served a necessary purpose, but they have clear shortcomings and so we need to move onto better formats. And these better formats cannot be proprietary. </p>
<p>These issues are entirely removed from the security and integrity issue. And not even about homogenized databases. It&#8217;s about usability and interoperability. </p>
<p>You do have a valid point on data and information size. There are definite use cases for people needing to share and utilize large, topologically or relationally connected, features. (something that Shapefiles don&#8217;t support either). </p>
<p>I agree that GeoRSS/KML/GML don&#8217;t address that. However, Spatialite does (will be talking more about that in a future post).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: truthman</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-270869</link>
		<dc:creator>truthman</dc:creator>
		<pubDate>Fri, 28 Aug 2009 15:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-270869</guid>
		<description>if it werent for shapefiles you likely wouldnt have a job, er at least this one.  

show some respect man.

if you can give me a usable 300000 parcels dataset, fully attributed in georss/gml/kml ill drop the shapefile.

oh and it has to be on the local machine.

    thought so.

theres a reason business doesnt use gmail. same goes for geodata. security and protection man. if the geodata is not already available publicly in some form (tabular, in a report etc) then most likely it never will be.

good luck man theres a lot to map out there.  having centralized homogenized databases are always nice.  but the good stuff will always be behind closed doors.</description>
		<content:encoded><![CDATA[<p>if it werent for shapefiles you likely wouldnt have a job, er at least this one.  </p>
<p>show some respect man.</p>
<p>if you can give me a usable 300000 parcels dataset, fully attributed in georss/gml/kml ill drop the shapefile.</p>
<p>oh and it has to be on the local machine.</p>
<p>    thought so.</p>
<p>theres a reason business doesnt use gmail. same goes for geodata. security and protection man. if the geodata is not already available publicly in some form (tabular, in a report etc) then most likely it never will be.</p>
<p>good luck man theres a lot to map out there.  having centralized homogenized databases are always nice.  but the good stuff will always be behind closed doors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Turner</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-268226</link>
		<dc:creator>Andrew Turner</dc:creator>
		<pubDate>Mon, 10 Aug 2009 18:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-268226</guid>
		<description>Stu - yes, Shapefiles are very legacy. That doesn&#039;t mean they should still be the de facto way to publish current data. We should be moving away from them, much as we don&#039;t share documents in WordPerfect or LotusNotes formats.

And I don&#039;t mean &quot;open&quot; necessarily in how they are developed - but how they can be used. Commercially developed formats that *require* the use of that single commercial application or suite prohibits access to the data and therefore severely limits the benefit or impact the data can have. 

Now that doesn&#039;t always matter. if you&#039;re sharing data within a single organization, or selling the data- then that is ok. But data that is meant to be open and broadly accessible should never be shared only in a way that requires buying a single vendor tool to access.</description>
		<content:encoded><![CDATA[<p>Stu &#8211; yes, Shapefiles are very legacy. That doesn&#8217;t mean they should still be the de facto way to publish current data. We should be moving away from them, much as we don&#8217;t share documents in WordPerfect or LotusNotes formats.</p>
<p>And I don&#8217;t mean &#8220;open&#8221; necessarily in how they are developed &#8211; but how they can be used. Commercially developed formats that *require* the use of that single commercial application or suite prohibits access to the data and therefore severely limits the benefit or impact the data can have. </p>
<p>Now that doesn&#8217;t always matter. if you&#8217;re sharing data within a single organization, or selling the data- then that is ok. But data that is meant to be open and broadly accessible should never be shared only in a way that requires buying a single vendor tool to access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stu Rich</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-268089</link>
		<dc:creator>Stu Rich</dc:creator>
		<pubDate>Sun, 09 Aug 2009 19:41:11 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-268089</guid>
		<description>&quot;Shapefiles are the bastard geodata denizens of the web. They are annoying in multiple ways. Foremost being that they are a proprietary data standard that is found entirely too common across geodata portals – especially government portals.&quot;  Really?  Pretty harsh if you ask me.  A couple of salient points to keep in mind:

1.  Shapefiles were around long before many of the other standards that you cite and the reason that there are so many of them is the GIS community has found them a very practical way to share data in a form that supports further analysis. 

2.  If memory serves, ESRI published the shapefile format before many other companies made their formats known.  In my view, just because a format is not published by an &quot;open&quot; standards body does not necessarily make it less desirable or less practical.  In fact, in my experience often commercially developed formats are often more useful than open formats particularly within a specific community of interest.</description>
		<content:encoded><![CDATA[<p>&#8220;Shapefiles are the bastard geodata denizens of the web. They are annoying in multiple ways. Foremost being that they are a proprietary data standard that is found entirely too common across geodata portals – especially government portals.&#8221;  Really?  Pretty harsh if you ask me.  A couple of salient points to keep in mind:</p>
<p>1.  Shapefiles were around long before many of the other standards that you cite and the reason that there are so many of them is the GIS community has found them a very practical way to share data in a form that supports further analysis. </p>
<p>2.  If memory serves, ESRI published the shapefile format before many other companies made their formats known.  In my view, just because a format is not published by an &#8220;open&#8221; standards body does not necessarily make it less desirable or less practical.  In fact, in my experience often commercially developed formats are often more useful than open formats particularly within a specific community of interest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-267636</link>
		<dc:creator>Maarten</dc:creator>
		<pubDate>Thu, 06 Aug 2009 21:24:40 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-267636</guid>
		<description>I agree, very informative and useful overview of the Geoweb formats landscape.</description>
		<content:encoded><![CDATA[<p>I agree, very informative and useful overview of the Geoweb formats landscape.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Britta</title>
		<link>http://highearthorbit.com/geoweb-standards-where-we-are/comment-page-1/#comment-267590</link>
		<dc:creator>Britta</dc:creator>
		<pubDate>Thu, 06 Aug 2009 14:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/geoweb-standards-where-we-are/#comment-267590</guid>
		<description>You are a geographic super hero. These posts are relevant and informative. 

Could you provide basic examples of when each might be appropriate to implement? 

Thanks! 

Britta</description>
		<content:encoded><![CDATA[<p>You are a geographic super hero. These posts are relevant and informative. </p>
<p>Could you provide basic examples of when each might be appropriate to implement? </p>
<p>Thanks! </p>
<p>Britta</p>
]]></content:encoded>
	</item>
</channel>
</rss>

