OSGeo - User contributions [en]

Board Meeting 2012-08-09

2012-08-01T08:48:03Z

Wiki-Desruisseaux: /* Agenda */

[[Category:Board]]
[[Category:Board Meetings 2012]]

This board meeting is scheduled for the 9th of August 2012 [http://www.timeanddate.com/worldclock/fixedtime.html?year=2012&month=08&day=09&hour=17&min=0&sec=0 at 17:00 UTC] on IRC and follow up voting on Skype or by email.

== Agenda ==
* Review past minutes: [[Board Meeting 2012-07-12]]
* Appoint secretary
* Action items from last and previous meetings
*# Ongoing: ''Arnulf to set up, schedule and run 2012 elections''
*# Peter Batty and Jo Cook to work on getting FOSS4G 2011 material online - discussions under way, need to get some (small) volunteer effort to pull things together
*# '''mpg''' to do inventory of committees and local chapters (carried over from previous meeting)
*#* Clean out and update Charter Membership (carried over from previous meeting again)
*# '''Daniel''' to resolve 'c3 vs. 'c6 issue
*# '''Jo''' report from the ELOgeo importation process
*# '''Daniel''' to decide what to do about QuickBooks issue
* Beijing FOSS4G conference actions:
** Cancellation notice from Beijing LOC (formal response to LOC and public announcement)
** Decide on location for AGM, Sol Katz, F2F board meeting (see: http://lists.osgeo.org/pipermail/board/2012-July/009809.html)
** Update or redirect http://2012.foss4g.org/ with cancellation notice, ref to FOSS4G 2013, location of AGM/Sol Katz/F2F, ???
* Funding request for the QGIS Developer Meeting in October 2012 (1,000€, see http://lists.osgeo.org/pipermail/board/2012-June/009701.html)
* Funding request for the First Latin American Conference of Free and Open Source GIS in October 2012. Mauricio Miranda presents the initiative
* Quick finances update - invoices sent to sponsors
* Continue dialog on how to associate with Eclipse (see board list mail from Jo)
* PDX-OSGeo local chapter formal recognition, [http://wiki.osgeo.org/wiki/PDX_OSGEO_Local_Chapter_Recognition some notes on what has been done]
* Finalize confirmation of board voting procedure - left over from a couple years ago - Frank to summarize.
* Clarify that the rights granted to code contributors who signed the [http://lists.osgeo.org/pipermail/board/2012-July/009912.html GeoTools Copyright Assignment]. Specifically, does it include the right to distribute their own work under a different OSI approved license?
* How to deal with alleged impartiality and favoritism of OSGeo, see mail threads around [http://lists.osgeo.org/pipermail/board/2012-July/009901.html "Asking permission for re-licensing..."] and follow-ups
** Identifying when a committee has been put in situation of Judge and Party (see the [http://sourceforge.net/mailarchive/forum.php?forum_name=geotools-administration&max_rows=25&style=nested&viewmonth=201207 geotools-admin thread])
* ''please add items''
* Confirm next meeting time and date [[Board Meeting 2012-xx-xx]]

== Minutes ==
* logistics
** detailed conversation log: http://logs.qgis.org/osgeo/%23osgeo.2012-08-09.log
** Attending:
** Absent:
** Chair:
** Secretary:

==== Assigned Tasks ====
# ...

==== Motions ====
# ...

==== Notes ====
* ...

Board Meeting 2012-08-09

2012-08-01T08:40:25Z

Wiki-Desruisseaux: /* Agenda */

[[Category:Board]]
[[Category:Board Meetings 2012]]

This board meeting is scheduled for the 9th of August 2012 [http://www.timeanddate.com/worldclock/fixedtime.html?year=2012&month=08&day=09&hour=17&min=0&sec=0 at 17:00 UTC] on IRC and follow up voting on Skype or by email.

== Agenda ==
* Review past minutes: [[Board Meeting 2012-07-12]]
* Appoint secretary
* Action items from last and previous meetings
*# Ongoing: ''Arnulf to set up, schedule and run 2012 elections''
*# Peter Batty and Jo Cook to work on getting FOSS4G 2011 material online - discussions under way, need to get some (small) volunteer effort to pull things together
*# '''mpg''' to do inventory of committees and local chapters (carried over from previous meeting)
*#* Clean out and update Charter Membership (carried over from previous meeting again)
*# '''Daniel''' to resolve 'c3 vs. 'c6 issue
*# '''Jo''' report from the ELOgeo importation process
*# '''Daniel''' to decide what to do about QuickBooks issue
* Beijing FOSS4G conference actions:
** Cancellation notice from Beijing LOC (formal response to LOC and public announcement)
** Decide on location for AGM, Sol Katz, F2F board meeting (see: http://lists.osgeo.org/pipermail/board/2012-July/009809.html)
** Update or redirect http://2012.foss4g.org/ with cancellation notice, ref to FOSS4G 2013, location of AGM/Sol Katz/F2F, ???
* Funding request for the QGIS Developer Meeting in October 2012 (1,000€, see http://lists.osgeo.org/pipermail/board/2012-June/009701.html)
* Funding request for the First Latin American Conference of Free and Open Source GIS in October 2012. Mauricio Miranda presents the initiative
* Quick finances update - invoices sent to sponsors
* Continue dialog on how to associate with Eclipse (see board list mail from Jo)
* PDX-OSGeo local chapter formal recognition, [http://wiki.osgeo.org/wiki/PDX_OSGEO_Local_Chapter_Recognition some notes on what has been done]
* Finalize confirmation of board voting procedure - left over from a couple years ago - Frank to summarize.
* Clarify that the rights granted to code contributors who signed the [http://lists.osgeo.org/pipermail/board/2012-July/009912.html GeoTools Copyright Assignment]. Specifically, does it include the right to distribute their own work under a different OSI approved license?
* How to deal with alleged impartiality and favoritism of OSGeo, see mail threads around [http://lists.osgeo.org/pipermail/board/2012-July/009901.html "Asking permission for re-licensing..."] and follow-ups
** Identifying when a committee has been put in situation of Judge and Party
* ''please add items''
* Confirm next meeting time and date [[Board Meeting 2012-xx-xx]]

== Minutes ==
* logistics
** detailed conversation log: http://logs.qgis.org/osgeo/%23osgeo.2012-08-09.log
** Attending:
** Absent:
** Chair:
** Secretary:

==== Assigned Tasks ====
# ...

==== Motions ====
# ...

==== Notes ====
* ...

Benchmarking 2011

2011-08-03T15:31:56Z

Wiki-Desruisseaux: Typo in Johann name.

== Basic Premise ==

Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers.

== Communication ==

Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking

Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)

=== Next IRC Meeting ===

* Wed August 3rd, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=03&hour=14&min=0&sec=0 14:00:00 UTC]
** Provisional Agenda:
*** Status of OSM vector styling from all teams
*** Discuss rasters to be used
*** Discuss testing methodology

=== Previous IRC Meetings ===

* [[Benchmarking_2011/MeetingLog | Meeting Log]]

== Participants ==

''Server Teams:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Confirmed'''
|-
| Cadcorp GeognoSIS
| [[User:Mpd|Martin Daly]]
| Yes
|-
| Constellation-SDI
| [[User:Desruisseaux|Martin Desruisseaux]], [[User:Eclesia|Johann Sorel]]
| Yes
|-
| GeoServer
| Andrea Aime, [[User:groldan|Gabriel Roldan]]
| Yes
|-
| Mapnik
| [[User:Springmeyer|Dane Springmeyer]]
| Yes
|-
| MapServer
| [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]
| Yes
|-
| Oracle MapViewer
| [[User:LJQian|LJ Qian]]
| Yes
|-
| QGIS Server
| [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler
| Yes
|}

''Data Teams:''

{| border="1"
|-
| '''Data Package'''
| '''Team Leader'''
| '''Comment'''
|-
| [http://imposm.org/docs/imposm/latest/ Imposm]
| Oliver Tonnhofer
| tool to be used to import OSM data
|-
| SPOT imagery
| [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]
|
|}

''Not Participating:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Comment'''
|-
| Erdas Apollo
| [mailto:dimitri.monie@erdas.com Dimitri Monie]
| Response from Luc Donea: Unable to participate
|-
| ESRI ArcServer
| Satish Sankaran
| discussing internally
|-
| MapGuide Open Source
| TBD (contacted mapguide-internals)
| Response from Jason Birch: Unable to participate
|}

== Timeline ==

{| border="1"
|-
| January 1st, 2011
| begin contacting all mapping servers
|-
| March 1st, 2011
| commitment due by all interested mapping servers
|-
| March 2nd, 2011
| exercise begins (and weekly meetings)
|-
| June 1st, 2011
| final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)
|-
| September 1st, 2011
| no further testing
|-
| September 2nd, 2011
| final results due from all teams
|-
| September 12-16, 2011
| present results at FOSS4G2011
|}

== Rules of Engagement (DRAFT) ==

# All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.
# Comparisons will be made of the best available version of the software, be it a formal release or a development version.
# One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.
# Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used.
# WMS output formats to be used will be png8 and png24 where possible

== Documenting Server Details and Differences ==

It is the responsibility of each team to document their setup with regard to data.

Please keep your notes either on a wiki subpage or in svn (or both).

Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.

A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes

And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011

== Datasets ==

=== OSM Vectors ===
* [[Benchmarking_2011/DB_Schema]]
* [[Benchmarking_2011/Imposm]]
* Sample styling: [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&layers=default&mode=map&map_imagetype=png&mapext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&imgext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&map_size=800+800&imgx=400&imgy=400&imgxy=800+800 mapserv6]
** [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Linux (with OpenLayers)]
** [http://12.189.158.75:8081/cgi-bin/mapserv.exe?MAP=C:/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Win64 (with OpenLayers)]

== SVN ==

The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).

== Hardware ==

windows_wms_bm (windows server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Windows Server 64bit

linux_wms_bm (linux server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Centos 5.5 x86-64

== External Related Links ==

* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]
* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]
* [[FOSS4G Benchmark|FOSS4G WMS Benchmark]]
* [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]

----

[[Category:FOSS4G2011]] [[Category:FOSS4G]]

Benchmarking 2011

2011-08-03T15:30:23Z

Wiki-Desruisseaux: Added Johan Sorel to the list of participants.

== Basic Premise ==

Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers.

== Communication ==

Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking

Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)

=== Next IRC Meeting ===

* Wed August 3rd, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=03&hour=14&min=0&sec=0 14:00:00 UTC]
** Provisional Agenda:
*** Status of OSM vector styling from all teams
*** Discuss rasters to be used
*** Discuss testing methodology

=== Previous IRC Meetings ===

* [[Benchmarking_2011/MeetingLog | Meeting Log]]

== Participants ==

''Server Teams:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Confirmed'''
|-
| Cadcorp GeognoSIS
| [[User:Mpd|Martin Daly]]
| Yes
|-
| Constellation-SDI
| [[User:Desruisseaux|Martin Desruisseaux]], [[User:Eclesia|Johan Sorel]]
| Yes
|-
| GeoServer
| Andrea Aime, [[User:groldan|Gabriel Roldan]]
| Yes
|-
| Mapnik
| [[User:Springmeyer|Dane Springmeyer]]
| Yes
|-
| MapServer
| [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]
| Yes
|-
| Oracle MapViewer
| [[User:LJQian|LJ Qian]]
| Yes
|-
| QGIS Server
| [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler
| Yes
|}

''Data Teams:''

{| border="1"
|-
| '''Data Package'''
| '''Team Leader'''
| '''Comment'''
|-
| [http://imposm.org/docs/imposm/latest/ Imposm]
| Oliver Tonnhofer
| tool to be used to import OSM data
|-
| SPOT imagery
| [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]
|
|}

''Not Participating:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Comment'''
|-
| Erdas Apollo
| [mailto:dimitri.monie@erdas.com Dimitri Monie]
| Response from Luc Donea: Unable to participate
|-
| ESRI ArcServer
| Satish Sankaran
| discussing internally
|-
| MapGuide Open Source
| TBD (contacted mapguide-internals)
| Response from Jason Birch: Unable to participate
|}

== Timeline ==

{| border="1"
|-
| January 1st, 2011
| begin contacting all mapping servers
|-
| March 1st, 2011
| commitment due by all interested mapping servers
|-
| March 2nd, 2011
| exercise begins (and weekly meetings)
|-
| June 1st, 2011
| final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)
|-
| September 1st, 2011
| no further testing
|-
| September 2nd, 2011
| final results due from all teams
|-
| September 12-16, 2011
| present results at FOSS4G2011
|}

== Rules of Engagement (DRAFT) ==

# All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.
# Comparisons will be made of the best available version of the software, be it a formal release or a development version.
# One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.
# Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used.
# WMS output formats to be used will be png8 and png24 where possible

== Documenting Server Details and Differences ==

It is the responsibility of each team to document their setup with regard to data.

Please keep your notes either on a wiki subpage or in svn (or both).

Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.

A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes

And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011

== Datasets ==

=== OSM Vectors ===
* [[Benchmarking_2011/DB_Schema]]
* [[Benchmarking_2011/Imposm]]
* Sample styling: [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&layers=default&mode=map&map_imagetype=png&mapext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&imgext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&map_size=800+800&imgx=400&imgy=400&imgxy=800+800 mapserv6]
** [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Linux (with OpenLayers)]
** [http://12.189.158.75:8081/cgi-bin/mapserv.exe?MAP=C:/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Win64 (with OpenLayers)]

== SVN ==

The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).

== Hardware ==

windows_wms_bm (windows server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Windows Server 64bit

linux_wms_bm (linux server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Centos 5.5 x86-64

== External Related Links ==

* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]
* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]
* [[FOSS4G Benchmark|FOSS4G WMS Benchmark]]
* [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]

----

[[Category:FOSS4G2011]] [[Category:FOSS4G]]

Benchmarking 2011

2011-08-03T14:08:31Z

Wiki-Desruisseaux: Changed the participant name for Constellation-SDI.

== Basic Premise ==

Following up on [[Benchmarking 2010|last year's exercise]], the performance shoot-out presentation at [[FOSS4G2011]] will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers.

== Communication ==

Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking

Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use [http://webchat.freenode.net/ webchat] to connect in browser)

=== Next IRC Meeting ===

* Wed August 3rd, 2011 @ [http://timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=03&hour=14&min=0&sec=0 14:00:00 UTC]
** Provisional Agenda:
*** Status of OSM vector styling from all teams
*** Discuss rasters to be used
*** Discuss testing methodology

=== Previous IRC Meetings ===

* [[Benchmarking_2011/MeetingLog | Meeting Log]]

== Participants ==

''Server Teams:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Confirmed'''
|-
| Cadcorp GeognoSIS
| [[User:Mpd|Martin Daly]]
| Yes
|-
| Constellation-SDI
| [[User:Desruisseaux|Martin Desruisseaux]]
| Yes
|-
| GeoServer
| Andrea Aime, [[User:groldan|Gabriel Roldan]]
| Yes
|-
| Mapnik
| [[User:Springmeyer|Dane Springmeyer]]
| Yes
|-
| MapServer
| [[User:Jmckenna|Jeff McKenna]], [[User:msmitherdc|Michael Smith]]
| Yes
|-
| Oracle MapViewer
| [[User:LJQian|LJ Qian]]
| Yes
|-
| QGIS Server
| [[User:Pirmin_Kalberer|Pirmin Kalberer]], Marco Hugentobler
| Yes
|}

''Data Teams:''

{| border="1"
|-
| '''Data Package'''
| '''Team Leader'''
| '''Comment'''
|-
| [http://imposm.org/docs/imposm/latest/ Imposm]
| Oliver Tonnhofer
| tool to be used to import OSM data
|-
| SPOT imagery
| [[User:Jeffaudi|Jean-Francois (Jeff) Faudi]]
|
|}

''Not Participating:''

{| border="1"
|-
| '''Mapping Server'''
| '''Development Team Leader'''
| '''Comment'''
|-
| Erdas Apollo
| [mailto:dimitri.monie@erdas.com Dimitri Monie]
| Response from Luc Donea: Unable to participate
|-
| ESRI ArcServer
| Satish Sankaran
| discussing internally
|-
| MapGuide Open Source
| TBD (contacted mapguide-internals)
| Response from Jason Birch: Unable to participate
|}

== Timeline ==

{| border="1"
|-
| January 1st, 2011
| begin contacting all mapping servers
|-
| March 1st, 2011
| commitment due by all interested mapping servers
|-
| March 2nd, 2011
| exercise begins (and weekly meetings)
|-
| June 1st, 2011
| final testing begins (no more changes to data/styles/hardware, but changes to software is allowed)
|-
| September 1st, 2011
| no further testing
|-
| September 2nd, 2011
| final results due from all teams
|-
| September 12-16, 2011
| present results at FOSS4G2011
|}

== Rules of Engagement (DRAFT) ==

# All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.
# Comparisons will be made of the best available version of the software, be it a formal release or a development version.
# One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.
# Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.). If a team does not document the steps on this wiki then that team's test results will not be used.
# WMS output formats to be used will be png8 and png24 where possible

== Documenting Server Details and Differences ==

It is the responsibility of each team to document their setup with regard to data.

Please keep your notes either on a wiki subpage or in svn (or both).

Generally teams keep notes on setup on the wiki while they put stylesheets and scripts in svn.

A good organization for wiki pages is to create a subpage like: http://wiki.osgeo.org/wiki/Benchmarking_2011/Mapnik_notes

And create a directory in svn named {servername}/{year} like: http://svn.osgeo.org/osgeo/foss4g/benchmarking/mapnik/2011

== Datasets ==

=== OSM Vectors ===
* [[Benchmarking_2011/DB_Schema]]
* [[Benchmarking_2011/Imposm]]
* Sample styling: [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&layers=default&mode=map&map_imagetype=png&mapext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&imgext=-11690811.758434+4826833.1534376+-11687378.549609+4830266.3622626&map_size=800+800&imgx=400&imgy=400&imgxy=800+800 mapserv6]
** [http://12.189.158.78:8081/cgi-bin/mapserv6?MAP=/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Linux (with OpenLayers)]
** [http://12.189.158.75:8081/cgi-bin/mapserv.exe?MAP=C:/benchmarking/wms/2011/mapserver/osm-google.map&mode=browse&template=openlayers&layers=default MapServer Win64 (with OpenLayers)]

== SVN ==

The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/).

== Hardware ==

windows_wms_bm (windows server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Windows Server 64bit

linux_wms_bm (linux server)
* System Type: Dell PowerEdge R410
* Ship Date: 7/7/2010
* Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
* 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
* 2TB 7.2K RPM SATA
* OS: Centos 5.5 x86-64

== External Related Links ==

* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout-2010 FOSS4G2010 Benchmarking Presentation]
* [http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout FOSS4G2009 Benchmarking Presentation]
* [[FOSS4G Benchmark|FOSS4G WMS Benchmark]]
* [http://sourceforge.net/projects/wmstester/ WMSTester - tool for testing not from OSGeo]

----

[[Category:FOSS4G2011]] [[Category:FOSS4G]]

GeoTools Provenance Review

2008-07-04T10:45:05Z

Wiki-Desruisseaux: Splitted by sections.

The work is being done on a module by module basis. Review artifacts are stored in the code repostiory. Actual issues are captures in the issue track.

== Wiki ==
* [http://docs.codehaus.org/display/GEOTOOLS/GeoTools+Provenance+Review GeoTools Provenance Review]

== Issue Tracker ==
* pending

=== Library ===

These modules make up the GeoTools library itself, and form a layered architecture covering a range of geospatial activities.

* http://maven.geotools.fr/reports/modules/library/api/review.html
* http://maven.geotools.fr/reports/modules/library/cql/review.html
* http://maven.geotools.fr/reports/modules/library/xml/review.html
* http://maven.geotools.fr/reports/modules/library/data/review.html
* http://maven.geotools.fr/reports/modules/library/jdbc/review.html
* http://maven.geotools.fr/reports/modules/library/main/review.html
* http://maven.geotools.fr/reports/modules/library/metadata/review.html
* http://maven.geotools.fr/reports/modules/library/referencing/review.html
* http://maven.geotools.fr/reports/modules/library/legacy/review.html
* http://maven.geotools.fr/reports/modules/library/coverage/review.html
* http://maven.geotools.fr/reports/modules/library/render/review.html
* http://maven.geotools.fr/reports/modules/library/sample-data/review.html

=== Plug-in ===

These plug-ins slot into the GeoTools library making additional capabilities and data formats avaiable.

* http://maven.geotools.fr/reports/modules/plugin/db2/review.html
* http://maven.geotools.fr/reports/modules/plugin/wfs/review.html
* http://maven.geotools.fr/reports/modules/plugin/wms/review.html
* http://maven.geotools.fr/reports/modules/plugin/image/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-access/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-extension/review.html
* http://maven.geotools.fr/reports/modules/plugin/imagemosaic/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-postgresql/review.html
* http://maven.geotools.fr/reports/modules/plugin/geometry/review.html
* http://maven.geotools.fr/reports/modules/plugin/arcsde/review.html
* http://maven.geotools.fr/reports/modules/plugin/shapefile/review.html
* http://maven.geotools.fr/reports/modules/plugin/geotiff/review.html
* http://maven.geotools.fr/reports/modules/plugin/referencing3D/review.html
* http://maven.geotools.fr/reports/modules/plugin/gtopo30/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-hsql/review.html
* http://maven.geotools.fr/reports/modules/plugin/arcgrid/review.html
* http://maven.geotools.fr/reports/modules/plugin/property/review.html
* http://maven.geotools.fr/reports/modules/plugin/imagepyramid/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-wkt/review.html
* http://maven.geotools.fr/reports/modules/plugin/postgis/review.html

=== Extentions ===

These modules are built on top of the geotools library and add additional analysis and functionality around the abstractions captured by the core library.

* http://maven.geotools.fr/reports/modules/extension/graph/review.html
* http://maven.geotools.fr/reports/modules/extension/shapefile-renderer/review.html
* http://maven.geotools.fr/reports/modules/extension/validation/review.html
* http://maven.geotools.fr/reports/modules/extension/brewer/review.html
* http://maven.geotools.fr/reports/modules/extension/widgets-swing/review.html
* http://maven.geotools.fr/reports/modules/extension/openoffice/review.html

=== Unsupported ===

These extensions and plug-ins work with the GeoTools library, but do not yet meet their QA and Providence Review checks. While this is mostly to prevent duplication of development effort, the unsupported modules that have completed a providence review can be distributed for feedback.

* http://maven.geotools.fr/reports/modules/unsupported/go/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gml/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gpx/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mif/review.html
* http://maven.geotools.fr/reports/modules/unsupported/ogr/review.html
* http://maven.geotools.fr/reports/modules/unsupported/vpf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/wps/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gml3/review.html
* http://maven.geotools.fr/reports/modules/unsupported/hsql/review.html
* http://maven.geotools.fr/reports/modules/unsupported/tile/review.html
* http://maven.geotools.fr/reports/modules/unsupported/xml-gpx/review.html
* http://maven.geotools.fr/reports/modules/unsupported/geometryless/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mysql/review.html
* http://maven.geotools.fr/reports/modules/unsupported/tiger/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio/review.html
* http://maven.geotools.fr/reports/modules/unsupported/community-schemas/review.html
* http://maven.geotools.fr/reports/modules/unsupported/temporal/review.html
* http://maven.geotools.fr/reports/modules/unsupported/repository/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mappane/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio-hdf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/epsg-oracle/review.html
* http://maven.geotools.fr/reports/modules/unsupported/oracle-spatial/review.html
* http://maven.geotools.fr/reports/modules/unsupported/postgis-versioned/review.html
* http://maven.geotools.fr/reports/modules/unsupported/geomedia/review.html
* http://maven.geotools.fr/reports/modules/unsupported/example/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio-netcdf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/imageio-ext-gdal/review.html
* http://maven.geotools.fr/reports/modules/unsupported/directory/review.html
* http://maven.geotools.fr/reports/modules/unsupported/widgets-swing-pending/review.html
* http://maven.geotools.fr/reports/modules/unsupported/jts-wrapper/review.html
* http://maven.geotools.fr/reports/modules/unsupported/caching/review.html

=== Demo ===

These files are used as teaching aids. We are considering releasing them as public domain to aliviate any initial adotpion concerns. They are all available under a public domain license.

* http://maven.geotools.fr/reports/demo/svgsupport/review.html
* http://maven.geotools.fr/reports/demo/libraryJTS/review.html
* http://maven.geotools.fr/reports/demo/introduction/review.html

=== Build tools ===

* http://maven.geotools.fr/reports/build/scm/review.html
* http://maven.geotools.fr/reports/build/dummy/review.html
* http://maven.geotools.fr/reports/build/dummy/jaxb/review.html
* http://maven.geotools.fr/reports/build/maven/rmic/review.html
* http://maven.geotools.fr/reports/build/maven/unopkg/review.html
* http://maven.geotools.fr/reports/build/maven/javadoc/review.html
* http://maven.geotools.fr/reports/build/maven/jar-collector/review.html
* http://maven.geotools.fr/reports/build/maven/jjtree-javacc/review.html

GeoTools Provenance Review

2008-07-03T16:43:05Z

Wiki-Desruisseaux: Added the links to the review reports.

The work is being done on a module by module basis. Review artifacts are stored in the code repostiory. Actual issues are captures in the issue track.

== Wiki ==
* [http://docs.codehaus.org/display/GEOTOOLS/GeoTools+Provenance+Review GeoTools Provenance Review]

== Issue Tracker ==
* pending

== Reports ==
* http://maven.geotools.fr/reports/modules/library/api/review.html
* http://maven.geotools.fr/reports/modules/library/cql/review.html
* http://maven.geotools.fr/reports/modules/library/xml/review.html
* http://maven.geotools.fr/reports/modules/library/data/review.html
* http://maven.geotools.fr/reports/modules/library/jdbc/review.html
* http://maven.geotools.fr/reports/modules/library/main/review.html
* http://maven.geotools.fr/reports/modules/library/metadata/review.html
* http://maven.geotools.fr/reports/modules/library/referencing/review.html
* http://maven.geotools.fr/reports/modules/library/legacy/review.html
* http://maven.geotools.fr/reports/modules/library/coverage/review.html
* http://maven.geotools.fr/reports/modules/library/render/review.html
* http://maven.geotools.fr/reports/modules/library/sample-data/review.html

* http://maven.geotools.fr/reports/modules/plugin/db2/review.html
* http://maven.geotools.fr/reports/modules/plugin/wfs/review.html
* http://maven.geotools.fr/reports/modules/plugin/wms/review.html
* http://maven.geotools.fr/reports/modules/plugin/image/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-access/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-extension/review.html
* http://maven.geotools.fr/reports/modules/plugin/imagemosaic/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-postgresql/review.html
* http://maven.geotools.fr/reports/modules/plugin/geometry/review.html
* http://maven.geotools.fr/reports/modules/plugin/arcsde/review.html
* http://maven.geotools.fr/reports/modules/plugin/shapefile/review.html
* http://maven.geotools.fr/reports/modules/plugin/geotiff/review.html
* http://maven.geotools.fr/reports/modules/plugin/referencing3D/review.html
* http://maven.geotools.fr/reports/modules/plugin/gtopo30/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-hsql/review.html
* http://maven.geotools.fr/reports/modules/plugin/arcgrid/review.html
* http://maven.geotools.fr/reports/modules/plugin/property/review.html
* http://maven.geotools.fr/reports/modules/plugin/imagepyramid/review.html
* http://maven.geotools.fr/reports/modules/plugin/epsg-wkt/review.html
* http://maven.geotools.fr/reports/modules/plugin/postgis/review.html

* http://maven.geotools.fr/reports/modules/extension/graph/review.html
* http://maven.geotools.fr/reports/modules/extension/shapefile-renderer/review.html
* http://maven.geotools.fr/reports/modules/extension/validation/review.html
* http://maven.geotools.fr/reports/modules/extension/brewer/review.html
* http://maven.geotools.fr/reports/modules/extension/widgets-swing/review.html
* http://maven.geotools.fr/reports/modules/extension/openoffice/review.html

* http://maven.geotools.fr/reports/modules/unsupported/go/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gml/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gpx/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mif/review.html
* http://maven.geotools.fr/reports/modules/unsupported/ogr/review.html
* http://maven.geotools.fr/reports/modules/unsupported/vpf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/wps/review.html
* http://maven.geotools.fr/reports/modules/unsupported/gml3/review.html
* http://maven.geotools.fr/reports/modules/unsupported/hsql/review.html
* http://maven.geotools.fr/reports/modules/unsupported/tile/review.html
* http://maven.geotools.fr/reports/modules/unsupported/xml-gpx/review.html
* http://maven.geotools.fr/reports/modules/unsupported/geometryless/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mysql/review.html
* http://maven.geotools.fr/reports/modules/unsupported/tiger/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio/review.html
* http://maven.geotools.fr/reports/modules/unsupported/community-schemas/review.html
* http://maven.geotools.fr/reports/modules/unsupported/temporal/review.html
* http://maven.geotools.fr/reports/modules/unsupported/repository/review.html
* http://maven.geotools.fr/reports/modules/unsupported/mappane/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio-hdf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/epsg-oracle/review.html
* http://maven.geotools.fr/reports/modules/unsupported/oracle-spatial/review.html
* http://maven.geotools.fr/reports/modules/unsupported/postgis-versioned/review.html
* http://maven.geotools.fr/reports/modules/unsupported/geomedia/review.html
* http://maven.geotools.fr/reports/modules/unsupported/example/review.html
* http://maven.geotools.fr/reports/modules/unsupported/coverageio-netcdf/review.html
* http://maven.geotools.fr/reports/modules/unsupported/imageio-ext-gdal/review.html
* http://maven.geotools.fr/reports/modules/unsupported/directory/review.html
* http://maven.geotools.fr/reports/modules/unsupported/widgets-swing-pending/review.html
* http://maven.geotools.fr/reports/modules/unsupported/jts-wrapper/review.html
* http://maven.geotools.fr/reports/modules/unsupported/caching/review.html

* http://maven.geotools.fr/reports/demo/svgsupport/review.html
* http://maven.geotools.fr/reports/demo/libraryJTS/review.html
* http://maven.geotools.fr/reports/demo/introduction/review.html

* http://maven.geotools.fr/reports/build/scm/review.html
* http://maven.geotools.fr/reports/build/dummy/review.html
* http://maven.geotools.fr/reports/build/dummy/jaxb/review.html
* http://maven.geotools.fr/reports/build/maven/rmic/review.html
* http://maven.geotools.fr/reports/build/maven/unopkg/review.html
* http://maven.geotools.fr/reports/build/maven/javadoc/review.html
* http://maven.geotools.fr/reports/build/maven/jar-collector/review.html
* http://maven.geotools.fr/reports/build/maven/jjtree-javacc/review.html

GeoTools Project Status

2006-04-24T01:24:25Z

Wiki-Desruisseaux: /* Infrastructure Transition */

== Basics ==

; Has the project been approved for incubation by the OSGeo board?
: Yes

; Has an Incubation committee member been assigned as Mentor?
: not yet

== Infrastructure Transition ==

''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''

; Has the projectname.osgeo.org domain been populated with the projects web presence?
: We are not willing to move away from Confluence, how may I update this page with a good link?
: However, a web server may be of interest for hosting static HTML pages automatically generated like Maven reports and Javadoc.

; Is the OSGeo bug tracker being used for the project?
: No it is not, once again we have an existing bug tracker Jira which allows for collaboration with several other projects

; Is the OSGeo mailing list manager being used for the project?
: Existing mailing list and archives are hosted by SF, any chance we grab archives?

; Is the OSGeo SVN or CVS system being used for the project?
: Not at this time, moving to SVN would be of interest.

; Are binary and source downloads available from the OSGeo download area?
: Not yet, but this also would be of interest.

== Community Functioning ==

; Is there a functioning user support mechanisms (ie. mailing list)?
: There is a active developers list and user list (http://docs.codehaus.org/display/GEOTOOLS/Mailing+Lists) weekly IRC chats (http://docs.codehaus.org/display/GEOT/3.1+Internet+Relay+Chat)

; Are source and binary downloads for the package available?
: Yes and we also have a javadoc (ie api) download see http://docs.codehaus.org/display/GEOTOOLS/Downloads

; Has a Project Steering Committee been formed, and given control of the project?
: Project has an exisiting Project Management Comittee see http://docs.codehaus.org/display/GEOT/4+Roles+and+Responsibilities

; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
: The project is well document here http://docs.codehaus.org/display/GEOT/Home

; How many active developers are there? Are they from multiple organizations?
: There are around 10 developers working on geotools as part of their day job, the expanded list goes up to around 30 with commit access. The important part is the number of responsible module maintainers. While the project is made up of individuals (who happen to work for organizations such as Penn State University, Refractions Reserach, The Open Planning Project, IBM, Oracle, Google others...)

== Foundation Membership ==

; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
: The home page has, but the formal developers guide will be updated as part of the incubation process (especially with respect to any changes in project procedures).

; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
: We will have the same look and feel but are concerned with some of the limitations

== Code Copyright Review ==

; Has a [[Code Provenance Review]] document been prepared for the project?
: Not yet, we are having module mainers produce reports which will be gather up into the required document.

; Have issues raised in the provenance review been adequately addressed?
: not yet

GeoTools Incubation Progress

2006-04-24T00:54:59Z

Wiki-Desruisseaux: /* code */

GeoTools is one of the round of projects out of the gate, and as an rather old project (lots of background) with an active development community (who is busy hacking) does not expect to finish all that quickly.

The following have been produced for the iccubation process:
* [[GeoTools Project Status]]

Representative: Jody Garnett (jgarnett@refractions.net)

= Initial Impressions =

Judging from the email list the number one question is, what needs to be done? Rather wait we are going to wing it and hope for futher direction.

Now that one month has gone buy we are getting much more specific direction:
* Advice on Name
* Project Status Template: [[GeoTools Project Status]]
* Perform an IP check, see [http://docs.codehaus.org/display/GEOTOOLS/2006/04/03/IRC+Logs+-+3+April+2006 IRC Meeting with FrankW]
* Discussion of Expectations

== Community Feedback ==

The GeoTools community responded with the following questions:
* rgould: What if I want to commit a patch or other code sent to me by someone else? Do they have to sign a CLA too?
** three line fix is okay
** three line w/ new functionality, or large change, requires a CLA
** If you can get a CLA
* bryce: Public domain contributions (ie gov employees)
** individual code: can sign w/ no conflict as themselves
** gov code: already public domain - osgeo does not need a license
** treat on a case by case basis

= What is in a Name =

GeoTools is a common name, that many conferences, other open source projects and so on try to adopt. Yes we know it is obvious. Since the project has been going for 10 years (congrats) in a very public manner with out complaint we are going to keep on keeping on. If pressed we will adopt the name "GeoTools.org" and call it a day.

= IP Check =

It seems that a manul review of each header will be needed, we know we have some issues with code Bryce has written (ie in public domain license rather then LGPL).

# Module Maintainer will check source
# Module Maintainer will document manual check on wiki
# Jody will gather this up into the document expected by the Incubation committee

=== Finding out who did what? ===
We initially thought an IP check would involve asking each contributor to sign something, this presented several problems.
We don't know if everyone who worked on geotools is even alive, let alone how to find the ones that are still ticking.

== Property to Check ==

What do we need to check?

=== documentation ===
We thought we may need to check documentaiton, but so far only source code has been mentioned.

If we do need to check the docs they have always had a strict license, as indicated in the developers guide, however we break it down by maintainer:
* Wiki
** news anouncements - can we ignore please?
** product branding logos - jody
* Developers Guide - james (1st) and jody (2nd)
* Users Guide - rueben
** Tutorials - rueben
** Snipits - rueben
** Articles - jody
* RnD - jody
** Feature Model - gabriel
** Converage - bryce
** Rest - jody

We have lost our early history of news to a crash (I still am sad), and we have had around 6 websites. Some of the generated websites will be in version control and will show up as part of the code IP check.

=== code ===

The code has always been under GPL (1.x) or LGPL (2.x):
* 1.x code code was GPL (c) leeds - jmacgill confirm?
* 2.x code had LGPL (c) GeoTools PMC at the top.
* 2.2.x code may get (c) OSGEO lets talk about it

=== module ===

The module section of code is kind of lame and has a long tangled history. It started off as "core" and contained implementations for all the interfaces we had ever defined. It may even of contained the interfaces. The conversion notes are in confluence.

Conversion? Yeah we converted it - into a single module called "main" (because we could not manage our build as everything was so brittle). This was done for GeoTools 2.0, for geotools 2.2 things are breaking up along different lines:
* API - Jody Garnett - Capturing the (from main) interfaces that have been through a Q&A check
* MAIN - PMC - sad but the definition of PMC was almost module maintainer of main for a while
** filter/expresison - cory
** rendering - jesse
* REFERENCING - martin
* LEGEND - andrea (may just want it deleted)
* ...

=== plugins ===
Plugins are bits of functionality that implement all the great stuff that makes geotools useful. They slot in at the various layers defined by the libary and are nice and targetted:
* postgis: justin
* oracle: marc
* ...

=== ext ====
Extentions and Functionality built on GeoTools.
* graph - justin
* validation - jody
*

=== demo ===
Demos and Examples ...
* property - jody