OSGeo - User contributions [en]

Google Code In 2017 Tasks

2017-10-08T20:04:23Z

Wiki-Sfkeller: /* QGIS */

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;User Interface
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

Choose tasks from any of the OSGeo projects below (these are official OSGeo projects, projects in OSGeo incubation, and OSGeo community projects):

== Content Management Systems ==

=== GeoNode ===

official website: http://geonode.org/

mentor: N/A

tasks: N/A

== Desktop ==

=== GRASS GIS ===

official website: http://grass.osgeo.org/

mentors: [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]]

more info: http://grasswiki.osgeo.org/wiki/GRASS_GCI_Ideas_2017

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Create a screenshot for the next 74 release announcement || ADVANCED || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 2 || Design the t-shirt for the next code-sprint || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 3 || Add examples to manual pages || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 4 || Make new tutorial videos for GRASS GIS || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 5 || Write a short blog entry about GRASS GIS (or a certain module) || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 6 || Enhance the visual index || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 7 || Make screenshots to populate the visual change log in new features pages (e.g., for New Features GRASS 7.4) || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Create icons/phrases to include in sticker sheets || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Give a talk about GRASS GIS to classmates || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Submit a patch for a certain bug or enhancement ticket || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Contribute tests for modules || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|+
|}

=== gvSIG ===

official website: http://www.gvsig.com/

mentor: N/A

tasks: N/A

=== Marble ===

official website: http://marble.kde.org/

mentor: N/A

tasks: N/A

=== Opticks ===

official website: http://opticks.org/

mentor: N/A

tasks: N/A

=== Virtual Terrain Project ===

official website: https://wiki.osgeo.org/wiki/Virtual_Terrain_Project

mentor: N/A

tasks: N/A

=== QGIS ===

official website: http://qgis.org

mentor: N/A

tasks: N/A

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Enhance map style of [http://plugins.qgis.org/plugins/vector_tiles_reader/ "Vector Tiles Reader"] plugin || INTERMEDIATE || Update the built-in base map QGIS styles (QML) for OpenMapTiles. (See also [https://github.com/geometalab/Vector-Tiles-Reader-QGIS-Plugin/issues/89 Issue #89]). || cartography/graphic designing (aka 'coding') || [[User:Sfkeller]] ||
|-
| 2 || tbd. || tbd. || tbd. || tbd. || pending ||
|+
|}

== Geospatial Libraries ==

=== FDO ===

official website: http://fdo.osgeo.org/

mentor: N/A

tasks: N/A

=== GDAL/OGR ===

official website: http://gdal.org/

mentor: N/A

tasks: N/A

=== Geoinformatica ===

official website: https://wiki.osgeo.org/wiki/Geoinformatica

mentor: N/A

tasks: N/A

=== GEOS ===

official website: https://trac.osgeo.org/geos/

mentor: [[User:Robe|Regina Obe]]

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a logo || INTERMEDIATE || something simple, and squarish || art || pending ||
|-
| 2 || create a comic strip of the set operations on geometries: union, intersection, difference || BEGINNER || use your imagination || art || pending ||
|+
|}

=== GeoTools ===

official website: http://www.geotools.org/

mentor: N/A

tasks: N/A

=== MetaCRS ===

official website: http://metacrs.osgeo.org/

mentor: N/A

tasks: N/A

=== Orfeo ToolBox (OTB) ===

official website: http://www.orfeo-toolbox.org/

mentor: N/A

tasks: N/A

=== OSSIM ===

official website: https://trac.osgeo.org/ossim/

mentor: N/A

tasks: N/A

=== pgRouting ===

official website: https://wiki.osgeo.org/wiki/PgRouting

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://github.com/pgRouting/pgrouting/wiki/Google-Code-In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || create a page for the pgRouting workshop using the Wikipedia example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || add the results and a brief explanation of the results to the page created on Task 1 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || create a page for the pgRouting workshop using the Hanoslav example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || add the results and a brief explanation of the results to the page created on Task 3 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== PostGIS ===

official website: http://postgis.net/

mentor: [[User:Robe|Regina Obe]]

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker with a PostGIS elephant ||BEGINNER || Use your imagination || art || [[User:Robe|Regina Obe]] ||
|-
|-
| 2 || create a page of 5 commonly used PostGIS queries and what they solve ||INTERMEDIATE || For this task look over our docs for ideas of some queries and pick 5 you think are most useful|| documentation || [[User:Robe|Regina Obe]] ||
|-
| 3 || create a screen cast of how to install PostGIS (pick any OS you want) || INTERMEDIATE || || documentation || [[User:Robe|Regina Obe]] ||
|-
| 4 || create a comic strip of the core postgis types: geometry, geography, raster, and topology talking to each other || BEGINNER || For this task imagine there are 4 friends geomie, geoggie, rasterfa, and topolo what kind of conversation would they have? Each has a different perspective on things, geomie sees the world as a flat simple plane you can fall off of if you walk too far, geoggie sees the world as round where you can walk in any direction forever, rasterfa sees the world as a flat colorful place and believes a picture is worth a 1000 words, and topolo believes in the interconnectivity of all shapes where one object starts another begins but shares the flat view with geomie || art || [[User:Robe|Regina Obe]] ||
|+
|}

=== Postal Address Geo-Coder ===

official website: https://wiki.osgeo.org/wiki/Postal_Address_Geo-Coder

mentor: N/A

tasks: N/A

=== Proj4php ===

official website: https://wiki.osgeo.org/wiki/Proj4php

mentor: N/A

tasks: N/A

== Metadata Catalogs ==

=== GeoNetwork ===

official website: http://geonetwork-opensource.org/

mentor: N/A

tasks: N/A

=== pycsw ===

official website: http://pycsw.org/

mentor: N/A

tasks: N/A

== Web Mapping ==

=== deegree ===

official website: http://www.deegree.org/

mentor: N/A

tasks: N/A

=== geomajas ===

official website: http://www.geomajas.org/

mentor: N/A

tasks: N/A

=== GeoMOOSE ===

official website: http://www.geomoose.org/

mentor: N/A

tasks: N/A

=== GeoServer ===

official website: http://geoserver.org/

mentor: N/A

tasks: N/A

=== GeoWebCache ===

official website: https://wiki.osgeo.org/wiki/GeoWebCache

mentor: N/A

tasks: N/A

=== istSOS ===

official website: http://wiki.osgeo.org/wiki/IstSOS

mentor: N/A

tasks: N/A

=== Mapbender ===

official website: http://mapbender.org/

mentor: N/A

tasks: N/A

=== MapFish ===

official website: http://www.mapfish.org/

mentor: N/A

tasks: N/A

=== MapGuide Open Source ===

official website: http://mapguide.osgeo.org/

mentor: N/A

tasks: N/A

=== MapProxy ===

official website: https://wiki.osgeo.org/wiki/MapProxy

mentor: N/A

tasks: N/A

=== MapServer ===

official website: http://mapserver.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker || BEGINNER|| For this task... || marketing || [[Jeff McKenna]] ||
|-
| 2 || Make a video promoting MapServer, the fastest mapping engine || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Install MS4W on a Windows machine, and take screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Find and fix mistakes/urls on the mapserver.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Give a presentation to classmates about MapServer || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 6 || Fix any bug in the issue tracker || ADVANCED || For this task... || coding,C || [[Jeff McKenna]] ||
|+
|}

=== OpenLayers ===

official website: http://openlayers.org/

mentor: N/A

tasks: N/A

=== PyWPS ===

official website: http://www.pywps.org/

mentor: N/A

tasks: N/A

=== Team Engine ===

official website: http://teamengine.sourceforge.net/

mentor: N/A

tasks: N/A

=== ZOO-Project ===

official website: http://www.zoo-project.org/

mentor: N/A

tasks: N/A

== Outreach ==

=== FOSS4G ===

official website: http://foss4g.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a video about the FOSS4G conference || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the FOSS4G conference to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Create a replacement page for http://foss4g.org listing all conferences || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a new social media page for FOSS4G (facebook?) || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

=== GeoForAll ===

official website: http://www.osgeo.org/education

mentor: N/A

tasks: N/A

=== OSGeo-Live ===

official website: http://live.osgeo.org/

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://wiki.osgeo.org/wiki/OSGeoLive_Google_Code_In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Download and install OSGeoLive || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || Make a video for downloading and installing OSGeo-Live || INTERMEDIATE || For this task... || marketing || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || QGIS quick start video [PART 1] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || QGIS quick start video [PART 2] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== OSGeo Foundation ===

official website: http://osgeo.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a short video about the OSGeo foundation || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the OSGeo foundation to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Checkout part of git.osgeo.org locally, and create a screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a page on the OSGeo wiki || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Style the page https://trac.osgeo.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

[[Category:Google Code In]]

Google Code In 2017 Tasks

2017-10-08T18:37:12Z

Wiki-Sfkeller: /* QGIS */

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;User Interface
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

Choose tasks from any of the OSGeo projects below (these are official OSGeo projects, projects in OSGeo incubation, and OSGeo community projects):

== Content Management Systems ==

=== GeoNode ===

official website: http://geonode.org/

mentor: N/A

tasks: N/A

== Desktop ==

=== GRASS GIS ===

official website: http://grass.osgeo.org/

mentors: [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]]

more info: http://grasswiki.osgeo.org/wiki/GRASS_GCI_Ideas_2017

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Create a screenshot for the next 74 release announcement || ADVANCED || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 2 || Design the t-shirt for the next code-sprint || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 3 || Add examples to manual pages || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 4 || Make new tutorial videos for GRASS GIS || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 5 || Write a short blog entry about GRASS GIS (or a certain module) || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 6 || Enhance the visual index || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 7 || Make screenshots to populate the visual change log in new features pages (e.g., for New Features GRASS 7.4) || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Create icons/phrases to include in sticker sheets || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Give a talk about GRASS GIS to classmates || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Submit a patch for a certain bug or enhancement ticket || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Contribute tests for modules || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|+
|}

=== gvSIG ===

official website: http://www.gvsig.com/

mentor: N/A

tasks: N/A

=== Marble ===

official website: http://marble.kde.org/

mentor: N/A

tasks: N/A

=== Opticks ===

official website: http://opticks.org/

mentor: N/A

tasks: N/A

=== Virtual Terrain Project ===

official website: https://wiki.osgeo.org/wiki/Virtual_Terrain_Project

mentor: N/A

tasks: N/A

=== QGIS ===

official website: http://qgis.org

mentor: N/A

tasks: N/A

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Enhance map style of [http://plugins.qgis.org/plugins/vector_tiles_reader/ "Vector Tiles Reader"] plugin || INTERMEDIATE || Update the built-in base map QGIS styles (QML) for OpenMapTiles. (See also [https://github.com/geometalab/Vector-Tiles-Reader-QGIS-Plugin/issues/89 Issue #89]). || cartography || [[User:Sfkeller]] ||
|-
| 2 || tbd. || tbd. || tbd. || tbd. || pending ||
|+
|}

== Geospatial Libraries ==

=== FDO ===

official website: http://fdo.osgeo.org/

mentor: N/A

tasks: N/A

=== GDAL/OGR ===

official website: http://gdal.org/

mentor: N/A

tasks: N/A

=== Geoinformatica ===

official website: https://wiki.osgeo.org/wiki/Geoinformatica

mentor: N/A

tasks: N/A

=== GEOS ===

official website: https://trac.osgeo.org/geos/

mentor: [[User:Robe|Regina Obe]]

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a logo || INTERMEDIATE || something simple, and squarish || art || pending ||
|-
| 2 || create a comic strip of the set operations on geometries: union, intersection, difference || BEGINNER || use your imagination || art || pending ||
|+
|}

=== GeoTools ===

official website: http://www.geotools.org/

mentor: N/A

tasks: N/A

=== MetaCRS ===

official website: http://metacrs.osgeo.org/

mentor: N/A

tasks: N/A

=== Orfeo ToolBox (OTB) ===

official website: http://www.orfeo-toolbox.org/

mentor: N/A

tasks: N/A

=== OSSIM ===

official website: https://trac.osgeo.org/ossim/

mentor: N/A

tasks: N/A

=== pgRouting ===

official website: https://wiki.osgeo.org/wiki/PgRouting

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://github.com/pgRouting/pgrouting/wiki/Google-Code-In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || create a page for the pgRouting workshop using the Wikipedia example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || add the results and a brief explanation of the results to the page created on Task 1 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || create a page for the pgRouting workshop using the Hanoslav example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || add the results and a brief explanation of the results to the page created on Task 3 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== PostGIS ===

official website: http://postgis.net/

mentor: [[User:Robe|Regina Obe]]

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker with a PostGIS elephant ||BEGINNER || Use your imagination || art || [[User:Robe|Regina Obe]] ||
|-
|-
| 2 || create a page of 5 commonly used PostGIS queries and what they solve ||INTERMEDIATE || For this task look over our docs for ideas of some queries and pick 5 you think are most useful|| documentation || [[User:Robe|Regina Obe]] ||
|-
| 3 || create a screen cast of how to install PostGIS (pick any OS you want) || INTERMEDIATE || || documentation || [[User:Robe|Regina Obe]] ||
|-
| 4 || create a comic strip of the core postgis types: geometry, geography, raster, and topology talking to each other || BEGINNER || For this task imagine there are 4 friends geomie, geoggie, rasterfa, and topolo what kind of conversation would they have? Each has a different perspective on things, geomie sees the world as a flat simple plane you can fall off of if you walk too far, geoggie sees the world as round where you can walk in any direction forever, rasterfa sees the world as a flat colorful place and believes a picture is worth a 1000 words, and topolo believes in the interconnectivity of all shapes where one object starts another begins but shares the flat view with geomie || art || [[User:Robe|Regina Obe]] ||
|+
|}

=== Postal Address Geo-Coder ===

official website: https://wiki.osgeo.org/wiki/Postal_Address_Geo-Coder

mentor: N/A

tasks: N/A

=== Proj4php ===

official website: https://wiki.osgeo.org/wiki/Proj4php

mentor: N/A

tasks: N/A

== Metadata Catalogs ==

=== GeoNetwork ===

official website: http://geonetwork-opensource.org/

mentor: N/A

tasks: N/A

=== pycsw ===

official website: http://pycsw.org/

mentor: N/A

tasks: N/A

== Web Mapping ==

=== deegree ===

official website: http://www.deegree.org/

mentor: N/A

tasks: N/A

=== geomajas ===

official website: http://www.geomajas.org/

mentor: N/A

tasks: N/A

=== GeoMOOSE ===

official website: http://www.geomoose.org/

mentor: N/A

tasks: N/A

=== GeoServer ===

official website: http://geoserver.org/

mentor: N/A

tasks: N/A

=== GeoWebCache ===

official website: https://wiki.osgeo.org/wiki/GeoWebCache

mentor: N/A

tasks: N/A

=== istSOS ===

official website: http://wiki.osgeo.org/wiki/IstSOS

mentor: N/A

tasks: N/A

=== Mapbender ===

official website: http://mapbender.org/

mentor: N/A

tasks: N/A

=== MapFish ===

official website: http://www.mapfish.org/

mentor: N/A

tasks: N/A

=== MapGuide Open Source ===

official website: http://mapguide.osgeo.org/

mentor: N/A

tasks: N/A

=== MapProxy ===

official website: https://wiki.osgeo.org/wiki/MapProxy

mentor: N/A

tasks: N/A

=== MapServer ===

official website: http://mapserver.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker || BEGINNER|| For this task... || marketing || [[Jeff McKenna]] ||
|-
| 2 || Make a video promoting MapServer, the fastest mapping engine || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Install MS4W on a Windows machine, and take screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Find and fix mistakes/urls on the mapserver.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Give a presentation to classmates about MapServer || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 6 || Fix any bug in the issue tracker || ADVANCED || For this task... || coding,C || [[Jeff McKenna]] ||
|+
|}

=== OpenLayers ===

official website: http://openlayers.org/

mentor: N/A

tasks: N/A

=== PyWPS ===

official website: http://www.pywps.org/

mentor: N/A

tasks: N/A

=== Team Engine ===

official website: http://teamengine.sourceforge.net/

mentor: N/A

tasks: N/A

=== ZOO-Project ===

official website: http://www.zoo-project.org/

mentor: N/A

tasks: N/A

== Outreach ==

=== FOSS4G ===

official website: http://foss4g.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a video about the FOSS4G conference || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the FOSS4G conference to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Create a replacement page for http://foss4g.org listing all conferences || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a new social media page for FOSS4G (facebook?) || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

=== GeoForAll ===

official website: http://www.osgeo.org/education

mentor: N/A

tasks: N/A

=== OSGeo-Live ===

official website: http://live.osgeo.org/

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://wiki.osgeo.org/wiki/OSGeoLive_Google_Code_In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Download and install OSGeoLive || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || Make a video for downloading and installing OSGeo-Live || INTERMEDIATE || For this task... || marketing || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || QGIS quick start video [PART 1] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || QGIS quick start video [PART 2] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== OSGeo Foundation ===

official website: http://osgeo.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a short video about the OSGeo foundation || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the OSGeo foundation to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Checkout part of git.osgeo.org locally, and create a screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a page on the OSGeo wiki || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Style the page https://trac.osgeo.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

[[Category:Google Code In]]

Google Code In 2017 Tasks

2017-10-08T14:24:28Z

Wiki-Sfkeller: /* QGIS */

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;User Interface
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

Choose tasks from any of the OSGeo projects below (these are official OSGeo projects, projects in OSGeo incubation, and OSGeo community projects):

== Content Management Systems ==

=== GeoNode ===

official website: http://geonode.org/

mentor: N/A

tasks: N/A

== Desktop ==

=== GRASS GIS ===

official website: http://grass.osgeo.org/

mentors: [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]]

more info: http://grasswiki.osgeo.org/wiki/GRASS_GCI_Ideas_2017

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Create a screenshot for the next 74 release announcement || ADVANCED || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 2 || Design the t-shirt for the next code-sprint || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 3 || Add examples to manual pages || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 4 || Make new tutorial videos for GRASS GIS || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 5 || Write a short blog entry about GRASS GIS (or a certain module) || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 6 || Enhance the visual index || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 7 || Make screenshots to populate the visual change log in new features pages (e.g., for New Features GRASS 7.4) || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Create icons/phrases to include in sticker sheets || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Give a talk about GRASS GIS to classmates || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Submit a patch for a certain bug or enhancement ticket || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Contribute tests for modules || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|+
|}

=== gvSIG ===

official website: http://www.gvsig.com/

mentor: N/A

tasks: N/A

=== Marble ===

official website: http://marble.kde.org/

mentor: N/A

tasks: N/A

=== Opticks ===

official website: http://opticks.org/

mentor: N/A

tasks: N/A

=== Virtual Terrain Project ===

official website: https://wiki.osgeo.org/wiki/Virtual_Terrain_Project

mentor: N/A

tasks: N/A

=== QGIS ===

official website: http://qgis.org

mentor: N/A

tasks: N/A

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Enhance map style of "Vector Tiles Reader" plugin || INTERMEDIATE || Update the built-in base map QGIS styles (QML) for OpenMapTiles. (See also [https://github.com/geometalab/Vector-Tiles-Reader-QGIS-Plugin/issues/89 Issue #89]). || cartography || [[User:Sfkeller]] ||
|-
| 2 || tbd. || tbd. || tbd. || tbd. || pending ||
|+
|}

== Geospatial Libraries ==

=== FDO ===

official website: http://fdo.osgeo.org/

mentor: N/A

tasks: N/A

=== GDAL/OGR ===

official website: http://gdal.org/

mentor: N/A

tasks: N/A

=== Geoinformatica ===

official website: https://wiki.osgeo.org/wiki/Geoinformatica

mentor: N/A

tasks: N/A

=== GEOS ===

official website: https://trac.osgeo.org/geos/

mentor: N/A

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a logo || INTERMEDIATE || something simple, and squarish || art || pending ||
|-
| 2 || create a comic strip of the set operations on geometries: union, intersection, difference || BEGINNER || use your imagination || art || pending ||
|+
|}

=== GeoTools ===

official website: http://www.geotools.org/

mentor: N/A

tasks: N/A

=== MetaCRS ===

official website: http://metacrs.osgeo.org/

mentor: N/A

tasks: N/A

=== Orfeo ToolBox (OTB) ===

official website: http://www.orfeo-toolbox.org/

mentor: N/A

tasks: N/A

=== OSSIM ===

official website: https://trac.osgeo.org/ossim/

mentor: N/A

tasks: N/A

=== pgRouting ===

official website: https://wiki.osgeo.org/wiki/PgRouting

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://github.com/pgRouting/pgrouting/wiki/Google-Code-In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || create a page for the pgRouting workshop using the Wikipedia example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || add the results and a brief explanation of the results to the page created on Task 1 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || create a page for the pgRouting workshop using the Hanoslav example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || add the results and a brief explanation of the results to the page created on Task 3 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== PostGIS ===

official website: http://postgis.net/

mentor: Regina Obe

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker with a PostGIS elephant ||BEGINNER || Use your imagination || art || [[User:Robe|Regina Obe]] ||
|-
|-
| 2 || create a page of 5 commonly used PostGIS queries and what they solve ||INTERMEDIATE || For this task look over our docs for ideas of some queries and pick 5 you think are most useful|| documentation || [[User:Robe|Regina Obe]] ||
|-
| 3 || create a screen cast of how to install PostGIS (pick any OS you want) || INTERMEDIATE || || documentation || [[User:Robe|Regina Obe]] ||
|-
| 4 || create a comic strip of the core postgis types: geometry, geography, raster, and topology talking to each other || BEGINNER || For this task imagine there are 4 friends geomie, geoggie, rasterfa, and topolo what kind of conversation would they have? Each has a different perspective on things, geomie sees the world as a flat simple plane you can fall off of if you walk too far, geoggie sees the world as round where you can walk in any direction forever, rasterfa sees the world as a flat colorful place and believes a picture is worth a 1000 words, and topolo believes in the interconnectivity of all shapes where one object starts another begins but shares the flat view with geomie || art || [[User:Robe|Regina Obe]] ||
|+
|}

=== Postal Address Geo-Coder ===

official website: https://wiki.osgeo.org/wiki/Postal_Address_Geo-Coder

mentor: N/A

tasks: N/A

=== Proj4php ===

official website: https://wiki.osgeo.org/wiki/Proj4php

mentor: N/A

tasks: N/A

== Metadata Catalogs ==

=== GeoNetwork ===

official website: http://geonetwork-opensource.org/

mentor: N/A

tasks: N/A

=== pycsw ===

official website: http://pycsw.org/

mentor: N/A

tasks: N/A

== Web Mapping ==

=== deegree ===

official website: http://www.deegree.org/

mentor: N/A

tasks: N/A

=== geomajas ===

official website: http://www.geomajas.org/

mentor: N/A

tasks: N/A

=== GeoMOOSE ===

official website: http://www.geomoose.org/

mentor: N/A

tasks: N/A

=== GeoServer ===

official website: http://geoserver.org/

mentor: N/A

tasks: N/A

=== GeoWebCache ===

official website: https://wiki.osgeo.org/wiki/GeoWebCache

mentor: N/A

tasks: N/A

=== istSOS ===

official website: http://wiki.osgeo.org/wiki/IstSOS

mentor: N/A

tasks: N/A

=== Mapbender ===

official website: http://mapbender.org/

mentor: N/A

tasks: N/A

=== MapFish ===

official website: http://www.mapfish.org/

mentor: N/A

tasks: N/A

=== MapGuide Open Source ===

official website: http://mapguide.osgeo.org/

mentor: N/A

tasks: N/A

=== MapProxy ===

official website: https://wiki.osgeo.org/wiki/MapProxy

mentor: N/A

tasks: N/A

=== MapServer ===

official website: http://mapserver.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker || BEGINNER|| For this task... || marketing || [[Jeff McKenna]] ||
|-
| 2 || Make a video promoting MapServer, the fastest mapping engine || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Install MS4W on a Windows machine, and take screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Find and fix mistakes/urls on the mapserver.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Give a presentation to classmates about MapServer || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 6 || Fix any bug in the issue tracker || ADVANCED || For this task... || coding,C || [[Jeff McKenna]] ||
|+
|}

=== OpenLayers ===

official website: http://openlayers.org/

mentor: N/A

tasks: N/A

=== PyWPS ===

official website: http://www.pywps.org/

mentor: N/A

tasks: N/A

=== Team Engine ===

official website: http://teamengine.sourceforge.net/

mentor: N/A

tasks: N/A

=== ZOO-Project ===

official website: http://www.zoo-project.org/

mentor: N/A

tasks: N/A

== Outreach ==

=== FOSS4G ===

official website: http://foss4g.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a video about the FOSS4G conference || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the FOSS4G conference to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Create a replacement page for http://foss4g.org listing all conferences || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a new social media page for FOSS4G (facebook?) || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

=== GeoForAll ===

official website: http://www.osgeo.org/education

mentor: N/A

tasks: N/A

=== OSGeo-Live ===

official website: http://live.osgeo.org/

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://wiki.osgeo.org/wiki/OSGeoLive_Google_Code_In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Download and install OSGeoLive || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || Make a video for downloading and installing OSGeo-Live || INTERMEDIATE || For this task... || marketing || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || QGIS quick start video [PART 1] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || QGIS quick start video [PART 2] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== OSGeo Foundation ===

official website: http://osgeo.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a short video about the OSGeo foundation || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the OSGeo foundation to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Checkout part of git.osgeo.org locally, and create a screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a page on the OSGeo wiki || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Style the page https://trac.osgeo.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

[[Category:Google Code In]]

Google Code In 2017 Tasks

2017-10-08T14:20:53Z

Wiki-Sfkeller: /* QGIS */ Added task Enhance map style of "Vector Tiles Reader" plugin.

<center>
[[Image:GCI-logo.jpg|400px|link=https://developers.google.com/open-source/gci/]] @ [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Effort for a Task =

* Each task is expected to take '''3-5 hours''' of work to complete
* Students have at least '''3 days''' to complete the task

= Types of Tasks =

There are 5 types of Code-in Tasks in general:

;Code
: Tasks related to writing or refactoring code
;Documentation/Training
: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research
: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance
: Tasks related to testing and ensuring code is of high quality
;User Interface
: Tasks related to user experience research or user interface design and interaction

= Beginner Tasks =

* A student can only complete a total of 2 beginner tasks
* Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name

= Example Tasks =

* Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
** Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
* "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
* "Fix an issue in the tracker for project XXX [DIFFICULT]"
* "Present the project XXX to your class [BEGINNER]"

= Project Tasks =

Choose tasks from any of the OSGeo projects below (these are official OSGeo projects, projects in OSGeo incubation, and OSGeo community projects):

== Content Management Systems ==

=== GeoNode ===

official website: http://geonode.org/

mentor: N/A

tasks: N/A

== Desktop ==

=== GRASS GIS ===

official website: http://grass.osgeo.org/

mentors: [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]]

more info: http://grasswiki.osgeo.org/wiki/GRASS_GCI_Ideas_2017

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Create a screenshot for the next 74 release announcement || ADVANCED || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 2 || Design the t-shirt for the next code-sprint || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 3 || Add examples to manual pages || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 4 || Make new tutorial videos for GRASS GIS || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 5 || Write a short blog entry about GRASS GIS (or a certain module) || INTERMEDIATE || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 6 || Enhance the visual index || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 7 || Make screenshots to populate the visual change log in new features pages (e.g., for New Features GRASS 7.4) || INTERMEDIATE || For this task... || documentation || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Create icons/phrases to include in sticker sheets || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Give a talk about GRASS GIS to classmates || BEGINNER || For this task... || marketing || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 8 || Submit a patch for a certain bug or enhancement ticket || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|-
| 9 || Contribute tests for modules || ADVANCED || For this task... || coding,C || [[User:Veroandreo|Veronica Andreo]], [[User:Lucadelu|Luca Delucchi]] ||
|+
|}

=== gvSIG ===

official website: http://www.gvsig.com/

mentor: N/A

tasks: N/A

=== Marble ===

official website: http://marble.kde.org/

mentor: N/A

tasks: N/A

=== Opticks ===

official website: http://opticks.org/

mentor: N/A

tasks: N/A

=== Virtual Terrain Project ===

official website: https://wiki.osgeo.org/wiki/Virtual_Terrain_Project

mentor: N/A

tasks: N/A

=== QGIS ===

official website: http://qgis.org

mentor: N/A

tasks: N/A

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Enhance map style of "Vector Tiles Reader" plugin || INTERMEDIATE || Update the built-in base map QGIS style for OpenMapTiles. It resides in a separate subdirectory of the plugin. || cartography || [[User:Sfkeller]] ||
|-
| 2 || tbd. || tbd. || tbd. || tbd. || pending ||
|+
|}

== Geospatial Libraries ==

=== FDO ===

official website: http://fdo.osgeo.org/

mentor: N/A

tasks: N/A

=== GDAL/OGR ===

official website: http://gdal.org/

mentor: N/A

tasks: N/A

=== Geoinformatica ===

official website: https://wiki.osgeo.org/wiki/Geoinformatica

mentor: N/A

tasks: N/A

=== GEOS ===

official website: https://trac.osgeo.org/geos/

mentor: N/A

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a logo || INTERMEDIATE || something simple, and squarish || art || pending ||
|-
| 2 || create a comic strip of the set operations on geometries: union, intersection, difference || BEGINNER || use your imagination || art || pending ||
|+
|}

=== GeoTools ===

official website: http://www.geotools.org/

mentor: N/A

tasks: N/A

=== MetaCRS ===

official website: http://metacrs.osgeo.org/

mentor: N/A

tasks: N/A

=== Orfeo ToolBox (OTB) ===

official website: http://www.orfeo-toolbox.org/

mentor: N/A

tasks: N/A

=== OSSIM ===

official website: https://trac.osgeo.org/ossim/

mentor: N/A

tasks: N/A

=== pgRouting ===

official website: https://wiki.osgeo.org/wiki/PgRouting

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://github.com/pgRouting/pgrouting/wiki/Google-Code-In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || create a page for the pgRouting workshop using the Wikipedia example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || add the results and a brief explanation of the results to the page created on Task 1 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || create a page for the pgRouting workshop using the Hanoslav example || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || add the results and a brief explanation of the results to the page created on Task 3 || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== PostGIS ===

official website: http://postgis.net/

mentor: Regina Obe

tasks:

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker with a PostGIS elephant ||BEGINNER || Use your imagination || art || [[User:Robe|Regina Obe]] ||
|-
|-
| 2 || create a page of 5 commonly used PostGIS queries and what they solve ||INTERMEDIATE || For this task look over our docs for ideas of some queries and pick 5 you think are most useful|| documentation || [[User:Robe|Regina Obe]] ||
|-
| 3 || create a screen cast of how to install PostGIS (pick any OS you want) || INTERMEDIATE || || documentation || [[User:Robe|Regina Obe]] ||
|-
| 4 || create a comic strip of the core postgis types: geometry, geography, raster, and topology talking to each other || BEGINNER || For this task imagine there are 4 friends geomie, geoggie, rasterfa, and topolo what kind of conversation would they have? Each has a different perspective on things, geomie sees the world as a flat simple plane you can fall off of if you walk too far, geoggie sees the world as round where you can walk in any direction forever, rasterfa sees the world as a flat colorful place and believes a picture is worth a 1000 words, and topolo believes in the interconnectivity of all shapes where one object starts another begins but shares the flat view with geomie || art || [[User:Robe|Regina Obe]] ||
|+
|}

=== Postal Address Geo-Coder ===

official website: https://wiki.osgeo.org/wiki/Postal_Address_Geo-Coder

mentor: N/A

tasks: N/A

=== Proj4php ===

official website: https://wiki.osgeo.org/wiki/Proj4php

mentor: N/A

tasks: N/A

== Metadata Catalogs ==

=== GeoNetwork ===

official website: http://geonetwork-opensource.org/

mentor: N/A

tasks: N/A

=== pycsw ===

official website: http://pycsw.org/

mentor: N/A

tasks: N/A

== Web Mapping ==

=== deegree ===

official website: http://www.deegree.org/

mentor: N/A

tasks: N/A

=== geomajas ===

official website: http://www.geomajas.org/

mentor: N/A

tasks: N/A

=== GeoMOOSE ===

official website: http://www.geomoose.org/

mentor: N/A

tasks: N/A

=== GeoServer ===

official website: http://geoserver.org/

mentor: N/A

tasks: N/A

=== GeoWebCache ===

official website: https://wiki.osgeo.org/wiki/GeoWebCache

mentor: N/A

tasks: N/A

=== istSOS ===

official website: http://wiki.osgeo.org/wiki/IstSOS

mentor: N/A

tasks: N/A

=== Mapbender ===

official website: http://mapbender.org/

mentor: N/A

tasks: N/A

=== MapFish ===

official website: http://www.mapfish.org/

mentor: N/A

tasks: N/A

=== MapGuide Open Source ===

official website: http://mapguide.osgeo.org/

mentor: N/A

tasks: N/A

=== MapProxy ===

official website: https://wiki.osgeo.org/wiki/MapProxy

mentor: N/A

tasks: N/A

=== MapServer ===

official website: http://mapserver.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Design a laptop sticker || BEGINNER|| For this task... || marketing || [[Jeff McKenna]] ||
|-
| 2 || Make a video promoting MapServer, the fastest mapping engine || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Install MS4W on a Windows machine, and take screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Find and fix mistakes/urls on the mapserver.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Give a presentation to classmates about MapServer || BEGINNER || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 6 || Fix any bug in the issue tracker || ADVANCED || For this task... || coding,C || [[Jeff McKenna]] ||
|+
|}

=== OpenLayers ===

official website: http://openlayers.org/

mentor: N/A

tasks: N/A

=== PyWPS ===

official website: http://www.pywps.org/

mentor: N/A

tasks: N/A

=== Team Engine ===

official website: http://teamengine.sourceforge.net/

mentor: N/A

tasks: N/A

=== ZOO-Project ===

official website: http://www.zoo-project.org/

mentor: N/A

tasks: N/A

== Outreach ==

=== FOSS4G ===

official website: http://foss4g.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a video about the FOSS4G conference || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the FOSS4G conference to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Create a replacement page for http://foss4g.org listing all conferences || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a new social media page for FOSS4G (facebook?) || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

=== GeoForAll ===

official website: http://www.osgeo.org/education

mentor: N/A

tasks: N/A

=== OSGeo-Live ===

official website: http://live.osgeo.org/

mentor: [[User:Cvvergara|Vicky Vergara]]

more info: https://wiki.osgeo.org/wiki/OSGeoLive_Google_Code_In

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Download and install OSGeoLive || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 2 || Make a video for downloading and installing OSGeo-Live || INTERMEDIATE || For this task... || marketing || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 3 || QGIS quick start video [PART 1] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|-
| 4 || QGIS quick start video [PART 2] || INTERMEDIATE || For this task... || documentation || [[User:Cvvergara|Vicky Vergara]] ||
|+
|}

=== OSGeo Foundation ===

official website: http://osgeo.org

mentor: [[Jeff McKenna]]

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|#
!width="200"|Name
!width="60"|Level
!width="200"|Description
!width="100"|Keywords
!width="200"|Mentor
!width="100"|Ticket
|-
| 1 || Make a short video about the OSGeo foundation || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 2 || Present the history of the OSGeo foundation to classmates || INTERMEDIATE || For this task... || marketing || [[Jeff McKenna]] ||
|-
| 3 || Checkout part of git.osgeo.org locally, and create a screenshot || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 4 || Create a page on the OSGeo wiki || BEGINNER || For this task... || documentation || [[Jeff McKenna]] ||
|-
| 5 || Style the page https://trac.osgeo.org || INTERMEDIATE || For this task... || documentation || [[Jeff McKenna]] ||
|+
|}

[[Category:Google Code In]]

FOSS4G 2016 Teams

2016-04-10T11:28:34Z

Wiki-Sfkeller: /* Main topics where chairs/heads needed */ Beautified wiki text. Still don't understand when there are 2 newlines an when only one...

=== Main topics where chairs/heads needed ===

* '''Conference Chair, and Local Organizing Committee Chair'''
** Till Adams

* '''Program Committee'''
** Chair: Volker Mische
** Committee: Marco Minghini, Ela Wołoszyńska-Wiśniewska, Candan Eylül Kilsedar, Michael Gould, Johan Van de Wauw, Christian Wygoda, Gérald Fenoy, Guido Stein, Codrina Ilie, Nicolas Bozon, Christian Mayer, Stefan Herle, Monia Elisa Molinari

* '''Academic/scientific track (AT)'''
** Chair: Franz-Josef Behr, A.P. Pradeepkumar
** Committee: Vipula Abeyratne, Seraphim Alvanides, Maria Antonia Brovelli, Massimiliano Cannata, Serena Coetzee, Luciene S. Delazar, Nimalika Fernando, Ajit Govind, Ivana Ivánová, Ari Jolma, Stefan Keller, Barend Köbben, Dimitris Kotzinos, Jyothi Kumari, Simone Lanucara, Peter Mooney, Antoni Pérez Navarro, Moses Murimi Ngigi, Venkatesh Raghavan, Darshana Rawal, Habitamu Taddese, Kalum Priyanath Udagepola, Tuong-Thuy Vu, Francis Nyongesa Wegulo, Christian Willmes
** Reviewers: We are just compiling the review board. Please contact Franz-Josef and Pradeep (academictrack at foss4g2016.org) if you would like to support as reviewer!

* '''Workshop organization'''
** Carmen Tawalika
** Danilo Bretschneider
** Angelos Totsos
** Technical stuff / software: Pirmin Kalberer, Anton Popov

* '''Financial Issues'''
** Torsten Brassat, who helped at earlier FOSSGIS conferences offered his time for this.

* '''Travel Grant Commissioner'''
** Christoph Baudson. CB was deeply involved in the early mapbender development.

* '''Social-events-organizer'''
** Martin Arimont,
** frame of the social events are set, but I think we need one or two heads caring for gala event and ice breaker especially.
** This may also include some offerings of field trips for the saturday - requested from Bonn Tourismus GmbH.

* '''Sponsorship & Exhibition''' & * '''Organisation Pre-Business Day 23.8.2016'''
** Hinrich Paulsen, Arnulf Christl
** Sponsorship is a source where we can generate early income, so to start this process early is a major part. Also I guess, that most companies are planning their financial budget this year, so it is important to let them know about the possibilities of sponsoring FOSS4G.

* '''Public Relations'''
** Gert-Jan van der Weijden, Marc Vloemans, Codrina Ilie
** I talked to Textkoch this FOSSGIS and he offered his help together with Monika Resch here (of course not for free :-(). Public relations work may play a major role to get many people attending our conference. So for this issues we need a group of people and also ideas on how to structure this. Klaus Greve also said, that we might talk to the public realtions office of the university first.
** Matthias Eilers takes care of the logo and the website design
** main page: [[FOSS4G_2016_PR]]

* '''Code Sprint'''
** Astrid Emde, Uli Rothstein
** We need an organizers of the code sprint. The group cares for room, snacks and acts as contact persons for this event.

* '''Green Event Commissioner'''
** Astrid Emde
** We want to give at least some tips, how attendees can avoid garbage, where to compensate CO2 consumption etc.

* '''Scheduler'''
** Uli Rothstein, Till Adams

* '''Graphics and Design'''
** Anton Popov

* '''Technical Infrastructure'''
** Oliver Rudzick
** There are competent people from WCCB, but we definetely need a group of persons taking care of the conference technique in general.

* '''Video Team'''
** Peter Körner

* '''Co-operation with WCCB, caterer, PCO'''
** Till Adams, Conrad Seyfert (MediaCompany - PCO)

* '''Co-operation with UN offices in Bonn'''
** Athina Trakas

* '''Volunteer Chair'''
** nn
** Coordinating volunteer work on-site and also for pre-conference preparing
** strategy to gather as much volunteer helpers as possible
** ...

* '''Homepage'''
** Anja Litka, Carmen Tawalika (Content)
** Küstenschmiede (contracted for technical support)
** main page: [[FOSS4G_2016_Homepage]]

* '''Awareness Crew'''
** Volker Grescho (OLANIS GmbH)
** Help all people at the conference but mainly solve problems between people in a fair way.
** we need at least one more female head for the awareness crew !!!

[[Category:FOSS4G2016]]

LIDAR Format Letter

2015-04-16T23:22:34Z

Wiki-Sfkeller: /* Signed */

=Open Letter of the Need for Open Standards in LiDAR=
April 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimized LAS" '''''proprietary format.''''' This is of grave concern given that fragmentation of the LAS format will reduce interoperability between applications and organisations, and introduce vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LiDAR data, and that OGC sponsors help prioritise the development of this open LiDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, ESRI join the OGC in consolidating an Open Standard for use of LiDAR data. This might include proposing ESRI's "Optimized LAS" as an Open Standard to remove any technical or legal hurdles in use of "Optimized LAS" as an Open Standard. A simple test to determine if "Optimized LAS" can be used as an Open Standard would be if "Optimized LAS" can legally be implemented by Open Source software such as libLAS or LASzip.
# Users and sponsors of LiDAR data, publicly state their preference for the use of an open LiDAR format over proprietary when selecting software and services.
# The custodians of the open LAS format [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)], who are part of [http://www.asprs.org/ American Society for Photogrammetry and Remote Sensing (ASPRS)], request the term "LAS" not to be included in the name of a proprietary format, as it makes such a proprietary format appear to be an approved derivative of LAS.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LiDAR format

# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.
# Martin Isenburg, founder of [http://rapidlasso.com rapidlasso GmbH] and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools], and [http://rapidlasso.com/PulseWaves PulseWaves].
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft], Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live], Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).
# Patrick Hogan, NASA World Wind Project Manager, committed to the US National Spatial Data Infrastructure principles, one being "to make geographic data more accessible to the public" [http://www.fgdc.gov/nsdi/nsdi.html NSDI]. Open standards are essential for this.
# Lene Fischer, Associate Professor, Department of Geosciences and Natural Resource Management, University of Copenhagen. User of Open and free Data from The Danish Geodata Agency - Using LAZ and LAS http://download.kortforsyningen.dk/content/dhmpunktsky.
# [http://www.ege-como.polimi.it/index.php?content=maria_brovelli Maria Antonia Brovelli], Full Professor, Department of Civil and Environmental Engineering, Politecnico di Milano. Geo For All, committed to Open Principles in Geo Education and Policy. Committed to Open Principles in Research.
# Ron Fortunato, President of [http://www.trilliumlearning.com/AmericaBridge/ Trillium Learning] LLC. Committed to open data standards that are necessary for education and all levels of communication.
# [http://www.geodatawiz.com/armin-schmidt Armin Schmidt], Chief Developer at [http://www.GeodataWIZ.com GeodataWIZ Ltd] and Chairman of [http://www.archprospection.org ISAP], committed to better science through Open Data.
# [http://www.linkedin.com/in/gconti Giuseppe Conti], CTO Trilogis Srl, Italy. Committed to open data standards that maximize opportunity for innovative solutions, unencumbered by artificial obstacles to data exchange.
# Jorge Gustavo Rocha, Professor, Computer Science Department, University of Minho, Portugal, committed to better science through Open Data.
# Jim Miller, University of Kansas, Professor, Computer Science, http://people.eecs.ku.edu/~miller/ Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.
# Prof. Jorg M. Hacker, Director/Chief Scientist of [http://www.airborneresearchaustralia.com Airborne Research Australia], Flinders University, Adelaide, Australia. Open formats have always been a great benefit to airborne LiDAR.
# Didier Richard, Head of IS Training Dept. in Education and Research Directorate of [http://www.ign.fr Institut National de l'Information Géographique et Forestière], France. OGC user, Contributor to OSGeO projects like GDAL.
# [http://www.linkedin.com/pub/adryane-gorayeb/74/517/96a Adryane Gorayeb], [http://www.ufc.br/ Federal University of Ceará Brazil], Geography Department. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/in/yuryryabov Yury Ryabov], PhD, Senior researcher at [http://www.istc.ru/istc/db/inst.nsf/wsu/i0001823 Russian Scientific-Research Centre for Ecological Safety], [http://www.interacademies.net/Academies/ByRegion/CentralEasternEurope/13383.aspx Russian Academy of Sciences], Saint Petersburg, Russia. Open data formats are essential for successful and reproducible scientific research.
# [http://www.linkedin.com/pub/teresa-lamelas-gracia/40/4a7/20b María Teresa Lamelas], [http://cud.unizar.es/ Centro Universitario de la Defensa Zaragoza], [http://geoforest.unizar.es/es/index.php GeoForest-IUCA]. Committed to open data standards for education and research.
# [http://www.linkedin.com/in/davidherries David Herries], [http://www.interpine.co.nz/SitePages/Home.aspx Using LiDAR for forest yield modelling at Interpine Innovation], Establishing open data standards provide scope for exponential growth in innovation. This is key to a rapidly developing technology like LiDAR.
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.
# [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member. Committed to open data standards for education and research.
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)
# Drew Fenton, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. Please protect Open Standards for geospatial data!
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch
# [[User:carlos_psig|Carlos López Quintanilla]], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [https://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.
# Bob Basques, Saint Paul, Mn., GIS Systems Developer for the City of Saint Paul Public Works, Technical Director for SharedGeo.

=Background=
==About LiDAR==

[http://en.wikipedia.org/wiki/Lidar LiDAR] (Light Detection And Ranging) is a form of high precision range measurement, much like a radar system, that uses laser light instead of electromagnetic waves. The standard LiDAR product is a 3D point cloud that can be conceptualized as a series of point measurements representing distance between the sensor to a returned emission.

For over a decade (since 2003), there has been a common format for storing LiDAR data, the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html “LAS” format], and open source libraries have been developed to read, write and process these LAS files: [http://live.osgeo.org/en/overview/liblas_overview.html libLAS] and [http://github.com/LASlib/LASlib LASlib]. These libraries have been incorporated within many LiDAR applications, allowing read/write access to a common exchange format, and resulting in full interoperability between the applications. There is also an open source compression algorithm for the LAS format called [http://laszip.org LASzip] that many LiDAR data portals use to compress LAS into smaller LAZ files for faster download. Many LiDAR software packages have added [http://laszip.org/#software-with-native-laz-support native support] for these compressed LAZ files.

==LAS Limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

:* While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
:* Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
: Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 "Optimized LAS"] format which is claimed to provide faster access and smaller file sizes (similar to the open [http://laszip.org LASzip] format). This announcement created a outburst of vocal protest in the LiDAR community [[http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ 1] [http://boundlessgeo.com/2014/01/lidar-format-wars/ 2] [http://www.spatiallyadjusted.com/2014/01/15/las-laz-lazzip-zlas-and-you/ 3] [http://www.northrivergeographic.com/archives/lidar-software 4] [http://boundlessgeo.com/2014/01/lidar-format-wars-2/ 5] [http://boundlessgeo.com/2014/02/lidar-format-wars-3/ 6]].

The "Optimized LAS" format is neither published, nor available under any open license, which provides both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

One year after releasing the "Optimized LAS" format, ESRI released a free Windows DLL that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between "free" and "open". Unless the Windows DLL is released under an "open" license, libLAS and related products will be legally prevented from incorporating ESRI's reader/writer code into their codebase, or from fixing any underlying bugs or performance limitations which may exist in ESRI's product.

==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==

The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.

Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:

: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and worked with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked diligently on this. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to [http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf at least 2007]. More recently, Carl Reed had an email dialogue with Lewis Graham to bring LAS into OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

[http://www.opengeospatial.org/ogc/organization/staff/ssimmons Scott Simmons] (Executive Director, Standards Program) has explained the OGC's continuing interest in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content.
: The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org) to register their interest and discuss details. OGC will also be holding an ad hoc session at the OGC's next [http://www.opengeospatial.org/event/1506tc Technical Committee meeting in Boulder, CO, USA in early June] to bring together all interested parties from all sectors (government, industry, academia) for this and plan next steps.

==History: LAS and ESRI's "Optimized LAS"==

Martin Isenburg, one of the leading experts in LIDAR formats, and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools] and [http://rapidlasso.com/PulseWaves PulseWaves], explains the history of LAS and "Optimized LAS":

: '''Summary:'''

:* The LAS format has been used successfully for over a decade.
:* Within last couple of years, ESRI has added native LAS support into ESRI products.
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.

: '''1998: Original LAS format definition'''

: The original development of the LAS format started in 1998 according to [http://groups.google.com/forum/#!topic/lasroom/zKqchDj1JL4/discussion Lewis Graham]. The effort was at first led by pioneers of the LiDAR industry until the format was donated to the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html ASPRS]. Since then ASPRS's [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] has been maintaining the LAS format, guiding it from the initial LAS 1.0 version until today's LAS 1.4 version. This effort successfully created an open data exchange format for discrete LiDAR points that is currently supported by practically every LiDAR-related software program.

: '''2011: ESRI joins LAS Working Group'''

: ESRI did not join the LWG of the ASPRS until rather late, the 24th of August in 2011. At that time ESRI was not a significant "player" in the LiDAR market given they did not have much support for LiDAR in any of their products. That was to change soon as they were planning to add LAS as a native data type in ArcGIS 10.1.

: Shortly before that, in June 2011, Martin Isenburg received a personal message from the ESRI development team: "I have a question about LAS compression. I’m evaluating some potential enhancements and support for [LAS and] LAZ is one of them. Compression time and amount is impressive." When inquiring two months later about the status of [http://laszip.org LAZ] integration Martin was told: "We’re in beta and working to finish the current release. I very much doubt LAZ will make it in because it’s too big a change at this time. So, we’ll be considering, for the following release, [for] what we want to do regarding compression and spatial indexing."

: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''

: In June 2012 ESRI released ArcGIS 10.1 and introduced the proprietary "LAS Dataset file (*.lasd)" that groups collections of files into one logical unit. This format of this useful LAS container file was not shared with others despite several private and eventually [http://groups.google.com/d/topic/lastools/jwHpi0efUgA/discussion public] requests.

: '''2012/2013: Collaboration Discussions'''

: There were encouraging follow-ups from the ESRI team about adopting the open LAZ format in January 2012: "I would be interested in having a more in depth meeting with you to better understand the great work you are doing with LAS and how we can possibly better partner on this." and again in December 2012: "If you have time, I'd like to set some time aside Tuesday afternoon to meet with <an important person> at the ESRI booth. Does 2pm sound okay?" The meeting went well and it looked as if ESRI was going to embrace the LAZ format because shortly after the meeting Martin got word that: "I hear from <an important person> that it was a success and that he had a good meeting with you. I wanted to see if we can have a telephone discussion on Wednesday or Thursday this week related to the potential of incorporating LAZ into ArcGIS."

: Then the first signs of hesitation showed. First there were legal issues raised in February 2013: "Currently the legal aspects are being reviewed. They were having some issues separating the LPGL aspects from LASzip from the remainder of LAStools etc." and then in April 2013 concerns about the code were made: "We have started to look into the integration of LAZ, but came across some issues. We don’t want to copy files from the other package, mix and match or hack around. We were hoping for an API to stream points out of a LAZ file as well as write LAZ files. There should be a simple code sample for that?" and - following up on that - in June 2013 Martin was told "I see value in LASzip becoming a de-facto standard that provides compression to the LAS format. If this is to happen then it needs to be bundled together with appropriate reference implementations, examples and documentation as a standard and so ensure that issues as defined earlier in email do not occur."

: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''

: At that time [http://laszip.org LASzip] was an open source project without sponsorship. The original funding from [http://www.erdc.usace.army.mil/Locations/ColdRegionsResearchandEngineeringLaboratory.aspx USACE] that had turned [http://laszip.org LASzip] from an academic prototype into an industry strength compression engine had long run out. So Martin asked ESRI to become a sponsor to create the clean [http://laszip.org LASzip] API that ESRI was after. The answer was: "ESRI often helps in the financing of Open Source projects and I could foresee ESRI possibly helping in LASzip. [...] If you are interested in promoting LASzip as such a standard and doing the required work then I would recommend you put together a proposal and I can look to get ESRI as a sponsor."

: Immediately Martin proposed to ESRI: "I hereby propose to write an easy to use open source DLL wrapper for LASzip that will make it easier to integrate LASzip in a standardized manner into other software products such as ArcGIS, LP 360, or Terrasolid. This will come with example code on how to use the DLL for reading and writing LAZ files and include a few compressed example files. I hereby ask ESRI to provide funding for this effort without imposing any limitations on the produced DLL API."

: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''

: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. The new proprietary *.lasx files with seemingly identical functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] in May 2011 and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.

: '''July 2013: Open LASzip API released'''

: After more requests for an easier interface to [http://laszip.org LASzip] (in particular for [http://forsys.cfr.washington.edu/fusion/fusionlatest.html USDA's FUSION]), Martin [http://groups.google.com/d/topic/lastools/oplsDhhnhDQ/discussion released] a clean, well-documented, and easy-to-use LASzip DLL (without ESRI funding). Martin expected that developers at ESRI would now use it to add read and write support for [http://laszip.org LAZ] to their next release of ArcGIS.

: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''

: In December of 2013, several LAStools users contacted Martin with suspicions that ESRI may be creating a proprietary LAS compression. Martin [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ broke the news] as soon as it became evident that ESRI had used the time it needed to resolve "legal issues" and "code problems" to put together their own proprietary compressed format with near-identical performance and functionality to [http://laszip.org LASzip]. A few days later ESRI released an [http://www.lidarnews.com/content/view/10214/ official FAQ] to confirming this was the case.

: From day one, Martin has worked with stakeholders, including ESRI, to avoid format fragmentation. Martin's core argument for resolving this to everybody's benefit was that - coincidentally - a natural break was happening in the LAS format with the introduction of the new LAS 1.4 point types. Martin outlined a detailed plan for how a joint development of [http://laszip.org LASzip] for LAS 1.4 between rapidlasso and ESRI could exploit this natural break in the LAS format to accomplish two things at once:
:# Add the unspecified technical additions that ESRI had hinted at desiring, and
:# Extend the [http://laszip.org LASzip] compression scheme to handle the new point types introduced with the LAS 1.4 specification. As there was no pressing need at the time to handle LAS 1.4 Martin had delayed the extension of [http://laszip.org LASzip] to the new LAS 1.4 point types to make sure a cooperation with ESRI would remain a viable option.

: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''

: In an attempt to convince ESRI management of the community desire for an open standard, Martin released an April Fools' Day [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ prank press release] pretending that ESRI had already agreed to the envisioned collaboration to develop a joint LiDAR compressor. Community [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ jubilant reactions (see comments)] left no doubt about the sentiment on this issue within the LiDAR community.

: '''October 2014: Announcement of [open] LAS Compatibility mode'''

: [http://www.csc.noaa.gov/digitalcoast/ Digital Coast, NOAA Coastal Services Center] became a Gold Sponsor of [http://laszip.org LASzip] for the development of the [http://rapidlasso.com/2014/10/06/rapidlasso-announces-laszip-compatibility-mode-for-las-1-4/ LAS 1.4 compatibility mode] that was [http://groups.google.com/d/topic/lastools/nUFMkKSz53g/discussion beta-released] in November 2014. This allowed support for the new point types in [http://laszip.org LASzip] without closing the door on a potential cooperation with ESRI for a joint LAS 1.4 compressor.

: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''

: In November 2014 [http://blog.lidarnews.com/esri-las-optimizer-updated ESRI announced] that they had added their [http://blog.lidarnews.com/esri-las-optimizer-updated own extension] for the new LAS 1.4 point types to "Optimized LAS", dismissing the opportunity to develop a joint compressor and avoid format fragmentation by exploiting this "natural break" in the LAS format as Martin had suggested.

: Since then, ESRI has been [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ promoting] "Optimized LAS". By including the term "LAS" in "Optimized LAS" and "zLAS", the distinction between the open LAS format and proprietary format is blurred. This is likely to mislead novice and future users, thereby endangering many years of standardization work. To date, [April 2014], the [http://www.asprs.org/a/society/committees/standards/LAS_1_4_r13.pdf custodians of the LAS format], the LAS Working Group (LWG) of the ASPRS has [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ yet to make an official statement] regarding use of the "LAS" name in promoting a proprietary LiDAR format.

=Value of Standards=

The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – An Introduction to Open Source Software for Government IT, Version 2.0, United Kingdom Cabinet Office https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf</ref>

The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=Further Reading=

# Paul Ramsey provides background to LAS vs Optimised LAS, http://boundlessgeo.com/2014/01/lidar-format-wars/
# Running commentary by Martin Isenburg, author of LASlib, http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/
# Earlier comment from Martin Isenburg, http://rapidlasso.com/2014/11/06/keeping-esri-honest/
# First call-to-action by Martin Isenburg, http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/
# ESRI Announces "Optimised LAS", http://blog.lidarnews.com/esri-announces-las-compression/
# ESRI description of "Optimised LAS", http://www.lidarnews.com/content/view/10214
# Discussion background on this topic at Geo for All list , http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html

=References=

<references />

LIDAR Format Letter

2015-04-02T22:30:23Z

Wiki-Sfkeller: /* Signed */

=Open Letter for the need for Open Standards in LiDAR=
March 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimised LAS" closed format. This is of concern as it reduces interoperability between applications and organisations, and introduces vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LIDAR data, and OGC sponsors prioritise the development of this LIDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, join the OGC in developing of an Open Standard for use of LIDAR data. This might include proposing ESRI's "Optimised LAS" as an Open Standard, and removing technical and legal hurdles to use of "Optimised LAS" as an Open Standard. A simple test to determine if "Optimised LAS" can be used as an Open Standard would be if "Optimised LAS" can legally be implemented by Open Source software such as LibLAS or LASzip.
# Users and sponsors of LIDAR data, and the [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] which is part of [http://www.asprs.org/ ASPRS], publicly state their preference for the use of an open format over closed when selecting software and services.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LIDAR format

# Suchith Anand , Geo for All , committed to Open Principles in Geo Education and Policy.
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft], Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live], Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; researcher in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).

=Background=
==About LIDAR==

[http://en.wikipedia.org/wiki/Lidar LIDAR] (Light Detection and Ranging) is a form of high precision range detection much like a radar system that uses laser light as the electromagnetic emission. One of LIDAR systems’ products is a “point cloud” data product that can be conceptualized as a series of point measurements representing distance from the sensor to a returned emission. A common storage format for these point cloud data is the LAS format.

To date, [March 2015] there has been a common format for storing LIDAR data, the “LAS” format, and an open source library, [http://live.osgeo.org/en/overview/liblas_overview.html libLAS], that can read and write the format. This libLAS library has been incorporated within many LIDAR applications, allowing read/write access to the common "LAS" format, and with resulting interoperability between these applications.

==LAS limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

: While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
: Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
:Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library LASzip can apply 20:1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
:Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

==Closed "Optimized LAS" format from ESRI==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 Optimized LAS] format which is claimed to provide faster access and smaller file sizes. ESRI has also released a free tool which is claimed to convert LAS files to and from Optimized LAS.

However, the Optimized LAS format is not published, or available under an open license, which provides both technical as well as legal barriers to other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

==OGCs efforts so far to enable Open standards in LiDAR ==

Carl Reed provided the following information on OGC's efforts so far to work towards enabling Open Standards in LiDAR.
: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and working with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked hard to try to make this work. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to at least 2007.http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf. More recently, Carl Reed had an email dialogue with Lewis Graham about bringing LAS into the OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

There is current interest by the OGC in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content. The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org ) to register their interest and discuss details. OGC will also be holding an ad hoc session at our next Technical Committee meeting in Boulder, CO, USA in early June to bring together all interested from all sectors (government, industry, academia) for this and plan next steps.

==Attempted community engagement in development of Optimised LAS==

TBD: Martin Isenburg (and possibly OGC members?) to add history in the development of the Optimised LAS format.
* Highlight community attempts to work collaboratively with ESRI. How did the community reach out? How did ESRI respond?
* It might make sense to merge the "OGC efforts" section and this section under one "History" heading.

=Value of Standards=

The importance of Open Standards is described is most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – An Introduction to Open Source Software for Government IT, Version 2.0, United Kingdom Cabinet Office https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf</ref>

The value of Open Standards have been described in numerous national studies on the effects of standards on economic
growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=See Also=
# Paul Ramsey provides background to LAS vs Optimised LAS, http://boundlessgeo.com/2014/01/lidar-format-wars/
# Running commentary by Martin Isenburg, author of LibLAS, http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/
# Earlier comment from Martin Isenburg, http://rapidlasso.com/2014/11/06/keeping-esri-honest/
# ESRI Announces "Optimised LAS", http://blog.lidarnews.com/esri-announces-las-compression/
# ESRI description of "Optimised LAS", http://www.lidarnews.com/content/view/10214
# Discussion background on this topic at Geo for All list , http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html

LIDAR Format Letter

2015-04-02T22:28:57Z

Wiki-Sfkeller: /* Signed */

=Open Letter for the need for Open Standards in LiDAR=
March 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimised LAS" closed format. This is of concern as it reduces interoperability between applications and organisations, and introduces vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LIDAR data, and OGC sponsors prioritise the development of this LIDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, join the OGC in developing of an Open Standard for use of LIDAR data. This might include proposing ESRI's "Optimised LAS" as an Open Standard, and removing technical and legal hurdles to use of "Optimised LAS" as an Open Standard. A simple test to determine if "Optimised LAS" can be used as an Open Standard would be if "Optimised LAS" can legally be implemented by Open Source software such as LibLAS or LASzip.
# Users and sponsors of LIDAR data, and the [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] which is part of [http://www.asprs.org/ ASPRS], publicly state their preference for the use of an open format over closed when selecting software and services.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LIDAR format

# Suchith Anand , Geo for All , committed to Open Principles in Geo Education and Policy.
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft], Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live], Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab], researcher in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).

=Background=
==About LIDAR==

[http://en.wikipedia.org/wiki/Lidar LIDAR] (Light Detection and Ranging) is a form of high precision range detection much like a radar system that uses laser light as the electromagnetic emission. One of LIDAR systems’ products is a “point cloud” data product that can be conceptualized as a series of point measurements representing distance from the sensor to a returned emission. A common storage format for these point cloud data is the LAS format.

To date, [March 2015] there has been a common format for storing LIDAR data, the “LAS” format, and an open source library, [http://live.osgeo.org/en/overview/liblas_overview.html libLAS], that can read and write the format. This libLAS library has been incorporated within many LIDAR applications, allowing read/write access to the common "LAS" format, and with resulting interoperability between these applications.

==LAS limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

: While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
: Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
:Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library LASzip can apply 20:1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
:Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

==Closed "Optimized LAS" format from ESRI==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 Optimized LAS] format which is claimed to provide faster access and smaller file sizes. ESRI has also released a free tool which is claimed to convert LAS files to and from Optimized LAS.

However, the Optimized LAS format is not published, or available under an open license, which provides both technical as well as legal barriers to other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

==OGCs efforts so far to enable Open standards in LiDAR ==

Carl Reed provided the following information on OGC's efforts so far to work towards enabling Open Standards in LiDAR.
: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and working with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked hard to try to make this work. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to at least 2007.http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf. More recently, Carl Reed had an email dialogue with Lewis Graham about bringing LAS into the OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

There is current interest by the OGC in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content. The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org ) to register their interest and discuss details. OGC will also be holding an ad hoc session at our next Technical Committee meeting in Boulder, CO, USA in early June to bring together all interested from all sectors (government, industry, academia) for this and plan next steps.

==Attempted community engagement in development of Optimised LAS==

TBD: Martin Isenburg (and possibly OGC members?) to add history in the development of the Optimised LAS format.
* Highlight community attempts to work collaboratively with ESRI. How did the community reach out? How did ESRI respond?
* It might make sense to merge the "OGC efforts" section and this section under one "History" heading.

=Value of Standards=

The importance of Open Standards is described is most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – An Introduction to Open Source Software for Government IT, Version 2.0, United Kingdom Cabinet Office https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf</ref>

The value of Open Standards have been described in numerous national studies on the effects of standards on economic
growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=See Also=
# Paul Ramsey provides background to LAS vs Optimised LAS, http://boundlessgeo.com/2014/01/lidar-format-wars/
# Running commentary by Martin Isenburg, author of LibLAS, http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/
# Earlier comment from Martin Isenburg, http://rapidlasso.com/2014/11/06/keeping-esri-honest/
# ESRI Announces "Optimised LAS", http://blog.lidarnews.com/esri-announces-las-compression/
# ESRI description of "Optimised LAS", http://www.lidarnews.com/content/view/10214
# Discussion background on this topic at Geo for All list , http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html

Point Clustering

2014-10-12T23:16:04Z

Wiki-Sfkeller: /* References */

== Point Clustering: Various Approaches ==

Please fill this in with any approaches that you have tried for Point Clustering along with code snippets. Please include discussion on why a particular method worked well or didn't work well and what circumstances it may be good for.

=== Possible Approaches ===
* Coordinate interleaving (i.e. 1. rounding input coordinates, 2. grouping/aggregating them, and then 3. averaging their original coordinates so that the cluster position is at the weighted coordinate of all input geometries).
* K-means Clustering
* Hierarchical Clustering
* Distance calculation for each coordinate pair

=== Input Parameters ===
Depending on algorithm...

Partitioning methods
* Map grid width ("quare / manhattan world", see coordinate interleaving/rounding)
* Some self-correlation threshold (see e.g. k-means)
* Predefined irregular polygons (e.g. zip code boundaries)

=== Implementations ===
* [http://mapserver.org/mapfile/cluster.html MapServer CLUSTER]

=== References ===
* [http://en.wikipedia.org/wiki/Data_clustering Wikipedia] Article on Data Clustering
* [http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/software.htm#pycluster PyCluster]: Python Cluster Functions (2013)
* [http://trac.osgeo.org/postgis/ticket/174 Point Clustering Utility Trigger] enhancement idea reported as ticket to PostGIS Trac (2012).
* [http://gis.stackexchange.com/questions/11567/spatial-clustering-with-postgis "Spatial Clustering with PostGIS] from gis.stackexchange.com (2011)
* [http://www.geocomputation.org/2000/GC015/Gc015.htm Using Genetic Algorithms in Clustering Problems]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference (2000)
* [http://www.geocomputation.org/2000/GC024/Gc024.htm Automatic clustering via boundary extraction for mining massive point-data sets]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference (2000)
* <s>[http://www.nabble.com/%27clustering%27-of-points-t1261780.html#a3347923 PostGIS Mailing List] thread on clustering points</s>
* <s>[http://www.nabble.com/clustering-points-t1404935.html#a3781371 Here] & [http://www.nabble.com/Visualizing-Point-Data-t1052056.html#a2741608 here]: Mapserver Mailing List threads on clustering points</s>

Point Clustering

2014-10-12T18:57:33Z

Wiki-Sfkeller:

== Point Clustering: Various Approaches ==

Please fill this in with any approaches that you have tried for Point Clustering along with code snippets. Please include discussion on why a particular method worked well or didn't work well and what circumstances it may be good for.

=== Possible Approaches ===
* Coordinate interleaving (i.e. 1. rounding input coordinates, 2. grouping/aggregating them, and then 3. averaging their original coordinates so that the cluster position is at the weighted coordinate of all input geometries).
* K-means Clustering
* Hierarchical Clustering
* Distance calculation for each coordinate pair

=== Input Parameters ===
Depending on algorithm...

Partitioning methods
* Map grid width ("quare / manhattan world", see coordinate interleaving/rounding)
* Some self-correlation threshold (see e.g. k-means)
* Predefined irregular polygons (e.g. zip code boundaries)

=== Implementations ===
* [http://mapserver.org/mapfile/cluster.html MapServer CLUSTER]

=== References ===
* [http://en.wikipedia.org/wiki/Data_clustering Wikipedia] Article on Data Clustering
* [http://www.nabble.com/%27clustering%27-of-points-t1261780.html#a3347923 PostGIS Mailing List] thread on clustering points
* [http://trac.osgeo.org/postgis/ticket/174 Point Clustering Utility Trigger] enhancement idea reported as ticket to PostGIS Trac.
* [http://www.nabble.com/clustering-points-t1404935.html#a3781371 Here] & [http://www.nabble.com/Visualizing-Point-Data-t1052056.html#a2741608 here]: Mapserver Mailing List threads on clustering points
* [http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/software.htm#pycluster PyCluster]: Python Cluster Functions
* [http://www.geocomputation.org/2000/GC015/Gc015.htm Using Genetic Algorithms in Clustering Problems]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference
* [http://www.geocomputation.org/2000/GC024/Gc024.htm Automatic clustering via boundary extraction for mining massive point-data sets]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference

Point Clustering

2014-10-12T18:57:12Z

Wiki-Sfkeller:

== Point Clustering: Various Approaches ==

Please fill this in with any approaches that you have tried for Point Clustering along with code snippets. Please include discussion on why a particular method worked well or didn't work well and what circumstances it may be good for.

=== Possible Approaches ===
* Coordinate interleaving (i.e. 1. rounding input coordinates, 2. grouping/aggregating them, and then 3. averaging their original coordinates so that the cluster position is at the weighted coordinate of all input geometries).
* K-means Clustering
* Hierarchical Clustering
* Distance calculation for each coordinate pair

=== Input Parameters ===
Depending on algorithm...
* Partitioning methods
** Map grid width ("quare / manhattan world", see coordinate interleaving/rounding)
** Some self-correlation threshold (see e.g. k-means)
** Predefined irregular polygons (e.g. zip code boundaries)

=== Implementations ===
* [http://mapserver.org/mapfile/cluster.html MapServer CLUSTER]

=== References ===
* [http://en.wikipedia.org/wiki/Data_clustering Wikipedia] Article on Data Clustering
* [http://www.nabble.com/%27clustering%27-of-points-t1261780.html#a3347923 PostGIS Mailing List] thread on clustering points
* [http://trac.osgeo.org/postgis/ticket/174 Point Clustering Utility Trigger] enhancement idea reported as ticket to PostGIS Trac.
* [http://www.nabble.com/clustering-points-t1404935.html#a3781371 Here] & [http://www.nabble.com/Visualizing-Point-Data-t1052056.html#a2741608 here]: Mapserver Mailing List threads on clustering points
* [http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/software.htm#pycluster PyCluster]: Python Cluster Functions
* [http://www.geocomputation.org/2000/GC015/Gc015.htm Using Genetic Algorithms in Clustering Problems]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference
* [http://www.geocomputation.org/2000/GC024/Gc024.htm Automatic clustering via boundary extraction for mining massive point-data sets]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference

Point Clustering

2014-10-12T18:51:23Z

Wiki-Sfkeller:

== Point Clustering: Various Approaches ==

Please fill this in with any approaches that you have tried for Point Clustering along with code snippets. Please include discussion on why a particular method worked well or didn't work well and what circumstances it may be good for.

=== Possible Approaches: ===
* Coordinate interleaving (i.e. 1. rounding input coordinates, 2. grouping/aggregating them, and then 3. averaging their original coordinates so that the cluster position is at the weighted coordinate of all input geometries).
* K-means Clustering
* Hierarchical Clustering
* Distance calculation for each coordinate pair

=== Implementations ===
* [http://mapserver.org/mapfile/cluster.html MapServer CLUSTER]

=== References ===
* [http://en.wikipedia.org/wiki/Data_clustering Wikipedia] Article on Data Clustering
* [http://www.nabble.com/%27clustering%27-of-points-t1261780.html#a3347923 PostGIS Mailing List] thread on clustering points
* [http://trac.osgeo.org/postgis/ticket/174 Point Clustering Utility Trigger] enhancement idea reported as ticket to PostGIS Trac.
* [http://www.nabble.com/clustering-points-t1404935.html#a3781371 Here] & [http://www.nabble.com/Visualizing-Point-Data-t1052056.html#a2741608 here]: Mapserver Mailing List threads on clustering points
* [http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/software.htm#pycluster PyCluster]: Python Cluster Functions
* [http://www.geocomputation.org/2000/GC015/Gc015.htm Using Genetic Algorithms in Clustering Problems]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference
* [http://www.geocomputation.org/2000/GC024/Gc024.htm Automatic clustering via boundary extraction for mining massive point-data sets]: paper from [http://www.geocomputation.org/ GeoComputation] 2000 conference

Edu current initiatives

2014-02-11T23:50:01Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
| Institute of Earth Sciences
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionu? Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciolkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Podör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| [http://www.mrt.ac.lk/tcp/osgeosl.html OSGeoSL ]
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutic
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| [http://osgeolab.sliit.lk/ OSGeoSLIIT]
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://www.ifs.hsr.ch/Geometa-Lab.12520.0.html?&L=4 Geometa Lab at HSR - University of Applied Sciences Rapperswil]
| Rapperswil
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| (published 2014-02-05)
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Edu current initiatives

2014-02-05T19:31:30Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */ Weblink updated for Geometa Lab

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
|
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionu? Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciolkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Podör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| [http://www.mrt.ac.lk/tcp/osgeosl.html OSGeoSL ]
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutic
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| In process of being established as OSGeoSLIIT
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://www.ifs.hsr.ch/Geometa-Lab.12520.0.html?&L=4 Geometa Lab at HSR - University of Applied Sciences Rapperswil]
| Rapperswil (St. Gallen)
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| ongoing
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Edu current initiatives

2014-02-01T01:04:30Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */ Website updated of Geometa Lab at HSR

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
|
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionu? Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciolkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Podör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| [http://www.mrt.ac.lk/tcp/osgeosl.html OSGeoSL ]
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutic
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| In process of being established as OSGeoSLIIT
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://www.hsr.ch/Master-of-Science-in-Engineeri.5983.0.html?&L=4 University of Applied Sciences (HSR)]
| Rapperswil (St. Gallen)
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| [http://www.ifs.hsr.ch/Geometa-Lab.12520.0.html Geometa Lab at HSR]
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Vienna Code Sprint 2014

2014-01-26T18:29:37Z

Wiki-Sfkeller: /* Participants */

''OSGeo Code Sprint 2014 official web site: [http://vienna2014.sprint.osgeo.org http://vienna2014.sprint.osgeo.org]. Please contact us if you are interested in our [http://vienna2014.sprint.osgeo.org/sponsoring.html sponsorship opportunities].''

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|260px|Airborne Interactive Ltd|link=http://www.airborne.aero/]]
 
http://www.airborne.aero/
|
[[File:Logo-Austrospace.png‎|260px|Austrospace|link=http://www.austrospace.at/]]
 
http://www.austrospace.at/
|
[[File:Logo-TYDAC.png‎|260px|TYDAC|link=http://www.tydac.ch]]
 
http://www.tydac.ch
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-FOSSGIS-e.V.png‎|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]
 
http://www.fossgis.de
|}

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-ITS-VR.jpg|260px|ITS Vienna Region|link=http://www.anachb.at/mehr]]
 
http://www.anachb.at/mehr
|}

'''Bronze Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-metaspatial.png|260px|metaspatial Institut|link=http://www.metaspatial.net/en/institute]]
 
[http://metaspatial.net/en/institute http://metaspatial.net/en/institute]
|
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com]]
 
[http://www.oslandia.com http://www.oslandia.com]
|
[[File:Logo-rapidlasso.png|260px|rapidlasso|link=http://rapidlasso.com]]
 
[http://rapidlasso.com http://rapidlasso.com]
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.jpg‎|260px|Azavea|link=http://www.azavea.com]]
 
http://www.azavea.com
|}

'''Venue Sponsor'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-City-of-Vienna.png|260px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]
 
[http://www.wien.gv.at/english/administration/ict/index.html http://www.wien.gv.at/]
|}

'''Other/in-kind sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Purpose ==

Get together project members to make decisions and tackle larger geospatial
problems (as done last year at the [[Boston Code Sprint 2013]] and previous
years: [[IslandWood Code Sprint 2012|Island Wood]] (2012),
[[Montreal Code Sprint 2011|Montreal]] (2011),
[[New York Code Sprint 2010|New York City]] (2010), and
[[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting
members of the "C Tribe" (e.g., MapServer, QGis, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course,
but we hope that "C Tribe" members will give this event special consideration.

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22].

The venue is not far from the center of Vienna (~25min via train and subway) and can be reached easily from the Vienna airport via train.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

== Hotel ==

Two blocks of rooms have been negotiated at the two hotels closest to the sprint venue, [http://www.hillinger.at Hotel Hillinger] ([http://www.openstreetmap.org/#map=19/48.23133/16.45037 map]) and [http://www.wienerkindl.at Hotel Wiener Kindl] ([http://www.openstreetmap.org/#map=19/48.22757/16.45428 map]). Please make your own choice.

The rooms are blocked for the sprint week i.e. 24.-28. March 2014 whereas +/- one day should be no problem.

Please find the lists of available rooms below. If you make a reservation for one of the listed rooms please indicate this by adding your name to the list. Thanks.

Don't hesitate to contact me if you need any assistance.

=== Hotel Wiener Kindl ===

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 65,- || 3 || <add your name> ||
|-
| 2 || € 80,- || 6 || <add your name> ||
|-
| 3 || € 90,- || 2 || <add your name> ||
|}

The rates include breakfast buffet, sat TV, direct dial telephone, ensuite bathroom with shower, minibar, and free WLAN.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee later

These rooms are blocked until 28.02.2014. Please make your reservation via mail to "wienerkindl@utanet.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

If you really want to save on budget you might consider a room with shared bathroom and sometimes also shared shower. Note that these rooms are available at the hotel as backup rooms but not recommended. You have been warned.

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl-low-budget
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 45,- || 3 || Radim Blazek ||
|-
| 2 || € 50,- || 2 || <add your name> ||
|}

=== Hotel Hillinger ===

'''Note, in case you've seen the previous note, that today I visited the hotel again and hopefully resolved all misunderstandings.'''

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Hillinger
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 2 || € 85,- || 15 are blocked of up to 50 || <add your name> || Most of the rooms have double beds and some twin beds. Ask for your preferred choice.
|-
| 1 || € 65,- || Same as above but single use || <add your name> ||
|-
| 3 || € 105,- || 4 || <add your name> || 2 of the rooms can also be used as 4 bed rooms for € 125,-.
|}

The rates include breakfast buffet, cable and pay-TV, air conditioning, direct dial telephone, ensuite bathroom with bathtub or shower, hairdryer, and free WLAN in the whole hotel. In addition they offer free usage of the climbing hall and fitness center on the other side of the street.

Accepted payment methods: cash or creditcard.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee from 7 to 3 days in advance
* 100% fee later

These rooms are blocked until 15.02.2014. Please make your reservation via mail to "hotel@hillinger.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

=== Alternatives ===

If you don't feel comfortable with both options we recommend to look for alternatives around Kagran ([http://www.openstreetmap.org/#map=15/48.2434/16.4341 map]) which is just a couple of stops away from the venue with the tram and also close to the city center with the subway.

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for four nights
* Breakfast and dinner (partly)

== Project Plans ==

TBD

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==

We are planning for attendance of 50-60 participants. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
any special needs.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accomodation || Work on || Notes
|-
| 1 || [[User:schpidi|Stephan Meissl]] || AT || first day || last day || home || MapServer || Definite - No special needs
|-
| 2 || [[User:ahocevar|Andreas Hocevar]] || AT || first day || last day || family || OpenLayers || Definite - No hotel needed
|-
| 3 || [[User:pwramsey3|Paul Ramsey]] || CA || Mar 23 (AC6164) || Mar 30 (AC9159) || TBD || PostGIS || Booked
|-
| 4 || [[User:msmitherdc|Michael Smith]] || || || || || PDAL/MapServer || Very Likely
|-
| 5 || [[Jeff McKenna]] || CA || Likely Mar 26 || Likely Mar 30 || || MapServer, ZOO-Project, pycsw || Very Likely
|-
| 6 || [[User:Dmorissette|Daniel Morissette]] || CA || || || || MapServer, GDAL/OGR || Very Likely
|-
| 7 || [[User:hobu|Howard Butler]] || USA || Mar 22 || Mar 29 || || MapServer, GDAL/OGR, PDAL || Booked
|-
| 8 || Olivier Courtin || || || || || PostGIS, TinyOWS || Very Likely
|-
| 9 || [[User:Lucadelu|Luca Delucchi]] || IT || || || || GRASS GIS || Very Likely
|-
| 10 || [[User:Landa|Martin Landa]] || CZ || || || || GRASS GIS, PostGIS, GDAL/OGR || Very Likely
|-
| 11 || [[User:Tbonfort|Thomas Bonfort]] || FR || Mar 24 midday || Mar 28 || || MapServer || Definite
|-
| 12 || [[User:Szekerest|Tamas Szekeres]] || HU || Mar 24 midday || Mar 28 || || MapServer, GDAL/OGR || Definite
|-
| 13 || [[User:Mloskot|Mateusz Loskot]] || || || || || PDAL || Likely
|-
| 14 || [[User:pcav|Paolo Cavallini]] || || || || || QGIS || Very likely
|-
| 15 || [[User:Neteler|Markus Neteler]] || IT || || || || GRASS GIS || Likely
|-
| 16 || [[User:kalxas|Angelos Tzotsos]] || GR || Mar 23 (OS0802) || Mar 29 (OS0801) || TBD || OSGeoLive, pycsw/GeoPython/GeoNode, OTB, ZOO-Project || Booked
|-
| 17 || [[User:Aghisla|Anne Ghisla]] || DE || Mar 24 || Mar 28 || || GRASS GIS/QGIS/Translations || Definite
|-
| 18 || [[User:Jachym|Jachym Cepicky]] || || || || || PyWPS/GeoPython (OpenLayers) || Likely
|-
| 19 || [[User:Jesus|Jorge de Jesus]] || || || || || PyWPS/REST/GeoPython || Likely
|-
| 20 || [[User:atrawog| Andreas Trawoeger]] || || || || || GRASS GIS || Very Likely
|-
| 21 || [[User:ortelius| Jeffrey Johnson]] || || || || || GeoNode/ GeoPython || Very Likely
|-
| 22 || [[User:pacesm| Martin Paces]] || || || || || EOxServer || Very Likely
|-
| 23 || [[User:fschindler| Fabian Schindler]] || || || || || EOxServer/MapServer || Definite
|-
| 24 || [[User:Djay|Gérald Fenoy]] || FR || || || || MapServer, ZOO-Project || Likely
|-
| 25 || Marco Hugentobler || CH || || || || QGIS || Very Likely
|-
| 26 || Mathias Walker || CH || || || || QGIS || Very Likely
|-
| 27 || [[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || || || || QGIS, GDAL/OGR || Likely
|-
| 28 || [[User:capooti|Paolo Corti]] || || || || || GeoNode/QGIS || Very Likely
|-
| 29 || [[Arnulf Christl]] - [[OSGeo]], [[Geo for All]] || DE || || || || Guest ||
|-
| 30 || [[User:rduivenvoorde|Richard Duivenvoorde]] || NL || tbd || tbd || tbd || QGIS, context help, vector tools || Very likely
|-
| 31 || [[User:timlinux|Tim Sutton]] || || || || || QGIS || likely
|-
| 32 || [[User:mbernasocchi|Marco Bernasocchi]] || CH || || || || QGIS || Very likely
|-
| 33 || [[User:MartinDobias|Martin Dobias]] || SK || || || || QGIS || Likely
|-
| 34 || Hugo Mercier || || || || || QGIS, SFCGAL, PostGIS || Very Likely
|-
| 35 || Vincent Mora || || || || || QGIS, SFCGAL || Very Likely
|-
| 36 || [[User:hellik|Helmut Kudrnovsky]] || AT || || || || GRASS GIS || Likely
|-
| 37 || [[User:lutra|Giovanni Manghi]] || PT/IT || || || || QGIS || Likely
|-
| 38 || [[User:Ginetto|Luigi Pirelli]] || ES/IT ||24(VY8710) 14:30|| 30(VY8711) ||tbd || QGIS || Booked flight
|-
| 39 || [[Milena Nowotarska | Milena Nowotarska]] || PL || || || || GRASS GIS/QGIS || Likely
|-
| 40 || [[User:Madi|Margherita Di Leo]] || IT || || || || GRASS GIS / INSPIRE || Likely
|-
| 41 || [[User:Macho|Werner Macho]] || AT || || || || QGIS || Likely
|-
| 42 || [[User:Vasile|Vasile Crăciunescu]] || RO || || || || GRASS GIS / INSPIRE/ Open GeoData || Very Likely
|-
| 43 || Radim Blazek || CZ || Mar 24 || Mar 27 || Wiener Kindl || QGIS ||
|-
| 44 || [[User:lastools|Martin Isenburg]] || DE || || || || QGIS, LAStools, light-weight data base || Definite
|-
| 45 || [[User:Johanvdw|Johan Van de Wauw]] || BE || || || || SAGA - QGis processing, OSGeo live || Likely, probably not all days
|-
| 46 || [[User:neumann|Andreas Neumann]] || CH || tbd || tbd || tbd || QGIS, QGIS Web Client || Very Likely
|-
| 47 || Denis Rouzaud || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 48 || Peter Wells || UK || tbd || tbd || tbd || QGIS || Very Likely
|-
| 49 || [[User:Jef|Jürgen Fischer]] || DE || tbd || tbd || tbd || QGIS || Very Likely
|-
| 50 || Yves Jacolin || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 51 || Stéphane Brunner || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 52 || Arnaud Morvan || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 53 || Alessandro Pasotti || IT || tbd || tbd || tbd || QGIS, QGIS Web Client, QGIS Plugins repo || Very Likely
|-
| 54 || [[User:Rouault|Even Rouault]] || FR || tbd || tbd || tbd || GDAL, MapServer, QGIS? || Likely
|-
| 55 || Rob Emanuele || US || tbd || tbd || tbd || GDAL || Likely
|-
| 56 || Stefano Cavallari || DE || Mar 24 || Mar 28 || tbd || GRASS/QGIS, Python || Definite
|-
| 57 || Anita Graser || AT || tbd || tbd || home || QGIS || Definite
|-
| 58 || Kenny Shepard || US || tbd || tbd || tbd || GDAL || Very Likely
|-
| 59 || Rafael Krucker || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| 60 || Tobias Schmitz || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| || || || || || || ||
|-
|}



== Individual Preparation ==

* Bring your own computer
* Install git, subversion and the compiler tools, and come with a working development environment if possible

== FAQ ==

* Is the Vienna Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.

== Social Activities ==

TBD

Ideas
* Skiing: The idea is to find a not too far away place the weekend after the sprint. Please add your name if you're interested: [[User:schpidi|Stephan Meissl]]

Isn't it a bit late for skiing at this time of the year in eastern Austria?

== Budget ==

TBD

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Vienna Code Sprint 2014

2014-01-26T18:27:19Z

Wiki-Sfkeller: /* Participants */ Added country relationship of Swiss (CH) participants :-)

''OSGeo Code Sprint 2014 official web site: [http://vienna2014.sprint.osgeo.org http://vienna2014.sprint.osgeo.org]. Please contact us if you are interested in our [http://vienna2014.sprint.osgeo.org/sponsoring.html sponsorship opportunities].''

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|260px|Airborne Interactive Ltd|link=http://www.airborne.aero/]]
 
http://www.airborne.aero/
|
[[File:Logo-Austrospace.png‎|260px|Austrospace|link=http://www.austrospace.at/]]
 
http://www.austrospace.at/
|
[[File:Logo-TYDAC.png‎|260px|TYDAC|link=http://www.tydac.ch]]
 
http://www.tydac.ch
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-FOSSGIS-e.V.png‎|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]
 
http://www.fossgis.de
|}

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-ITS-VR.jpg|260px|ITS Vienna Region|link=http://www.anachb.at/mehr]]
 
http://www.anachb.at/mehr
|}

'''Bronze Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-metaspatial.png|260px|metaspatial Institut|link=http://www.metaspatial.net/en/institute]]
 
[http://metaspatial.net/en/institute http://metaspatial.net/en/institute]
|
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com]]
 
[http://www.oslandia.com http://www.oslandia.com]
|
[[File:Logo-rapidlasso.png|260px|rapidlasso|link=http://rapidlasso.com]]
 
[http://rapidlasso.com http://rapidlasso.com]
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.jpg‎|260px|Azavea|link=http://www.azavea.com]]
 
http://www.azavea.com
|}

'''Venue Sponsor'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-City-of-Vienna.png|260px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]
 
[http://www.wien.gv.at/english/administration/ict/index.html http://www.wien.gv.at/]
|}

'''Other/in-kind sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Purpose ==

Get together project members to make decisions and tackle larger geospatial
problems (as done last year at the [[Boston Code Sprint 2013]] and previous
years: [[IslandWood Code Sprint 2012|Island Wood]] (2012),
[[Montreal Code Sprint 2011|Montreal]] (2011),
[[New York Code Sprint 2010|New York City]] (2010), and
[[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting
members of the "C Tribe" (e.g., MapServer, QGis, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course,
but we hope that "C Tribe" members will give this event special consideration.

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22].

The venue is not far from the center of Vienna (~25min via train and subway) and can be reached easily from the Vienna airport via train.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

== Hotel ==

Two blocks of rooms have been negotiated at the two hotels closest to the sprint venue, [http://www.hillinger.at Hotel Hillinger] ([http://www.openstreetmap.org/#map=19/48.23133/16.45037 map]) and [http://www.wienerkindl.at Hotel Wiener Kindl] ([http://www.openstreetmap.org/#map=19/48.22757/16.45428 map]). Please make your own choice.

The rooms are blocked for the sprint week i.e. 24.-28. March 2014 whereas +/- one day should be no problem.

Please find the lists of available rooms below. If you make a reservation for one of the listed rooms please indicate this by adding your name to the list. Thanks.

Don't hesitate to contact me if you need any assistance.

=== Hotel Wiener Kindl ===

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 65,- || 3 || <add your name> ||
|-
| 2 || € 80,- || 6 || <add your name> ||
|-
| 3 || € 90,- || 2 || <add your name> ||
|}

The rates include breakfast buffet, sat TV, direct dial telephone, ensuite bathroom with shower, minibar, and free WLAN.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee later

These rooms are blocked until 28.02.2014. Please make your reservation via mail to "wienerkindl@utanet.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

If you really want to save on budget you might consider a room with shared bathroom and sometimes also shared shower. Note that these rooms are available at the hotel as backup rooms but not recommended. You have been warned.

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl-low-budget
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 45,- || 3 || Radim Blazek ||
|-
| 2 || € 50,- || 2 || <add your name> ||
|}

=== Hotel Hillinger ===

'''Note, in case you've seen the previous note, that today I visited the hotel again and hopefully resolved all misunderstandings.'''

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Hillinger
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 2 || € 85,- || 15 are blocked of up to 50 || <add your name> || Most of the rooms have double beds and some twin beds. Ask for your preferred choice.
|-
| 1 || € 65,- || Same as above but single use || <add your name> ||
|-
| 3 || € 105,- || 4 || <add your name> || 2 of the rooms can also be used as 4 bed rooms for € 125,-.
|}

The rates include breakfast buffet, cable and pay-TV, air conditioning, direct dial telephone, ensuite bathroom with bathtub or shower, hairdryer, and free WLAN in the whole hotel. In addition they offer free usage of the climbing hall and fitness center on the other side of the street.

Accepted payment methods: cash or creditcard.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee from 7 to 3 days in advance
* 100% fee later

These rooms are blocked until 15.02.2014. Please make your reservation via mail to "hotel@hillinger.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

=== Alternatives ===

If you don't feel comfortable with both options we recommend to look for alternatives around Kagran ([http://www.openstreetmap.org/#map=15/48.2434/16.4341 map]) which is just a couple of stops away from the venue with the tram and also close to the city center with the subway.

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for four nights
* Breakfast and dinner (partly)

== Project Plans ==

TBD

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==

We are planning for attendance of 50-60 participants. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
any special needs.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accomodation || Work on || Notes
|-
| 1 || [[User:schpidi|Stephan Meissl]] || AT || first day || last day || home || MapServer || Definite - No special needs
|-
| 2 || [[User:ahocevar|Andreas Hocevar]] || AT || first day || last day || family || OpenLayers || Definite - No hotel needed
|-
| 3 || [[User:pwramsey3|Paul Ramsey]] || CA || Mar 23 (AC6164) || Mar 30 (AC9159) || TBD || PostGIS || Booked
|-
| 4 || [[User:msmitherdc|Michael Smith]] || || || || || PDAL/MapServer || Very Likely
|-
| 5 || [[Jeff McKenna]] || CA || Likely Mar 26 || Likely Mar 30 || || MapServer, ZOO-Project, pycsw || Very Likely
|-
| 6 || [[User:Dmorissette|Daniel Morissette]] || CA || || || || MapServer, GDAL/OGR || Very Likely
|-
| 7 || [[User:hobu|Howard Butler]] || USA || Mar 22 || Mar 29 || || MapServer, GDAL/OGR, PDAL || Booked
|-
| 8 || Olivier Courtin || || || || || PostGIS, TinyOWS || Very Likely
|-
| 9 || [[User:Lucadelu|Luca Delucchi]] || IT || || || || GRASS GIS || Very Likely
|-
| 10 || [[User:Landa|Martin Landa]] || CZ || || || || GRASS GIS, PostGIS, GDAL/OGR || Very Likely
|-
| 11 || [[User:Tbonfort|Thomas Bonfort]] || France || Mar 24 midday || Mar 28 || || MapServer || Definite
|-
| 12 || [[User:Szekerest|Tamas Szekeres]] || Hungary || Mar 24 midday || Mar 28 || || MapServer, GDAL/OGR || Definite
|-
| 13 || [[User:Mloskot|Mateusz Loskot]] || || || || || PDAL || Likely
|-
| 14 || [[User:pcav|Paolo Cavallini]] || || || || || QGIS || Very likely
|-
| 15 || [[User:Neteler|Markus Neteler]] || IT || || || || GRASS GIS || Likely
|-
| 16 || [[User:kalxas|Angelos Tzotsos]] || GR || Mar 23 (OS0802) || Mar 29 (OS0801) || TBD || OSGeoLive, pycsw/GeoPython/GeoNode, OTB, ZOO-Project || Booked
|-
| 17 || [[User:Aghisla|Anne Ghisla]] || DE || Mar 24 || Mar 28 || || GRASS GIS/QGIS/Translations || Definite
|-
| 18 || [[User:Jachym|Jachym Cepicky]] || || || || || PyWPS/GeoPython (OpenLayers) || Likely
|-
| 19 || [[User:Jesus|Jorge de Jesus]] || || || || || PyWPS/REST/GeoPython || Likely
|-
| 20 || [[User:atrawog| Andreas Trawoeger]] || || || || || GRASS GIS || Very Likely
|-
| 21 || [[User:ortelius| Jeffrey Johnson]] || || || || || GeoNode/ GeoPython || Very Likely
|-
| 22 || [[User:pacesm| Martin Paces]] || || || || || EOxServer || Very Likely
|-
| 23 || [[User:fschindler| Fabian Schindler]] || || || || || EOxServer/MapServer || Definite
|-
| 24 || [[User:Djay|Gérald Fenoy]] || FR || || || || MapServer, ZOO-Project || Likely
|-
| 25 || Marco Hugentobler || CH || || || || QGIS || Very Likely
|-
| 26 || Mathias Walker || CH || || || || QGIS || Very Likely
|-
| 27 || [[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || || || || QGIS, GDAL/OGR || Likely
|-
| 28 || [[User:capooti|Paolo Corti]] || || || || || GeoNode/QGIS || Very Likely
|-
| 29 || [[Arnulf Christl]] - [[OSGeo]], [[Geo for All]] || DE || || || || Guest ||
|-
| 30 || [[User:rduivenvoorde|Richard Duivenvoorde]] || NL || tbd || tbd || tbd || QGIS, context help, vector tools || Very likely
|-
| 31 || [[User:timlinux|Tim Sutton]] || || || || || QGIS || likely
|-
| 32 || [[User:mbernasocchi|Marco Bernasocchi]] || CH || || || || QGIS || Very likely
|-
| 33 || [[User:MartinDobias|Martin Dobias]] || SK || || || || QGIS || Likely
|-
| 34 || Hugo Mercier || || || || || QGIS, SFCGAL, PostGIS || Very Likely
|-
| 35 || Vincent Mora || || || || || QGIS, SFCGAL || Very Likely
|-
| 36 || [[User:hellik|Helmut Kudrnovsky]] || AT || || || || GRASS GIS || Likely
|-
| 37 || [[User:lutra|Giovanni Manghi]] || PT/IT || || || || QGIS || Likely
|-
| 38 || [[User:Ginetto|Luigi Pirelli]] || ES/IT ||24(VY8710) 14:30|| 30(VY8711) ||tbd || QGIS || Booked flight
|-
| 39 || [[Milena Nowotarska | Milena Nowotarska]] || PL || || || || GRASS GIS/QGIS || Likely
|-
| 40 || [[User:Madi|Margherita Di Leo]] || IT || || || || GRASS GIS / INSPIRE || Likely
|-
| 41 || [[User:Macho|Werner Macho]] || AT || || || || QGIS || Likely
|-
| 42 || [[User:Vasile|Vasile Crăciunescu]] || RO || || || || GRASS GIS / INSPIRE/ Open GeoData || Very Likely
|-
| 43 || Radim Blazek || CZ || Mar 24 || Mar 27 || Wiener Kindl || QGIS ||
|-
| 44 || [[User:lastools|Martin Isenburg]] || DE || || || || QGIS, LAStools, light-weight data base || Definite
|-
| 45 || [[User:Johanvdw|Johan Van de Wauw]] || BE || || || || SAGA - QGis processing, OSGeo live || Likely, probably not all days
|-
| 46 || [[User:neumann|Andreas Neumann]] || CH || tbd || tbd || tbd || QGIS, QGIS Web Client || Very Likely
|-
| 47 || Denis Rouzaud || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 48 || Peter Wells || UK || tbd || tbd || tbd || QGIS || Very Likely
|-
| 49 || [[User:Jef|Jürgen Fischer]] || DE || tbd || tbd || tbd || QGIS || Very Likely
|-
| 50 || Yves Jacolin || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 51 || Stéphane Brunner || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 52 || Arnaud Morvan || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 53 || Alessandro Pasotti || IT || tbd || tbd || tbd || QGIS, QGIS Web Client, QGIS Plugins repo || Very Likely
|-
| 54 || [[User:Rouault|Even Rouault]] || FR || tbd || tbd || tbd || GDAL, MapServer, QGIS? || Likely
|-
| 55 || Rob Emanuele || US || tbd || tbd || tbd || GDAL || Likely
|-
| 56 || Stefano Cavallari || DE || Mar 24 || Mar 28 || tbd || GRASS/QGIS, Python || Definite
|-
| 57 || Anita Graser || AT || tbd || tbd || home || QGIS || Definite
|-
| 58 || Kenny Shepard || US || tbd || tbd || tbd || GDAL || Very Likely
|-
| 59 || Rafael Krucker || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| 60 || Tobias Schmitz || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| || || || || || || ||
|-
|}



== Individual Preparation ==

* Bring your own computer
* Install git, subversion and the compiler tools, and come with a working development environment if possible

== FAQ ==

* Is the Vienna Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.

== Social Activities ==

TBD

Ideas
* Skiing: The idea is to find a not too far away place the weekend after the sprint. Please add your name if you're interested: [[User:schpidi|Stephan Meissl]]

Isn't it a bit late for skiing at this time of the year in eastern Austria?

== Budget ==

TBD

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Vienna Code Sprint 2014

2014-01-26T18:24:20Z

Wiki-Sfkeller: /* Participants */

''OSGeo Code Sprint 2014 official web site: [http://vienna2014.sprint.osgeo.org http://vienna2014.sprint.osgeo.org]. Please contact us if you are interested in our [http://vienna2014.sprint.osgeo.org/sponsoring.html sponsorship opportunities].''

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|260px|Airborne Interactive Ltd|link=http://www.airborne.aero/]]
 
http://www.airborne.aero/
|
[[File:Logo-Austrospace.png‎|260px|Austrospace|link=http://www.austrospace.at/]]
 
http://www.austrospace.at/
|
[[File:Logo-TYDAC.png‎|260px|TYDAC|link=http://www.tydac.ch]]
 
http://www.tydac.ch
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-FOSSGIS-e.V.png‎|260px|FOSSGIS e.V.|link=http://www.fossgis.de]]
 
http://www.fossgis.de
|}

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-ITS-VR.jpg|260px|ITS Vienna Region|link=http://www.anachb.at/mehr]]
 
http://www.anachb.at/mehr
|}

'''Bronze Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-metaspatial.png|260px|metaspatial Institut|link=http://www.metaspatial.net/en/institute]]
 
[http://metaspatial.net/en/institute http://metaspatial.net/en/institute]
|
[[File:Logo-Oslandia.png|260px|Oslandia|link=http://www.oslandia.com]]
 
[http://www.oslandia.com http://www.oslandia.com]
|
[[File:Logo-rapidlasso.png|260px|rapidlasso|link=http://rapidlasso.com]]
 
[http://rapidlasso.com http://rapidlasso.com]
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Azavea.jpg‎|260px|Azavea|link=http://www.azavea.com]]
 
http://www.azavea.com
|}

'''Venue Sponsor'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-City-of-Vienna.png|260px|City of Vienna MA 14|link=http://www.wien.gv.at/english/administration/ict/index.html]]
 
[http://www.wien.gv.at/english/administration/ict/index.html http://www.wien.gv.at/]
|}

'''Other/in-kind sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Purpose ==

Get together project members to make decisions and tackle larger geospatial
problems (as done last year at the [[Boston Code Sprint 2013]] and previous
years: [[IslandWood Code Sprint 2012|Island Wood]] (2012),
[[Montreal Code Sprint 2011|Montreal]] (2011),
[[New York Code Sprint 2010|New York City]] (2010), and
[[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting
members of the "C Tribe" (e.g., MapServer, QGis, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course,
but we hope that "C Tribe" members will give this event special consideration.

== Venue ==

The City of Vienna MA 14 gladly provides the location for the Vienna Code Sprint for up to 60 sprinters in [http://www.wien.gv.at/stadtplan/grafik.aspx?lang=de-AT&bookmark=zHClRv95TUbsTHFEFcAeRO5RphlRnHnkur2pH4Oprw-b-b&bmadr=25723751 their very new office called STAR 22].

The venue is not far from the center of Vienna (~25min via train and subway) and can be reached easily from the Vienna airport via train.

== Dates and Times ==

March 24-28 2014

Note: March 19-21 FOSSGIS Berlin

Duration: Full week

== Agenda ==

TBD

== Hotel ==

Two blocks of rooms have been negotiated at the two hotels closest to the sprint venue, [http://www.hillinger.at Hotel Hillinger] ([http://www.openstreetmap.org/#map=19/48.23133/16.45037 map]) and [http://www.wienerkindl.at Hotel Wiener Kindl] ([http://www.openstreetmap.org/#map=19/48.22757/16.45428 map]). Please make your own choice.

The rooms are blocked for the sprint week i.e. 24.-28. March 2014 whereas +/- one day should be no problem.

Please find the lists of available rooms below. If you make a reservation for one of the listed rooms please indicate this by adding your name to the list. Thanks.

Don't hesitate to contact me if you need any assistance.

=== Hotel Wiener Kindl ===

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 65,- || 3 || <add your name> ||
|-
| 2 || € 80,- || 6 || <add your name> ||
|-
| 3 || € 90,- || 2 || <add your name> ||
|}

The rates include breakfast buffet, sat TV, direct dial telephone, ensuite bathroom with shower, minibar, and free WLAN.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee later

These rooms are blocked until 28.02.2014. Please make your reservation via mail to "wienerkindl@utanet.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

If you really want to save on budget you might consider a room with shared bathroom and sometimes also shared shower. Note that these rooms are available at the hotel as backup rooms but not recommended. You have been warned.

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Wiener-Kindl-low-budget
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 1 || € 45,- || 3 || Radim Blazek ||
|-
| 2 || € 50,- || 2 || <add your name> ||
|}

=== Hotel Hillinger ===

'''Note, in case you've seen the previous note, that today I visited the hotel again and hopefully resolved all misunderstandings.'''

{| style="border: solid grey 1px" class="sortable"
|+ Hotel-Hillinger
|-
| # Beds || Rate || # Rooms || Reservations || Notes
|-
| 2 || € 85,- || 15 are blocked of up to 50 || <add your name> || Most of the rooms have double beds and some twin beds. Ask for your preferred choice.
|-
| 1 || € 65,- || Same as above but single use || <add your name> ||
|-
| 3 || € 105,- || 4 || <add your name> || 2 of the rooms can also be used as 4 bed rooms for € 125,-.
|}

The rates include breakfast buffet, cable and pay-TV, air conditioning, direct dial telephone, ensuite bathroom with bathtub or shower, hairdryer, and free WLAN in the whole hotel. In addition they offer free usage of the climbing hall and fitness center on the other side of the street.

Accepted payment methods: cash or creditcard.

Cancellation policy:
* Free cancellation until 7 days in advance
* 50% fee from 7 to 3 days in advance
* 100% fee later

These rooms are blocked until 15.02.2014. Please make your reservation via mail to "hotel@hillinger.at" and indicate that you're participating at the "OSGeo Vienna Code Sprint" in order to get a room of the block.

=== Alternatives ===

If you don't feel comfortable with both options we recommend to look for alternatives around Kagran ([http://www.openstreetmap.org/#map=15/48.2434/16.4341 map]) which is just a couple of stops away from the venue with the tram and also close to the city center with the subway.

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for four nights
* Breakfast and dinner (partly)

== Project Plans ==

TBD

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==

We are planning for attendance of 50-60 participants. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
any special needs.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accomodation || Work on || Notes
|-
| 1 || [[User:schpidi|Stephan Meissl]] || Austria || first day || last day || home || MapServer || Definite - No special needs
|-
| 2 || [[User:ahocevar|Andreas Hocevar]] || Austria || first day || last day || family || OpenLayers || Definite - No hotel needed
|-
| 3 || [[User:pwramsey3|Paul Ramsey]] || Canada || Mar 23 (AC6164) || Mar 30 (AC9159) || TBD || PostGIS || Booked
|-
| 4 || [[User:msmitherdc|Michael Smith]] || || || || || PDAL/MapServer || Very Likely
|-
| 5 || [[Jeff McKenna]] || CA || Likely Mar 26 || Likely Mar 30 || || MapServer, ZOO-Project, pycsw || Very Likely
|-
| 6 || [[User:Dmorissette|Daniel Morissette]] || CA || || || || MapServer, GDAL/OGR || Very Likely
|-
| 7 || [[User:hobu|Howard Butler]] || USA || Mar 22 || Mar 29 || || MapServer, GDAL/OGR, PDAL || Booked
|-
| 8 || Olivier Courtin || || || || || PostGIS, TinyOWS || Very Likely
|-
| 9 || [[User:Lucadelu|Luca Delucchi]] || IT || || || || GRASS GIS || Very Likely
|-
| 10 || [[User:Landa|Martin Landa]] || CZ || || || || GRASS GIS, PostGIS, GDAL/OGR || Very Likely
|-
| 11 || [[User:Tbonfort|Thomas Bonfort]] || France || Mar 24 midday || Mar 28 || || MapServer || Definite
|-
| 12 || [[User:Szekerest|Tamas Szekeres]] || Hungary || Mar 24 midday || Mar 28 || || MapServer, GDAL/OGR || Definite
|-
| 13 || [[User:Mloskot|Mateusz Loskot]] || || || || || PDAL || Likely
|-
| 14 || [[User:pcav|Paolo Cavallini]] || || || || || QGIS || Very likely
|-
| 15 || [[User:Neteler|Markus Neteler]] || IT || || || || GRASS GIS || Likely
|-
| 16 || [[User:kalxas|Angelos Tzotsos]] || GR || Mar 23 (OS0802) || Mar 29 (OS0801) || TBD || OSGeoLive, pycsw/GeoPython/GeoNode, OTB, ZOO-Project || Booked
|-
| 17 || [[User:Aghisla|Anne Ghisla]] || DE || Mar 24 || Mar 28 || || GRASS GIS/QGIS/Translations || Definite
|-
| 18 || [[User:Jachym|Jachym Cepicky]] || || || || || PyWPS/GeoPython (OpenLayers) || Likely
|-
| 19 || [[User:Jesus|Jorge de Jesus]] || || || || || PyWPS/REST/GeoPython || Likely
|-
| 20 || [[User:atrawog| Andreas Trawoeger]] || || || || || GRASS GIS || Very Likely
|-
| 21 || [[User:ortelius| Jeffrey Johnson]] || || || || || GeoNode/ GeoPython || Very Likely
|-
| 22 || [[User:pacesm| Martin Paces]] || || || || || EOxServer || Very Likely
|-
| 23 || [[User:fschindler| Fabian Schindler]] || || || || || EOxServer/MapServer || Definite
|-
| 24 || [[User:Djay|Gérald Fenoy]] || FR || || || || MapServer, ZOO-Project || Likely
|-
| 25 || Marco Hugentobler || || || || || QGIS || Very Likely
|-
| 26 || Mathias Walker || || || || || QGIS || Very Likely
|-
| 27 || [[User:Pirmin_Kalberer|Pirmin Kalberer]] || || || || || QGIS, GDAL/OGR || Likely
|-
| 28 || [[User:capooti|Paolo Corti]] || || || || || GeoNode/QGIS || Very Likely
|-
| 29 || [[Arnulf Christl]] - [[OSGeo]], [[Geo for All]] || DE || || || || Guest ||
|-
| 30 || [[User:rduivenvoorde|Richard Duivenvoorde]] || NL || tbd || tbd || tbd || QGIS, context help, vector tools || Very likely
|-
| 31 || [[User:timlinux|Tim Sutton]] || || || || || QGIS || likely
|-
| 32 || [[User:mbernasocchi|Marco Bernasocchi]] || || || || || QGIS || Very likely
|-
| 33 || [[User:MartinDobias|Martin Dobias]] || SK || || || || QGIS || Likely
|-
| 34 || Hugo Mercier || || || || || QGIS, SFCGAL, PostGIS || Very Likely
|-
| 35 || Vincent Mora || || || || || QGIS, SFCGAL || Very Likely
|-
| 36 || [[User:hellik|Helmut Kudrnovsky]] || AT || || || || GRASS GIS || Likely
|-
| 37 || [[User:lutra|Giovanni Manghi]] || PT/IT || || || || QGIS || Likely
|-
| 38 || [[User:Ginetto|Luigi Pirelli]] || ES/IT ||24(VY8710) 14:30|| 30(VY8711) ||tbd || QGIS || Booked flight
|-
| 39 || [[Milena Nowotarska | Milena Nowotarska]] || PL || || || || GRASS GIS/QGIS || Likely
|-
| 40 || [[User:Madi|Margherita Di Leo]] || IT || || || || GRASS GIS / INSPIRE || Likely
|-
| 41 || [[User:Macho|Werner Macho]] || AT || || || || QGIS || Likely
|-
| 42 || [[User:Vasile|Vasile Crăciunescu]] || RO || || || || GRASS GIS / INSPIRE/ Open GeoData || Very Likely
|-
| 43 || Radim Blazek || CZ || Mar 24 || Mar 27 || Wiener Kindl || QGIS ||
|-
| 44 || [[User:lastools|Martin Isenburg]] || DE || || || || QGIS, LAStools, light-weight data base || Definite
|-
| 45 || [[User:Johanvdw|Johan Van de Wauw]] || BE || || || || SAGA - QGis processing, OSGeo live || Likely, probably not all days
|-
| 46 || [[User:neumann|Andreas Neumann]] || CH || tbd || tbd || tbd || QGIS, QGIS Web Client || Very Likely
|-
| 47 || Denis Rouzaud || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 48 || Peter Wells || UK || tbd || tbd || tbd || QGIS || Very Likely
|-
| 49 || [[User:Jef|Jürgen Fischer]] || DE || tbd || tbd || tbd || QGIS || Very Likely
|-
| 50 || Yves Jacolin || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 51 || Stéphane Brunner || CH || tbd || tbd || tbd || QGIS || Very Likely
|-
| 52 || Arnaud Morvan || FR || tbd || tbd || tbd || QGIS || Very Likely
|-
| 53 || Alessandro Pasotti || IT || tbd || tbd || tbd || QGIS, QGIS Web Client, QGIS Plugins repo || Very Likely
|-
| 54 || [[User:Rouault|Even Rouault]] || FR || tbd || tbd || tbd || GDAL, MapServer, QGIS? || Likely
|-
| 55 || Rob Emanuele || US || tbd || tbd || tbd || GDAL || Likely
|-
| 56 || Stefano Cavallari || DE || Mar 24 || Mar 28 || tbd || GRASS/QGIS, Python || Definite
|-
| 57 || Anita Graser || AT || tbd || tbd || home || QGIS || Definite
|-
| 58 || Kenny Shepard || US || tbd || tbd || tbd || GDAL || Very Likely
|-
| 59 || Rafael Krucker || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| 60 || Tobias Schmitz || CH || Mar 24 || Mar 28 || budget or youth hostel || QGIS || Very Likely
|-
| || || || || || || ||
|-
|}



== Individual Preparation ==

* Bring your own computer
* Install git, subversion and the compiler tools, and come with a working development environment if possible

== FAQ ==

* Is the Vienna Code Sprint just a coding event?
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.

== Social Activities ==

TBD

Ideas
* Skiing: The idea is to find a not too far away place the weekend after the sprint. Please add your name if you're interested: [[User:schpidi|Stephan Meissl]]

Isn't it a bit late for skiing at this time of the year in eastern Austria?

== Budget ==

TBD

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Edu current initiatives

2014-01-26T16:07:45Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
|
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionu? Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciolkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Podör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| In process of being established
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutic
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| In process of being established
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://wiki.hsr.ch/StefanKeller/wiki.cgi?GeometaLab University of Applied Sciences (HSR) - Geometa Lab]
| Rapperswil (St. Gallen)
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| [http://www.gis.hsr.ch GISpunkt] / [http://www.ifs.hsr.ch/Bessere-Software-Einfach-sc.5736.0.html?&no_cache=1&L=4 Institute for Software (IFS)]
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Edu current initiatives

2014-01-26T16:07:10Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */ Added Geometa Lab from HSR Switzerland as lab no. 65.

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
|
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionu? Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciolkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Podör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| In process of being established
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutic
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| In process of being established
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://wiki.hsr.ch/StefanKeller/wiki.cgi?GeometaLab University of Applied Sciences (HSR) -Geometa Lab]
| Rapperswil (St. Gallen)
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| [http://www.gis.hsr.ch GISpunkt] / [http://www.ifs.hsr.ch/Bessere-Software-Einfach-sc.5736.0.html?&no_cache=1&L=4 Institute for Software (IFS)]
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Edu current initiatives

2014-01-26T16:03:17Z

Wiki-Sfkeller: /* 2) Continue to expand the ICA-OSGeo Network */

== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==

'''The official website is online at ''http://www.geoforall.org'''''

=== 1) Continue to build up our educational material federated content databases ===

[http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites 
[http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share

[[Webinar Series ]]

===2) Continue to expand the ICA-OSGeo Network ===

This effort is led by Suchith Anand at the University of Nottingham, UK.

In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].


It is really good to see our rapidly expanding global spread.

Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.

The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the ICA-OSGeo Map) :

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!
! Laboratory name and institution
! City
! Country
! Continent
! Coordinates (longitude, latitude)
! Application recieved / Announced
! Notes (collaborations, etc)
! Contact names
! Contact emails
|-
| 1.
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]
| Nottingham
| UK
| Europe
| -1.250296, 52.831497
|
|
| Jeremy Morley
| Jeremy dot Morley at nottingham.ac.uk
|-
| 2.
| [http://www.sigte.udg.edu/ University of Girona]
| Girona
| Spain
| Europe
| 2.837305, 41.967426
| 2012-09-10
|
| Lluís Vicens
| lluis at sigte.udg.edu
|-
| 3.
| [http://www.osgl.soton.ac.uk/ University of Southampton]
| Southampton
| UK
| Europe
| -1.396873, 50.936974
| 2013-04-30
|
| Jason Sadler
| osgl at geodata.soton.ac.uk
|-
| 4.
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]
| Prague
| Czech Republic
| Europe
| 14.390363, 50.10183
| 2012-11-23
|
| Martin Landa
|
|-
| 5.
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]
| Newcastle
| UK
| Europe
| -1.611536, 54.980656
| 2013-01-17
|
| Philip James
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)
|-
| 6.
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]
| Como
| Italy
| Europe
| 9.095939, 45.803516
| 2013-02-25
|
| Maria Brovelli
| geowb at geomatica.como.polimi.it
|-
| 7.
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]
| Warwick
| UK
| Europe
| -1.56273, 52.380531
| 2013-03-23
|
| Nataliya Tkachenko
| geolab at warwick.ac.uk
|-
| 8.
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]
| Warsaw
| Poland
| Europe
| 21.039473, 52.198849
| 2013-03-18
|
| Ela Woloszynska-Wisniewska
| ela at gridw.pl
|-
| 9.
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)
| Lugano
| Switzerland
| Europe
| 8.961098, 46.028362
| 2013-09-03
|
| Massimiliano Cannata
| geomatica at supsi.ch
|-
| 10.
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]
| Zurich
| Switzerland
| Europe
| 8.5481, 47.3764
| 2013-09-20
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]
| Ionuț Iosifescu
| iosifescu at ethz.ch
|-
| 11.
| University of Molise
| Molise
| Italy
| Europe
| 14.493651, 41.630815
|
| in process of being established
| Rosella Nocera
|
|-
| 12.
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)
| Warsaw
| Poland
| Europe
| 21.012229, 52.229676
|
| in process of being established
| Agata Ciołkosz-Styk
|
|-
| 13.
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]
| Bucharest
| Romania
| Europe
| 26.103889, 44.432500
|
| in process of being established; new website under development
| Andreea Marin
| andreea dot marin09 at yahoo dot com
|-
| 14.
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]
| Székesfehérvár
| Hungary
| Europe
| 18.418833, 47.188778
|
| in process of being established
| Andrea Pődör
|
|-
| 15.
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]
| Stuttgart
| Germany
| Europe
| 9.17370, 48.77996
| 2013-10-14
|
| Franz-Josef Behr
| franz-josef.behr at hft-stuttgart.de
|-
| 16.
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]
| Paraná
| Brazil
| South America
| -49.26141, -25.427074
| 2012-05-23
|
| Silvana Camboim
|
|-
| 17.
| [http://www.unesp.br/ São Paulo State University] (UNESP)
| São Paulo
| Brazil
| South America
| -46.654129, -23.576574
|
|
|
|
|-
| 18.
| National Amazonian University of Madre de Dios (UNAMAD)
| Puerto Maldonado
| Peru
| South America
| -73.245789, -3.745845
| 2013-02-01
| in process of being established
| Andrea Birgit Chavez
|
|-
| 19.
| [http://ltaat.fcien.edu.uy Universidad de la República]
| Montevideo
| Uruguay
| South America
| -56.176441, -34.902405
| 2013-03-01
| new website under development
| Virginia Fernandez
| vfernandez at presidencia.gub.uy
|-
| 20.
| University of Campinas
| Campinas
| Brazil
| South America
| -47.063239, -22.907105
|
| in process of being established
|
|
|-
| 21.
| Federal University of Alagoas
| Maceió
| Brazil
| South America
| -35.735098, -9.666251
|
| in process of being established
|
|
|-
| 22.
| [http://gis.ncsu.edu/osgeorel/ Center for Earth Observation, North Carolina State University]
| Raleigh, NC
| USA
| North America
| -78.6764, 35.7818
| 2012-10-18
|
| Helena Mitasova
| hmitaso at ncsu.edu
|-
| 23.
| [http://www.umass.edu/ University of Massachusetts Amherst]
| Amherst
| USA
| North America
| -72.524696, 42.393578
| 2012-10-18
| website: coming soon
| Charlie Schweik
|
|-
| 24.
| [https://sites.google.com/site/foss4gku/ University of Kansas]
| Lawrence, KS
| USA
| North America
| -95.251311, 38.958578
| 2013-08-23
|
| Xingong Li
| lixi at ku.edu
|-
| 25.
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]
| Davis
| USA
| North America
| -121.766945, 38.548801
| 2013-02-04
| in process of being established
| Alex Mandel
| aimandel at ucdavis.edu
|-
| 26.
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]
| Zacatecas
| Mexico
| North America
| -102.5791, 22.7608
| 2013-04-05
| in process of being established
| Manual Haro
| manuel.haro at zacatecas.gob.mx
|-
| 27.
| Kent State University
| Kent, Ohio
| USA
| North America
| -81.357886,41.153667
| 2013-08-30
|
| Xinyue Ye
| xye5 at kent.edu
|-
| 28.
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]
| Charlotte, NC
| USA
| North America
| -80.730000, 35.306944
| 2013-09-05
|
| Wenwu Tang
| WenwuTang at uncc.edu
|-
| 29.
| [http://www.nottingham.edu.my/Geography/Newsitems/Establishing-Open-Source-Geospatial-Lab.aspx University of Nottingham, Malaysia campus]
| Semenyih
| Malaysia
| Asia
| 101.721298, 3.172932
| 2012-01-09
| website in development
| Tuong Thuy Vu
| Tuongthuy.Vu at nottingham.edu.my
|-
| 30.
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)
| Johor Bahru
| Malaysia
| Asia
| 101.874222, 2.943748
|
| in process of being established
|
|
|-
| 31.
| National College of Public Administration and Governance(NCPAG), University of the Philippines
| Manila
| Philippines
| Asia
| 121.059875, 14.656005
|
| in process of being established
| Noriel Christopher Tiglao
|
|-
| 32.
| Environmental Science for Social Change (ESSC)
| Quezon City
| Philippines
| Asia
| 121.062241, 14.64372
|
| in process of being established
| Maning Sambale
|
|-
| 33.
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad
| Hyderabad
| India
| Asia
| 78.3503, 17.4454
| 2011-08-22
|
| Dr K S Rajan
|
|-
| 34.
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)
| Islamabad
| Pakistan
| Asia
| 73.175045, 33.520060
|
|
|Rizwan Bulbul
|bulbul(dot)rizwan(at)gmail(dot)com
|-
| 35.
| [http://www.up.ac.za/cgis University of Pretoria]
| Pretoria
| South Africa
| Africa
| 28.22847, -25.75429
| 2012-05-15
|
| Serena Coetzee
| serena dot coetzee at up dot ac dot za
|-
| 36.
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)
| Nairobi
| Kenya
| Africa
| 36.858574, -1.249038
|
| in process of being established
| Hussein Farah
| farah at rcmrd.org
|-
| 37.
| University of Ghana
| Accra
| Ghana
| Africa
| -0.191617, 5.650366
|
| in process of being established
| Foster Mensah
|
|-
| 38.
| The University of Melbourne
| Melbourne
| Australia
| Australia
| 144.962006, -37.797932
| 2013-07-22
|
| Chris Pettit
|
|-
| 39.
| [http://gisc.tamucc.edu Texas A&M University]
| Corpus Christi
| USA
| North America
| -97.328799, 27.714506
| 2013-09-09
| in process of being established
| Rick Smith
| Richard.Smith at tamucc.edu
|-
| 40.
| [http://www.geomaticsindia-cept.org/ CEPT University]
| Ahmedabad
| India
| Asia
| 72.566004,23.039568
| 2012-07-18
| in process of being established
| Prof. Anjana Vyas & Ms. Darshana Rawal
| anjanavyas at cept.ac.in rawalnet at cept.ac.in
|-
| 41.
| National University of San Juan
| San Juan
| Argentina
| South America
| -68.521408, -31.527273
| 2012-06-15
| in process of being established
| Agustin Arroqui
| aarroqui at unsj.edu.ar
|-
| 42.
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]
| Tempe, AZ
| USA
| North America
| -111.940005, 33.425510
| 2013-09-27
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]
| geodacenter at asu.edu
|-
| 43.
| National Technical University of Athens
| Athens
| Greece
| Europe
| 23.729310, 37.983716
| 2013-09-26
| in process of being established
|
|
|-
| 44.
| IGN- France
| Paris
| France
| Europe
| 2.352222, 48.856614
| 2013-09-26
| in process of being established
| Benedicte Bucher
|
|-
| 45.
| Universitat Oberta de Catalunya
| Barcelona
| Spain
| Europe
| 2.173403, 41.385064
| 2013-09-27
| in process of being established
| Dr. Antoni Pérez Navarro
| aperezn at uoc.edu
|-
| 46.
| [http://www.isric.org ISRIC - World Soil Information foundation]
| Wageningen
| The Netherlands
| Europe
| 5.665662,51.9875
|2013-10-02
|website in construction
| Jorge de Jesus
| jorge.mendesdejesus at wur.nl
|-
| 47.
| Universidade da Coruña
| A Coruña (España)
| Spain
| Europe
| -8.411540, 43.362344
| 2013-10-15
| in process of being established
| Alberto Varela García
|
|-
| 48.
| Universiti Sains Malaysia
| Penang
| Malaysia
| Asia
| 100.484623, 5.263234
|2013-10-16
|in process of being established
| Ruslan Rainis
|
|-
| 49.
| Kathmandu University
| Dhulikhel
| Nepal
| Asia
| 85.550000, 27.616667
|2012-12-24
|in process of being established
| Shashish Maharjan
|
|-
| 50
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]
| San Michele all'Adige (Trento)
| Italy
| Europe
| 11.133042,46.187865
|2013-10-16
|
| Luca Delucchi
| luca.delucchi at fmach.it
|-
| 51.
| [http://gis.research.southwales.ac.uk/ University of South Wales ]
| Cardiff
| United Kingdom
| Europe
| -3.179090,51.481581
|2013-10-31
|
| Dr Mark Ware
| mark.ware at southwales.ac.uk
|-
| 52.
| Portland State University
| Portland, Oregon
| USA
| North America
| -122.676207,45.523452
| 2013-10-22
| In process of being established
| David Percy
| percy at pdx.edu
|-
| 53.
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]
| Nairobi
| Kenya
| Africa
| 36.821946,-1.292066
| 2013-10-29
| In process of being established
| Muyambi Fortunate
| fbenda at icpac.net
|-
|-
| 54.
| [http://www.labocart.ufc.br/ Federal University of Ceará ]
| Ceará
| Brazil
| South America
| -38.543395,-3.718394
| 2013-10-29
| In process of being established
| Prof. Dr. Adryane Gorayeb
| adryanegorayeb at yahoo dot com dot br
|-
| 55.
| [http://geospecial.wordpress.com/ University of Gloucestershire ]
| Gloucester and Cheltenham
| United Kingdom
| Europe
| -2.223409, 51.872215
| 2013-11-06
| In process of being established
| Dr Robert Berry
| rberry at glos.ac.uk
|-
| 56.
| [http://mrt.ac.lk/foa/ University of Moratuwa ]
| Moratuwa
| Sri Lanka
| Asia
| 79.9008, 6.7964
| 2013-11-11
| In process of being established
| Aruna Wickramasinghe
| toaruna at gmail.com
|-
| 57.
| [http://www.fudan.edu.cn/ Fudan University]
| Shanghai
| China
| Asia
| 121.452, 31.198
| 2013-11-14
| [http://lab.osstat.org/ Open Source STATistics]
| Zhijie Zhang
| epistat at gmail.com
|-
| 58.
| Haskell Indian Nations University
| Lawrence, Kansas
| USA
| North America
| -95.230691, 38.938859
| 2013-11-22
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]
| Dave McDermott
| dmcdermott at haskell.edu
|-
| 59.
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165/ University of Zagreb, Faculty of Geodesy]
| Zagreb
| Croatia
| Europe
| 15.963888, 45.808500
| 2013-11-25
| In process of being established
| Dražen Tutić
| dtutic at geof.hr
|-
| 60.
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]
| La Paz
| Bolivia
| South America
| -68.1547, -16.4949
| 2013-11-24
| In process of being established
| Raul Fernando Molina Rodriguez
| rafemoro at gmail.com rmolina@geo.gob.bo
|-
| 61.
| Geodesy and Geomatics Engineering, University of New Brunswick
| Fredericton, NB
| Canada
| North America
| -66.641474, 45.950252
| 2013-12-10
| In process of being established
| Emmanuel Stefanakis
| emmanuel.stefanakis at gmail.com
|-
| 62.
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]
| Belihuloya, Sabaragamuwa
| Sri Lanka
| Asia
| 80.78995, 6.7102
| 2013-12-12
| In process of being established
| Thilantha Dammalage
| thilantha9 at gmail.com
|-
| 63.
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]
| Malabe
| Sri Lanka
| Asia
| 79.973166667, 6.914866667
| 2013-12-13
| In process of being established
| Nimalika Fernando
| nimalikaf at gmail.com
|-
| 64.
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]
| Geneva
| Switzerland
| Europe
| 6.1487, 46.2253
| 2013-12-19
| In process of being established
| Gregory Giuliani
| gregory.giuliani at unige.ch
|-
| 65.
| [http://wiki.hsr.ch/StefanKeller/wiki.cgi?GeometaLab University of Applied Sciences - Institute for Software - Geometa Lab]
| Rapperswil (St. Gallen)
| Switzerland
| Europe
| 8.81690, 47.22341
| 2014-01-26
| In process of being established
| Prof. Stefan Keller
| sfkeller at hsr.ch (and/or at gmail.ch)
|-
|}

== Interested in adding your own node into the ICA-OSGeo Labs network? ==

As the lab network is expanding fast ,we have also setup nodal contacts for each regions

# Anne Ghisla - Asia & Australia
# Helena Mitasova - North America
# Charlie Schweik - South America
# Suchith Anand - Europe & Africa

Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova ‎[hmitaso at ncsu.edu]‎, Charlie Schweik ‎[cschweik at pubpol.umass.edu]‎, Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.

The key requirements for establishing a local OSGL are:

(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.

(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.

(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.

From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.

We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.

== Meetings ==
; Next meeting:
* '''[[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC'''

; Past Meetings:
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC

== ISC OSGeo Lab Network Research and Teaching Areas ==

[[ICA_OSGeo_Lab_Research_areas]]
 
[[ICA_OSGeo_Lab_Teaching_areas]]

[[Category: Education]]
[[Category: ICA OSGeo Lab Network]]

Geoservices REST API

2013-05-09T12:58:38Z

Wiki-Sfkeller: /* Signed */

This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard. It is being collaboratively edited, targeting completion before the end of May 2013.

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go below.''

May 2013

We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.

We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.

People have listed different reasons for concern. They are described below.

== Signed ==
''Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.''

* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live]
* [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Prinicipal Scientist for RadiantBlue Technologies Inc.
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
* [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]
* Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]
* [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member
* [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]
* [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]
* [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.
* [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.
* [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.
* [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.
* Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client
* [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.
* [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.
* [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter
* [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Italy
* [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain
* [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain
* [[User:Fsteggink|Frank Steggink]], GIS software developer at [http://www.vicrea.nl Vicrea], The Netherlands, member of the Dutch Local Chapter
* [[User:Olivier.courtin|Olivier Courtin]], [http://www.oslandia.com Oslandia] co-founder, core contributor or/and PSC member of [http://mapserver.org Mapserver] and [http://www.postgis.org/ PostGIS]. OGC TC member.
* [[User:Bolosig|Wladimir Szczerban]], OSGeo Spanish Local Chapter Member, Spain
* [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member.
* [[User:Vmische|Volker Mische]], geospatial software engineer, creator of GeoCouch
* [[User:Ivansanchez|Iván Sánchez]], OSGeo Spanish Local Chapter Member, head of [http://www.openstreetmap.es OpenStreetMap Spain], [http://osmfoundation.org OpenStreetMap Foundation] member, [http://hot.openstreetmap.org/ Humanitarian OpenStreetMap Team] member, [http://www.idee.es/ Spanish SDI working group] member
* [[User:Gabi|Gabriel Carrión]], Strategy Manager at [http://www.gvsig.com gvSIG association]
* [http://strk.keybit.net Sandro Santilli], OSGeo Charter Member, [http://postgis.net PostGIS] and [http://trac.osgeo.org/geos GEOS] PSC member and core hacker.
* [[User:Javiarch|Javier Diaz]], member of Geoinquietos Bs As [http://wiki.osgeo.org/wiki/Category:Geoinquietos_Buenos_Aires], member of the Organizing Committee FOSS4G Bs As 2013 [http://www.foss4g-ba.org/]
* [[User: JoCook|Jo Cook]], Consultant at [http://isharemaps.com| Astun Technology], former Director of OSGeo, Charter Member, founder of UK Local Chapter, Deputy Chair of [http://2013.foss4g.org| FOSS4G 2013]
* [[User: Fpenarru | Francisco José Peñarrubia]], CTO and co-founder at [http://www.scolab.es SCOLAB]. Members of [http://www.gvsig.com gvSIG Association]
* [[User: Ganesh|Shanmugam Ganeshkumar]], Director of [http://www.geoicon.com GeoICON], member OSGeo Malaysia Chapter
* [[User:Barryrowlingson|Barry Rowlingson]], Senior Researcher, Lancaster University and Software Sustainability Institute Fellow
* [[User: Sfkeller|Stefan Keller]], University of Applied Sciences, Rapperswil (Switzerland), Member of Swiss OSM (SOSM) and QGIS association and of organizing committees of pgConf.DE and FOSSGIS 2013, and member of eCH (e-government standards of Switzerland)

= Concerns =
--- DRAFT ____

''Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)''

== Summary ==
As at May 2013, OGC members have been asked to decide whether to accept the "GeoServices REST API" as an OGC standard. This is a contentious issue, with many people arguing that introduction of the “GeoServices REST API” will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC's reputation as a champion of interoperability.

The key points of contention revolve around the fact that the proposed "GeoServices REST API" does not build upon or extend existing OGC standards, but rather addresses similar requirements using an alternative API. In particular, the overlap and/or duplication of existing standards is widespread: OGC's core standards of WMS, WMTS, WFS, SE/SLD, WCS, CS/W are all duplicated to a significant extent. This defeats the purpose of having standards in the first place.

Duplication of standards will likely result in a combination of the following:
# The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.
# Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.
# Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.
# This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.
# After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.
# One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation. Backward compatibility to the existing WxS standards is important in this respect.
# Given backwards compatibility with the ESRI Restful implementation is mandated, this is not an Open Standard, and should not be ratified as if it was.

== Political Concerns ==

* Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.
* It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a newcomer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?

== Commercial Concerns ==

* Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.
* Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.
* Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.
* Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.

== Technical Concerns ==

* The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.
* At least as far as "imagery" is concerned, OGC standards arguably are substantially more mature, powerful, flexible, and modular then the ESRI "Geoservice REST API" Part 6 (and some design principles suggest that scalability may be hampered as well):
** data model:
*** the ESRI "Geoservice REST API" appears constrained to 2-D imagery, plus optional time stamps. OGC has established a [http://en.wikipedia.org/wiki/Coverage_data unified coverage model] which fully supports n-D spatio-temporal data. It allows use and exchange of coverages between different services, such as [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS], [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS], WPS, and SWE.
*** OGC coverages support both regular and irregular grids; the ESRI "Geoservice REST API" supports only regular grids, more specifically: only rectified grids with quadrilateral pixels.
*** the ESRI "Geoservice REST API" lacks support for temporal data; it only offers timestamps, measured in milliseconds; this is inconvenient for users and immediately excludes, e.g., geological dates. OGC has established uniform handling of horizontal, vertical, and temporal coordinate reference systems (CRSs), following a deep consensus process with GIS science and backwards compatible with EPSG. The ESRI "Geoservice REST API" specific way of handling coordinates is not known to support this, thereby excluding appropriate timeseries handling in remote sensing, air traffic, MetOcean, etc.
*** OGC coverages provide a concise, versatile model for supporting different binary formats; the ESRI "Geoservice REST API" supports only very few selected 2-D formats, excluding, e.g., JPEG2000, NetCDF, HDF, etc.
*** the ESRI "Geoservice REST API" lacks a clear model of their data structures, it can be deduced only implicitly from the operation mechanics.
** service model:
*** The ESRI "Geoservice REST API" Part 6 lacks conciseness, thereby opening up ways for implementations that are not interoperable. For developers of alternative implementations this may mean they have to acquire ESRI licenses for finding out the intended behavior.
*** Functionality in the ESRI "Geoservice REST API" appears randomly chosen, with no clear concept visible; this burdens implementers while still leaving holes of functionality. For example, this functionality appears restricted to mapping applications and does not easily extend into other domains.
*** It has been said that the ESRI "Geoservice REST API" can be seen as a "wrapper around OGC W*S" services. This is not true for WCS (and WCPS), at least: the ESRI "Geoservice REST API" Part 6 is too poor in functionality and too different in mechanics to accomplish this.
** In summary, the ESRI "Geoservice REST API" Imaging part is at a technological level where WCS departed from some 5 years ago. Inconciseness of the specification at large will make it difficult for third parties to come up with interoperable implementations. Therefore, Part 6 of the ESRI "Geoservice REST API", if to become a standard, needs to be discussed in the WCS.SWG for harmonization, clarification, and improvement.

== Methodological Concerns ==

* No public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
* The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.
* OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.
* ESRI/OGC have specifically [http://lists.osgeo.org/pipermail/discuss/2013-May/011659.html rejected requests] to openly share their justifications document being selectively sent to OGC voters.

= History =

Todo: please expand
* Explain how this standard came to be
* Based on ArcGIS Server API
* Attempted but failed to go through OGC fast track process
* Recent voting history: refer to: http://lists.osgeo.org/pipermail/discuss/2013-May/011602.html

= References =
Todo: Link to key external docs, such as the proposed standards

[[Category: OGC]]
[[Category: Standards]]

Geoservices REST API

2013-05-09T12:52:02Z

Wiki-Sfkeller: /* Signed */

This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard. It is being collaboratively edited, targeting completion before the end of May 2013.

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go below.''

May 2013

We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.

We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.

People have listed different reasons for concern. They are described below.

== Signed ==
''Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.''

* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live]
* [[Mark Lucas]], Founding member and board of directors for OSGeo foundation, Prinicipal Scientist for RadiantBlue Technologies Inc.
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
* [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]
* Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]
* [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member
* [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]
* [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]
* [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.
* [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.
* [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.
* [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.
* Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client
* [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.
* [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.
* [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter
* [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Italy
* [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain
* [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain
* [[User:Fsteggink|Frank Steggink]], GIS software developer at [http://www.vicrea.nl Vicrea], The Netherlands, member of the Dutch Local Chapter
* [[User:Olivier.courtin|Olivier Courtin]], [http://www.oslandia.com Oslandia] co-founder, core contributor or/and PSC member of [http://mapserver.org Mapserver] and [http://www.postgis.org/ PostGIS]. OGC TC member.
* [[User:Bolosig|Wladimir Szczerban]], OSGeo Spanish Local Chapter Member, Spain
* [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member.
* [[User:Vmische|Volker Mische]], geospatial software engineer, creator of GeoCouch
* [[User:Ivansanchez|Iván Sánchez]], OSGeo Spanish Local Chapter Member, head of [http://www.openstreetmap.es OpenStreetMap Spain], [http://osmfoundation.org OpenStreetMap Foundation] member, [http://hot.openstreetmap.org/ Humanitarian OpenStreetMap Team] member, [http://www.idee.es/ Spanish SDI working group] member
* [[User:Gabi|Gabriel Carrión]], Strategy Manager at [http://www.gvsig.com gvSIG association]
* [http://strk.keybit.net Sandro Santilli], OSGeo Charter Member, [http://postgis.net PostGIS] and [http://trac.osgeo.org/geos GEOS] PSC member and core hacker.
* [[User:Javiarch|Javier Diaz]], member of Geoinquietos Bs As [http://wiki.osgeo.org/wiki/Category:Geoinquietos_Buenos_Aires], member of the Organizing Committee FOSS4G Bs As 2013 [http://www.foss4g-ba.org/]
* [[User: JoCook|Jo Cook]], Consultant at [http://isharemaps.com| Astun Technology], former Director of OSGeo, Charter Member, founder of UK Local Chapter, Deputy Chair of [http://2013.foss4g.org| FOSS4G 2013]
* [[User: Fpenarru | Francisco José Peñarrubia]], CTO and co-founder at [http://www.scolab.es SCOLAB]. Members of [http://www.gvsig.com gvSIG Association]
* [[User: Ganesh|Shanmugam Ganeshkumar]], Director of [http://www.geoicon.com GeoICON], member OSGeo Malaysia Chapter
* [[User:Barryrowlingson|Barry Rowlingson]], Senior Researcher, Lancaster University and Software Sustainability Institute Fellow
* [[User: Sfkeller|Stefan Keller]], University of Applied Sciences, Rapperswil (Switzerland), Member of Swiss OSM (SOSM) and QGIS association and of organizing committees of pgConf.DE and FOSSGIS 2013

= Concerns =
--- DRAFT ____

''Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)''

== Summary ==
As at May 2013, OGC members have been asked to decide whether to accept the "GeoServices REST API" as an OGC standard. This is a contentious issue, with many people arguing that introduction of the “GeoServices REST API” will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC's reputation as a champion of interoperability.

The key points of contention revolve around the fact that the proposed "GeoServices REST API" does not build upon or extend existing OGC standards, but rather addresses similar requirements using an alternative API. In particular, the overlap and/or duplication of existing standards is widespread: OGC's core standards of WMS, WMTS, WFS, SE/SLD, WCS, CS/W are all duplicated to a significant extent. This defeats the purpose of having standards in the first place.

Duplication of standards will likely result in a combination of the following:
# The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.
# Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.
# Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.
# This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.
# After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.
# One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation. Backward compatibility to the existing WxS standards is important in this respect.
# Given backwards compatibility with the ESRI Restful implementation is mandated, this is not an Open Standard, and should not be ratified as if it was.

== Political Concerns ==

* Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.
* It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a newcomer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?

== Commercial Concerns ==

* Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.
* Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.
* Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.
* Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.

== Technical Concerns ==

* The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment] for more details on this issue.
* The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.
* At least as far as "imagery" is concerned, OGC standards arguably are substantially more mature, powerful, flexible, and modular then the ESRI "Geoservice REST API" Part 6 (and some design principles suggest that scalability may be hampered as well):
** data model:
*** the ESRI "Geoservice REST API" appears constrained to 2-D imagery, plus optional time stamps. OGC has established a [http://en.wikipedia.org/wiki/Coverage_data unified coverage model] which fully supports n-D spatio-temporal data. It allows use and exchange of coverages between different services, such as [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS], [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS], WPS, and SWE.
*** OGC coverages support both regular and irregular grids; the ESRI "Geoservice REST API" supports only regular grids, more specifically: only rectified grids with quadrilateral pixels.
*** the ESRI "Geoservice REST API" lacks support for temporal data; it only offers timestamps, measured in milliseconds; this is inconvenient for users and immediately excludes, e.g., geological dates. OGC has established uniform handling of horizontal, vertical, and temporal coordinate reference systems (CRSs), following a deep consensus process with GIS science and backwards compatible with EPSG. The ESRI "Geoservice REST API" specific way of handling coordinates is not known to support this, thereby excluding appropriate timeseries handling in remote sensing, air traffic, MetOcean, etc.
*** OGC coverages provide a concise, versatile model for supporting different binary formats; the ESRI "Geoservice REST API" supports only very few selected 2-D formats, excluding, e.g., JPEG2000, NetCDF, HDF, etc.
*** the ESRI "Geoservice REST API" lacks a clear model of their data structures, it can be deduced only implicitly from the operation mechanics.
** service model:
*** The ESRI "Geoservice REST API" Part 6 lacks conciseness, thereby opening up ways for implementations that are not interoperable. For developers of alternative implementations this may mean they have to acquire ESRI licenses for finding out the intended behavior.
*** Functionality in the ESRI "Geoservice REST API" appears randomly chosen, with no clear concept visible; this burdens implementers while still leaving holes of functionality. For example, this functionality appears restricted to mapping applications and does not easily extend into other domains.
*** It has been said that the ESRI "Geoservice REST API" can be seen as a "wrapper around OGC W*S" services. This is not true for WCS (and WCPS), at least: the ESRI "Geoservice REST API" Part 6 is too poor in functionality and too different in mechanics to accomplish this.
** In summary, the ESRI "Geoservice REST API" Imaging part is at a technological level where WCS departed from some 5 years ago. Inconciseness of the specification at large will make it difficult for third parties to come up with interoperable implementations. Therefore, Part 6 of the ESRI "Geoservice REST API", if to become a standard, needs to be discussed in the WCS.SWG for harmonization, clarification, and improvement.

== Methodological Concerns ==

* No public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
* The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.
* OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.
* ESRI/OGC have specifically [http://lists.osgeo.org/pipermail/discuss/2013-May/011659.html rejected requests] to openly share their justifications document being selectively sent to OGC voters.

= History =

Todo: please expand
* Explain how this standard came to be
* Based on ArcGIS Server API
* Attempted but failed to go through OGC fast track process
* Recent voting history: refer to: http://lists.osgeo.org/pipermail/discuss/2013-May/011602.html

= References =
Todo: Link to key external docs, such as the proposed standards

[[Category: OGC]]
[[Category: Standards]]

FOSS4G 2010 Breakout Sessions

2010-09-13T09:14:54Z

Wiki-Sfkeller: /* QGIS user & developer meeting */

[[Category:FOSS4G]]
[[Category:FOSS4G2010]]

back to [[FOSS4G 2010]]

= Introduction =
During the [http://2010.foss4g.org/ FOSS4G2010 conference] in Barcelona, Spain, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

This year, Breakout Sessions sessions will be held on Wednesday 8th September ('''and possibly at other times as well - depending on interest'''). A number of rooms will be available. Most popular sessions will get bigger rooms.

'''Room allocation to be determined'''

==Organising Contact==
* [[Tyler Mitchell]]
* [[Mauricio Miranda]]
* Other volunteers welcome - sign up here!

==Timeslots Available==

At this stage, each room is scheduled for one hour between 18:00 to 19:00.

Remember the Gala Dinner is scheduled at 20:00.

=Room Assignments=
== Rooms Available ==

We will need to share the biggest rooms because we have more sessions than rooms.

Add your name to the "Moderator" column if you feel as a session's leader.

Please, contact us to ask for changes.

{| class="wikitable" border="1"
|-
! width="120" | Room
! width="250" | Tuesday 07
! width="250" | Wednesday 08
! width="300" | Moderator
|-
| Room 3
|
*Flex Mapping (Alternatives to HTML)
|
|
Sébastien Deleuze
|-
| Room 4 (75 pax)
|
|
*QGIS user & developer meeting
*Tiling meeting
|
|-
| Room 5 (250 pax)
|
|
*Spatial Data Infrastructure
*Virtualization and Cloud Computing BoF
*Java GeoSpatial

|
|-
| Room 6 (320 pax)
|
|
*Sensor Web BoF
*Biodiversity/conservation projects and FOSS4G tools
*Spatial OLAP

|
*Simon Jirka
*Javier de la Torre 
*-

|-
| Room 8 (100 pax)
|
|
*Web Client (OpenLayers/GeoExt)

|
|-
| Room 11 (78 pax)
|
|
*WPS BoF

|
*Bastian Schäffer
|-
| Room 12 (90 pax)
|
|
*Spatial Databases BoF

|
|}

= Proposed Topics =

* Add yours below...

==Web Client (OpenLayers/GeoExt)==

The first half of this session will be focused on OpenLayers, and the second half will focus on GeoExt. We can decide on topics at the start of each session, but we'll likely cover ideas for OpenLayers 3.0/GeoExt 1.0, getting more developers involved, and just some general Q/A time.

'''Coming:'''

* Tim Schaub
* Eric Lemoine
* Frédéric Junod
* David Jonglez - for the first half, at least
* Florin Iosub
* Xurxo Méndez
* [[Ricardo Pinho|Ricardo Pinho]] (depending on the schedule)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Hugo Pereira
* [[Just van den Broecke|Just van den Broecke]]
* Simon Lopez
* Richard Greenwood
* Andreas Hocevar
* Volker Grabsch
* Matthias Pohl
* Kris Geusebroek - for the first (OpenLayers) half at least
* Jeroen van Wilgenburg
* Edwin Commandeur
* Cédric Moullet
* Julien-Samuel Lacroix
* Pierre Giraud
* Sébastien Deleuze
* Add your name here

(promised link should go here - but all changes are gone due to session timeout)

==Spatial Databases BoF==

Relational and non-relational persistence layers, let's get together and talk about interoperability, appropriate use cases, architecture and where we should be moving the spatial persistence state-of-the-art!

'''Coming:'''

* Paul Ramsey (PostGIS)
* Nicklas Avén (PostGIS)
* Brent Wood (NIWA)
* Peter Baumann (Jacobs University / rasdaman)
* Vincent Picavet (Oslandia/PostGIS)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Olivier Courtin (PostGIS)
* Hugo Pereira
* Volker Mische (CouchDB/GeoCouch)
* [[user:sebastian.ovide|Sebastián Ovide]]
* [[user:hal_sk | Haruyuki Seki]]
* [[user:aross | Andrew Ross]] (Ingres)
* Alex Trofast (Ingres)
* Paolo Corti
* Add your name here

==WPS BoF==

Several presentation on Web Processing selected
for presentation at FOSS4G2010 indicates a growing
interest amongst the communities.

If you are interested please add your names below...

'''Who's coming:'''

* Venkatesh Raghavan
* [[Markus Neteler]]
* [[Daniel Kastl]]
* Maria Brovelli
* [[Ian Turton]]
* [[Gerald Fenoy]]
* Nicolas Bozon
* [[Jody Garnett]]
* [[User:fpenarru | Fran Peñarrubia]]
* [[User:MarkusSchneider | Markus Schneider]]
* Luca Delucchi
* Milan Antonovic
* [[User:Maxi71 | Massimiliano cannata]]
* Luca Casagrande
* [[User:Rajsingh| Raj Singh ]]
* [[User:Jesus|Jorge de Jesus]] (Plymouth Marine Laboratory)
* Bertrand Gervais
* [[User:Schpidi | Stephan Meissl]]
* [[Sebastián Cruz|Sebastián Cruz]]
* Fernando González
* Víctor González
* Bastian Schäffer
* Add your name here

==Sensor Web BoF==

The use of Sensor Web implementations has constantly increased during the last years.

If you are interested please add your names below...

'''Who's coming:'''

* Simon Jirka
* Marjorie Robert
* [[User:Maxi71 | Massimiliano cannata]]
* Graeme Mcferren
* Sarawut Ninsawat
* Brent Wood (NIWA)
* Jorge Piera
* Alain Tamayo
* Maria Brovelli
* Add your name here

==Biodiversity/conservation projects and FOSS4G tools==

More and more Open Source is catching on Biodiversity and conservation projects. Most of them are publicly funded so most of the time all the source they develop is Open Source. Aditionally Biodiversity and conservation heavily rely on GIS and they have specific needs. From geospatial niche modeling to species distributions, occurrence catalog, etc, there is a lot to talk about!

If you are interested please add your names below...

'''Coming:'''

* Javier de la Torre (Vizzuality)
* Brent Wood (NIWA)
* [[Markus Neteler]]
* [[User:jesus| Jorge de Jesus]] (Plymouth Marine Laboratory)
* [[User:Aghisla|Anne Ghisla]]
* Andrew W Hill (University of Colorado, Boulder)
* Add your name here

==Spatial Data Infrastructure==

A birds of a feather session about using open source for spatial data infrastructure. Come discuss implementation strategies, best practices, INSPIRE.

'''Who's coming:'''

* Sebastian Benthall (GeoNode)
* David Winslow (GeoNode)
* Ariel Núñez (GeoNode)
* David Jonglez
* [[Ricardo Pinho|Ricardo Pinho]] (depending on the schedule)
* Hugo Pereira
* Maria Brovelli
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Virtualization and Cloud Computing BoF==

Virtualization and Cloud Computing is growing fast on the GIS world, let's get together and talk about the use cases and share opinions and suggestions about how can we take the most out of this new technology!

If you are interested please add your name below...

'''Coming:'''
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Cédric Moullet
* Add your name here

==Spatial OLAP==

Spatial OLAP can be defined as a visual platform built especially to support rapid and easy spatiotemporal analysis and exploration of data following a multidimensional approach comprised of aggregation levels available in cartographic displays as well as in tabular and diagram displays. Let's talk about new improvements combining GIS and BI technologies.

If you are interested please add your name below...

'''Coming:'''
* [[Nuno Guerreiro|Nuno Guerreiro]]
* [[User:Rajsingh| Raj Singh ]]
* Add your name here

==Flex Mapping (Alternatives to HTML)==

Flex is a highly productive, free, open source framework for building expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.
OpenScales is an open source (LGPL) mapping framework written in ActionScript 3 and Flex that allows developers to building Rich Internet Mapping Applications.
There are alternatives to HTML mapping, let's discuss about them...

'''Report'''

Attendees :
* Sébastien Deleuze (Atos Worldline) - OpenScales lead developer
* Simon Lopez (Atos Worldline) - OpenScales core developer
* Claude Philipona (Camptocamp)
* Eric Lemoine (Camptocamp) - OL core developer
* David Jonglez (Capgemini)
* Vincent Heurteau (Geomatys) - GeoAPI core developer
* Sebastián Cruz (Xoomcode)
* [[Mauricio Miranda]] (Xoomcode)
* Fabio Panettieri (Xoomcode)
* Javier de la Torre (Vizzuality)

Discussions :
* Sébastien presented us the 1.2 and 2.0 OpenScales RoadMaps. Lots of interesting stuff : 3D, Mobile, ...
* David presented a prototype of Flash/Flex Mapping API build on the basis of asGeoAPI (Didier Richard work), OpenScales and Openzoom.
* David and Mauricio exposed their wish to put the project under incubation within OSGeo process.
* Sébastien agreed with the idea to open the gouvernance (on a meritocracy basis) but he should check this other people implied in such decision
* David asked if OpenLayers community could coach OpenScales community in this incubation process in order to manage the interest of the different competitors around the table.
* David propose to share Capgemini prototype as soon as Atos Worldline confirms its wish to initiate the OSGeo incubation process and to open the governance of the project.

Decisions :
I notice 2 decisions :
* First, Sebastien have to come back with the decision of his hierarchy to inform the community of t
* Second, asking OpenLayers community to coach OpenScales in the OSGeo incubation

You can check Sébastien answer here : http://groups.google.com/group/openscales-dev/msg/20963a67a6f63077

==QGIS user & developer meeting==

Topics:
* What's new in QGIS 1.5
* Interesting plugins
* What's coming in the next QGIS release
* Discussion

If you are interested please add your name below...

'''Coming:'''
* Marco Hugentobler
* [[User:Pirmin_Kalberer| Pirmin Kalberer]]
* Mathias Walker
* [[User:Vasile| Vasile Crăciunescu]]
* [[User:Lmotta| Luiz Motta]]
* Richard Duivenvoorde
* [[User:hdus | Horst Düster]]
* [[User:yoichi | Yoichi Kayama]]
* Nobusuke Iwasaki
* [[Milena Nowotarska | Milena Nowotarska]]
* [[User:antonys | Antony Scott]]
* [[User:Sfkeller | Stefan Keller]]
* Add your name here

== Java GeoSpatial (GeoTools, GeoServer, uDig, etc...) ==

Topics:

If you are a user or developer in the "Java Tribe" come check out this BOF. You can let the developers know what you like, what you don't like, and what sorts of features and developments you would like to see in the future.

'''Coming:'''

* [[User:jdeolive | Justin Deoliveira]]
* [[User:cholmes | Chris Holmes]]
* Add your name here

==Tiling meeting==

At the moment we're next to room 5 in the working area. Just follow Chris Schmidt.

Topics:
* current state of tiling implementations
* future of our implementations

'''Coming:'''

* [[User:stvn | Steven Ottens]]
* [[User:pauldendulk | Paul den Dulk]]

User:Sfkeller

2010-09-13T09:14:21Z

Wiki-Sfkeller:

>> http://wiki.hsr.ch/StefanKeller/wiki.cgi?LabsGeometaInfo <<

FOSS4G 2010 Breakout Sessions

2010-09-13T09:13:00Z

Wiki-Sfkeller: /* QGIS user & developer meeting */

[[Category:FOSS4G]]
[[Category:FOSS4G2010]]

back to [[FOSS4G 2010]]

= Introduction =
During the [http://2010.foss4g.org/ FOSS4G2010 conference] in Barcelona, Spain, there will be conference rooms available for people to hold Breakout Sessions (aka Birds-of-a-Feather).

Breakout Sessions sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

This year, Breakout Sessions sessions will be held on Wednesday 8th September ('''and possibly at other times as well - depending on interest'''). A number of rooms will be available. Most popular sessions will get bigger rooms.

'''Room allocation to be determined'''

==Organising Contact==
* [[Tyler Mitchell]]
* [[Mauricio Miranda]]
* Other volunteers welcome - sign up here!

==Timeslots Available==

At this stage, each room is scheduled for one hour between 18:00 to 19:00.

Remember the Gala Dinner is scheduled at 20:00.

=Room Assignments=
== Rooms Available ==

We will need to share the biggest rooms because we have more sessions than rooms.

Add your name to the "Moderator" column if you feel as a session's leader.

Please, contact us to ask for changes.

{| class="wikitable" border="1"
|-
! width="120" | Room
! width="250" | Tuesday 07
! width="250" | Wednesday 08
! width="300" | Moderator
|-
| Room 3
|
*Flex Mapping (Alternatives to HTML)
|
|
Sébastien Deleuze
|-
| Room 4 (75 pax)
|
|
*QGIS user & developer meeting
*Tiling meeting
|
|-
| Room 5 (250 pax)
|
|
*Spatial Data Infrastructure
*Virtualization and Cloud Computing BoF
*Java GeoSpatial

|
|-
| Room 6 (320 pax)
|
|
*Sensor Web BoF
*Biodiversity/conservation projects and FOSS4G tools
*Spatial OLAP

|
*Simon Jirka
*Javier de la Torre 
*-

|-
| Room 8 (100 pax)
|
|
*Web Client (OpenLayers/GeoExt)

|
|-
| Room 11 (78 pax)
|
|
*WPS BoF

|
*Bastian Schäffer
|-
| Room 12 (90 pax)
|
|
*Spatial Databases BoF

|
|}

= Proposed Topics =

* Add yours below...

==Web Client (OpenLayers/GeoExt)==

The first half of this session will be focused on OpenLayers, and the second half will focus on GeoExt. We can decide on topics at the start of each session, but we'll likely cover ideas for OpenLayers 3.0/GeoExt 1.0, getting more developers involved, and just some general Q/A time.

'''Coming:'''

* Tim Schaub
* Eric Lemoine
* Frédéric Junod
* David Jonglez - for the first half, at least
* Florin Iosub
* Xurxo Méndez
* [[Ricardo Pinho|Ricardo Pinho]] (depending on the schedule)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Hugo Pereira
* [[Just van den Broecke|Just van den Broecke]]
* Simon Lopez
* Richard Greenwood
* Andreas Hocevar
* Volker Grabsch
* Matthias Pohl
* Kris Geusebroek - for the first (OpenLayers) half at least
* Jeroen van Wilgenburg
* Edwin Commandeur
* Cédric Moullet
* Julien-Samuel Lacroix
* Pierre Giraud
* Sébastien Deleuze
* Add your name here

(promised link should go here - but all changes are gone due to session timeout)

==Spatial Databases BoF==

Relational and non-relational persistence layers, let's get together and talk about interoperability, appropriate use cases, architecture and where we should be moving the spatial persistence state-of-the-art!

'''Coming:'''

* Paul Ramsey (PostGIS)
* Nicklas Avén (PostGIS)
* Brent Wood (NIWA)
* Peter Baumann (Jacobs University / rasdaman)
* Vincent Picavet (Oslandia/PostGIS)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Olivier Courtin (PostGIS)
* Hugo Pereira
* Volker Mische (CouchDB/GeoCouch)
* [[user:sebastian.ovide|Sebastián Ovide]]
* [[user:hal_sk | Haruyuki Seki]]
* [[user:aross | Andrew Ross]] (Ingres)
* Alex Trofast (Ingres)
* Paolo Corti
* Add your name here

==WPS BoF==

Several presentation on Web Processing selected
for presentation at FOSS4G2010 indicates a growing
interest amongst the communities.

If you are interested please add your names below...

'''Who's coming:'''

* Venkatesh Raghavan
* [[Markus Neteler]]
* [[Daniel Kastl]]
* Maria Brovelli
* [[Ian Turton]]
* [[Gerald Fenoy]]
* Nicolas Bozon
* [[Jody Garnett]]
* [[User:fpenarru | Fran Peñarrubia]]
* [[User:MarkusSchneider | Markus Schneider]]
* Luca Delucchi
* Milan Antonovic
* [[User:Maxi71 | Massimiliano cannata]]
* Luca Casagrande
* [[User:Rajsingh| Raj Singh ]]
* [[User:Jesus|Jorge de Jesus]] (Plymouth Marine Laboratory)
* Bertrand Gervais
* [[User:Schpidi | Stephan Meissl]]
* [[Sebastián Cruz|Sebastián Cruz]]
* Fernando González
* Víctor González
* Bastian Schäffer
* Add your name here

==Sensor Web BoF==

The use of Sensor Web implementations has constantly increased during the last years.

If you are interested please add your names below...

'''Who's coming:'''

* Simon Jirka
* Marjorie Robert
* [[User:Maxi71 | Massimiliano cannata]]
* Graeme Mcferren
* Sarawut Ninsawat
* Brent Wood (NIWA)
* Jorge Piera
* Alain Tamayo
* Maria Brovelli
* Add your name here

==Biodiversity/conservation projects and FOSS4G tools==

More and more Open Source is catching on Biodiversity and conservation projects. Most of them are publicly funded so most of the time all the source they develop is Open Source. Aditionally Biodiversity and conservation heavily rely on GIS and they have specific needs. From geospatial niche modeling to species distributions, occurrence catalog, etc, there is a lot to talk about!

If you are interested please add your names below...

'''Coming:'''

* Javier de la Torre (Vizzuality)
* Brent Wood (NIWA)
* [[Markus Neteler]]
* [[User:jesus| Jorge de Jesus]] (Plymouth Marine Laboratory)
* [[User:Aghisla|Anne Ghisla]]
* Andrew W Hill (University of Colorado, Boulder)
* Add your name here

==Spatial Data Infrastructure==

A birds of a feather session about using open source for spatial data infrastructure. Come discuss implementation strategies, best practices, INSPIRE.

'''Who's coming:'''

* Sebastian Benthall (GeoNode)
* David Winslow (GeoNode)
* Ariel Núñez (GeoNode)
* David Jonglez
* [[Ricardo Pinho|Ricardo Pinho]] (depending on the schedule)
* Hugo Pereira
* Maria Brovelli
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Add your name here

==Virtualization and Cloud Computing BoF==

Virtualization and Cloud Computing is growing fast on the GIS world, let's get together and talk about the use cases and share opinions and suggestions about how can we take the most out of this new technology!

If you are interested please add your name below...

'''Coming:'''
* [[Ricardo Pinho|Ricardo Pinho]]
* Hugo Pereira
* [[Sebastián Cruz|Sebastián Cruz]]
* [[user:sebastian.ovide|Sebastián Ovide]]
* Cédric Moullet
* Add your name here

==Spatial OLAP==

Spatial OLAP can be defined as a visual platform built especially to support rapid and easy spatiotemporal analysis and exploration of data following a multidimensional approach comprised of aggregation levels available in cartographic displays as well as in tabular and diagram displays. Let's talk about new improvements combining GIS and BI technologies.

If you are interested please add your name below...

'''Coming:'''
* [[Nuno Guerreiro|Nuno Guerreiro]]
* [[User:Rajsingh| Raj Singh ]]
* Add your name here

==Flex Mapping (Alternatives to HTML)==

Flex is a highly productive, free, open source framework for building expressive web applications that deploy consistently on all major browsers, desktops, and operating systems.
OpenScales is an open source (LGPL) mapping framework written in ActionScript 3 and Flex that allows developers to building Rich Internet Mapping Applications.
There are alternatives to HTML mapping, let's discuss about them...

'''Report'''

Attendees :
* Sébastien Deleuze (Atos Worldline) - OpenScales lead developer
* Simon Lopez (Atos Worldline) - OpenScales core developer
* Claude Philipona (Camptocamp)
* Eric Lemoine (Camptocamp) - OL core developer
* David Jonglez (Capgemini)
* Vincent Heurteau (Geomatys) - GeoAPI core developer
* Sebastián Cruz (Xoomcode)
* [[Mauricio Miranda]] (Xoomcode)
* Fabio Panettieri (Xoomcode)
* Javier de la Torre (Vizzuality)

Discussions :
* Sébastien presented us the 1.2 and 2.0 OpenScales RoadMaps. Lots of interesting stuff : 3D, Mobile, ...
* David presented a prototype of Flash/Flex Mapping API build on the basis of asGeoAPI (Didier Richard work), OpenScales and Openzoom.
* David and Mauricio exposed their wish to put the project under incubation within OSGeo process.
* Sébastien agreed with the idea to open the gouvernance (on a meritocracy basis) but he should check this other people implied in such decision
* David asked if OpenLayers community could coach OpenScales community in this incubation process in order to manage the interest of the different competitors around the table.
* David propose to share Capgemini prototype as soon as Atos Worldline confirms its wish to initiate the OSGeo incubation process and to open the governance of the project.

Decisions :
I notice 2 decisions :
* First, Sebastien have to come back with the decision of his hierarchy to inform the community of t
* Second, asking OpenLayers community to coach OpenScales in the OSGeo incubation

You can check Sébastien answer here : http://groups.google.com/group/openscales-dev/msg/20963a67a6f63077

==QGIS user & developer meeting==

Topics:
* What's new in QGIS 1.5
* Interesting plugins
* What's coming in the next QGIS release
* Discussion

If you are interested please add your name below...

'''Coming:'''
* Marco Hugentobler
* [[User:Pirmin_Kalberer| Pirmin Kalberer]]
* Mathias Walker
* [[User:Vasile| Vasile Crăciunescu]]
* [[User:Lmotta| Luiz Motta]]
* Richard Duivenvoorde
* [[User:hdus | Horst Düster]]
* [[User:yoichi | Yoichi Kayama]]
* Nobusuke Iwasaki
* [[Milena Nowotarska | Milena Nowotarska]]
* [[User:antonys | Antony Scott]]
* Stefan Keller
* Add your name here

== Java GeoSpatial (GeoTools, GeoServer, uDig, etc...) ==

Topics:

If you are a user or developer in the "Java Tribe" come check out this BOF. You can let the developers know what you like, what you don't like, and what sorts of features and developments you would like to see in the future.

'''Coming:'''

* [[User:jdeolive | Justin Deoliveira]]
* [[User:cholmes | Chris Holmes]]
* Add your name here

==Tiling meeting==

At the moment we're next to room 5 in the working area. Just follow Chris Schmidt.

Topics:
* current state of tiling implementations
* future of our implementations

'''Coming:'''

* [[User:stvn | Steven Ottens]]
* [[User:pauldendulk | Paul den Dulk]]

Geodata Metadata Requirements

2009-07-05T22:18:14Z

Wiki-Sfkeller: /* Webcrawlers perspective or: How to boost your geodata? */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]
* [[ebRIM]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a [[RESTful]] authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a [[RESTful]] request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** (Geo) Sitemaps Protocol including GeoRSS and [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt] (see sitemaps.org)
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also the [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm 'friends' container in OAI-PMH] metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

The following are notes on initial development. [[DCLite4G]] contains details of the finalised model which now has an XML namespace at [http://dclite4g.xmlns.com/ dclite4g.xmlns.com], intended for use in RDF documents though also usable in the context of Atom or KML.

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<pre>
<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>
</pre>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Only '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* [http://www.osgeo.org/geonetwork GeoNetwork opensource] (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/ GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]
* [http://lists.osgeo.org/mailman/listinfo/geodata OSGeo-Geodata Mailing list] (discussion archives, please join the list)

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

* I find it difficult to believe that these "requirements" can be useful without switching their basis from FGDC to ISO-19115. I have posted more extensive comments as Discussion. Please read and comment. -- Bruce

[[Category:Public Geospatial Data Committee]]

[[Category:Standards]]

Geodata Metadata Requirements

2009-07-05T22:17:39Z

Wiki-Sfkeller: /* Webcrawlers perspective or: How to boost your geodata? */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]
* [[ebRIM]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a [[RESTful]] authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a [[RESTful]] request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** (Geo) Sitemaps Protocol including [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt] (see sitemaps.org)
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also the [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm 'friends' container in OAI-PMH] metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

The following are notes on initial development. [[DCLite4G]] contains details of the finalised model which now has an XML namespace at [http://dclite4g.xmlns.com/ dclite4g.xmlns.com], intended for use in RDF documents though also usable in the context of Atom or KML.

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<pre>
<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>
</pre>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Only '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* [http://www.osgeo.org/geonetwork GeoNetwork opensource] (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/ GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]
* [http://lists.osgeo.org/mailman/listinfo/geodata OSGeo-Geodata Mailing list] (discussion archives, please join the list)

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

* I find it difficult to believe that these "requirements" can be useful without switching their basis from FGDC to ISO-19115. I have posted more extensive comments as Discussion. Please read and comment. -- Bruce

[[Category:Public Geospatial Data Committee]]

[[Category:Standards]]

Geodata Metadata Requirements

2009-07-05T22:16:15Z

Wiki-Sfkeller: /* Webcrawlers perspective or: How to boost your geodata? */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]
* [[ebRIM]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a [[RESTful]] authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a [[RESTful]] request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also the [http://www.openarchives.org/OAI/2.0/guidelines-friends.htm 'friends' container in OAI-PMH] metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

The following are notes on initial development. [[DCLite4G]] contains details of the finalised model which now has an XML namespace at [http://dclite4g.xmlns.com/ dclite4g.xmlns.com], intended for use in RDF documents though also usable in the context of Atom or KML.

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<pre>
<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>
</pre>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Only '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* [http://www.osgeo.org/geonetwork GeoNetwork opensource] (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/ GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]
* [http://lists.osgeo.org/mailman/listinfo/geodata OSGeo-Geodata Mailing list] (discussion archives, please join the list)

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

* I find it difficult to believe that these "requirements" can be useful without switching their basis from FGDC to ISO-19115. I have posted more extensive comments as Discussion. Please read and comment. -- Bruce

[[Category:Public Geospatial Data Committee]]

[[Category:Standards]]

D-A-CH

2008-04-11T21:38:07Z

Wiki-Sfkeller: /* Mitgliederliste */

''This is the start page of the German Language Chapter as per [[Local Chapter Guidelines]]''

''Das ist die deutschsprachige Einstiegsseite zur OSGeo Foundation, die zu einer regionalen Gruppe werden könnte wie sie in den [[Local Chapter Guidelines]] beschrieben wird.

== Presse ==

Artikel über die OSGeo (erschienen in der "GIS-Zeitschrift für Geoinformatik", 11/07, S.38-41)

[http://wiki.osgeo.org/images/c/c6/GIS_OSGeo.pdf Download]

== Einführung ==
Bitte tragen Sie sich in die [[Deutsch#Mitgliederliste | Mitgliederliste]] ein, wenn Sie Interesse an einem deutschsprachigen [[Local Chapters]] haben. Der Eintrag ist freiwillig, dieses Wiki und alle enthaltenen Informationen sind öffentlich sichtbar. Die Kommunikation erfolgt über die [http://lists.osgeo.org/mailman/listinfo/viscom-discuss-de Mailing-Liste discuss-de] ([http://lists.osgeo.org/pipermail/viscom-discuss-de/ Archiv]) oder dieses Wiki.
Eingeladen an dem deutschsprachigen Local Chapter mitzuwirken sind ausdrücklich alle Interessierten, völlig unabhängig davon ob Anwender oder Entwickler, völlig unabhängig davon ob erfahren im Umgang mit OS-GIS-Software oder "Neuling". Die OSGeo lebt von der Beteiligung jedes Einzelnen, jeder Beitrag ist willkommen.

== Unser Name ==
Wir brauchen einen offiziellen Namen für die deutschsprachige Gruppe der OSGe, Vorschläge:
* OSGeo DACH

Der Begriff der "Foundation" lässt sich ebenfalls nicht gut [http://dict.leo.org/ende?lp=ende&lang=de&searchLoc=0&cmpType=relaxed&sectHdr=on&spellToler=on&search=Foundation&relink=on direkt übersetzen], in vielen Dokumenten ist deshalb von der "OSGeo Foundation" zu lesen, was allerdings gegen die Vorgaben zur Nutzung des OSGeo Logo und Markennamen geht.

== Rechtsform, Konto ==
Die OSGeo Foundation ist als non-profit Firma in Delaware, USA gegründet worden. Dort gibt es auch ein Konto und wird das Budget verwaltet. Für formale Arbeiten und als zentrale Anlaufstelle für Fragen rund um die OSGeo wurde Tyler Mitchell als Executive Director angestellt, seine Stelle wird auch aus diesem Budget finanziert. Unabhängig davon werden wir nationale Konten benötigen, da die Transferkosten und der Aufwand, Geld über internationale Grenzen zu transportieren, nach wie vor unsinnig ist.

In Deutschland gibt es bereits ein Netzwerk und Organisation für die Förderung Freier Software. Die GAV e.V. (GRASS Anwender-Vereinigung) ist eine formale Organisation der Rechtsform "eingetragener Verein", die bereits seit 1999 die gleichen Ziele verfolgt wie die OSGeo. Der GAV und OSGeo sind im Gespräch, wie eine Kooperation gestaltet werden kann. Eine erste, pragmatische Kooperation betrifft die Überschüsse der letzten FOSSGIS-Konferenzen, die das Organisationsteam zweckgebunden an den GAV e.V. gespendet hat. Bei Konferenzen und zu Marketing-Zwecken der OSGeo auf Messen im deutschsprachigen Raum konnte dieser Überschuß bereits sinnvoll genutzt werden, z.B. um den Druck von Informationsmaterial zu finanzieren.
* [http://www.grass-verein.de/ GAV] (GRASS Anwender-Vereinigung e.V.)
* [http://www.fossgis.de FOSSGIS.de] (Organisationsteam der FOSSGIS-Konferenzen)

== Ziele ==
Die Ziele der deutschsprachigen OSGeo Arbeitsgruppe entwickeln sich durch die Beiträge der Mitglieder. Eine erste Orientierung geben die [[Local Chapter Guidelines | Richtlinien für lokale Gruppen]], einzelne Schwerpunkte werden sich im Laufe der Arbeit herauskristallisieren.
* Bereitstellung eines Netzwerkes für die Mitglieder, ggf. mit Job-Börse.
* Organisation der jährlichen deutschsprachigen Konferenz (siehe [[FOSSGIS 2006]])
* Kontaktstelle für neue Mitglieder und Sponsoren
* Führung eines Regionalbüros mit Konto, Telefon, Ansprechpartner
* Übersetzung von Dokumenten, Inhalten, Webseiten und Lokalisierung von Software (Anpassung an örtliche Besonderheiten)
* Lösungen im deutschsprachigen Raum bewerben
* Erstellung von regionalisierten Software-Paketen
* Training, Support und Entwicklung von e-Learning Inhalten in deutscher Sprache
* Förderung von offenen Standards und freien Zugang zu räumlichen Daten im deutschsprachigen Umfeld.
* Förderung der OSGeo Foundation durch Präsentationen, Informationsveranstaltungen, Messestände, etc.

== Komitees ==

An dieser Stelle folgen nach und nach die Komitees der deutschsprachigen OSGeo Gemeinschaft. Fühlen Sie sich frei selber ein Komitee zu gründen oder sich einem bestehenden anzuschließen.

* [[Komitee für Bildung und Dokumentationserstellung | Komitee für Bildung und Dokumentationserstellung]]

== Kommunikation ==
Die Kommunikaiton läuft über dieses Wiki, Mailing Listen, Webseite und natürlich das persönliche Gespräch auf Messen, Konferenzen und Anwendertreffen. Das neue OSGeo Portal bietet eine einfache Möglichkeit zur Übersetzung ins Deutsche. Falls Sie bei der Übersetzung gerne helfen möchten wenden Sie sich bitte an die Translation Group des [[WebCom | Website Committee]].

Zur Zeit gibt es die folgenden Mailinglisten, auf denen vornehmlich in deutscher Sprache kommuniziert wird:

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"
|viscom-discuss-de@lists.osgeo.org
|Ursprünglich Diskussionsliste des D-A-CH 'visibilitiy-commitees'. Gedacht als offene Liste zur Diskussion von allgemeinen Belangen. Orginsation von Messe-Auftritten wie Linux-Tag, OpenSource-Park der Intergeo. Aktuell wird eine Umbenunnung der Liste in einen sprechenderen Namen diskutiert -> DACH@@lists.osgeo.org, fossgis@lists.osgeo.org, fossgis-poeüple@lists.osgeo.org, .... )
|-
|gav-talk@grass-verein.de
|öffentlich Diskussionsliste der GRASS Anwendervereinigung (?)
|-
|mapserver-de@freegis.org
|techn. Fragen zum UMN MapServer
|-
|nas@lists.osgeo.org
|techn. und organisatorische Liste zum Thema Schaffung einer Freien NAS-Schnittstelle.
|-
|grass-de@grass-verein.de
|Auf dieser Liste schreiben die Mitglieder der deutschsprachigen GRASS Anwender-Vereinigung e.V. (GAV).
|-
|fossgis@freegis.org
|Mehr oder weniger geschlossene Liste des Orga-Teams der FOSSGIS zur Vorbereitung der Konferenzen. Wer sich beteiligen möchte meldet sich auf der Liste, eigenständige Anmeldung ist nicht möglich.
|-
|
|
|}

== Steuerung ==
Die deutschprachige Gruppe der OSGeo ist noch informell. Beteiligen Sie sich an der Gestaltung, indem Sie sich einbringen. Entscheidungen werden wie bei Open Source üblich per Email an die Mailing Liste geschickt und diskutiert. Beschlussfähige Vorschläge werden von einem Mitglied vorgeschlagen und von einem zweiten Mitglied unterstützt.

=== Wahl ===
Die Wahl erfolgt über Ablehung, Zustimmung oder Gleichgültigkeit:
-1 = Veto, Ablehung
-0 = nicht einverstanden, beugt sich aber der Mehrheit
0 = trägt die Entscheidung der anderen mit, kann aber nicht beurteilen, ob sie gut ist (zu wenig Information, keine Zeit sich zu informieren, etc.)
+0 = unterstützt den Antrag passiv, kann aber nicht aktiv zum Thema beisteuern
+1 = Zustimmung, unterstützt den Antrag voll und arbeitet auch mit

=== Veto ===
Wer mit -1 wählt legt ein Veto ein. Damit das Veto angenommen werden kann muss es innerhalb der Wahlfrist begründet und am besten gleich mit einem Alternativvorschlag eingebracht werden.

=== Unterstützung ===
Wer mit +1 wählt muss auch bereit sein aktiv mit der Lösung mitzumachen. Sonst gibt es zu viele faule Beobachter und zu wenige Arbeiter.

=== Veto überstimmen ===
Ein Veto kann überstimmt werden
* durch eine absolute Mehrheit der Mitglieder
* oder wenn mindestens vier Mitglieder mit einer +1 wählen.

Alle Ergebnis können immer angefochten werden (bis uns was besseres einfällt).

== Offizieller Status und Dokumente ==
Die OSGeo Foundation ist eine rechtliche Organisation die aus mittlerweile 59 Mitgliedern und 9 Direktoren besteht. Alle offiziellen Projekte und Dokumente müssen von dem Direktorium abgenommen werden bevor sie offiziellen Status erreichen. Offizielle Dokumente werden in den statischen Dokumenten-Ordner auf osgeo.org hinterlegt und werden dadurch "Official Policy" der OSGeo Foundation. Sobald die Mitgliederliste 10 bis 15 Einträge hat, die sich aktiv einbringen wollen, können wir einen Antrag auf einen eigenen Projektbereich mit Dokumentenordner, SVN, Webseite, etc. und offiziellem Status beantragen. Im deutschsprachigen [http://www.fossgis.de/wiki FOSSGIS Konferenz Wiki] finden Sie ebenfalls eine Vielzahl von Präsentationen und Unterlagen.

Die Sammlung deutschsprachiger Dokumente ist der Migration zum Opfer gefallen, wird aber nach und nach wieder aufgebaut. Falls Sie selbst Dokumente beisteuern können wenden Sie dich bitte an das [[Marketing Committee]].
* [[Intern: Entwurf Artikel GIS BUSINESS | ]]

== Weitere Wiki-Seiten zu regionalen (''local'') Themen und Veranstaltungen ==
* [http://wiki.osgeo.org/index.php/Deutsch/NAS Entwicklung freier NAS-Schnittstelle]
* [http://wiki.osgeo.org/index.php/LinuxTag_2007 LinuxTag 2007]
* [[AGIT_2007]]
* [[Intergeo_2007]]
* [[FOSSGIS 2008]]

== Mitgliederliste ==
* [[User:Arnulf Christl | Arnulf Christl]]
* [[User:Ofreier | Olaf Freier]] ([http://www.hinte-messe.de/ Hinte GmbH])
* [[User:Peter Stamm | Peter Stamm]]
* [[User:Schmitz | Sebastian Schmitz]]
* [[User:Astrid Emde | Astrid Emde]]
* [[User:Uli Rothstein | Uli Rothstein]]
* [[User:Sven Boehme | Sven Boehme]]
* [[User:Garand | Michel Garand]]
* [[User:christoph | Christoph Baudson]]
* [[User:dietmar | Dietmar Fleischhauer]]
* [[User:Georgloesel | Georg Lösel]]
* [[User:Olaf Knopp | Olaf Knopp]]
* [[User:Torsten Brassat | Torsten Brassat]]
* [[User:Jtmapmedia | Jörg Thomsen]]
* [[User:Silke Reimer | Silke Reimer]]
* [[User:Till Adams | Till Adams]]
* [[User:Athina Trakas | Athina Trakas]]
* [[User:mlechner | Marco Lechner]]
* [[User:maltehm | Malte Halbey-Martin]]
* [[User:Kai Behncke | Kai Behncke]]
* [[User:Cplass | Christian Plass]]
* [[User:Thomas Kastler | Thomas Kastler]]
* [[User:Constanze Tschritter | Constanze Tschritter]]
* [[User:Marko Samson | Marko Samson]]
* [[User:Markus Weißmann | Markus Weißmann]]
* [[User:Robert.Dettmann | Robert Dettmann]] ([http://www.creata-software.de/ creaTa Software GmbH])
* [[User:Verena Diewald | Verena Diewald]]
* [[User:sholl | Stephan Holl]]
* [[User:GEppelt | Gunter Eppelt]]
* [[User:Sholler | Sebastian Holler]]
* [[User:Thomas Baschetti | Thomas Baschetti]]
* [[User:Peter Loewe| Peter Löwe]]
* [[User:Peter_panther| Florian Thürkow]]
* [[User:Fjbehr| Dr. Franz-Josef Behr]]
* [[User:crischan| Christian Wygoda (FH Eberswalde)]]
* [[User:Uwe.Seidel| Uwe Seidel (http://www.seicontec.net)]]
* [[User:Khoffmann | Karsten Hoffmann]]
* [[User:Schpidi | Stephan Meißl]]
* [[User:rnuske | Robert Nuske]]
* [[User:gritibaenz | Adrian Matter]]
* [[User:Martin Hüben | Martin Hüben]]
* [[User:Simon Appelt | Simon Appelt]]
* [[User:Liechtm | Matthias Liechti]]
* [[User:hporath | Holger Porath]]
* [[User:Pirmin_Kalberer | Pirmin Kalberer]]
* [[User:gerhard | Gerhard Schrotter]]
* [[User:Simon Schneider | Simon Schneider]]
* Ladzinski
* [[User:Neumann | Andreas Neumann]]
* [[User: hdus | Dr. Horst Düster]]
* [[User: shj | Hans-Jörg Stark]]
* [[User: edi.gonzales | Stefan Ziegler]]
* [[User: cmoe | Cédric Möri]]
* [[User:Sfkeller | Stefan Keller]]
* Bitte tragen Sie sich hier mit Link auf Ihren OSGeo-Wiki Account ein.

[[Category:Local Chapters]]

Geodata Metadata Model

2007-09-05T06:29:06Z

Wiki-Sfkeller: /* See Also */

Work in progress on extrapolating something least useless/ most stable from [[Geodata Metadata Requirements]]

[[Image:Schema_diagram.png]]

== See Also ==

* [[Geodata Metadata Requirements]]
* [[Simple Catalog Interface]]
* [http://gis.hsr.ch/wiki/OSGeodata_Discovery OSGeodata Discovery at geometa.info]

[[Category:Public Geospatial Data Committee]]

FOSS4G2007 Tourism

2007-09-02T11:15:39Z

Wiki-Sfkeller: /* Must-see places, features, etc. */

This page is dedicated to collect information helpful for everyone interested in tourist activities in Victoria, during FOSS4G 2007. Please, add any information you would consider helpful for people visiting Victoria, BC.

List of proposed topics:

== Must-see places, features, etc. ==

* Walk or Harbour Ferry to/from [http://maps.google.com/maps?q=300+St+Lawrence+St,+Victoria,+BC,+Canada+(Fisherman's+Wharf) Fisherman's Wharf] and have some Fish and Chips at Barb's Place, or an ice cream cone. Check out floating homes, the fish boats, and the tame harbour seals that frequent the floats.
** Harbour Ferry from the docks in front of the Empress, frequent service to/from Fisherman's Wharf.
** Walk along the harbour, keeping the water to your right and following the paths and streets along the shoreline, you will eventually arrive at Fisherman's Wharf.
* Take an evening walk on the [http://maps.google.com/maps?ll=48.4152%2c-123.3847&om=1&t=k&z=17 Ogden Point breakwater].
** Enjoy views of the Olympic mountains to the south, and the sun going down over the Sooke Hills to the west
** Watch the locals fish off the breakwater
** Watch divers in the "underwater marine park" off the breakwater
** Watch for harbor seals in the waters inside the breakwater
** Stroll all the way out (~1km) to the marker lighthouse
** Have a desert, coffee, dinner, or glass of wine at the Ogden Point Cafe at the foot of the breakwater
** Walk Government Street, Menzies Street or Oswego Street from the harbour, heading south to the ocean (about 10 minutes). Turn right at the ocean and along the ocean paths until you get to the foot of the breakwater (another 5-10 minutes).
* Have a drink in the [http://www.fairmont.com/empress/GuestServices/Restaurants/TheBengalLounge.htm Bengal Lounge].
** Excellent service, British Empire surroundings, overstuffed leather chairs, what's not to like?
** Oh, the prices are really high. But it's an ''experience''.
* Visit Beacon Hill Park.
** Walk south along Douglas Street until you get to the [http://maps.google.com/maps?q=126+Douglas+Street,+Victoria,+BC+(Beacon+Drive-In) Beacon Drive-In].
** Have a soft-serve ice cream, or some onion rings.
** Turn east and walk into the park. Walk to the top of Beacon Hill, admire the view. Walk back down and through the flower gardens.
** Head north through the park, to the Mayor's Grove of trees. Note the engangered Gary Oaks.
** Continue north, across Southgate to Humboldt, turn left.
** Note the St Ann's academy grounds on your left before you arrive back at the convention centre.
* Go to [http://maps.google.com/maps?f=q&hl=en&geocode=&q=government+and+fisgard,+victoria,+bc&sll=48.416869,-123.364363&sspn=0.007776,0.014141&ie=UTF8&z=16&iwloc=addr&om=1 China Town].
** Walk north on Government Street, admire the touristic knick knack shops.
** At Fisgard Street, admire the [http://www.victoria.ca/visitors/about_viewsgate.shtml Gate of Harmonious Interest].
** Walk down into China Town. If it is lunch time, consider having [http://en.wikipedia.org/wiki/Dim_sum dim sum] at Dom Mee's restaurant.
** Turn left and walk through Fan Tan Alley, the narrowest street in Canada.
** Fan Tan Alley lets out on Pandora Street, turn right and have a beer at Swan's, a local brew pub.
** Or, cross Pandora Street and enter Market Square, and the Old Town area around lower Johnson Street.
* [http://www.craigdarrochcastle.com/ Criagdarroch Castle] is [http://maps.google.com/maps?q=1050+joan+crescent,+victoria,+bc+(Craigdarroch%20Castle) located] about a 20 minute walk from downtown.
** Built by a local coal baron, it is a late-19th century gem of provincial opulance.
** Walk away from the harbor on Fort Street, past numerous antique stores and auction houses.
** You'll cross Cook Street, leave down town and head up a long moderate hill.
** When you see a middle school on your left, you are almost there. Look for Joan Cresent on your right.
** Turn and walk up the hill on Joan Crescent, you will come to the castle.

== Victoria By Bus ==
"Catch a movie, meander through Butchart Gardens, swirl down a waterslide or watch the sun set at an ocean-side park. All this and more is as easy as hopping a bus."

In addition to locations listed on the Victoria Regional Transit System's [http://www.bctransit.com/regions/vic/schedules/explore/default.cfm Explore Victoria] page, you can use the bus system to explore various parts of Victoria and the surrounding municipalities.

== Public / Online geodata and maps ==

=== Online Maps of Victoria ===

* [http://victoria.openguides.org victoria.openguides.org]
* [http://travel.yahoo.com/p-map-191501850-map_of_victoria_bc-i Victoria, BC in the Yahoo!]

== Walking with GPS ==

Where can I get some waypoints about Victoria?

* [http://www.openstreetmap.org/?mlat=48.432935738&mlon=-123.369299678&zoom=12 OpenStreetMap.org] - GPS tracks of Victoria,BC
* [http://www.bchotels.info/ Victoria Hotels] with downloadable GPS waypoint data
* [http://freefind.com/servlet/freefind/find.html?id=2267514&pageid=r&mode=ALL&n=0&_charset_=UTF-8&bcd=%C3%B7&scs=1&q1=canada+victoria&q2=&q3=&q4=&rpp=10&dl=m&stm= waypoint.org] - search result with Victoria, BC waypoints

== Helpful notes ==

Tourism information, phone numbers, must-know, etc.

Tourism Victoria
710 - 1175 Douglas Street
Victoria, BC V8W 2E1
Phone: (250) 953-2033, Fax: (250) 382-6539

* [http://www.victoria.ca City of Victoria in BC]
* [http://www.victoria-bc.com/ Victoria Travel Guide]
* [http://www.travel-victoria.com/ Travel and Tourism Victoria]

== Other ==

There is also a lot of useful information available on the official website of [http://www.foss4g2007.org/ FOSS4G 2007]:

* [http://www.foss4g2007.org/about_victoria/ About Victoria]
* [http://www.foss4g2007.org/dining_shopping/ From Wining and Dining to Shopping]
* [http://www.foss4g2007.org/vancouver_island/ Nanaimo and Vancouver Island]
* [http://www.foss4g2007.org/special_activities/ Whale Watching and Bus Tours]

[[Category:FOSS4G2007]]

Journal Volume 3

2007-08-31T06:13:00Z

Wiki-Sfkeller: /* Special Edition - FOSS4G Proceedings */

This is the planning and work page for the OSGeo [[Journal]] - Volume 3 publication.

If you want to contribute an article, add it to this list in the appropriate category.

'''Please review the [[Journal License and Guidelines]] page before adding your article to either article list.'''

------

== Deadlines ==
* Articles welcome: '''Now'''
* Articles requiring peer review, Submission Ends: '''September 30, 2007'''
* Article Submission Ends: '''October 10, 2007'''
* First Draft: '''October 25, 2007'''
* Final Publication: '''November 15, 2007'''

== Special Edition - FOSS4G Proceedings ==
This volume of the Journal will have a focus on the proceedings and papers presented at the [http://www.foss4g2007.org|FOSS4G Conference Event]. There will still be room for other articles, though it may be limited depending on how many articles come from the conference presenters. If there are many FOSS4G articles, then the 'normal' articles will be postponed to the next volume.

If you are interested in providing a paper for this purpose, please add yourself to the following section. Otherwise, add your normal article to the sections further below.
#Your FOSS4G paper goes here.... include your name, your email and the title of your article
#Hans Plum, Markus Lupp plum@lat-lon.de, Interoperabilty for 3D geodata: Experiences with CityGML and OGC Web Services
#Barde Julien, julien@mbari.org, A generic approach to manage metadata standards
#Peter Staub, peterstaub@ethz.ch, A Model-Driven Web Feature Service for Enhanced Semantic Interoperability
#Stefan Keller, sfkeller (at) hsr.ch, db4o2D - Object Database Extension for 2D Geospatial Types

== Normal Edition ==
=== Contributors / Topics ===
See [[Journal]] for definition of the following categories. Add yourself if you are interested. Note that all categories don't have to be filled, so this serves as a rough outline for the types of content we generally hope to have.

=== Editorials ===
# Tyler Mitchell: '''General updates'''

=== News ===
# Editor: Jason Fournier
# Additional contributors welcome...

=== Event Reports (2-3 articles) ===
# ...

=== Project Introductions (1-2 articles) ===
# ...

=== Case Studies (2-3 articles) ===
# Peter Löwe: '''Wanderlust 2.0: The state and future of hiking trail management in Germany with FOSS GIS'''

=== Integration Studies (2-3 articles) ===
# ...

=== Topical Studies (1-2 articles) ===
# Markus Neteler: '''Open Source Quality Assessment System: The GRASS Case''' (about[http://grass.itc.it/devel/index.php#quality GRASS-QA])
# ...

=== Programming Tutorials (1-2 articles) ===
# ...

=== Interview(s) ===
# ...

=== Developer Announcements ===
# OSGeo project summaries
# OSGeo Local Chapter updates
# deegree3: the shape of things to come. (Markus Lupp)
# ...

[[Category:Journal]]
[[Category:FOSS4G2007]]

Response to INSPIRE Metadata Draft

2007-03-15T18:11:00Z

Wiki-Sfkeller:

* See [[Reading the INSPIRE Metadata Draft]] for preparatory material.
* See [http://inspire.jrc.it/ir/sdic_view_step1_only.cfm?id=2163 FOSS SDIC]

Any member of the Free and Open Source Geospatial software community is welcome to participate in creating this response. Please add your name, and contact details on your userpage, to the list of participants and at any key stage (first stable draft; when sending the response).

Due 15.03.2007? -- [[User:Sfkeller|Stefan]] 19:11, 15 March 2007 (CET)

= Participants =

* [[User:JoWalsh|Jo Walsh]]
* [[User:Neteler|Markus Neteler]]
* [[User:Ianibbo|Ian Ibbotson]]
* [[User:Jencek|Jan Růžička]]
* [[User:Sfkeller|Stefan Keller]]

Response to INSPIRE Metadata Draft

2007-03-15T18:10:02Z

Wiki-Sfkeller: /* Participants */

* See [[Reading the INSPIRE Metadata Draft]] for preparatory material.
* See [http://inspire.jrc.it/ir/sdic_view_step1_only.cfm?id=2163 FOSS SDIC]

Any member of the Free and Open Source Geospatial software community is welcome to participate in creating this response. Please add your name, and contact details on your userpage, to the list of participants and at any key stage (first stable draft; when sending the response).

= Participants =

* [[User:JoWalsh|Jo Walsh]]
* [[User:Neteler|Markus Neteler]]
* [[User:Ianibbo|Ian Ibbotson]]
* [[User:Jencek|Jan Růžička]]
* [[User:Sfkeller|Stefan Keller]]

Talk:DCLite4G

2007-03-15T09:07:57Z

Wiki-Sfkeller: /* Implementations of OAI-PMH */

OAI-PMH - stefan, why don't we want to require GetRecord ??
:Just thought, ListRecords (incl. temporal query parameters) would be enough for harvesting. But I don't mind. -- [[User:Sfkeller|Stefan]] 09:30, 15 March 2007 (CET)

== Interfaces ==

My current thinking after talking to pramsey about [[Simple Catalog Interface]]s is to separate out interfaces for different classes of data search / retrieval tasks. According to this narrative: data, services (including presentation) and "relationships" are three different classes of thing which CSW/ebRIM is trying to treat of all at once and that is why it is being so slow and overcomplex.

=== Service metadata ===

Many people are more interested in repositories of information about web services. They want to do realtime access "find-bind".

=== Package metadata ===

Right now this is the domain of things like shape files, GML files etc. Theoretically it could be any resource you visit and the resource doesnt change between visits. This also applies to local filesystem and data management.

=== Publishing metadata ===

Other people are more interested in the publish side - real data syndication between repositories - the kind of thing that OAI-PRE will one day support. In the meantime we have to make something out of what we have got. Jeroen writes,

For the harvesting of the catalog itself, GeoNetwork has a custom
interface/ process. This process will go out to some XML service
(provided by another GeoNetwork node at this stage) and will request
a very brief result set from the other catalog that contains file
identifier (UUID), time stamp and catalog ID. By comparing those
with its internally cached records it will decide to request new or
updated records and it will remove those not found anymore.

== Implementations ==

=== Implementations of OAI-PMH ===

Each entry has a name of the implementation, whether it's a software or a webapplication (or an instance of both), progamming language and an example weblink). Some are using oai_dc 'DClite4G style'.

Harvesters:
* Google (Lang. n/a; Ex. spec. http://www.google.com/sitemaps )
* OAI Home - Tools (Lang. many; Home http://www.openarchives.org/tools/tools.html)
* geometa.info (Lang. Java; Ex.: http://geometa.info )

Metadata Providers:
* GeoNetwork? (Provider; Webapplication/Open source; Lang. Java+XSLT; Ex. tbd.)
* GeoShop.com (Lang. C; Ex. http://urlx.org/ibbinfoshop.ch/1d987 )
* Geometa-Ed. HSR (Lang. PHP; Ex. http://urlx.org/geometa.info/0363d )
* Geometa-Ed. Chur (Lang. PHP; Ex. http://urlx.org/geometa.info/67333 )
* List of OAI tools: http://www.openarchives.org/tools/tools.html
* List of OAI data providers: http://www.openarchives.org/

Candidate Projects (harvesters and metadata providers):
* uDig (Provider+Harvester; Desktop Software/Open source; Lang. Java; Ex. tbd.)
* OSGEO (Provider; Instance/Open Source; Lang. C+Scripts; Ex. tbd.)
* Canton of Aargau? (Provider; Instance/Closed source; Lang .NET; Ex. tbd).

Talk:DCLite4G

2007-03-15T08:47:39Z

Wiki-Sfkeller: /* Implementations of OAI-PMH */

OAI-PMH - stefan, why don't we want to require GetRecord ??
:Just thought, ListRecords (incl. temporal query parameters) would be enough for harvesting. But I don't mind. -- [[User:Sfkeller|Stefan]] 09:30, 15 March 2007 (CET)

== Interfaces ==

My current thinking after talking to pramsey about [[Simple Catalog Interface]]s is to separate out interfaces for different classes of data search / retrieval tasks. According to this narrative: data, services (including presentation) and "relationships" are three different classes of thing which CSW/ebRIM is trying to treat of all at once and that is why it is being so slow and overcomplex.

=== Service metadata ===

Many people are more interested in repositories of information about web services. They want to do realtime access "find-bind".

=== Package metadata ===

Right now this is the domain of things like shape files, GML files etc. Theoretically it could be any resource you visit and the resource doesnt change between visits. This also applies to local filesystem and data management.

=== Publishing metadata ===

Other people are more interested in the publish side - real data syndication between repositories - the kind of thing that OAI-PRE will one day support. In the meantime we have to make something out of what we have got. Jeroen writes,

For the harvesting of the catalog itself, GeoNetwork has a custom
interface/ process. This process will go out to some XML service
(provided by another GeoNetwork node at this stage) and will request
a very brief result set from the other catalog that contains file
identifier (UUID), time stamp and catalog ID. By comparing those
with its internally cached records it will decide to request new or
updated records and it will remove those not found anymore.

== Implementations ==

=== Implementations of OAI-PMH ===

Each entry has a name of the implementation, whether it's a software or a webapplication (or an instance of both), progamming language and an example weblink). Most are using oai_dc 'DClite4G style'.

Harvesters:
* Google (Lang. n/a; Ex. spec. http://www.google.com/sitemaps )
* OAI Home - Tools (Lang. many; Home http://www.openarchives.org/tools/tools.html)
* geometa.info (Lang. Java; Ex.: http://geometa.info )

Metadata Providers:
* GeoNetwork? (Provider; Webapplication/Open source; Lang. Java+XSLT; Ex. tbd.)
* GeoShop.com (Lang. C; Ex. http://urlx.org/ibbinfoshop.ch/1d987 )
* Geometa-Ed. HSR (Lang. PHP; Ex. http://urlx.org/geometa.info/0363d )
* Geometa-Ed. Chur (Lang. PHP; Ex. http://urlx.org/geometa.info/67333 )
* List of OAI tools: http://www.openarchives.org/tools/tools.html
* List of OAI data providers: http://www.openarchives.org/

Candidate Projects (harvesters and metadata providers):
* uDig (Provider+Harvester; Desktop Software/Open source; Lang. Java; Ex. tbd.)
* OSGEO (Provider; Instance/Open Source; Lang. C+Scripts; Ex. tbd.)
* Canton of Aargau? (Provider; Instance/Closed source; Lang .NET; Ex. tbd).

Talk:DCLite4G

2007-03-15T08:35:36Z

Wiki-Sfkeller:

OAI-PMH - stefan, why don't we want to require GetRecord ??
:Just thought, ListRecords (incl. temporal query parameters) would be enough for harvesting. But I don't mind. -- [[User:Sfkeller|Stefan]] 09:30, 15 March 2007 (CET)

== Interfaces ==

My current thinking after talking to pramsey about [[Simple Catalog Interface]]s is to separate out interfaces for different classes of data search / retrieval tasks. According to this narrative: data, services (including presentation) and "relationships" are three different classes of thing which CSW/ebRIM is trying to treat of all at once and that is why it is being so slow and overcomplex.

=== Service metadata ===

Many people are more interested in repositories of information about web services. They want to do realtime access "find-bind".

=== Package metadata ===

Right now this is the domain of things like shape files, GML files etc. Theoretically it could be any resource you visit and the resource doesnt change between visits. This also applies to local filesystem and data management.

=== Publishing metadata ===

Other people are more interested in the publish side - real data syndication between repositories - the kind of thing that OAI-PRE will one day support. In the meantime we have to make something out of what we have got. Jeroen writes,

For the harvesting of the catalog itself, GeoNetwork has a custom
interface/ process. This process will go out to some XML service
(provided by another GeoNetwork node at this stage) and will request
a very brief result set from the other catalog that contains file
identifier (UUID), time stamp and catalog ID. By comparing those
with its internally cached records it will decide to request new or
updated records and it will remove those not found anymore.

== Implementations ==

=== Implementations of OAI-PMH ===

Each entry has a name of the implementation, whether it's a software or a webapplication (or an instance of both), progamming language and an example weblink). Most are using oai_dc 'DClite4G style'.

Harvesters:
* Google (Lang. n/a; Ex. spec. http://www.google.com/sitemaps )
* geometa.info (Lang. Java; Ex.: http://geometa.info )

Metadata Providers:
* GeoNetwork? (Provider; Webapplication/Open source; Lang. Java+XSLT; Ex. tbd.)
* GeoShop.com (Lang. C; Ex. http://urlx.org/ibbinfoshop.ch/1d987 )
* Geometa-Ed. HSR (Lang. PHP; Ex. http://urlx.org/geometa.info/0363d )
* Geometa-Ed. Chur (Lang. PHP; Ex. http://urlx.org/geometa.info/67333 )

Candidate Projects to implement OAI-PMH:
* uDig (Provider+Harvester; Desktop Software/Open source; Lang. Java; Ex. tbd.)
* OSGEO (Provider; Instance/Open Source; Lang. C+Scripts; Ex. tbd.)
* Canton of Aargau? (Provider; Instance/Closed source; Lang .NET; Ex. tbd).

Talk:DCLite4G

2007-03-15T08:30:00Z

Wiki-Sfkeller:

Geodata Metadata Requirements

2006-10-21T13:58:26Z

Wiki-Sfkeller: /* Guidelines for a minimal OAI-PMH implementation */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Only '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-21T13:58:15Z

Wiki-Sfkeller: /* Guidelines for a minimal OAI-PMH implementation */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Onle '''three''' operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-20T12:45:19Z

Wiki-Sfkeller: /* Examples */ dc:identifiert point to metadata records

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = identifier of the metadata record (ev. a machine readable URI)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS (GetMap/GetFeatures) // seems redundant to id. but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point metadata defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-20T12:40:31Z

Wiki-Sfkeller: /* Examples */ onLineSrc changed to onlineRessource

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onlineResource = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an onlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onlineResource = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onlineResource = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an onlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onlineResource = a http URI entered by dataset owner // dataset binding
dclite4g:onlineResource = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/services/wms/</dclite4g:onlineResource>
<dclite4g:onlineResource>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onlineResource>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-20T12:39:07Z

Wiki-Sfkeller: /* Dublin Core lite for Geo (DClite4G) */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:OnlineResource (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g:onlineResource || [0..*] || URI || (formerly called onLineSrc) If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128: OnlineResource (can be the same as described in dct:hasPart (dataSetURI) of a service metadata record) || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128: DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: OnlineResource (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: OnlineResource and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: OnlineResource elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-15T13:50:24Z

Wiki-Sfkeller: /* OAI Implementations */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI implementations ===

OAI with Dublin Core:
* 'Geo-Metadatabase' (GMDB), open source (GPL, PHP)
* GeoShop, infoGrips GmbH, Zurich, Switzerland (C, Java)
* GeoNetwork, open source (GPL, Java)

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-14T17:50:21Z

Wiki-Sfkeller: /* Discovery */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data manager; iso19115:???|| Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAI-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

== Guidelines for a minimal OAI-PMH implementation ==

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

=== OAI Implementations ===

OAI with Dublin Core:
* GMDB
* GeoShop
* GeoNetwork

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-14T16:43:20Z

Wiki-Sfkeller: /* Information model for metadata exchange */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the 'Dublin Core lite for Geo' (DClite4G) model (http://tinyurl.com/kfkyv).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data owner || Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAM-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Guidelines for a minimal OAI-PMH implementation ====

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-12T21:40:40Z

Wiki-Sfkeller: /* Dublin Core lite for Geo (DClite4G) */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the http://tinyurl.com/kfkyv model (:->).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || Either a URI to a dataset or a dc:identifier (which points to a metadata record of dc:type='dataset'). Only applicable if type 'service'; N/A for type 'dataset'. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data owner || Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAM-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Guidelines for a minimal OAI-PMH implementation ====

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-12T18:47:29Z

Wiki-Sfkeller: /* Dublin Core lite for Geo (DClite4G) */ Added full mapping to iso19115/128

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the http://tinyurl.com/kfkyv model (:->).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Equal to iso19115/128?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to (meta-)data manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type, up to (meta-)data manager || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || A dc:identifier. Only applicable if type 'service'; N/A for type 'dataset'. A dc:identifier which points to a metadata record of dc:type 'dataset' for which it is 'responsible' for. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to (meta-)data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || Up to (meta-)data manager, WxS spec. do foresee this || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to (meta-)data owner || Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to (meta-)data owner || Ok?
|}

Legend: 'Equal to' means possible to derive from iso19128 (= WxS GetCapabilities).

Remarks:
* General:
** DC attributes/properties left as they are: dc:Audience; dc:Contributor; dc:Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAM-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Guidelines for a minimal OAI-PMH implementation ====

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry

Geodata Metadata Requirements

2006-10-12T18:39:04Z

Wiki-Sfkeller: /* Dublin Core lite for Geo (DClite4G) */

One goal of the [[Public Geospatial Data Project]] is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential [[Geodata Repository]] is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The [http://www.fgdc.gov/metadata/|US Federal Geographic Data Committee metadata standard] emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is perpetual work in progress. See also:

* [[Geodata Metadata Translata]]
* [[Simple Catalog Interface]]
* [[Geometa Engine]]

= Draft Metadata model =

Attempting to abstract the minimal metadata model below ([[#Information model for metadata exchange|DClite4G]]) out into [[Geodata Metadata Model]] (see there), which serves for a metadata management tool. This is what OSGeo Geodata Committee participants have identified as their core needs for metadata.

It was generated from an [http://frot.org/osgeo/geometadata.rdf RDF model]. This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.

== Data Set ==

This is an draft to define a metadata information model for a OSGeo catalogue. [[Geodata_Metadata_Requirements#Information_model_for_metadata_exchange|Below]] there is another minimal metadata information model targeted for metadata exchange and harvesting (name proposed: DClite4G).

* Title: Title of the data set. Corresponds to Dublin Core '''title'''
* Description: Text description of the data set. Corresponds to Dublin Core '''description''' element.
* Originator
** Person: A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
** Organization: A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the [http://xmlns.com/foaf/0.1/ FOAF] vocabulary.
* Spatial Data Organization: Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )
* Datasource: URL from which the data can be downloaded via different protocols
** WFS: For Vector data in GML
** File at HTTP URL: For Raster data described in GML
** BitTorrent: URL of bittorrent .torrent tracker file.
** Other Web API: For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )
* License information: Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.
* Publication date: Corresponds to Dublin Core '''date''': ISO compliant date of publication.
* Timespan
* Time Period
** start date and end date
** single date
** Extents
* Spatial Domain: A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.
** bounding coordinates: FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons [http://georss.org/ GeoRSS] decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.
** Projection (Raster, Vector, Coverage): Original projection of the data (reference to an ?)
** Horizontal and vertical datum;
** Horizontal and vertical units.
** Resolution (Raster,Coverage): (property of DataSet). e.g. map units per pixel where map units are defined by SRS. can be different in horizontal / vertical axes e.g. non square pixels
** Colour Depth (Raster): 8/16/24 bit etc - this is useful rather than required
** Transparency (Raster)
** Scale (Vector):Map scale at which vectors are considered accurate. Quantified as a fractional/dimensionless number - 'inches per inch' - on a scale between 1 and 0 - or inverse scale such as 1:50000 - and we would want to store this in a consistent way.
* Layers: DataSet has multiple Layers
** Name
** Description
** Extent: can be non-rectangular
** Scale Hinting: minscale / maxscale - cf resolution and scale - are these actually properties of layers and not really of data sets? (eg data set contains multiple layers - will they be in any way likely to contain different scale properties?)
** Optional extra properties
* Taxonomy/Ontology: Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= Discovery =

== Requirements ==

A discovery resource is essential to expose resultant metadata as per this document. Below are requirements:

Publish:
* ability to publish/register a web service
* ability to publish/register a static resource
* ability to harvest and classify public and private resources
* ability to establish and maintain user/group/role based authentication
* ability to provide a RESTful authentication mechansim

Find:
* ability to discover the existence of a web service
* ability to discover the existence of a resource which is available via web services (i.e WMS layer, WFS feature type)
* ability to discover the existence of a static resource (dataset, document, etc.)

Bind:
* ability to perform discovery operations with spatial, aspatial and temporal predicates
* ability to provide a RESTful request API
* ability to provide responses in XML
* ability to expose resource/service metadata in a manner which facilitates dynamic connection to a resource/service

== Webcrawlers perspective or: How to boost your geodata? ==

Geoinformation content needs to be published and get disseminated somehow before it is being found by users. Following are some thoughts to help discovery/search services/brokers and their webcrawlers/harvesters/aggregators to do a better job. So the main question here is: What can content owners do to promote their information. It's mainly registration, declaration and citation. -- [[User:Sfkeller|Stefan]] 11:25, 2 October 2006 (CEST) (http://tinyurl.com/ghhb2)

* Self-registration through content provider
** submit URL (like DNS)
** Do a 'ping' (like RSS)
** register through UDDI (if SOAP is 'unavoidable'...)
* Self-declaration:
** Machine-readable only ('invisible'):
*** GeoRSS feed of feeds which contains GeoRSS encoded metadata records ('RSS of RSS')
*** OPML (natural to RSS, but more complicated than just 'RSS of RSS')
*** Something similar to [http://en.wikipedia.org/wiki/Robots_Exclusion_Standard robots.txt]
*** HTML link: <nowiki><link rel="alternate" type="application/rss+xml" title="RSS" href="http://rss.news.yahoo.com/rss/tech"></nowiki>
** Visible/human readable:
*** Feed icons
*** Chicklets
* Citation through others:
** XML link or relationship inside metadata record (see also 'friend' in OAI-PMH metadata set header)
** HTML link pointing to Webpage (suboptimal)

Note: See also "RSS auto-discovery": e.g. '"Blog Optimization", SES San Jose (aug. 2006): 1. Submit your feeds... Or: "Pimp My Blog in 8 Steps" (sept. 2006): (...) 3. Sign up for feedburner.com, (...) 8. Enable auto discovery (feed icon, chicklet).'

== Information model for metadata exchange ==

This is the http://tinyurl.com/kfkyv model (:->).

Some design considerations:
* This is a minimal metadata information model regarding to a metadata exchange protocol for harvesting (e.g. no filter nor GML implementation needed) and according to the ideas about a [[Simple Catalog Interface]]/protocol.
* Based on Dublin Core (DC) and Catalogue Services Specification 2.0.1, OGC 04-021r3, p.22.
* Dublin Core need refined semantics of some properties/attributes.
* Have had hard times with the abundance use of namespaces. This is because DC specs and other XML 'practices' specialize properties/attribute types instead of specializing whole classes.
* All properties/attributes have cardinality [0..1] except for identifiers (which are mandatory) and for those attributes which are really needed (as unbounded) for automation!
* Take all information one can in an automated manner, e.g. from data set resource.

Details:
* Services are included in attribute 'format' in the sense that WMS, etc. are just protocol bindings to geodata. Real well known services on it's own like filter or label placement services have a place there too. They could be still detected by challenging them with GetCatabilites (taken from OWS/WxS).
* Indicating of quality of service could be a nice task for search service provider; no need to add it as attribute
* Relationships between features is part of schema metadata: How to handle this...?

==== Dublin Core lite for Geo (DClite4G) ====

* Aligned and rearranged after some discussions on osgeodata-list and geotools-devel-list. Next steps: first consensus on approach/fields, then consensus about which encoding (DC, RDF or GeoRSS?). - [[User:Sfkeller|Stefan]] 08:33, 26 September 2006 (CEST)

;Figure: Analysis UML class diagram of minimal metadata information model 'Dublin Core lite for Geo' (DClite4G) which consists of a single entity set (green); two entities/instances/records are shown, a 'dataset' (left, grey) and a 'service' (right, red).
[[Image:DClite4G.png|center|Class diagram of 'Dublin Core lite for Geo' (DClite4G)]]

'''Dublin Core lite for Geo''' (DClite4G) (Mandatory subset of DC elements plus georesource relationships, some XML content exept dc:identifier may be null/empty):
{| border="1" cellspacing="0" cellpadding="10" style="border-collapse:collapse;"
|-
|'''Attr. name'''|| '''Card.''' || '''Attr. type''' || '''Explanation''' || '''Poss. to autom.?''' || '''Status'''
|-
|dc:identifier || [1] || URI || A unique identifier which unambigiously identifies an item within a given context (i.e. a catalogue/repository, a model and a language) used for extracting and referencing metadata. Note that still several records can co-exist with the same dc:identifier either in different sets implementing different metadata models or because of multiple instances of records using different languages in title, etc. Note also that this identifier is not necessary the identifier of a resource. To access the resource associated with a metadata record, one must use dct:hasPart and dclite4g:onLineSrc (see also [http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm OAI-PMH] and GeoTools) || iso19128:Identifier, iso19115: CI_Citation.identifier, else up to metadata manager || Ok?
|-
|dc:title || [0..1] || string (XML encoded) || A name given to the resource (regardless e.g. of naming restrictions of file systems). If a layer or file name exist in addition to a title this can be appended with // (tbd! proposal) and concatenated at end of this title string. || iso19128:title, iso19115: CI_Citation.title || Ok
|-
|dct:abstract || [0..1] || URI or string (XML encoded)|| A description of the resource. Either a URI reference to a human readable resource or a string. In case of dc:type 'service' (OWS) its the abstract (string) from of GetCapabilities document (GeoTools ServiceInfo has two fields: abstract and description...?) Subtype of dc:description; we use this as WMS, csw:record and ISO 19115 are using it. || iso19128:abstract, iso19115: MD_DataIdentification.abstract || Ok
|-
|dc:type || [0..1] || enumeration || The nature or genre of the content of the resource. 'dataset' or 'service' else 'document, 'text', 'image', 'sound', etc. (see [http://dublincore.org/documents/dcmi-type-vocabulary/ DCMI type (controlled) vocabulary]). (Not yet defined for Web Processing Service which have no specific georesource they are responsible for. What about special documents like OGC:SLD, OGC:WMC etc.?) || if WxS/OWS then 'service' else 'dataset' or another media type || Ok
|-
|dc:format || [0..1] || URI || A machine readable reference to either a [http://www.iana.org/assignments/media-types/ internet media (mime) type (recommended)] or a an xml schema namespace URI linking to an namespace authority. In case of dc:type='service' multiple schemas are to expect: insert them comma-separated? || 19128:AuthorityURL, iso19115: AuthorityURL || Ok
|-
|dct:spatial || [0..1] || dcmiBox:Box with CRS || Subtype of dc:coverage. (CRS=WGS84; other possible values offered by dct: Point and TGN) || iso19128:EX_BoundingBox, iso19115: EX_BoundingBox || Ok
|-
|dct:modified || [0..1] || date || Date of last (published) change of resource (see [http://www.w3.org/TR/NOTE-datetime W3C Encoding rules]). Subtype of dc:date || Timestamp of resource; GetCapabilities || Ok
|-
|dc:subject || [0..1] || string (ASCII) || A keyword list; e.g. ISO 19115 classification list. (clarification needed: separated by comma) || KeywordList, iso19115: MD_TopicCategoryCode || Ok
|-
|dclite4g: onLineSrc || [0..*] || URI || If dc:type='service' then this is the baseURL to it. If dc:type='dataset' it's either a dc:identifier which points to a metadata record of type 'service' or a dataset URL e.g. uri:ftp:// host.com/path/filename. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point of the resource. || if dc:type='dataset' given by provider, if dc:type='service' iso19128:OnlineResource || Ok?
|-
|dct:hasPart || [0..*] || URI || A dc:identifier. Only applicable if type 'service'; N/A for type 'dataset'. A dc:identifier which points to a metadata record of dc:type 'dataset' for which it is 'responsible' for. Subtype of dc:relation. Note that in some implementations this seems redundant to dc:identifier but in fact this is the real access point the resource associated with a metadata record. || iso19128:DataURL, iso19115: MD_metadata.dataSetURI || Ok?
|-
|dc:source || [0..1] || URI or string (XML encoded) || Description from which the present resource is derived, lineage information. Either an URI reference to a human readable resource or a string. (Note: Server base URLs and file URIs are handled elsewhere) || Up to data owner || Ok
|-
|dc:publisher || [0..1] || string (XML encoded) || Civic Address: if type service derived from GetCapabilities ('ContactInformation') else flattened KML style (= xAL) (still awaiting consensus in other OGC specs. or GeoRSS) || Title element of 19128:Attribution; OrganisationName element of 19115:CI_ResponsibleParty || Ok
|-
|dc:language || [0..1] || enumeration || RFC 1766 (ISO 639, followed optionally by country ISO 3166). Max. Cardinality is intentionally 1 which for the sake of simplicity means that translations of a metadata record in different languages is recorded in several metadata instances and not in multiple dc:language, dc:title or dct:abstract occurrences. || (could be guessed from title/description?) || Ok
|-
|dc:rights || [0..1] || URI or string (XML encoded) || License information link about the resource. Probably also (link to) disclaimers. Either an URI reference to a human readable resource or a string (machine readable licenses is an issue; [http://backend.userland.com/creativeCommonsRssModule this] could be an starting point. || Up to data owner, GetCapabilities || Ok
|-
|dc:relation || [0..*] || URI || A reference to a related resource. DClite4G uses following subtypes: dc:hasPart and iso19115: onLineSrc (see above). If using DC unqualified dc:relation could be used. This could be a machine readable reference to other metadata providers in order to let discover other (meta) data providers. Note that OAI-PMH has such a relationship called '[http://www.openarchives.org/OAI/2.0/guidelines-friends.htm friends]' but on the metadata collection/set level. ------------------------------------------------------------------------------- || Placeholder; should be refined in a specific model; meaning up to data owner || Ok?
|}

Legend: 'Poss. to autom.' means Possible to automate. iso19128 = WMS

Remarks:
* General:
** DC attributes/properties left as they are...: Audience; Contributor; Creator.
** All attributes/properties have at most cardinality 1 except iso19115: onLineSrc and dct:hasPart (and dc:relation from complementary part of DClite4G).
** Depending on the modeling approach, even these elements can become cardinality 1. NOTE that datasets (geodata resources) and services (data access services) in principle have a many-to-many relationship: Here a geodata resource (dc:type dataset) can have many iso19115: onLineSrc elements and a dc:type data_access_service has only one dc:description which can be a GetCapabilities document.
** No additinal DC attributes/properties required; few of them need to be specialized (see dct:...);
** See for some general explanations about [http://cicharvest.grainger.uiuc.edu/qualifieddc.asp dc/dct here].
** Assume metadata (as opposite to many geodata sets) is always free and open information, like [http://creativecommons.org/licenses/by-sa/2.5/ Creative Commons Share Alike]
** An encoding still has to be discussed (see following example). need schemaLocation in OSGeo!?
* Details:
** GetCapabilities adds following attributes (not yet modeled here): Fees, ScaleHint and Style.
** Sorted out or highly disputed (non-DC) elements: fees, scalehint, harvestinterval.
** dct:modified and dct:spatial can be sync'ed from dataset.
** Attribute 'relation': This was'nt discussed yet. Simply helps harvesters to discover more (meta) data providers.
** Attribute 'publisher': Carl mentioned such a structure [http://lists.eogeo.org/pipermail/georss/2006-May/000514.html here] which includes StreetAddress, addressee, primaryAddressNumber, streetName, city, state, zipCode, countryCode (like in KML and behind Google geocoding service!?)
** Keywords is included in attribute 'dc:subject'; I think people have a hard time to agree on an enumerated list (see the success of folksonomy).
* Note that OAM-PMH...
** puts a XML envelope around this metadata and adds a header containing two attributes: 'identifier' to identify an metadata record and 'datestamp' as date of last (published) change of metadata record.
** requires to define a name for metadata sets. Let's don't care about this yet.

==== Guidelines for a minimal OAI-PMH implementation ====

OAI-PMH means ''Open Archives Initiative Protocol for Metadata Harvesting''. For an introduction to OAI-PMH 2 see [http://www.gis.hsr.ch/wiki/OAI-PMH here].

This is a draft implementation guideline for a minimal OAI-PMH implementation for geospatial resources which contains following five steps:

* '''1. Join the community''': Register to the 'OAI Implementers list' at the [http://www.openarchives.org/ OAI Homepage]
* '''2. Read the spec.''': [http://www.openarchives.org/OAI/openarchivesprotocol.html The Harvesting Protocol (version 2.0) specification] together with [http://www.openarchives.org/OAI/2.0/guidelines.htm Implementation Guidelines]
* '''3. Look at existing [http://www.openarchives.org/tools/tools.html tools]'''.
* '''4. Implement protocol with DC model following these recommendations and test it''': [http://www.purl.org/NET/oai_explorer The official OAI Repository Explorer].
* '''5. Extend it''' later eventually with specific metadata models like ISO19139 or DClite4G and respective XML formats.

Following are more specific guidelines for a minimal OAI-PMH implementation of a so called 'data provider' using only the mandatory 'unqualified' Dublin Core (DC):

* Three operations (verbs) are needed: Identify, ListMetadataFormats and ListRecords.
* Following operations are not required (initially): ListIdentifiers, ListSets, GetRecord.
* No incremental harvesting (resumption process for ListXxx operations with more than 1000 records)
* No compression as defined in the OAI-PMH spec. (compression at lower http level still possible)
* Date granularity may be 'day' not seconds (YYYY-MM-DD)
* Keeping track of deleted record may not be supported (deletedRecord=no)
* Mandatory DC supported as data model is sufficient for a start but with specific semantics (e.g. coverage, relation) (see also example below):
** dc:description contains dct:abstract
** dc:coverage contains bounding box encoding as defined in http://georss.org/simple.html#Box
** dc:date means in fact dct:modified
** dc:relation is filled in with dclite4g:onLineSrc. If dc:type='service' dct:hasPart can be derived from GetCapabilities.

==== Examples ====

Some examples of '''DClite4G''' instances/records:
(legend: 'literal' is a constant, // is a comment) (http://tinyurl.com/eaaaj)

'''A web mapping service instance example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a service instance. Can also be called a 'data access point' (Note GetCapabilities finally needs to be delivered by some service owner!):

dc:identifier = baseURI of the service // in fact just an id to identify a metadata record
dc:title = WxS Service/Title
dct:abstract = WxS Service/Abstract
dc:type = 'service'
dc:format = namespace to OGC:WxS schema.xsd
dct:spatial = Root BoundingBox // from Capabilities XML
dct:modified = timestamp // e.g. from HTTP header or updateSequence
dc:subject = WxS Service/KeywordList
dclite4g:onLineSrc = baseURI of WxS // seems redundant to id but is the real link to the service
dct:hasPart = a dc:identifier which points to each Layer element
dct:hasPart = another dc:identifier, etc.
dc:source = null // N/A. Note: Not meant as an OnlineResource
dc:publisher = WxS Service ContactInformation/Organization
dc:language = maybe HTTP header for lang (ISO3166 code), soon supported by WMS
dc:rights = WxS Services Fees/AccessConstraints
dc:relation = definition up to metadata provider

'''A dataset example derived from GetCapabilities''': Mapping OGC:WxS GetCapabilities to a dataset/georesource/data access point (Note: There is no hasPart relationship in datasets):

dc:identifier = 'data access point' to dataset (baseURI plus Layername)
dc:title = WxS Layer/Title
dct:abstract = WxS Layer/Abstract
dc:type = 'dataset'
dc:format = namespace to format
dct:spatial = BoundingBox from Layer/BoundingBox
dct:modified = timestamp from HTTP header maybe or updateSequence
dc:subject = Layer/KeywordList
dclite4g:onLineSrc = a baseURI of WxS // seems redundant to id but is the real 'data access point'
dclite4g:onLineSrc = another baseURI of WxS // another dataset binding
dc:source = null // Note: Not meant as an OnlineResource
dc:publisher = from Service if available?
dc:language = from Service if available?
dc:rights = from Service if available?
dc:relation = definition up to metadata provider

'''A dataset example delivered by a dataset owner''':

dc:identifier = a data access point defined by dataset owners context
dc:title = entered by dataset owner
dct:abstract = entered by dataset owner
dc:type = 'dataset'
dc:format = namespace to format entered by dataset owner
dct:spatial = BoundingBox from data warehouse
dct:modified = file timestamp from data warehouse
dc:subject = keyword list entered by dataset owner
dclite4g:onLineSrc = a http URI entered by dataset owner // dataset binding
dclite4g:onLineSrc = a baseURI of a WxS entered by dataset owner // another binding
dc:source = entered by dataset owner // Note: Not online resource
dc:publisher = entered by dataset owner
dc:language = entered by dataset owner (or derived?)
dc:rights = entered by dataset owner
dc:relation = definition up to metadata provider

'''A dataset example with OAI-PMH XML encoding in DClite4G format''':

Notes:
* Example values are only for explanation purposes and purely fictive.
* XML Schema (= geometadc.xsd? or dclite4g.xsd?) still tbd.
* This record is not yet validated!
* Took 'dclite4g' as envelope name.

<dclite4g:qualifieddc
xmlns:dclite4g="http://www.osgeo.org/schemas/dclite4g/0.01"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:dct="http://purl.org/dc/terms/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.osgeo.org/schemas/dclite4g/ dclite4g.xsd">

<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dct:abstract>Elevation data collected for the National Elevation
Dataset (NED).</dct:abstract>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dct:spatial>
<Box projection="EPSG:4326" name="Geographic">
<northlimit>34.353</northlimit>
<eastlimit>-96.223</eastlimit>
<southlimit>28.229</southlimit>
<westlimit>-108.44</westlimit>
</Box>
</dct:spatial>
<dct:modified>2004-03-01</dct:modified>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid_georss.xml</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/services/wms/</dclite4g:onLineSrc>
<dclite4g:onLineSrc>uri:http://www.osgeo.org/geodata/ned_grid.shp</dclite4g:onLineSrc>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>


<dc:publisher>U.S. Geological Survey</dc:publisher>
<dc:language>en</dc:language>
<dc:rights>uri:http://www.usgs.gov/pubprod/</dc:rights>
</dclite4g:qualifieddc>

'''Same record example as before but with unqualified DC encoding''':

Note that this unqualified DC record can be seen as a mapping from DClite4G by using it's well defined semantics and content 'encoding'. See explanations above to understand the semantics of these DC-elements:

...
<dc:identifier>www.osgeo.org/geodata/:f264-77d2-09ce-aa39-f0f0</dc:identifier>
<dc:title>National Elevation Mapping Service for Texas</dc:title>
<dc:description>Elevation data collected for the National Elevation
Dataset (NED).</dc:description>
<dc:type>dataset</dc:type>
<dc:format>...uri to the schema of the information model
(xsd, realxng, schematron, ili, ...)</dc:format>
<dc:coverage>34.353 -96.223 28.229 -108.44</dc:coverage>
<dc:date>2004-03-01</dc:date>
<dc:subject>Elevation, Hypsography, and Contours</dc:subject>
<dc:relation>uri:http://www.osgeo.org/services/wms/</dc:relation>
<dc:source>Lineage: Based on 30m horizontal and 15m vertical accuracy.</dc:source>
...

== Other Relevant Info ==
* [[Simple_Catalog_Interface]]
* [http://www.gis.hsr.ch/wiki/OSGeodata OSGeodata on GISpunkt Wiki] - These pages are about the search of an open, lean and mean "protocol for the incremental exchange of metadata about geographic resources between systems". Profiled specifications like WFS or OAI-PMH are currently on our short list. Delving into 'Open Archives Initiative Protocol for Metadata Harvesting' (OAI-PMH) is strongly encouraged. It's a low barrier interoperability specification based around metadata harvesting model, it's stable (subsequent revisions are backwards compatible) and uses unqualified Dublin Core as default metadata information model; there exist open source tools (like OAICat) and it has been adopted among others by Google and Yahoo! but it's not a search protocol.
* See here a [http://www.gis.hsr.ch/wiki/OAI-PMH comparison between CSW, WFS and OAI-PMH].

= References =

== Geospatial ==

* [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html FGDC geospatial metadata model]

* [http://dcs.dlese.org/preview/admin/view.do?id=TEST-000-000-000-008 GEON geospatial metadata model]

* [http://gcmd.nasa.gov/Aboutus/standards/fgdc_to_dif.html DIF geospatial metadata model]

* [http://georss.org/ GeoRSS]

* [http://en.wikipedia.org/wiki/Web_Feature_Service WFS]

* [http://geoapi.sourceforge.net/stable/site/index.html GeoAPI] contains an implementation of ISO 19115

== RDF ==

* [http://www.w3.org/RDF/ Resource Description Framework]

* [http://www.w3.org/TR/rdf-primer/ RDF Primer]

* [http://www.w3.org/TR/owl-guide/ OWL Web Ontology Language Guide]

* [http://sweet.jpl.nasa.gov/ontology/ Semantic Web for Earth and Environmental Terminology] OWL Ontologies at NASA

* [http://www.dublincore.org/documents/dces/ Dublin Core] metadata model for documents

* [http://xmlns.com/foaf/0.1/ FOAF] metadata model for people and organisations

* [http://usefulinc.com/doap/ DOAP] metadata model for open source software projects and code repositories

== Notes ==

metadata isn't an easy task. The balance between completeness and people simply ignoring to generate it...

I wish I had had a prexisting plan of how to index and search for the data sets on extent and 'type' that we were adding

=== From [[Geodata Packaging Working Group]]: ===

** Specifications of a data set
*** Creator
*** Date
*** License
*** Data Type
*** Topic
*** Spatial Extent
*** Coordinate System/Projection
*** Target Scale/Precision
*** Attribute Data

== See Also ==

* [[Geodata Discovery Working Group]]
* [[Geodata Repository]]
* [[Geodata processing at telascience.org]]

= Comments =

* I would like to propose an additional element for the metadata model--data source (or lineage). If the data is derived from some other data, we should be able to backtrack and look at its parent/s. "Lineage" is a conditional element in FGDC but I think it's important enough that we should include it in our model. I suppose this can also be included in the Description but wouldn't it be nice to have this included as a required element? This is useful when checking for errors/consistency. -Perry