OSGeo - User contributions [en]

OSGeo Community Sprint 2022

2020-01-17T15:47:35Z

Wiki-Normanb:

Annual Code Sprint comes to Athens (Greece) in 2020!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Community_Sprint_2020#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:logo_daem.png|220px|Municipality of Athens, DAEM S.A.|link=https://www.cityofathens.gr/en/]]
 
https://www.cityofathens.gr/en/
|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Bh-logo.jpg|320px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:Logo-EOX.png|160px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
|}

== Dates and Times ==

* Date: May 25-29 (5 days)
* Time: 8:30am to 4:30pm each day

== Other Events from January to September 2020 ==

* [http://2020.foss4g.org/ FOSS4G 2020], August 24-29 in Calgary, Canada
* FOSS4G Europe 2020, July 13-18 (?) in Valmiera, Latvia
* ''please add your event''

== Location ==

* [http://www.serafio.gr/portfolio/main-hall/ Serafio main hall], Municipality of Athens
* [https://www.openstreetmap.org/#map=19/37.97325/23.70656 OpenStreetMap]

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''OSGeoLive''':
** Work towards 14.0 release in August

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="25"|Fri
!width="60"|Accommodation
!width="60"|Likelihood
!width="30"|Food Restrictions
!width="60"|social event
|-
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x || x || x || booked || Organizer :) || No || x ||
|-
| 2 ||[[User:tomkralidis|Tom Kralidis]] || CA || tomkralidis at gmail.com || self || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x || x || x || x || TBD || Likely || No || x ||
|-
| 3 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc at gmail.com || US Army Corps || PDAL, MapServer, proj, GDAL || x || x || x || x || x || TBD || Likely || No || x ||
|-
| 4 ||[[User:dmorissette|Daniel Morissette]] || CA || dmorissette at mapgears.com || Mapgears || MapServer, GDAL/OGR, MapML || x || x || x || x || x || TBD || Very Likely || No || x ||
|-
| 5 ||[[User:Cvvergara|Vicky Vergara]] || MX || vicky at georepublic.de || Georepublic, OSGeo || pgRouting, OSGeoLive || x || x || x || x || x || TBD || Very Likely || No fish || x ||
|-
| 6 ||[[User:Neteler|Markus Neteler]] || DE || neteler at mundialis.de || mundialis || GRASS GIS,... || x || x || x || x || x || TBD || Likely || No || x ||
|-
| 7 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl at eox.at || EOX IT Services GmbH || MapServer, EOxServer || x || x || x || x || x || TBD || Very likely || No || x ||
|-
| 8 ||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey at cleverelephant.ca || Crunchy Data || PostGIS, GEOS || ? || x || x || x || x || TBD || Very likely || No || x ||
|-
| 9 ||[[User:pierotofy|Piero Toffanin]] || US || pt at uav4geo.com || OpenDroneMap || OpenDroneMap, PDAL, rio-tiler, DroneDB || ? || x || x || x || x || TBD || Very likely || No || x ||
|-
| 10 ||[[User:hobu|Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PDAL, Entwine, DroneDB, GDAL, PROJ || x || x || x || x || x || TBD || Very likely || No || x ||
|-
| 11 ||Connor Manning || US || connor@hobu.co || Hobu, Inc. || Entwine, PDAL || x || x || x || x || x || TBD || Very likely || No || x ||
|-
| 12 ||[[User:Chiossif|Christos Iossifides]] || GR || chiossif (at) gmail.com || NTUA || GRASS GIS || x || x || x || x || x || booked || Very likely || No || x ||
|-
| 13 ||[[User:Chambbj|Brad Chambers]] || US || brad.chambers at gmail.com || Grover Consulting Services || PDAL || x || x || x || x || x || TBD || Very likely || No || x ||
|-
| 14 ||[[User:Roelandtn|Nicolas Roelandt]] || FR || roelandtn.pro (at) gmail.com || self || OSGeoLive || x || x || x || x || x || TBD || likely || No || x ||
|-
| 15 ||[[User:Colivier|Olivier Courtin]] || FR || o (at) datapink.com || DataPink || RoboSat.pink, PGStrom || x || x || x || x || x || TBD || likely || No || x ||
|-
| 16 ||[[User:normanb|Norman Barker]] || US || norman (at) tiledb.com || TileDB.com || TileDB || x || x || x || x || x || TBD || likely || No || x ||
|-
| 17 ||[[User:stavrosp|Stavros Papadopoulos]] || US || stavros (at) tiledb.com || TileDB.com || TileDB || x || x || x || x || x || TBD || likely || No || x ||
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Gitter channel: https://gitter.im/OSGeo/Sprint

== Costs ==

Participants should plan for the following costs:

* Travel to Athens
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Greece]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place May 25-29, 2020.

We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place in Athens and will be hosted by [https://www.cityofathens.gr/en/, Municipality of Athens] and organized by members of the local OSGeo Greek chapter.

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2020/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.

== Event Owner ==
* [[User:kalxas|Angelos Tzotsos]]
* [[User:Chiossif|Christos Iossifides]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!

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

OSGeo Community Sprint 2019

2019-01-24T16:30:07Z

Wiki-Normanb: /* Participants */

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2019#Sponsoring |Sponsoring the Event]].

; Venue Sponsor
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-UMN.png|140px|University of Minnesota|link=https://twin-cities.umn.edu/]]
 
https://twin-cities.umn.edu/

|}

;Gold Sponsors
{| border=0 cellspacing=15 cellpadding=10

||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/

||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
|}

; Silver Sponsors

{| border=0 cellspacing=15 cellpadding=10
||
[[File:Logo-Hobu.png|140px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Logo-EOX.png|120px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[Image:Logo-tydac.png|160px|Tydac|link=http://www.tydac.ch/]]
 
[http://www.tydac.ch/ http://www.tydac.ch/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}

; Bronze Sponsors
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:sharedgeo_logo.png|170px|link=https://www.sharedgeo.org/]]
 
[https://www.sharedgeo.org/ https://www.sharedgeo.org/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}

== Dates and Times ==

* Date: May 14-17 (4 days)
* Time: 8:30am to 4:30pm each day

== Other Events from January to May 2019 ==

* ''OSGeo's 13th birthday Feb 4''
* ''[http://2019.foss4g-na.org/ FOSS4G-NA 2019], April 16-19 in San Diego, CA''
* ''please add your event''

== Location ==

* University of Minnesota - Twin Cities

=== Coding Venue ===
* Wilson Research Collaboration Studio: https://www.lib.umn.edu/wilsonstudio
* Wilson Library, West Bank
* [https://www.openstreetmap.org/#map=19/44.97095/-93.24392| OpenStreetMap]

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''Distance''' || '''Notes'''
|-
| [https://www.marriott.com/hotels/travel/mspdc-courtyard-minneapolis-downtown/?scid=bb1a189a-fec3-4d19-a255-54ba596febe2 Courtyard by Marriott Minneapolis] || 175$+ || .5 mile || Walking distance to Wilson Library, University Campus
|-
| [https://www.graduatehotels.com/minneapolis/ Graduate Minneapolis] || 185$+ || 1.9 miles || On University Campus and Light Rail transportation
|-
| [https://hamptoninn3.hilton.com/en/hotels/minnesota/hampton-inn-and-suites-minneapolis-university-area-MSPUAHX/index.html Hampton Inn & Suites Minneapolis] || 152$+ || 2.2 miles || On Light Rail transportation
|}

=== How to get there ===

'''Flights''' - [https://www.mspairport.com/flights-and-airlines Minneapolis-St. Paul International Airport (MSP)]

Sixteen commercial passenger airlines service the Minneapolis-St. Paul International Airport (MSP); 11 are located at Terminal 1 - Lindbergh and five are located at the Terminal 2 - Humphrey.

'''Light Rail Transit''' - [https://www.mspairport.com/directions/ground-transportation/light-rail-transit Light rail transit (LRT)] trains stop at both Terminal 1-Lindbergh and Terminal 2-Humphrey and connect travelers to 17 other destinations, including downtown Minneapolis to the north and Mall of America to the south.

[https://www.metrotransit.org/blue-line-map Metro Transit Map of LRT Stations] shows the light rail stops; take the Blue Line to the Cedar-Riverside stop for the Wilson Library, University of Minnesota venue.

== Schedule ==
* breakfast each day around 8:30am
* lunch every day around 12:30pm

== Social Events ==

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''MapServer''':
** placeholder target
* add your project

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Sun
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="25"|Fri
!width="25"|Sat
!width="25"|Sun
!width="60"|Likelihood
!width="30"|Food Restrictions
|-
| 1 ||[[Steve Lime]] || US || steve.lime@state.mn.us || State of Minnesota || MapServer || x || x || x || x || x || x || x || x || Certain ||
|-
| 2||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PROJ, GDAL, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 3||[[Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entinwe, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 4||[[User:jimk|Jim Klassen]] || US || jklassen@sharedgeo.org || SharedGeo || MapServer, GDAL, GeoMoose || || x || x || x || x || x || x || || Certain ||
|-
| 5||[[User:blammo|Bob Basques]] || US || bbasques@sharedgeo.org || SharedGeo || MapServer, GeoMoose || x || x || x || x || x || x || x || || Certain ||
|-
| 6||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey@cleverelephant.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 7||[[User:theduckylittle|Dan "Ducky" Little]] || US || theduckylittle@gmail.com || || MapServer, GeoMoose || || x || x || x || x || x || x || || Certain || No pref
|-
| 8||[[User:Dmorissette|Daniel Morissette]] || CA || dmorissette@mapgears.com || Mapgears || MapServer, GDAL/OGR || || x || x || x || x || x || x || || 99% ||
|-
| 9 ||[[Kari Geurts]] || US || kari.geurts@state.mn.us || State of Minnesota || || x || x || x || x || x || x || x || x || Certain ||
|-
| 10 ||[[Even Rouault]] || France || even.rouault at spatialys.com || Spatialys || GDAL/OGR, PROJ, Mapserver || || || x || x || x || x || || || 50% ||
|-
| 11 ||[[Piero Toffanin]] || US || pt at masseranolabs.com || MasseranoLabs || OpenDroneMap || || || x || x || x || x || || || 50% ||
|-
| 12 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl@eox.at || EOX || MapServer, EOxServer || || x || x || x || x || || || || 50% ||
|-
| 13 ||[[User:normanb|Norman Barker]] || US || norman@tiledb.io || TileDB || GDAL || || || x || x || x || x || || || Certain ||
|-
| # ||[[User:your osgeo profile|Your name]] || DE || email || organization || project || x || x || x || x || x || x || x || x || ? || ?
|}

== Communication ==

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

== Costs ==

Participants should plan for the following costs:

* Travel to Minneapolis/St. Paul
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:B_plug.jpg]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place May 14-17, 2019.

We expect about 50 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place at the University of Minnesota - Twin Cities in Minneapolis and will be hosted by [https://research.umn.edu/units/uspatial, U-Spatial] and organized by [https://www.sharedgeo.org/, SharedGeo] and members of the local OSGeo user group (TCMUG).

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2019/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.

== Event Owner ==
* SharedGeo
* U-Spatial
* [[User:Sdlime|Steve Lime]]
* [[User:Kaguerts|Kari Geurts]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!
[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Philadelphia Code Sprint 2015

2015-01-21T22:40:00Z

Wiki-Normanb: /* Participants */

'''Gold Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-LocationTech.png‎|300px|LocationTech|link=http://www.locationtech.org]]
 
[http://www.locationtech.org LocationTech]
|
|}

'''Silver Sponsors'''

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Airborne-Interactive.png|200px|Airborne Interactive|link=http://www.airborne.aero/]]
 
[http://www.airborne.aero/ Airborne Interactive]
|
|}

'''Bronze Sponsors'''
{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-AGI.png|100px|AGI|link=http://www.cesiumjs.org/]]
 
[http://www.cesiumjs.org/ AGI]
|
[[File:Logo-CartoDB-sponsorship.png|150px|CartoDB|link=http://www.cartodb.com]]
 
[http://www.cartodb.com CartoDB]
|
[[File:Logo-CoordinateSolutions.png|150px|Coordinate Solutions|link=http://www.coordinatesolutions.com]]
 
[http://www.coordinatesolutions.com Coordinate Solutions]
|
|}

{| border=0 cellspacing=15 cellpadding=10
|
[[File:Logo-Hobu.png|100px|Hobu|link=http://www.hobu.co]]
 
[http://www.hobu.co Hobu]
|
[[File:Logo-Mapzen.png|100px|Mapzen|link=http://www.mapzen.com]]
 
[http://www.mapzen.com/ Mapzen]
|
[[File:MobileGeographics 400.png|90px|Mobile Geographics|link=http://www.mobilegeographics.com/]]
 
[http://www.mobilegeographics.com Mobile Geographics]
|
[[File:logo-openscg.png|150px|OpenSCG|link=http://www.openscg.com]]
 
[http://www.openscg.com OpenSCG]
|}

'''Event Organizer'''

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

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:

* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009))

While past code sprints have targeted
members of the "C Tribe" (e.g., MapServer, GRASS, GDAL, Proj, PostGIS,
MapGuide, OpenLayers), other open source geospatial tribes are welcome to join the sprint.

The event organizer, Azavea, is also proposing that this be a joint code sprint with the Eclipse Foundation's LocationTech working group. There are several developers
that work on projects associated with both OSGeo and LocationTech, and we believe
it be an opportunity for some healthy exchange and collaboration.

== Venue ==

=== Potential Workspace ===

Azavea's office is in Center City Philadelphia and we can host up to 40 people. However, based on the number of people attending in Vienna, we would like to plan for more. We currently expect to use the following venue:

'''Friends Center''' - http://www.friendscentercorp.org/ - Conference Center operated by the Society of Friends; has wifi, but not enough bandwidth, so would have to push for augmentation. We will occupy the Cherry St Room, which includes some breakout rooms around it. Friends Center is in a central location, close to public transit and has space for 75 - 100 people. It is located at 1501 Cherry Street, Philadelphia, PA 19102.

We may also use Azavea's office and other location for social events.

=== Philadelphia ===

The three potential sites are all walking distance to:
* Reading Terminal Market
* Chinatown
* City Hall
* Franklin Institute
* Old City
* Liberty Bell
* Washington Square
* Rittenhouse Square
* Philadelphia Museum of Art (and other museums listed below

== Dates and Times ==

Dates:
* Welcome event: evening of Mon, Feb 9
* Sprint: Tues, Feb 10 - Fri, Feb 13 (4 days)

== Agenda ==

TBD

== Getting There ==
'''Flights''' - Philadelphia (PHL) is a hub for American/US Air and Southwest and also has a good number of international carriers with regular direct flights, including Air Canada, Air France, Lufthansa, British Air and Qatar Airways. Other regional options include Newark Airport (EWR) which has a rail link to the Newark Airport train station, which is about a 50 min train ride to Philadelphia 30th St Station. Newark airport has a broad range of international flights, including Porter Airlines from Toronto.

'''Rail''' - Philadelphia is about 2hrs from Washington DC and 1hr 15min from New York Penn Station by Amtrak rail.

'''Bus''' - Philadelphia is connected to Washington, Baltimore and New York via the Greyhound, Peter Pan, Mega Bus and Bolt Bus companies.

== Hotel ==

We have a hotel block with the Loews Hotel for $149/night

Loews Philadelphia Hotel 
1200 Market Street 
Philadelphia, PA, 19107 
http://www.loewshotels.com/philadelphia-hotel/ 
Phone:215-627-1200 

Reservations:1-888-575-6397 
Use code AZAV15 for group rate

And you can book online at https://resweb.passkey.com/Resweb.do?mode=welcome_ei_new&eventID=12682514

== Costs ==

Participants should plan for the following costs:

* Travel to Philadelphia
* Accommodation for four nights
* Registration fee (optional)

== Project Plans ==

TBD

* Cesium / MapServer Suite / PostGIS : Discussions on streaming 3D vector data (buildings)
** Vincent Picavet, Vincent Mora, ADDYOURNAME

== 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 70 - 100. Please add your name and the projects
you are hoping to sprint and note the likeliness of your attendance as well as
the preferred dates.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Arrival || Departure || Accommodation || Work on || Notes
|-
| 1 || [[User:rcheetham|Robert Cheetham]] || US || first day || last day || Home || TBD || Definite - No special needs
|-
| 2 || Kenny Shepard || US || first day || last day || Home || TBD || Likely
|-
| 3 || Rob Emanuele || US || first day || last day || Home || GeoTrellis || Likely
|-
| 4 || Michael Smith || US || first day || last day || || PDAL, MapServer || Likely
|-
| 6 || Howard Butler || US || first day || last day || Loews Hotel || PDAL, GDAL, libspatialindex || Booked
|-
| 7 || Daniel Morissette || CA || Mon @4pm || Friday am || Loews Hotel || MapServer, GDAL/OGR || Booked
|-
| 8 || Michael P. Gerlek || US || first day || last day || Loews Hotel || PDAL and friends || Almost certainly
|-
| 9 || Stephan Meißl || AT || first day || last day || || MapServer || Likely
|-
|10 || Brad Chambers || US || first day || last day || Loews Hotel || PDAL || Likely
|-
|11 || Andrew Ross || CA || first day || last day, bit early || [https://www.marriott.com/hotels/travel/phlri-residence-inn-philadelphia-center-city/ Residence Inn Philly Center] || Various || Booked
|-
|12 || Steve Lime || US || first day || last day || TBD || MapServer || Booked
|-
|13 || Connor Manning || US || first day || last day || Loews Hotel || PDAL || Booked
|-
|14 || Andrew Bell || US || first day || last day || Loews Hotel || PDAL || Booked
|-
|15 || [[User:Jive|Jody Garnett]] || CA || first day || last day+1 || || uDig || Booked
|-
|16 || Markus Schütz || AT || first day || last day || TBD || Potree|| Likely
|-
|17 || [[Jeff McKenna]] || CA || Tues (evening) || Saturday || TBD || MapServer || Likely
|-
|18 || Thomas Bonfort || FR ||first day || Sunday || TBD || MapServer || Booked
|-
|19 || Patrick Cozzi || US || first day || last day || Home || Cesium || Likely
|-
|20 || Matt Amato || US || first day || last day || Home || Cesium || Likely
|-
|21 || Dan Bagnell || US || first day || last day || Home || Cesium || Likely
|-
|22 || Tom Fili || US || first day || last day || Home || Cesium || Likely
|-
| 23 || Uday Verma || US || first day || last day || Loews Hotel || PDAL, plas.io || Booked
|-
| 24 || Eugene Cheipesh || US || first day || last day || Home || GeoTrellis || Likely
|-
| 25 || Vincent Mora || FR || first day || last day || TBD || Cesium, PostGIS || Very Likely
|-
| 26 || Vincent Picavet || FR || first day || last day || TBD || PointClouds, PostGIS, Cesium || Very Likely
|-
| 27 || Andrew Thompson || US || first day || last day || Home || TBD || Definite - organizing
|-
| 28 || Norman Barker || US || first day || last day || TBD || libspatialindex, gdal, pouchdb || Definite
|}

== Individual Preparation ==

* Bring your own computer
* Install SVN, Git and other dev tools, and come with a working development environment
* Spend some time getting to know the code base and open issues, if possible

== FAQ ==

* Is the Philadelphia 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 ==

=== Museums ===
* Philadelphia Museum of Art
* Barnes Foundation
* Rodin Museum
* Pennsylvania Academy of Fine Arts
* African American Museum in Philadelphia
* National Museum of Jewish-American History
* Academy of Natural Sciences
* U-Penn Museum of Anthropology and Archaology
* Rosenbach Museum
* Independence Seaport Museum
* Mutter Museum
* Eastern State Penitentiary
* Philadelphia History Museum

=== Tours ===
* Rocky Movie Location Tour - South Philadelphia
* Taste of Philadelphia Food Tour - Reading Terminal Market
* Emergence of a Modern Metropolis Philadelphia Walking Tour - Philadelphia Center for Architecture

=== Music ===
* WXPN's Free at Noon - Free concerts at WXPN on Fridays at Noon
* Art After Five - Concerts in the museum on Friday evenings

=== Sports ===
* Flyers (NHL) - Various dates
* 76ers (NBA) - Various dates
* Union (MLS) - Various dates
* Wings (NLL) - Various dates

=== Breweries ===
In Philadelphia:
* Yards Brewing Co
* Philadelphia Brewing Co
* Triumph Brewing Co
* Yuengling Brewing Co
* Dock Street Brewing Co
* Manayunk Brewery & Restaurant
* Nodding Head Brewery & Restaurant

Nearby Philadelphia:
* Flying Fish Brewery
* Iron Hill Brewery & Restaurant
* Sly Fox Beer
* Victory Brewing Co
* McKenzie Brew House

== Sponsors ==

We have three sponsorship levels:

* Gold: >$2500
* Silver: $1500
* Bronze: $750

We encourage sponsors to support nutriment and entertainment for the
sprinters as they work hard and play hard for four or five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following honors:

* Your logo or portrait at the top of this page
* 30-min slot to talk about how you are using FOSS GIS at the sprint
* Mention in all of our public communication
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)

To sponsor, please contact Robert Cheetham (cheetham at azavea dot com) directly.

=== 2015 Sponsors ===
==== Gold ====
[http://www.locationtech.org/ LocationTech]
==== Silver ====
[http://www.airborne.aero/ Airborne Interactive]
==== Bronze ====
[http://www.agi.com/ AGI]
[http://www.cartodb.com CartoDB]
[http://www.coordinatesolutions.com/ Coordinate Solutions]
[http://www.hobu.co Hobu]
[http://www.mapzen.com/ Mapzen]
[http://www.mobilegeographics.com Mobile Geographics]
[http://www.openscg.com OpenSCG]

==== Event Organizer ====
[http://www.azavea.com/ Azavea]

== Budget ==

Our expenses include:

* lodging
* meals
* social activities

We will cover our expenses in three ways:

* sponsorships
* participant registration fees
* surplus from previous years

EbRIM

2007-03-21T03:52:18Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog. It is intentionally going to focus on the use case, rather than the technology involved. The only mention of technology buzzwords will be now in mentioning that the ebXML documents can be generated using a XSL stylesheet from OGC W*S services (use the xsl document() function to recursively call the describe function), and Omar can be interfaced using SOAP, JAXR, or a RESTful KVPs. In addition Omar can classify objects using all the standard OGC/ISO taxonomies. Technical comments will be in italics.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

Rather than going into usual use case scenarios of pre/post conditions, basic flow and alternative flows this document will story board the use case basic flow using screenshots from Omar.

=== Search Use Case ===
[[Image:Search.jpeg]]

* Search
** Search by bbox
''Using the gml:EnvelopeType slot for a ebRIM extrinsic object (a dataset in this case!) we have a trigger in PostGIS to create a spatial index for optimising geometry searches. A custom adhoc query allows searching the metadata catalog with any geometry that can be expressed in (extended) well known text.''
*** Specify search by using an adhoc findByWKT query and list the results
[[Image:WktQuery.jpeg]]

Drill down and find the service offering the data
[[Image:EbRIMDetails.JPG]]

Find the service, organisation, contact info, fees, access constraints, extents offering this dataset.

** Search by classification
''Perform a service search based on a ISO 19119 Geographic services taxonomy classification''
''/urn:x-ogc:specification:csw-ebrim:ClassificationScheme:ISO-19119:Services/2000/2300/OGC-WCS''

[[Image:ServiceQuery.JPG]]

Drill down and find the organisation, contact info, fees, access constraints, datasets and extents offered by this service

*** Search by keywords
''Perform a language dependent search (ebXML documents support native language based description and names) for datasets and services''
[[Image:KeywordsSearch.JPG]]

Drill down and find the services/datasets, contact info, fees, access constraints and extents.

=== Discover Use Case ===
[[Image:Discover.jpeg]]

''Since we are using standard classifications, the difference between search and discovery is minimal. We can '''discover''' using the web based gui, jaxr, soap, and RESTful invocation''. See above.

=== Process Use Case ===
[[Image:Process.jpeg]]

''The process use case is the most interesting to the developer, it allows the search of the catalog for data and processing services according to ISO taxonomies, and then to '''register''' the output of the processing service with the same catalog - the mind boggles as to how powerful this can be''

'''Screenshot to come - watch this space!!'''

EbRIM

2007-03-21T03:44:21Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog. It is intentionally going to focus on the use case, rather than the technology involved. The only mention of technology buzzwords will be now in mentioning that the ebXML documents can be generated using a XSL stylesheet from OGC W*S services, and Omar can be interfaced using SOAP, JAXR, or a RESTful KVPs. In addition Omar can classify objects using all the standard OGC/ISO taxonomies. Technical comments will be in italics.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

Rather than going into usual use case scenarios of pre/post conditions, basic flow and alternative flows this document will story board the use case basic flow using screenshots from Omar.

=== Search Use Case ===
[[Image:Search.jpeg]]

* Search
** Search by bbox
''Using the gml:EnvelopeType slot for a ebRIM extrinsic object (a dataset in this case!) we have a trigger in PostGIS to create a spatial index for optimising geometry searches. A custom adhoc query allows searching the metadata catalog with any geometry that can be expressed in (extended) well known text.''
*** Specify search by using an adhoc findByWKT query and list the results
[[Image:WktQuery.jpeg]]

Drill down and find the service offering the data
[[Image:EbRIMDetails.JPG]]

Find the service, organisation, contact info, fees, access constraints, extents offering this dataset.

** Search by classification
''Perform a service search based on a ISO 19119 Geographic services taxonomy classification''
''/urn:x-ogc:specification:csw-ebrim:ClassificationScheme:ISO-19119:Services/2000/2300/OGC-WCS''

[[Image:ServiceQuery.JPG]]

Drill down and find the organisation, contact info, fees, access constraints, datasets and extents offered by this service

*** Search by keywords
''Perform a language dependent search (ebXML documents support native language based description and names) for datasets and services''
[[Image:KeywordsSearch.JPG]]

Drill down and find the services/datasets, contact info, fees, access constraints and extents.

=== Discover Use Case ===
[[Image:Discover.jpeg]]

''Since we are using standard classifications, the difference between search and discovery is minimal. We can '''discover''' using the web based gui, jaxr, soap, and RESTful invocation''. See above.

=== Process Use Case ===
[[Image:Process.jpeg]]

''The process use case is the most interesting to the developer, it allows the search of the catalog for data and processing services according to ISO taxonomies, and then to '''register''' the output of the processing service with the same catalog - the mind boggles as to how powerful this can be''

'''Screenshot to come - watch this space!!'''

EbRIM

2007-03-21T03:42:42Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog. It is intentionally going to focus on the use case, rather than the technology involved. The only mention of technology buzzwords will be now in mentioning that the ebXML documents can be generated using a XSL stylesheet from OGC W*S services, and Omar can be interfaced using SOAP, JAXR, or a RESTful KVPs. In addition Omar can classify objects using all the standard OGC/ISO taxonomies. Technical comments will be in italics.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

Rather than going into usual use case scenarios of pre/post conditions, basic flow and alternative flows this document will story board the use case basic flow using screenshots from Omar.

=== Search Use Case ===
[[Image:Search.jpeg]]

* Search
** Search by bbox
''Using the gml:EnvelopeType slot for a ebRIM extrinsic object (a dataset in this case!) we have a trigger in PostGIS to create a spatial index for optimising geometric search. A custom adhoc query allows searching the metadata catalog with any geometry that can be expressed in (extended) well known text.''
*** Specify search by using an adhoc findByWKT query and list the results
[[Image:WktQuery.jpeg]]

Drill down and find the service offering the data
[[Image:EbRIMDetails.JPG]]

Find the service, organisation, contact info, fees, access constraints, extents offering this dataset.

** Search by classification
''Perform a service search based on a ISO 19119 Geographic services taxonomy classification''
''/urn:x-ogc:specification:csw-ebrim:ClassificationScheme:ISO-19119:Services/2000/2300/OGC-WCS''

[[Image:ServiceQuery.JPG]]

Drill down and find the organisation, contact info, fees, access constraints, datasets and extents offered by this service

*** Search by keywords
''Perform a language dependent search (ebXML documents support native language based description and names) for datasets and services''
[[Image:KeywordsSearch.JPG]]

Drill down and find the services/datasets, contact info, fees, access constraints and extents.

=== Discover Use Case ===
[[Image:Discover.jpeg]]

''Since we are using standard classifications, the difference between search and discovery is minimal. We can '''discover''' using the web based gui, jaxr, soap, and RESTful invocation''. See above.

=== Process Use Case ===
[[Image:Process.jpeg]]

''The process use case is the most interesting to the developer, it allows the search of the catalog for data and processing services according to ISO taxonomies, and then to '''register''' the output of the processing service with the same catalog - the mind boggles as to how powerful this can be''

'''Screenshot to come - watch this space!!'''

EbRIM

2007-03-21T03:38:59Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog. It is intentionally going to focus on the use case, rather than the technology involved. The only mention of technology buzzwords will be now in mentioning that the ebXML documents can be generated using a XSL stylesheet from OGC W*S services, and Omar can be interfaced using SOAP, JAXR, or a RESTful KVPs. In addition Omar can classify objects using all the standard OGC/ISO taxonomies. Technical comments will be in italics.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

Rather than going into usual use case scenarios of pre/post conditions, basic flow and alternative flows this document will story board the use case basic flow using screenshots from Omar.

=== Search Use Case ===
[[Image:Search.jpeg]]

* Search
** Search by bbox
''Using the gml:EnvelopeType slot for a ebRIM extrinsic object (a dataset in this case!) we have a trigger in PostGIS to create a spatial index for optimising geometric search. A custom adhoc query allows searching the metadata catalog with any geometry that can be expressed in (extended) well known text.''
*** Specify search by using an adhoc findByWKT query and list the results
[[Image:WktQuery.jpeg]]

Drill down and find the service offering the data
[[Image:EbRIMDetails.JPG]]

Find the service, organisation, contact info, fees, access constraints, extents offering this dataset.

** Search by classification
''Perform a service search based on a ISO 19119 Geographic services taxonomy classification''
''/urn:x-ogc:specification:csw-ebrim:ClassificationScheme:ISO-19119:Services/2000/2300/OGC-WCS''

[[Image:ServiceQuery.JPG]]

Drill down and find the organisation, contact info, fees, access constraints, datasets and extents offered by this service

*** Search by keywords
''Perform a language dependent search (ebXML documents support native language based description and names) for datasets and services''
[[Image:KeywordsSearch.JPG]]

Drill down and find the services/datasets, contact info, fees, access constraints and extents.

=== Discover Use Case ===
[[Image:Discover.jpeg]]

''Since we are using standard classifications, the difference between search and discovery is minimal. We can '''discover''' using the web based gui, jaxr, soap, and RESTful invocation''. See above.

=== Process Use Case ===
[[Image:Process.jpeg]]

EbRIM

2007-03-21T03:37:05Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog. It is intentionally going to focus on the use case, rather than the technology involved. The only mention of technology buzzwords will be now in mentioning that the ebXML documents can be generated using a XSL stylesheet from OGC W*S services, and Omar can be interfaced using SOAP, JAXR, or a RESTful KVPs. In addition Omar can classify objects using all the standard OGC/ISO taxonomies. Technical comments will be in italics.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

Rather than going into usual use case scenarios of pre/post conditions, basic flow and alternative flows this document will story board the use case basic flow using screenshots from Omar.

=== Search Use Case ===
[[Image:Search.jpeg]]

* Search
** Search by bbox
''Using the gml:EnvelopeType slot for a ebRIM extrinsic object (a dataset in this case!) we have a trigger in PostGIS to create a spatial index for optimising geometric search. A custom adhoc query allows searching the metadata catalog with any geometry that can be expressed in (extended) well known text.''
*** Specify search by using an adhoc findByWKT query and list the results
[[Image:WktQuery.jpeg]]

Drill down and find the service offering the data
[[Image:EbRIMDetails.JPG]]

Find the service, organisation, contact info, fees, access constraints, extents offering this dataset.

** Search by classification
''Perform a service search based on a ISO 19119 Geographic services taxonomy classification''
''/urn:x-ogc:specification:csw-ebrim:ClassificationScheme:ISO-19119:Services/2000/2300/OGC-WCS''

[[Image:ServiceQuery.JPG]]

Drill down and find the organisation, contact info, fees, access constraints, datasets and extents offered by this service

*** Search by keywords
''Perform a language dependent search (ebXML documents support native language based description and names) for datasets and services''
[[Image:KeywordsSearch.JPG]]

Drill down and find the services/datasets, contact info, fees, access constraints and extents.

=== Discover Use Case ===
[[Image:Discover.jpeg]]

=== Process Use Case ===
[[Image:Process.jpeg]]

EbRIM

2007-03-21T03:34:24Z

Wiki-Normanb:

File:KeywordsSearch.JPG

2007-03-21T03:33:44Z

Wiki-Normanb:

EbRIM

2007-03-21T03:28:42Z

Wiki-Normanb:

EbRIM

2007-03-21T03:26:51Z

Wiki-Normanb:

File:ServiceQuery.JPG

2007-03-21T03:26:03Z

Wiki-Normanb: ebRIM service Query

ebRIM service Query

EbRIM

2007-03-21T03:22:58Z

Wiki-Normanb:

EbRIM

2007-03-21T03:22:11Z

Wiki-Normanb:

File:EbRIMDetails.JPG

2007-03-21T03:20:49Z

Wiki-Normanb:

File:WktQuery.jpeg

2007-03-21T03:17:05Z

Wiki-Normanb: Omar WKT Query

Omar WKT Query

EbRIM

2007-03-21T03:11:37Z

Wiki-Normanb:

EbRIM

2007-03-21T03:10:55Z

Wiki-Normanb:

EbRIM

2007-03-21T03:06:01Z

Wiki-Normanb:

EbRIM

2007-03-21T03:05:31Z

Wiki-Normanb:

EbRIM

2007-03-21T03:03:46Z

Wiki-Normanb:

EbRIM

2007-03-21T02:58:57Z

Wiki-Normanb:

File:Process.jpeg

2007-03-21T02:58:27Z

Wiki-Normanb: ebRIM process use case

ebRIM process use case

EbRIM

2007-03-21T02:45:04Z

Wiki-Normanb:

File:Discover.jpeg

2007-03-21T02:44:29Z

Wiki-Normanb: ebrim discover use case

ebrim discover use case

EbRIM

2007-03-21T02:16:16Z

Wiki-Normanb:

EbRIM

2007-03-21T02:15:44Z

Wiki-Normanb:

EbRIM

2007-03-20T23:34:23Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

=== Search Use Case ===
[[Image:Search.jpeg]]

File:Search.jpeg

2007-03-20T23:33:54Z

Wiki-Normanb: Catalog Search Use Case

Catalog Search Use Case

EbRIM

2007-03-20T23:33:09Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

=== Search Use Case ===
[[Image:Example.jpg]]

EbRIM

2007-03-20T23:25:40Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case and will hopefully assist the reader in evaluating the usefulness of the ebRIM metadata catalog.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

EbRIM

2007-03-20T23:24:15Z

Wiki-Normanb:

== ebRIM ==

=== Introduction ===

This isn't a discussion about ebRIM and its pro's and con's, for that browse the IRC archives and pick the flame bait that is to your taste :-).

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case.

''Full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

EbRIM

2007-03-20T23:23:54Z

Wiki-Normanb:

== ebRIM ==

This isn't a discussion about ebRIM and its pro's and con's, for that browse the IRC archives and pick the flame bait that is to your taste :-).

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case.

''full details on setting up ebxmlrr (omar) with the ogc profile and PostGIS are available here http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc''

EbRIM

2007-03-20T23:22:17Z

Wiki-Normanb:

EbRIM

2007-03-20T23:21:49Z

Wiki-Normanb:

== ebRIM ==

This isn't a discussion about ebRIM and its pro's and con's, for that browse and IRC lists and pick the flame bait that is to your taste.

This is a discussion of how a user (developer or end user) would use an ebRIM catalog for a simple use case.

Geodata Metadata Requirements

2007-03-20T23:20:17Z

Wiki-Normanb:

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 '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]]
* [https://geodata.osgeo.org/servlets/SummarizeList?listName=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