<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wiki-Mikel</id>
	<title>OSGeo - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wiki-Mikel"/>
	<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/wiki/Special:Contributions/Wiki-Mikel"/>
	<updated>2026-04-12T18:02:49Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.9</generator>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Mikel&amp;diff=109203</id>
		<title>User:Mikel</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Mikel&amp;diff=109203"/>
		<updated>2017-09-09T01:43:45Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: Created page with &amp;quot;{{OSGeo Member |Name=Mikel Maron |JobTitle=Community Team Lead |Company=Mapbox |Address=1509 16th St NW |Country=USA |State=DC |City=Washington |Coordinate=38.8938,-77.0146 |L...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Mikel Maron&lt;br /&gt;
|JobTitle=Community Team Lead&lt;br /&gt;
|Company=Mapbox&lt;br /&gt;
|Address=1509 16th St NW&lt;br /&gt;
|Country=USA&lt;br /&gt;
|State=DC&lt;br /&gt;
|City=Washington&lt;br /&gt;
|Coordinate=38.8938,-77.0146&lt;br /&gt;
|LocalChapter=North America&lt;br /&gt;
|Email=mikel@mapbox.com&lt;br /&gt;
|Phone=415-283-5207&lt;br /&gt;
|SocialMedia=@mikel;&lt;br /&gt;
|Website=http://groundtruth.in/&lt;br /&gt;
|Photo=Mikel.jpg&lt;br /&gt;
|Languages=English;&lt;br /&gt;
|Info=Mikel leads the Community Team, building diverse collaborations centered on amazing mapping tools and open data, to make positive change on complex, global problems.&lt;br /&gt;
&lt;br /&gt;
As Presidential Innovation Fellow at the US State Department Mikel drove OpenStreetMap adoption across federal agencies. He is co-founder of the Humanitarian OpenStreetMap Team, co-founder of Map Kibera and GroundTruth Initiative and Board member of the OpenStreetMap Foundation. He holds a master’s degree in Evolutionary and Adaptive Systems from the University of Sussex, and bachelor’s degree in Computer Science from UC Santa Cruz.&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=No&lt;br /&gt;
|Committee=No&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=No&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo_Advocate]]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=File:Mikel.jpg&amp;diff=109202</id>
		<title>File:Mikel.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=File:Mikel.jpg&amp;diff=109202"/>
		<updated>2017-09-09T01:41:38Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=UnitedNations_Committee&amp;diff=88161</id>
		<title>UnitedNations Committee</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=UnitedNations_Committee&amp;diff=88161"/>
		<updated>2015-11-17T15:34:54Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Members */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Background ==&lt;br /&gt;
The OSGeo Board of Directors met with the UN GIS team at FOSS4G in Seoul, Korea in September 2015.  The UN GIS team is very interested in having OSGeo &amp;quot;at the table&amp;quot;, and is interested in an exchange of official letters (an MoU would take many years to pass through on their side apparently) to formalize the relationship.  Mr. Kyoung-Soo Eom, chief of the UN Geospatial Information Section, has invited OSGeo to be part of a working group on Geospatial Information and Services for Disasters.&lt;br /&gt;
&lt;br /&gt;
== Goals ==&lt;br /&gt;
&lt;br /&gt;
* Develop a closer relationship with the UN.&lt;br /&gt;
&lt;br /&gt;
* Establish a formal agreement between OSGeo and the UN.&lt;br /&gt;
&lt;br /&gt;
* Establish communication between the UN GIS team and the OSGeo community.&lt;br /&gt;
&lt;br /&gt;
* Promote the use of Open Source geospatial tools by the UN's member states and committees.&lt;br /&gt;
&lt;br /&gt;
== Communication ==&lt;br /&gt;
&lt;br /&gt;
* a new &amp;quot;UN&amp;quot; mailing list has been created, please subscribe at https://lists.osgeo.org/mailman/listinfo/un&lt;br /&gt;
&lt;br /&gt;
== Activities ==&lt;br /&gt;
* OSGeo has formally expressed interest in joining the [[UN-GGIM-Working-Group]] on Geospatial Information and Services for Disasters &lt;br /&gt;
** this was discussed at OSGeo's [[Board_Meeting_2015-10-15]]&lt;br /&gt;
** the UN is looking for feedback on the working group's [http://wiki.osgeo.org/wiki/UN-GGIM-Working-Group#Draft_terms_of_reference_.28TOR.29 TOR draft]&lt;br /&gt;
&lt;br /&gt;
== Next steps ==&lt;br /&gt;
* put out call for members for this new committee to Discuss list&lt;br /&gt;
* organize a monthly meeting, possibly using IRC or Slack&lt;br /&gt;
* draft official letter for formalizing relationship with UN&lt;br /&gt;
&lt;br /&gt;
== Meetings ==&lt;br /&gt;
&lt;br /&gt;
* Next meeting: 2015-11-17 @[http://www.timeanddate.com/worldclock/fixedtime.html?year=2015&amp;amp;month=11&amp;amp;day=17&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0 16:00 UTC] (1 hour in length)&lt;br /&gt;
** IRC-channel: #osgeo channel on freenode.net&lt;br /&gt;
*** how to connect: choose your favorite IRC client, or go directly through browser with [https://webchat.freenode.net/ webchat]&lt;br /&gt;
** Agenda:&lt;br /&gt;
*** discuss structure of committee (chair, frequency of meetings)&lt;br /&gt;
*** discuss goals of committee&lt;br /&gt;
*** next steps&lt;br /&gt;
*** ''please add your items here''&lt;br /&gt;
&lt;br /&gt;
== Members ==&lt;br /&gt;
&lt;br /&gt;
* [[Jeff McKenna]]&lt;br /&gt;
* [[Jochen Albrecht]]	&lt;br /&gt;
* [[Bob Basques]]&lt;br /&gt;
* [[Massimiliano_Cannata]]&lt;br /&gt;
* [[User:Ticheler|Jeroen Ticheler]]&lt;br /&gt;
* [[Micha Silver]]&lt;br /&gt;
* [[User:GodwinYeboah|Godwin Yeboah]]&lt;br /&gt;
* [[User:Assefa|Yewondwossen Assefa]]&lt;br /&gt;
* [[User:Nikos|Nikos Alexandris]]&lt;br /&gt;
* [[User:AndrewTurner|Andrew Turner]]&lt;br /&gt;
* [[Venkatesh Raghavan]]&lt;br /&gt;
* [[User:Djay|Gérald Fenoy]]&lt;br /&gt;
* [[User:Pmooney|Peter MOONEY]]&lt;br /&gt;
* [[User:13scoter|Scott Hatcher]]&lt;br /&gt;
* [[User:kotzino|Dimitris Kotzinos]]&lt;br /&gt;
* [[User:ElaWoloszynska|Ela Wołoszyńska-Wiśniewska]]&lt;br /&gt;
* [[User:Jachym|Jachym Cepicky]]&lt;br /&gt;
* [[User:endofcap|Sanghee Shin]]&lt;br /&gt;
* [[User:Giulianoramat|Giuliano Ramat]]&lt;br /&gt;
* [[User:Gregory.giuliani|Gregory Giuliani]]&lt;br /&gt;
* [[User:Till Adams|Till Adams]]&lt;br /&gt;
* [[Tanya Haddad]]&lt;br /&gt;
* [[User:Maria gridw|Maria Andrzejewska]]&lt;br /&gt;
* [[User:rburhum|Ragi Y. Burhum (OSGeo - California / OSGeo Perú)]]&lt;br /&gt;
* [[User:darkblue_b|Brian M Hamlin]]&lt;br /&gt;
* [[User:Danielkastl|Daniel Kastl]]&lt;br /&gt;
* [[User:WernerLeyh|Werner Leyh]]&lt;br /&gt;
* [[User:Bruce.bannerman|Bruce Bannerman]]&lt;br /&gt;
* [[User:Ortelius|Jeffrey Johnson]]&lt;br /&gt;
* [[User:pnaciona|Pericles Nacionales]]&lt;br /&gt;
* [[User:Novacite|Junyoung Choi]]&lt;br /&gt;
* [[User:dirkf|Dirk Frigne]]&lt;br /&gt;
* [[User:pierzen|Pierre Béland]]&lt;br /&gt;
* [[User:maria|Maria Antonia Brovelli]]&lt;br /&gt;
* [[User:Mikel|Mikel Maron]]&lt;br /&gt;
* ''add your name''&lt;br /&gt;
&lt;br /&gt;
[[Category:UnitedNations]]&lt;br /&gt;
[[Category:Committees]]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4G2008_CodeSprint&amp;diff=30349</id>
		<title>FOSS4G2008 CodeSprint</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4G2008_CodeSprint&amp;diff=30349"/>
		<updated>2008-10-04T11:14:01Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Back to [[FOSS4G2008]]...&lt;br /&gt;
&lt;br /&gt;
== Date and Organizing Contacts ==&lt;br /&gt;
&lt;br /&gt;
'''Date:''' Saturday 4 October 2008 &lt;br /&gt;
We have decided to do this on the Saturday so 'sprinters' don't miss any workshops or socialising during the week. &lt;br /&gt;
&lt;br /&gt;
'''Venue:''' Cape Town City Council offices&lt;br /&gt;
&lt;br /&gt;
'''Organising Contact:''' Tim Sutton&lt;br /&gt;
&lt;br /&gt;
'''Contact Email:''' tim@linfiniti.com&lt;br /&gt;
&lt;br /&gt;
== Procedure ==&lt;br /&gt;
&lt;br /&gt;
Read the sections below which provide some background. If you would like to hold a code sprint, add your name (as coordinator)  and project name below, then create a detailed project sprint section below. The project sprint section should include some or all of the following details:&lt;br /&gt;
&lt;br /&gt;
* '''Attending''' - a list of people who plan to attend&lt;br /&gt;
* '''Goals''' - a brief list of the things you hope to achieve and plan to work on during your sprint session&lt;br /&gt;
* '''Preparation (optional)''' - a list of items that should be taken care of before the code sprint so that the appropriate groundwork is in place&lt;br /&gt;
* '''Out of scope (optional)''' - items that will not be in scope for the sprint session&lt;br /&gt;
&lt;br /&gt;
If you are planning to attend the code sprint, please add your name to the relevant project sprint section below.&lt;br /&gt;
&lt;br /&gt;
All sprint attendees it will be a good idea to subscribe to this page by ticking the 'watch this page' box at the bottom of the page so that you can be updated if there are any changes in arrangements.&lt;br /&gt;
&lt;br /&gt;
== Interested to organize a code sprint ==&lt;br /&gt;
&lt;br /&gt;
* Markus Neteler: GRASS GIS&lt;br /&gt;
* Andrea Antonello: JGrass / uDig&lt;br /&gt;
&lt;br /&gt;
== Code Sprint - what's that? ==&lt;br /&gt;
&lt;br /&gt;
A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...&lt;br /&gt;
&lt;br /&gt;
== Rooms ==&lt;br /&gt;
&lt;br /&gt;
[[image:RoomA.JPG]]&lt;br /&gt;
[[image:RoomJ.JPG]]&lt;br /&gt;
[[image:RoomG1.JPG]]&lt;br /&gt;
[[image:RoomH.JPG]]&lt;br /&gt;
&lt;br /&gt;
One or more of these rooms will be used for the code sprint depending on turn out.&lt;br /&gt;
&lt;br /&gt;
== Motivation and Direction ==&lt;br /&gt;
&lt;br /&gt;
A day, a code base, and your imagination?&lt;br /&gt;
&lt;br /&gt;
On the Saturday after the conference, a big room with internet connectivity, lots of tables and flip charts will be arranged.  Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.&lt;br /&gt;
&lt;br /&gt;
Is this your First Sprint? Here is some background information to get you started:&lt;br /&gt;
&lt;br /&gt;
* http://www.infrae.com/about/activities/sprintathon/tips &lt;br /&gt;
* http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html &lt;br /&gt;
* Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint &lt;br /&gt;
&lt;br /&gt;
To participate, start a section below for your project.&lt;br /&gt;
&lt;br /&gt;
== OSGeo Marketing ==&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* Jeroen Ticheler&lt;br /&gt;
* Arnulf Christl&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
* Optimize the new OSGeo logo vectors to be very precise and scalable.&lt;br /&gt;
* Update pages with the OSGeo logo(s).&lt;br /&gt;
&lt;br /&gt;
== GRASS ==&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;strike&amp;gt;[[Markus Neteler]]&amp;lt;/strike&amp;gt; (since it was moved to Saturday, just booked the flight without realizing)&lt;br /&gt;
* [[User:Wolf|Wolf Bergenheim]] via IRC&lt;br /&gt;
* [[User:Landa|Martin Landa]] via IRC&lt;br /&gt;
* [[User:mlennert|Moritz Lennert]] via IRC (tbc)&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
* Hack session: fix bugs, new features&lt;br /&gt;
* Maybe invite power users to get in touch?&lt;br /&gt;
: Remote users via IRC channel&lt;br /&gt;
&lt;br /&gt;
== Udig / JGrass ==&lt;br /&gt;
&lt;br /&gt;
Cross project code sprint with the JGrass and uDig projects.&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[User:Moovida | Andrea Antonello]]&lt;br /&gt;
* [[User:silli | Silvia Franceschi]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
To be defined...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Quantum GIS (QGIS) ==&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[Tim Sutton]]&lt;br /&gt;
* Horst Duster&lt;br /&gt;
* Marco Hugentobler&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
* Hack session: fix bugs, new features&lt;br /&gt;
* Maybe invite power users to get in touch?&lt;br /&gt;
: Remote users via IRC channel&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[Erik Uzureau]]&lt;br /&gt;
* [[User:tschaub|Tim Schaub]]&lt;br /&gt;
* [[Eric Lemoine]]&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
* OpenLayers 2.8 Release Planning&lt;br /&gt;
* OpenLayers 3.0 Brainstorming Session&lt;br /&gt;
&lt;br /&gt;
== SEXTANTE ==&lt;br /&gt;
&lt;br /&gt;
Code Sprint to integrate the SEXTANTE library with other Java-GIS projects&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[User:Volaya | Victor Olaya]]&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
*To improve GeoTools-SEXTANTE integration&lt;br /&gt;
*To discuss the integration of SEXTANTE as a base element for WPS processes.&lt;br /&gt;
*To introduce SEXTANTE to other projects and show them how to incorporate SEXTANTE-based processes in them&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo packaging &amp;amp; Repo ==&lt;br /&gt;
=== Goals ===&lt;br /&gt;
* Initiate the provision of an OSGeo run repo for packaging OSGeo projects &amp;amp; educational material&lt;br /&gt;
* Tentative target platforms: Ubuntu 8.10 with a view to packages flowing into Debian Sid initially.&lt;br /&gt;
* Other platforms to be supported in the future as more people resources are available&lt;br /&gt;
* Support the continued development of the Live DVD.&lt;br /&gt;
* Start packaging initial selection of educational material&lt;br /&gt;
=== Attending ===&lt;br /&gt;
[[User:Tbowden | Tim Bowden]]&lt;br /&gt;
&lt;br /&gt;
== Geomajas ==&lt;br /&gt;
&lt;br /&gt;
Code Sprint to integrate the Geomajas project with other Java-GIS projects&lt;br /&gt;
&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[User:dirkf | Dirk Frigne]]&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
*To improve the contents of the website &lt;br /&gt;
*To get into contact with other projects we want to integrate with&lt;br /&gt;
*To share some ideas about work that can be established in common&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GeoNetwork ==&lt;br /&gt;
=== Attending ===&lt;br /&gt;
&lt;br /&gt;
* [[User:fxp | Francois Prunayre]]&lt;br /&gt;
* Paul Hasenohr&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
* To improve multilingual support (installer, documentation, GAST)&lt;br /&gt;
* To add support for WPS in harvesting engine&lt;br /&gt;
&lt;br /&gt;
== OpenStreetMap ==&lt;br /&gt;
* Mikel Maron&lt;br /&gt;
* Josh Livni&lt;br /&gt;
&lt;br /&gt;
=== Goals ===&lt;br /&gt;
&lt;br /&gt;
Partyserver: web service to produce party render, animated GPX videos&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSS4G]]&lt;br /&gt;
[[Category:Code Sprints]]&lt;br /&gt;
[[Category:FOSS4G2008]]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GDAL_SoC_Ideas&amp;diff=13041</id>
		<title>GDAL SoC Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GDAL_SoC_Ideas&amp;diff=13041"/>
		<updated>2007-03-21T14:34:02Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GDAL/OGR Related ideas for the [[Google Summer of Code]] 2007:&lt;br /&gt;
&lt;br /&gt;
# Write an OGC WMS (Web Map Service) driver, likely somewhat modelled on the WCS driver implementation.  &lt;br /&gt;
#* [http://portal.opengeospatial.org/files/?artifact_id=1081&amp;amp;version=1&amp;amp;format=pdf WMS Specification]&lt;br /&gt;
#* [http://svn.osgeo.org/gdal/trunk/gdal/frmts/wcs WCS Code]&lt;br /&gt;
#* [http://www.gdal.org/gdal_drivertut.html GDAL Raster Driver Tutorial]&lt;br /&gt;
# Extend the existing KML vector feature writer to also support reading KML, and otherwise generalize this driver.  &lt;br /&gt;
#* [http://svn.osgeo.org/gdal/trunk/gdal/ogr/ogrsf_frmts/kml writer code]&lt;br /&gt;
#* [http://www.gdal.org/ogr/drv_kml.html driver docs]&lt;br /&gt;
#* [http://www.gdal.org/ogr/ogr_drivertut.html OGR Driver Tutorial]&lt;br /&gt;
# Implement a raster reader/writer for KML. -- More info in [[GDAL2Tiles SoC 2007]]&lt;br /&gt;
#* [http://earth.google.com/kml KML Docs]&lt;br /&gt;
#* [http://www.gdal.org/gdal_drivertut.html GDAL Raster Driver Tutorial]&lt;br /&gt;
# Implement GeoPNG/GeoJPEG by embeding coordinate system and geotransformation information (possibly in GML) as chunks in PNG and JPEG files (see GML JP2 for a model of how this might be done). &lt;br /&gt;
#* [http://portal.opengeospatial.org/files/?artifact_id=13252 GMLJP2 Specification]&lt;br /&gt;
#* GMLJP2 Code: [http://svn.osgeo.org/gdal/trunk/gdal/gcore/gdaljp2metadata.cpp gdaljp2metadata.cpp] [http://svn.osgeo.org/gdal/trunk/gdal/gcore/gdalgmlcoverage.cpp gdalgmlcoverage.cpp]&lt;br /&gt;
#* [http://svn.osgeo.org/gdal/trunk/gdal/frmts/png PNG Driver (using libpng)]&lt;br /&gt;
#* [http://svn.osgeo.org/gdal/trunk/gdal/frmts/jpeg JPEG Driver (using libjpeg)]&lt;br /&gt;
# OGR WFS read driver using existing OGR GML driver for feature parsing.&lt;br /&gt;
#* [http://portal.opengeospatial.org/files/?artifact_id=14145 OGC WFS Specification]&lt;br /&gt;
#* [http://www.gdal.org/ogr/ogr_drivertut.html OGR Driver Tutorial]&lt;br /&gt;
# Design a SAR (Synthetic Aperture RADAR) &amp;quot;Processor&amp;quot; using GDAL as a data reader/processed data writer&lt;br /&gt;
#* Provide enhancements to relevant drivers (and potentially write new drivers) for reading new/common unprocessed SAR data sources, including metadata support where needed&lt;br /&gt;
#* Implement an end-to-end Range-Doppler Algorithm processor for platforms where processing details are available&lt;br /&gt;
# Develop a driver for GeoRSS&lt;br /&gt;
#* [http://georss.org GeoRSS specification]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Shirts&amp;diff=4916</id>
		<title>Shirts</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Shirts&amp;diff=4916"/>
		<updated>2006-05-31T15:56:57Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Purchasers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is about our shirt order for Where 2.0 (and beyond).&lt;br /&gt;
&lt;br /&gt;
=== Design/Style ===&lt;br /&gt;
&lt;br /&gt;
Using [http://ocs.landsend.com/ Lands' End].&lt;br /&gt;
&lt;br /&gt;
We will be using fabric style &amp;quot;W&amp;quot;, which gives lots of style choices for the order (Tees, etc).  However, the style you select must support color=BLACK.  The logo will be done up in OSGeo Green.&lt;br /&gt;
&lt;br /&gt;
Two images (PDF and EPS) are stored in the VisCom file repository at osgeo.org.&lt;br /&gt;
&lt;br /&gt;
Logo submitted morning of May 24th, work started 25th.  Within the 3 week &amp;quot;rush&amp;quot; window, so the $400 rush fee applies.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Purchasers ===&lt;br /&gt;
&lt;br /&gt;
'''Confirmed (Where purchase)'''&lt;br /&gt;
&lt;br /&gt;
# Tyler Mitchell (tylermitchell-AT-shaw.ca) [060393-Large]&lt;br /&gt;
# Dave McIlhagga (dmcilhagga-AT-dmsolutions.ca) [large T]&lt;br /&gt;
# Jo Walsh (jo-AT-frot.org)  [&amp;quot;small/girlie-sized&amp;quot;]&lt;br /&gt;
# mpg (mpg-AT-osgeo.org)&lt;br /&gt;
# Frank (warmerdam-AT-pobox.com) [large T (060393)]&lt;br /&gt;
# Gary Lang (gary.lang-AT-autodesk.com)&lt;br /&gt;
# Schuyler (schuyler-AT-nocat.net)  [med or lg]&lt;br /&gt;
# Rich Gibson (rich.gibson-AT-gmail.com)&lt;br /&gt;
# Mark Lucas (mlucas17-AT-mac.com)  [large T]&lt;br /&gt;
# Andrew Mackles (andrew.mackles-AT-autodesk.com) [medium]&lt;br /&gt;
# Sean Sternfeldt (sean.sternfeldt-AT-autodesk.com)&lt;br /&gt;
# Allan Doyle (adoyle-AT-eogeo.org)  [large T]&lt;br /&gt;
# Chris Holmes (cholmes-AT-openplans.org)&lt;br /&gt;
# Arnulf Christl (arnulf.christl-AT-ccgis.de)&lt;br /&gt;
# Dylan Beaudette (dylan.beaudette-AT-gmail.com)&lt;br /&gt;
# David Enns (david.enns-AT-mapitout.com)&lt;br /&gt;
# John Graham (johng-AT-telascience.org) [Pima Polos xl xxl]&lt;br /&gt;
# Mikel Maron (mikel_maron-AT-yahoo.com) [xl T]&lt;br /&gt;
# Autodesk-1 (peter.moran-AT-autodesk.com) [T]&lt;br /&gt;
# Autodesk-2 (peter.moran-AT-autodesk.com) [T]&lt;br /&gt;
# Autodesk-3 (peter.moran-AT-autodesk.com) [T]&lt;br /&gt;
# Tim Schaub (tim-AT-commenspace.org) [Large T (060393)]&lt;br /&gt;
# Josh Livni (josh-AT_livniconsulting.com) [medium T (060393)]&lt;br /&gt;
# Jason Birch (jason.birch-AT-nanaimo.ca) [item #075973, size XXL] - Please give to Dave McIlhagga&lt;br /&gt;
&lt;br /&gt;
'''Confirmed (self-purchase)'''&lt;br /&gt;
&lt;br /&gt;
# Daniel Morissette (dmorissette-AT-mapgears.com)  [item #060393 (T), 2 size L, 2 size M (4 shirts total)]&lt;br /&gt;
# Tom Kralidis (tom.kralidis-AT-ec.gc.ca)  [item #060393, size L]&lt;br /&gt;
# Markus Neteler (neteler-AT-osgeo.org) [size L]&lt;br /&gt;
# Jeff McKenna (jmckenna-AT-dmsolutions.ca) [size XXL]&lt;br /&gt;
# Perry Nacionales (pnaciona-AT-osgeo.org) [size S]&lt;br /&gt;
# Aaron Koning (aaronkoning-AT-gmail.com) [size XXL]&lt;br /&gt;
# Mateusz Loskot (mateusz-AT-loskot.net)&lt;br /&gt;
# Paulo Marcondes (paulomarcondes-AT-gmail.com) [item #060393 (T w/o pocket), XL]&lt;br /&gt;
# CCGIS-1 (arnulf.christl-AT-ccgis.de)&lt;br /&gt;
# CCGIS-2 (arnulf.christl-AT-ccgis.de)&lt;br /&gt;
# CCGIS-3 (arnulf.christl-AT-ccgis.de)&lt;br /&gt;
# CCGIS-4 (arnulf.christl-AT-ccgis.de)&lt;br /&gt;
# Mike Adair (mike.adair-AT-nrcan.gc.ca) [size XL]&lt;br /&gt;
# Dave Patton (dpatton-AT-confluence.org) [Item Number: 060393, size L]&lt;br /&gt;
# Ari Jolma (ari.jolma-AT-tkk.fi) [Pima Polo XL]&lt;br /&gt;
# Jeroen Ticheler (Jeroen-AT-Ticheler.net) [#060393, Men, size XL]&lt;br /&gt;
# Marco Lechner (marco.lechner@geographie.uni-freiburg.de) [#060393W-BLA-M]&lt;br /&gt;
# Steve Lime (steve.lime-AT-dnr.state.mn.us) [size L]&lt;br /&gt;
# David Bitner (david.bitner-AT-gmail.com) [size L]&lt;br /&gt;
# Bob Basques (bob.b-AT-gritechnologies.com) [#065529 size XL]&lt;br /&gt;
&lt;br /&gt;
'''VIP Give-Aways'''&lt;br /&gt;
''these will just be T-shirts''&lt;br /&gt;
# Nat T. ''(two votes - mpg + others)''&lt;br /&gt;
# Mike Liebhold ''(two votes - Schuyler, Tyler)''&lt;br /&gt;
# an extra for Nat T., for Jack D.? ''(might be dangerous!)''&lt;br /&gt;
# 10 for FOSSGIS organization team (the sponsors)&lt;br /&gt;
# ''other suggestions?''&lt;br /&gt;
&lt;br /&gt;
=== Lands' End Account ===&lt;br /&gt;
&lt;br /&gt;
* set up under mpg's name and address (Seattle, WA)&lt;br /&gt;
* username: osgeo&lt;br /&gt;
* password: ''(ask mpg)''&lt;br /&gt;
&lt;br /&gt;
Contact info:&lt;br /&gt;
* work order #0637017W&lt;br /&gt;
* Jef Riley (fef.riley-AT-landsend.com)&lt;br /&gt;
* 800-535-3060 x8296&lt;br /&gt;
&lt;br /&gt;
=== To Do ===&lt;br /&gt;
&lt;br /&gt;
* logo now being set up, will confirm price&lt;br /&gt;
* get order date deadline&lt;br /&gt;
* get shirt orders collected&lt;br /&gt;
* set delivery to San Jose&lt;br /&gt;
* arrange payment via Arnulf&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=AJAX_WebMapping_Project_Request&amp;diff=3387</id>
		<title>AJAX WebMapping Project Request</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=AJAX_WebMapping_Project_Request&amp;diff=3387"/>
		<updated>2006-04-10T10:19:53Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[https://mail.osgeo.org/servlets/SummarizeList?listName=webmap-discuss webmap-discuss list has been set up]&lt;br /&gt;
&lt;br /&gt;
Motion &amp;quot;AJAX WebMapping&amp;quot; mailing list from Cameron Shorter by email:&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
What could be good is if we set up a ajax-mapping list which has &lt;br /&gt;
representatives from all the OS AJAX web mapping projects.&lt;br /&gt;
&lt;br /&gt;
== Aims ==&lt;br /&gt;
On it we can discuss ideas on how to implement different functionality &lt;br /&gt;
with the long term aim that we develop a set of common libraries that we &lt;br /&gt;
all can use.&lt;br /&gt;
&lt;br /&gt;
== OSGeo Projects ==&lt;br /&gt;
* mapbuilder&lt;br /&gt;
* mapbender&lt;br /&gt;
* ka-map (interested)&lt;br /&gt;
* worldkit (interested)&lt;br /&gt;
* OpenLayers (interested)&lt;br /&gt;
* [http://maps.civicactions.net/ CivicMaps] (another possible..)&lt;br /&gt;
&lt;br /&gt;
After adoption (going throughthis incubator) the mailing list &amp;quot;AJAX WebMapping&amp;quot; would be part of the OSGeo project infrastructure (run by CollabNet). Alternatively, it could be set up as a list of an existing project, probably ka.map or MapBuilder, once they moved into osgeo.&lt;br /&gt;
&lt;br /&gt;
== Discussion ==&lt;br /&gt;
&lt;br /&gt;
[[Talk:AJAX_WebMapping_Project_Request]]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=AJAX_WebMapping_Project_Request&amp;diff=3386</id>
		<title>AJAX WebMapping Project Request</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=AJAX_WebMapping_Project_Request&amp;diff=3386"/>
		<updated>2006-04-10T10:18:49Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Motion &amp;quot;AJAX WebMapping&amp;quot; mailing list from Cameron Shorter by email:&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
What could be good is if we set up a ajax-mapping list which has &lt;br /&gt;
representatives from all the OS AJAX web mapping projects.&lt;br /&gt;
&lt;br /&gt;
== Aims ==&lt;br /&gt;
On it we can discuss ideas on how to implement different functionality &lt;br /&gt;
with the long term aim that we develop a set of common libraries that we &lt;br /&gt;
all can use.&lt;br /&gt;
&lt;br /&gt;
== OSGeo Projects ==&lt;br /&gt;
* mapbuilder&lt;br /&gt;
* mapbender&lt;br /&gt;
* ka-map (interested)&lt;br /&gt;
* worldkit (interested)&lt;br /&gt;
* OpenLayers (interested)&lt;br /&gt;
* [http://maps.civicactions.net/ CivicMaps] (another possible..)&lt;br /&gt;
&lt;br /&gt;
After adoption (going throughthis incubator) the mailing list &amp;quot;AJAX WebMapping&amp;quot; would be part of the OSGeo project infrastructure (run by CollabNet). Alternatively, it could be set up as a list of an existing project, probably ka.map or MapBuilder, once they moved into osgeo.&lt;br /&gt;
&lt;br /&gt;
== Discussion ==&lt;br /&gt;
&lt;br /&gt;
[[Talk:AJAX_WebMapping_Project_Request]]&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3046</id>
		<title>WMS Tile Caching</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3046"/>
		<updated>2006-03-31T11:55:35Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Related Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Goal ==&lt;br /&gt;
&lt;br /&gt;
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.&lt;br /&gt;
&lt;br /&gt;
The two main questions to be addressed are:&lt;br /&gt;
# How does a server advertise its cacheable image tiles?&lt;br /&gt;
# How does a client request possibly cached image tiles?&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== WMS-C as WMS Profile ===&lt;br /&gt;
&lt;br /&gt;
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.&lt;br /&gt;
&lt;br /&gt;
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:&lt;br /&gt;
&lt;br /&gt;
# Minimal query string arguments (i.e. no optional arguments permitted, versus &amp;amp;sect;7.2)&lt;br /&gt;
# Fixed query string argument ordering and case (versus &amp;amp;sect;6.4.1; q.v. also &amp;amp;sect;7.2.2, Table 8)&lt;br /&gt;
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters&lt;br /&gt;
# Fixed precision on bounding box values (clarifying &amp;amp;sect;6.5.6)&lt;br /&gt;
# Fixed tile size in pixels&lt;br /&gt;
# Fixed layer name and/or layer name ordering&lt;br /&gt;
# Fixed styling&lt;br /&gt;
# Fixed output format&lt;br /&gt;
&lt;br /&gt;
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?&lt;br /&gt;
&lt;br /&gt;
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&amp;amp;sect; 7.2).&lt;br /&gt;
&lt;br /&gt;
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.&lt;br /&gt;
&lt;br /&gt;
=== Calculating Valid Tile Extents for a Given Request ===&lt;br /&gt;
&lt;br /&gt;
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.&lt;br /&gt;
&lt;br /&gt;
=== Possible Tile Scheme Parameters ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;This service suppports tiling.&amp;quot; || ''none'' || ''&amp;amp;lt;KeywordList&amp;amp;gt;'' contains the string 'tiled', perhaps? (&amp;amp;sect;7.1.4.5.3)&lt;br /&gt;
|-&lt;br /&gt;
| Projection || EPSG:4326 || ''&amp;amp;lt;SRS&amp;amp;gt;'' &lt;br /&gt;
|-&lt;br /&gt;
| Maximal extent || (-180,-90,180,90) || ''&amp;amp;lt;BoundingBox&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.7)&lt;br /&gt;
|-&lt;br /&gt;
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&amp;amp;lt;DataURL&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.14)&lt;br /&gt;
|-&lt;br /&gt;
| Tile size in pixels || some power of 2 || &amp;amp;lt;Layer&amp;amp;gt; attribute ''fixedWidth'', ''fixedHeight'' (&amp;amp;sect;7.1.4.6)&lt;br /&gt;
|-&lt;br /&gt;
| Minimum scale || ''none'' || ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' or ''&amp;amp;lt;DataURL&amp;amp;gt;'' (see note, above)&lt;br /&gt;
|-&lt;br /&gt;
| Scale quantization factor || 2 || ''&amp;amp;lt;DataURL&amp;amp;gt;''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Other Considerations ==&lt;br /&gt;
&lt;br /&gt;
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?&lt;br /&gt;
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:&lt;br /&gt;
&lt;br /&gt;
 http://domain.tld/service?L=0&amp;amp;X=1&amp;amp;Y=2&lt;br /&gt;
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).&lt;br /&gt;
&lt;br /&gt;
== Distributed Caching ==&lt;br /&gt;
&lt;br /&gt;
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.&lt;br /&gt;
* Alternately, one could do [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.&lt;br /&gt;
&lt;br /&gt;
== Existing Tiling Schemes ==&lt;br /&gt;
&lt;br /&gt;
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]&lt;br /&gt;
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]&lt;br /&gt;
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request&lt;br /&gt;
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]&lt;br /&gt;
&lt;br /&gt;
Note: WW and OnEarth schemes are pretty much the same, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels.&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ossim.org/tiki-read_article.php?articleId=3 osgPlanet]&lt;br /&gt;
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])&lt;br /&gt;
* [http://worldkit.org/ worldKit]&lt;br /&gt;
* [http://mapbuilder.sf.net/ Community MapBuilder]&lt;br /&gt;
* other AJAX map clients, presumably&lt;br /&gt;
&lt;br /&gt;
== Interested Parties ==&lt;br /&gt;
* [[User:SchuylerErle|Schuyler Erle]]&lt;br /&gt;
* [[User&amp;quot;Adoyle&amp;quot;|Allan Doyle]]&lt;br /&gt;
* [[user&amp;quot;Nhv&amp;quot;|Norman Vine]]&lt;br /&gt;
* [[user&amp;quot;Joshli&amp;quot;|Josh Lieberman]]&lt;br /&gt;
* [[user&amp;quot;Adamhill&amp;quot;|Adam Hill]]&lt;br /&gt;
* [[user&amp;quot;bitner&amp;quot;|David Bitner]]&lt;br /&gt;
* [[user:Mikel|Mikel Maron]]&lt;br /&gt;
* ''add yourself''&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3045</id>
		<title>WMS Tile Caching</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3045"/>
		<updated>2006-03-31T11:55:23Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Interested Parties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Goal ==&lt;br /&gt;
&lt;br /&gt;
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.&lt;br /&gt;
&lt;br /&gt;
The two main questions to be addressed are:&lt;br /&gt;
# How does a server advertise its cacheable image tiles?&lt;br /&gt;
# How does a client request possibly cached image tiles?&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== WMS-C as WMS Profile ===&lt;br /&gt;
&lt;br /&gt;
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.&lt;br /&gt;
&lt;br /&gt;
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:&lt;br /&gt;
&lt;br /&gt;
# Minimal query string arguments (i.e. no optional arguments permitted, versus &amp;amp;sect;7.2)&lt;br /&gt;
# Fixed query string argument ordering and case (versus &amp;amp;sect;6.4.1; q.v. also &amp;amp;sect;7.2.2, Table 8)&lt;br /&gt;
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters&lt;br /&gt;
# Fixed precision on bounding box values (clarifying &amp;amp;sect;6.5.6)&lt;br /&gt;
# Fixed tile size in pixels&lt;br /&gt;
# Fixed layer name and/or layer name ordering&lt;br /&gt;
# Fixed styling&lt;br /&gt;
# Fixed output format&lt;br /&gt;
&lt;br /&gt;
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?&lt;br /&gt;
&lt;br /&gt;
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&amp;amp;sect; 7.2).&lt;br /&gt;
&lt;br /&gt;
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.&lt;br /&gt;
&lt;br /&gt;
=== Calculating Valid Tile Extents for a Given Request ===&lt;br /&gt;
&lt;br /&gt;
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.&lt;br /&gt;
&lt;br /&gt;
=== Possible Tile Scheme Parameters ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;This service suppports tiling.&amp;quot; || ''none'' || ''&amp;amp;lt;KeywordList&amp;amp;gt;'' contains the string 'tiled', perhaps? (&amp;amp;sect;7.1.4.5.3)&lt;br /&gt;
|-&lt;br /&gt;
| Projection || EPSG:4326 || ''&amp;amp;lt;SRS&amp;amp;gt;'' &lt;br /&gt;
|-&lt;br /&gt;
| Maximal extent || (-180,-90,180,90) || ''&amp;amp;lt;BoundingBox&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.7)&lt;br /&gt;
|-&lt;br /&gt;
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&amp;amp;lt;DataURL&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.14)&lt;br /&gt;
|-&lt;br /&gt;
| Tile size in pixels || some power of 2 || &amp;amp;lt;Layer&amp;amp;gt; attribute ''fixedWidth'', ''fixedHeight'' (&amp;amp;sect;7.1.4.6)&lt;br /&gt;
|-&lt;br /&gt;
| Minimum scale || ''none'' || ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' or ''&amp;amp;lt;DataURL&amp;amp;gt;'' (see note, above)&lt;br /&gt;
|-&lt;br /&gt;
| Scale quantization factor || 2 || ''&amp;amp;lt;DataURL&amp;amp;gt;''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Other Considerations ==&lt;br /&gt;
&lt;br /&gt;
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?&lt;br /&gt;
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:&lt;br /&gt;
&lt;br /&gt;
 http://domain.tld/service?L=0&amp;amp;X=1&amp;amp;Y=2&lt;br /&gt;
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).&lt;br /&gt;
&lt;br /&gt;
== Distributed Caching ==&lt;br /&gt;
&lt;br /&gt;
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.&lt;br /&gt;
* Alternately, one could do [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.&lt;br /&gt;
&lt;br /&gt;
== Existing Tiling Schemes ==&lt;br /&gt;
&lt;br /&gt;
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]&lt;br /&gt;
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]&lt;br /&gt;
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request&lt;br /&gt;
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]&lt;br /&gt;
&lt;br /&gt;
Note: WW and OnEarth schemes are pretty much the same, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels.&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ossim.org/tiki-read_article.php?articleId=3 osgPlanet]&lt;br /&gt;
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])&lt;br /&gt;
* [http://worldkit.org/ WorldKit]&lt;br /&gt;
* [http://mapbuilder.sf.net/ Community MapBuilder]&lt;br /&gt;
* other AJAX map clients, presumably&lt;br /&gt;
&lt;br /&gt;
== Interested Parties ==&lt;br /&gt;
* [[User:SchuylerErle|Schuyler Erle]]&lt;br /&gt;
* [[User&amp;quot;Adoyle&amp;quot;|Allan Doyle]]&lt;br /&gt;
* [[user&amp;quot;Nhv&amp;quot;|Norman Vine]]&lt;br /&gt;
* [[user&amp;quot;Joshli&amp;quot;|Josh Lieberman]]&lt;br /&gt;
* [[user&amp;quot;Adamhill&amp;quot;|Adam Hill]]&lt;br /&gt;
* [[user&amp;quot;bitner&amp;quot;|David Bitner]]&lt;br /&gt;
* [[user:Mikel|Mikel Maron]]&lt;br /&gt;
* ''add yourself''&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3044</id>
		<title>WMS Tile Caching</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3044"/>
		<updated>2006-03-31T11:55:10Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Interested Parties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Goal ==&lt;br /&gt;
&lt;br /&gt;
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.&lt;br /&gt;
&lt;br /&gt;
The two main questions to be addressed are:&lt;br /&gt;
# How does a server advertise its cacheable image tiles?&lt;br /&gt;
# How does a client request possibly cached image tiles?&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== WMS-C as WMS Profile ===&lt;br /&gt;
&lt;br /&gt;
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.&lt;br /&gt;
&lt;br /&gt;
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:&lt;br /&gt;
&lt;br /&gt;
# Minimal query string arguments (i.e. no optional arguments permitted, versus &amp;amp;sect;7.2)&lt;br /&gt;
# Fixed query string argument ordering and case (versus &amp;amp;sect;6.4.1; q.v. also &amp;amp;sect;7.2.2, Table 8)&lt;br /&gt;
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters&lt;br /&gt;
# Fixed precision on bounding box values (clarifying &amp;amp;sect;6.5.6)&lt;br /&gt;
# Fixed tile size in pixels&lt;br /&gt;
# Fixed layer name and/or layer name ordering&lt;br /&gt;
# Fixed styling&lt;br /&gt;
# Fixed output format&lt;br /&gt;
&lt;br /&gt;
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?&lt;br /&gt;
&lt;br /&gt;
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&amp;amp;sect; 7.2).&lt;br /&gt;
&lt;br /&gt;
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.&lt;br /&gt;
&lt;br /&gt;
=== Calculating Valid Tile Extents for a Given Request ===&lt;br /&gt;
&lt;br /&gt;
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.&lt;br /&gt;
&lt;br /&gt;
=== Possible Tile Scheme Parameters ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;This service suppports tiling.&amp;quot; || ''none'' || ''&amp;amp;lt;KeywordList&amp;amp;gt;'' contains the string 'tiled', perhaps? (&amp;amp;sect;7.1.4.5.3)&lt;br /&gt;
|-&lt;br /&gt;
| Projection || EPSG:4326 || ''&amp;amp;lt;SRS&amp;amp;gt;'' &lt;br /&gt;
|-&lt;br /&gt;
| Maximal extent || (-180,-90,180,90) || ''&amp;amp;lt;BoundingBox&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.7)&lt;br /&gt;
|-&lt;br /&gt;
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&amp;amp;lt;DataURL&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.14)&lt;br /&gt;
|-&lt;br /&gt;
| Tile size in pixels || some power of 2 || &amp;amp;lt;Layer&amp;amp;gt; attribute ''fixedWidth'', ''fixedHeight'' (&amp;amp;sect;7.1.4.6)&lt;br /&gt;
|-&lt;br /&gt;
| Minimum scale || ''none'' || ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' or ''&amp;amp;lt;DataURL&amp;amp;gt;'' (see note, above)&lt;br /&gt;
|-&lt;br /&gt;
| Scale quantization factor || 2 || ''&amp;amp;lt;DataURL&amp;amp;gt;''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Other Considerations ==&lt;br /&gt;
&lt;br /&gt;
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?&lt;br /&gt;
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:&lt;br /&gt;
&lt;br /&gt;
 http://domain.tld/service?L=0&amp;amp;X=1&amp;amp;Y=2&lt;br /&gt;
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).&lt;br /&gt;
&lt;br /&gt;
== Distributed Caching ==&lt;br /&gt;
&lt;br /&gt;
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.&lt;br /&gt;
* Alternately, one could do [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.&lt;br /&gt;
&lt;br /&gt;
== Existing Tiling Schemes ==&lt;br /&gt;
&lt;br /&gt;
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]&lt;br /&gt;
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]&lt;br /&gt;
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request&lt;br /&gt;
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]&lt;br /&gt;
&lt;br /&gt;
Note: WW and OnEarth schemes are pretty much the same, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels.&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ossim.org/tiki-read_article.php?articleId=3 osgPlanet]&lt;br /&gt;
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])&lt;br /&gt;
* [http://worldkit.org/ WorldKit]&lt;br /&gt;
* [http://mapbuilder.sf.net/ Community MapBuilder]&lt;br /&gt;
* other AJAX map clients, presumably&lt;br /&gt;
&lt;br /&gt;
== Interested Parties ==&lt;br /&gt;
* [[User:SchuylerErle|Schuyler Erle]]&lt;br /&gt;
* [[User&amp;quot;Adoyle&amp;quot;|Allan Doyle]]&lt;br /&gt;
* [[user&amp;quot;Nhv&amp;quot;|Norman Vine]]&lt;br /&gt;
* [[user&amp;quot;Joshli&amp;quot;|Josh Lieberman]]&lt;br /&gt;
* [[user&amp;quot;Adamhill&amp;quot;|Adam Hill]]&lt;br /&gt;
* [[user&amp;quot;bitner&amp;quot;|David Bitner]]&lt;br /&gt;
* [[user:Mikel|Mikel Maorn]]&lt;br /&gt;
* ''add yourself''&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3043</id>
		<title>WMS Tile Caching</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3043"/>
		<updated>2006-03-31T11:54:51Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Related Projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Goal ==&lt;br /&gt;
&lt;br /&gt;
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.&lt;br /&gt;
&lt;br /&gt;
The two main questions to be addressed are:&lt;br /&gt;
# How does a server advertise its cacheable image tiles?&lt;br /&gt;
# How does a client request possibly cached image tiles?&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== WMS-C as WMS Profile ===&lt;br /&gt;
&lt;br /&gt;
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.&lt;br /&gt;
&lt;br /&gt;
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:&lt;br /&gt;
&lt;br /&gt;
# Minimal query string arguments (i.e. no optional arguments permitted, versus &amp;amp;sect;7.2)&lt;br /&gt;
# Fixed query string argument ordering and case (versus &amp;amp;sect;6.4.1; q.v. also &amp;amp;sect;7.2.2, Table 8)&lt;br /&gt;
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters&lt;br /&gt;
# Fixed precision on bounding box values (clarifying &amp;amp;sect;6.5.6)&lt;br /&gt;
# Fixed tile size in pixels&lt;br /&gt;
# Fixed layer name and/or layer name ordering&lt;br /&gt;
# Fixed styling&lt;br /&gt;
# Fixed output format&lt;br /&gt;
&lt;br /&gt;
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?&lt;br /&gt;
&lt;br /&gt;
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&amp;amp;sect; 7.2).&lt;br /&gt;
&lt;br /&gt;
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.&lt;br /&gt;
&lt;br /&gt;
=== Calculating Valid Tile Extents for a Given Request ===&lt;br /&gt;
&lt;br /&gt;
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.&lt;br /&gt;
&lt;br /&gt;
=== Possible Tile Scheme Parameters ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;This service suppports tiling.&amp;quot; || ''none'' || ''&amp;amp;lt;KeywordList&amp;amp;gt;'' contains the string 'tiled', perhaps? (&amp;amp;sect;7.1.4.5.3)&lt;br /&gt;
|-&lt;br /&gt;
| Projection || EPSG:4326 || ''&amp;amp;lt;SRS&amp;amp;gt;'' &lt;br /&gt;
|-&lt;br /&gt;
| Maximal extent || (-180,-90,180,90) || ''&amp;amp;lt;BoundingBox&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.7)&lt;br /&gt;
|-&lt;br /&gt;
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&amp;amp;lt;DataURL&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.14)&lt;br /&gt;
|-&lt;br /&gt;
| Tile size in pixels || some power of 2 || &amp;amp;lt;Layer&amp;amp;gt; attribute ''fixedWidth'', ''fixedHeight'' (&amp;amp;sect;7.1.4.6)&lt;br /&gt;
|-&lt;br /&gt;
| Minimum scale || ''none'' || ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' or ''&amp;amp;lt;DataURL&amp;amp;gt;'' (see note, above)&lt;br /&gt;
|-&lt;br /&gt;
| Scale quantization factor || 2 || ''&amp;amp;lt;DataURL&amp;amp;gt;''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Other Considerations ==&lt;br /&gt;
&lt;br /&gt;
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?&lt;br /&gt;
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:&lt;br /&gt;
&lt;br /&gt;
 http://domain.tld/service?L=0&amp;amp;X=1&amp;amp;Y=2&lt;br /&gt;
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).&lt;br /&gt;
&lt;br /&gt;
== Distributed Caching ==&lt;br /&gt;
&lt;br /&gt;
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.&lt;br /&gt;
* Alternately, one could do [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.&lt;br /&gt;
&lt;br /&gt;
== Existing Tiling Schemes ==&lt;br /&gt;
&lt;br /&gt;
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]&lt;br /&gt;
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]&lt;br /&gt;
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request&lt;br /&gt;
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]&lt;br /&gt;
&lt;br /&gt;
Note: WW and OnEarth schemes are pretty much the same, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels.&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ossim.org/tiki-read_article.php?articleId=3 osgPlanet]&lt;br /&gt;
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])&lt;br /&gt;
* [http://worldkit.org/ WorldKit]&lt;br /&gt;
* [http://mapbuilder.sf.net/ Community MapBuilder]&lt;br /&gt;
* other AJAX map clients, presumably&lt;br /&gt;
&lt;br /&gt;
== Interested Parties ==&lt;br /&gt;
* [[User:SchuylerErle|Schuyler Erle]]&lt;br /&gt;
* [[User&amp;quot;Adoyle&amp;quot;|Allan Doyle]]&lt;br /&gt;
* [[user&amp;quot;Nhv&amp;quot;|Norman Vine]]&lt;br /&gt;
* [[user&amp;quot;Joshli&amp;quot;|Josh Lieberman]]&lt;br /&gt;
* [[user&amp;quot;Adamhill&amp;quot;|Adam Hill]]&lt;br /&gt;
* [[user&amp;quot;bitner&amp;quot;|David Bitner]]&lt;br /&gt;
* ''add yourself''&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3042</id>
		<title>WMS Tile Caching</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=WMS_Tile_Caching&amp;diff=3042"/>
		<updated>2006-03-31T11:54:07Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: /* Other Considerations */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Goal ==&lt;br /&gt;
&lt;br /&gt;
The goal of a '''WMS Tile Caching''' proposal, perhaps ''WMS-C'' for short, is to find a way to optimize the delivery of map imagery across the Internet. The proposal needs to offer ideally some means by which map clients can fetch tiles from existing servers, in such a way that the images can be cached on the server, or at an intermediate location, or even be completely pre-generated, if desired. Further, the proposal needs to offer a way of advertising that a cached tile set is available for a given layer from a particular WMS or WMS proxy. The proposal should leverage the existing investment in OGC-compliant WMS servers on the 'Net.&lt;br /&gt;
&lt;br /&gt;
The two main questions to be addressed are:&lt;br /&gt;
# How does a server advertise its cacheable image tiles?&lt;br /&gt;
# How does a client request possibly cached image tiles?&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
&lt;br /&gt;
=== WMS-C as WMS Profile ===&lt;br /&gt;
&lt;br /&gt;
One approach to take might be to define ''WMS-C'' (as in ''Web Mapping Service - Cached'') as a constrained profile of [http://www.opengeospatial.org/docs/01-068r2.pdf OGC WMS] that permits servers to optimize their image generation, and allows tiles to be cached at intermediate points. A WMS-C service would likely only deliver images for bounding boxes aligned to a given rectangular origin and grid, and only at particular scale levels.&lt;br /&gt;
&lt;br /&gt;
The basic idea is that, unlike with WMS, two different requests for a given WMS-C tile should form the exact same HTTP GET request. This invites several constraints on WMS ''GetMap'' requests:&lt;br /&gt;
&lt;br /&gt;
# Minimal query string arguments (i.e. no optional arguments permitted, versus &amp;amp;sect;7.2)&lt;br /&gt;
# Fixed query string argument ordering and case (versus &amp;amp;sect;6.4.1; q.v. also &amp;amp;sect;7.2.2, Table 8)&lt;br /&gt;
# Fixed range of possible bounding boxes, computed from the WMS-C profile parameters&lt;br /&gt;
# Fixed precision on bounding box values (clarifying &amp;amp;sect;6.5.6)&lt;br /&gt;
# Fixed tile size in pixels&lt;br /&gt;
# Fixed layer name and/or layer name ordering&lt;br /&gt;
# Fixed styling&lt;br /&gt;
# Fixed output format&lt;br /&gt;
&lt;br /&gt;
Some means of identifying these constraints programmatically on a per-server basis, a la ''GetCapabilities'' might be desirable. From the table below, it appears that minimum/maximum scale (and scale quantization factor, which should probably never be other than 2) are the only suggested tiling regime parameters that would be difficult to directly express in a WMS GetCapabilities document. Is there some existing way to add custom parameters to a GetCapabilities declaration?&lt;br /&gt;
&lt;br /&gt;
Note that the ''LAYERS'', ''STYLES'', ''SRS'', ''HEIGHT'', ''WIDTH'', and ''FORMAT'' arguments to a ''GetMap'' request would become fixed for a particular WMS-C tiled layer, but the WMS specification would still require the inclusion of these arguments in every WMS-C request (&amp;amp;sect; 7.2).&lt;br /&gt;
&lt;br /&gt;
A WMS-C proxy or server should be free to return an exception or a redirect, if it receives a WMS request that is not WMS-C compliant, or involves a bounding box that does not correspond to a single tile in the cache.&lt;br /&gt;
&lt;br /&gt;
=== Calculating Valid Tile Extents for a Given Request ===&lt;br /&gt;
&lt;br /&gt;
WMS tile caching implies fixed scale or zoom levels. Typically, each valid scale level would be half that of the next larger scale. It would be worth writing reference code to help developers figure out which tiles they need to load to cover a given bounding box at a given scale.&lt;br /&gt;
&lt;br /&gt;
=== Possible Tile Scheme Parameters ===&lt;br /&gt;
&lt;br /&gt;
{| cellpadding=&amp;quot;5&amp;quot; cellspacing=&amp;quot;1&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
| '''Parameter''' || '''Default value''' || '''Specifiable in WMS GetCapabilities?'''&lt;br /&gt;
|-&lt;br /&gt;
| &amp;quot;This service suppports tiling.&amp;quot; || ''none'' || ''&amp;amp;lt;KeywordList&amp;amp;gt;'' contains the string 'tiled', perhaps? (&amp;amp;sect;7.1.4.5.3)&lt;br /&gt;
|-&lt;br /&gt;
| Projection || EPSG:4326 || ''&amp;amp;lt;SRS&amp;amp;gt;'' &lt;br /&gt;
|-&lt;br /&gt;
| Maximal extent || (-180,-90,180,90) || ''&amp;amp;lt;BoundingBox&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.7)&lt;br /&gt;
|-&lt;br /&gt;
| Number of horizontal and vertical tiles at the maximal extent || ''none'' || Could be implied by ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.8, but note that the format is weakly specified)... Alternately, could use ''&amp;amp;lt;DataURL&amp;amp;gt;'' (&amp;amp;sect;7.1.4.5.14)&lt;br /&gt;
|-&lt;br /&gt;
| Tile size in pixels || some power of 2 || &amp;amp;lt;Layer&amp;amp;gt; attribute ''fixedWidth'', ''fixedHeight'' (&amp;amp;sect;7.1.4.6)&lt;br /&gt;
|-&lt;br /&gt;
| Minimum scale || ''none'' || ''&amp;amp;lt;ScaleHint&amp;amp;gt;'' or ''&amp;amp;lt;DataURL&amp;amp;gt;'' (see note, above)&lt;br /&gt;
|-&lt;br /&gt;
| Scale quantization factor || 2 || ''&amp;amp;lt;DataURL&amp;amp;gt;''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Other Considerations ==&lt;br /&gt;
&lt;br /&gt;
* Would non-rectangular tessellations yield more efficient results? If so, which tessellations to consider? Also, are the processing and bandwidth advantages of a non-rectangular tessellation outweighed by the potential implementation complexity?&lt;br /&gt;
* Norm Vine rightly points out that a tile request basically boils (or should boil down to) Layer + Zoom Level + Row + Column. Can we define an even simpler method for requesting tiles from servers in the know? How are those capabilities advertised, if not shoehorned into WMS? Note that WorldWind basically already has a mechanism for this. Their tiling requests basically look like:&lt;br /&gt;
&lt;br /&gt;
 http://domain.tld/service?L=0&amp;amp;X=1&amp;amp;Y=2&lt;br /&gt;
* Like all caching schemes, WMS-C caches would need to be cognizant of expiration. Easy with using the proper HTTP headers. There is a wide range of freshness/staleness, with OpenStreetMap being highly volatile, and Landsat being pretty stable (until the ice caps melt ;).&lt;br /&gt;
&lt;br /&gt;
== Distributed Caching ==&lt;br /&gt;
&lt;br /&gt;
* A WMS-C standard would permit tile caching through [http://www.coralcdn.org/ Coral]. However, the World Wind community's experience has been that using Coral to serve tiles results in frustratingly high latency.&lt;br /&gt;
* Alternately, one could do [[Distributed Tile Caching|peer-to-peer tile caching]] optimized specifically for geographic space, which might still suffer the latency issues associated with P2P networks.&lt;br /&gt;
&lt;br /&gt;
== Existing Tiling Schemes ==&lt;br /&gt;
&lt;br /&gt;
* Mikel Maron's description of [http://lists.eogeo.org/pipermail/tiling/2006-March/000017.html OnEarth's LandSat tiling scheme]&lt;br /&gt;
* World Wind's LandSat tiling scheme: [http://www.ceteranet.com/nww-tile-struct.pdf PDF], [http://www.worldwindcentral.com/wiki/Making_Layers wiki]&lt;br /&gt;
* World Wind ''QuadTileSet'' [http://rafb.net/paste/results/S3I8Zr92.html sample description], [http://forum.worldwind.arc.nasa.gov/lofiversion/index.php?t2965.html forum discussion], [http://rafb.net/paste/results/z2dQKa54.html sample PHP code] to fetch WW tiles for a given WMS GetMap request&lt;br /&gt;
* osgPlanet's C++ code for [http://www.remotesensing.org/cgi-bin/cvsweb.cgi/osgPlanet/src/osgPlanet/osgPlanetGridUtility.cpp?rev=HEAD;content-type=text%2Fx-cvsweb-markup tiling the Earth]&lt;br /&gt;
&lt;br /&gt;
Note: WW and OnEarth schemes are pretty much the same, the WW client just allows you to specify arbitrary tile sizes, coverages and number of levels.&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ossim.org/tiki-read_article.php?articleId=3 osgPlanet]&lt;br /&gt;
* [http://worldwind.arc.nasa.gov/ NASA WorldWind] ([http://www.worldwindcentral.com/wiki/Main_page wiki])&lt;br /&gt;
* [http://brainoff.com/worldkit/ WorldKit]&lt;br /&gt;
* [http://mapbuilder.sf.net/ Community MapBuilder]&lt;br /&gt;
* other AJAX map clients, presumably&lt;br /&gt;
&lt;br /&gt;
== Interested Parties ==&lt;br /&gt;
* [[User:SchuylerErle|Schuyler Erle]]&lt;br /&gt;
* [[User&amp;quot;Adoyle&amp;quot;|Allan Doyle]]&lt;br /&gt;
* [[user&amp;quot;Nhv&amp;quot;|Norman Vine]]&lt;br /&gt;
* [[user&amp;quot;Joshli&amp;quot;|Josh Lieberman]]&lt;br /&gt;
* [[user&amp;quot;Adamhill&amp;quot;|Adam Hill]]&lt;br /&gt;
* [[user&amp;quot;bitner&amp;quot;|David Bitner]]&lt;br /&gt;
* ''add yourself''&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Public_Geospatial_Data_Project&amp;diff=2495</id>
		<title>Public Geospatial Data Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Public_Geospatial_Data_Project&amp;diff=2495"/>
		<updated>2006-03-22T15:41:39Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Mikel: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;''This project was recently approved as [[Public Geospatial Data Committee|official foundation committee]].''&lt;br /&gt;
&lt;br /&gt;
== Mission ==&lt;br /&gt;
&lt;br /&gt;
=== Promote the use of open geospatial formats ===&lt;br /&gt;
Providing best-practise guidelines and examples for use of open and free standards for data (GML, WMS, WFS-T) and metadata (Dublin Core, RDF).&lt;br /&gt;
&lt;br /&gt;
=== Promote public access to state-collected geodata ===&lt;br /&gt;
&lt;br /&gt;
Lead by example in demonstrating economic value and research activity generated by open access to public geographic information.&lt;br /&gt;
&lt;br /&gt;
=== Run a repository of open geodata ===&lt;br /&gt;
A collection of geospatial datasets shall be hosted by the PGDP.&lt;br /&gt;
Additionally, links to other open data repostories shall be collected.&lt;br /&gt;
&lt;br /&gt;
=== Present and explain licenses for public geodata ===&lt;br /&gt;
The PGDP aims to collect licenses suitable for the publishing of public geodata. The license shall be presented along with a summary of its benefits and focus.&lt;br /&gt;
&lt;br /&gt;
== Approach ==&lt;br /&gt;
&lt;br /&gt;
The Public Geospatial Data Project of the Open Source Geospatial Foundation is currently in the &amp;quot;definition phase&amp;quot;. That means that we're in the process of putting together information about the kinds of things we could do, which organizations might be relevant, how the project might be structured, etc. Since the entire OSGeo is new, we're really working out the process for starting a non-software based project as we go.&lt;br /&gt;
&lt;br /&gt;
'''Likely scenario'''&lt;br /&gt;
* Information gathering&lt;br /&gt;
* Develop list of potential participants&lt;br /&gt;
* Invite people/organizations to express interest&lt;br /&gt;
* Discuss potential charter (is there an &amp;quot;official&amp;quot; OSGeo name for this?)&lt;br /&gt;
* Present charter to OSGeo Board for approval (or do the members also get to vote on it?)&lt;br /&gt;
** Charter should probably have &amp;quot;Terms of Reference&amp;quot; - i.e. what the group will do&lt;br /&gt;
** Charter should probably have an initial list of participants/organizations (not all need to be members)&lt;br /&gt;
** Charter should name a Chair and a Vice Chair (or co-chairs?) (must proposed chair already be a member or can s/he become a member by virtue of being part of this?)&lt;br /&gt;
* Assuming project is approved - Get to work!&lt;br /&gt;
&lt;br /&gt;
== Potential Members ==&lt;br /&gt;
If you add people/orgs to this list, please indicate whether you're adding yourself/your organization or whether you are &amp;quot;nominating&amp;quot; the person/organization as a potential member.&lt;br /&gt;
&lt;br /&gt;
=== Individuals ===&lt;br /&gt;
&lt;br /&gt;
''Please add yourself''&lt;br /&gt;
&lt;br /&gt;
* David Bitner (self)&lt;br /&gt;
* Allan Doyle (self)&lt;br /&gt;
* Florian Kindl (nominated)&lt;br /&gt;
* Pericles S. Nacionales (self)&lt;br /&gt;
* Markus Neteler (self)&lt;br /&gt;
* Jo Walsh (nominated)&lt;br /&gt;
* Helton Uchoa (self) - [[User:Uchoa]]&lt;br /&gt;
* Aaron Racicot (self) - Ecotrust - aaronr at ecotrust.org&lt;br /&gt;
* Daniel Brookshier (self)&lt;br /&gt;
* Schuyler Erle (self)&lt;br /&gt;
* Jeff McKenna (DM Solutions)&lt;br /&gt;
* Steve Coast (nominated)&lt;br /&gt;
* Mikel Maron (self)&lt;br /&gt;
&lt;br /&gt;
=== Organizations ===&lt;br /&gt;
* [http://www.eogeo.org EOGEO] (self)&lt;br /&gt;
* [http://www.openstreetmap.org/ OpenStreetMap Project] (potential)&lt;br /&gt;
* [http://www.gsdi.org GSDI Association] (potential)&lt;br /&gt;
&lt;br /&gt;
== Events ==&lt;br /&gt;
Events where we can either promote our positions or are likely to run into like-minded individuals.&lt;br /&gt;
&lt;br /&gt;
* [http://www.asia-commons.net/ Asian Conference on the Digital Commons - April 18-20, 2006, Bangkok, Thailand]&lt;br /&gt;
* [http://conferences.oreillynet.com/where2006/ Where 2.0 - June 13-14, 2006, San Jose, California, USA]&lt;br /&gt;
* [http://www.foss4g2006.org/ FOSS4G2006 - Free And Open Source Software for Geoinformatics - September 12-15, 2006, Lausanne, Switzerland]&lt;br /&gt;
&lt;br /&gt;
== Existing Work ==&lt;br /&gt;
&lt;br /&gt;
=== Geo Data Licenses ===&lt;br /&gt;
* [http://sig.cwriter.org/index.php/PGL Public Geodata License]&lt;br /&gt;
* [http://cemml.carleton.ca:8080/OGUG/pgl Group PGL-Canada]&lt;br /&gt;
* [http://creativecommons.org/ Creative Commons]&lt;br /&gt;
&lt;br /&gt;
=== Geo Data Repositories / Group Collection Projects ===&lt;br /&gt;
* [http://www.openstreetmap.org/ OpenStreetMap Project]&lt;br /&gt;
* [http://freeearthfoundation.com/ Free Earth Foundation]&lt;br /&gt;
* [http://geobase.ca/ Canadian Base Data]&lt;br /&gt;
* [http://geotorrent.org/ Various Free Datasets via Bittorrent]&lt;br /&gt;
* [http://www.iscgm.org/cgi-bin/fswiki/wiki.cgi Global Map] - International Steering Committee for Global Mapping&lt;br /&gt;
* [http://www.geonames.org Geonames.org] - Geonames is integrating geographical data such as names, altitude, population and others from various sources&lt;br /&gt;
* [http://www.geo-one-stop.gov/ Geospatial One Stop]&lt;br /&gt;
* [http://gcmd.nasa.gov/index.html Global Change Master Directory]&lt;br /&gt;
&lt;br /&gt;
=== Geo Data Repository &amp;amp; Policy Research ===&lt;br /&gt;
* [http://geodatacommons.umaine.edu/CGDPlone University of Maine Commons for Geographic Data]&lt;br /&gt;
* [http://metrogis.org MetroGIS] Twin Cities, MN Metro Area Public Agency Data Sharing Effort&lt;br /&gt;
* [http://www.gis.state.mn.us MN Governor's Council on Geographic Information]&lt;br /&gt;
&lt;br /&gt;
=== Geo Data Policy Advocacy ===&lt;br /&gt;
* [http://www.publicgeodata.org/ Public Geodata Project] (IRC: [irc://freenode/publicgeodata publicgeodata]) with the support of the Open Knowledge Foundation&lt;br /&gt;
* [http://okfn.org/geo/manifesto.php Open Access to State-Collected Geospatial Data Manifesto]&lt;br /&gt;
&lt;br /&gt;
=== Open Access ===&lt;br /&gt;
There are also more general open access movements, often aimed at scientific data, that could provide a venue for broadening awareness of the geo-specific issues.&lt;br /&gt;
&lt;br /&gt;
* [http://oa.mpg.de/openaccess-golm/index.html Berlin 4 Open Access - From Promise to Practice - March 29-31, 2006 Golm, Germany]&lt;br /&gt;
* [http://oa.mpg.de/openaccess-berlin/berlindeclaration.html Berlin Declaration on Open Access to Knowledge in the Sciences and Humanities]&lt;br /&gt;
* [http://www.locusforums.org/forum/ The Locus Forum] - &amp;quot;The Locus Association is a trade association of private organisations working to increase opportunities and reduce barriers to fair trade between the public and private sector, particularly in the use of Public Sector Information.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Further Reading ==&lt;br /&gt;
&lt;br /&gt;
* [http://technology.guardian.co.uk/weekly/story/0,,1726229,00.html Give us back our crown jewels] - 2006-03-09 article in the Guardian&lt;br /&gt;
* [http://www.directionsmag.com/article.php?article_id=2107&amp;amp;trv=1 Why Europe Needs to Provide its Own Public Geodata ] by Jo Walsh (Feb 15, 2006)&lt;br /&gt;
* [http://www.systemed.net/blog/entry060311122655.html ShareAlike considered harmful for geodata] by Richard Fairhurst, a critique of GPL-like licensing situations with suggested LGPL-like model for distribution.&lt;br /&gt;
*  &amp;quot;Open Source Software for Spatial Data Infrastructure (FOSSDI)&amp;quot;. SDIC submitted 2005 to INSPIRE/EU. &amp;lt;br&amp;gt; [http://mpa.itc.it/markus/papers/sdic_call_fossdi.pdf PDF with layout] | [http://inspire.jrc.it/ir/sdic_view_step1_only.cfm?id=2163 HTML without layout]&lt;br /&gt;
* [http://mitworld.mit.edu/video/270/ Open Networks and Open Society: The Relationship between Freedom, Law, and Technology] - MIT World video featuring Hal Abelson, John Wilbanks, Creative Commons&lt;/div&gt;</summary>
		<author><name>Wiki-Mikel</name></author>
	</entry>
</feed>