OSGeo - User contributions [en]

OSGeo Community Sprint 2019

2019-02-21T15:57:49Z

Wiki-Greenwood: /* 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:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Logo-EOX.png|160px|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/]
||
[[File:Bh-logo.jpg|320px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Logo-extensis.png|190px|link=https://www.extensis.com/]]
 
[https://www.extensis.com/ https://www.extensis.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 5 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 ==
* Monday (5/13) - Welcome Gathering at [http://www.townhallbrewery.com/ Town Hall Brewery] (time TBD)
* Tuesday (5/14) - Pizza at [[surlybrewing.com|Surley Brewing]] (time TBD)
* Wednesday (5/15) - Free Portrait Photos (10:00am - 3:00pm) by [https://www.billadams.photo/ Bill Adams Photography]

== 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 ||
|-
| 14 ||[[User:kirk|Kirk McKelvey]] || US || kmckelvey@extensis.com || Extensis (was LizardTech) || || || || x || x || x || x || || || Very Likely ||
|-
| 15 ||Martin Davis || CA || martin.davis@crunchydata.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 16 ||Jody Garnett || CA || jody.garnett@gmail.com || OSGeo || || || || x || x || x || x || || || Certain ||
|-
| 17 ||Andrew Bell || US || andew@hobu.co || Hobu || || || || x || x || x || x || || || Certain ||
|-
| 18 ||[[User:greenwood|Rich Greenwood]] || US || rich@greenwoodmap.com || Greenwood Mapping, Inc. || || || || x || x || x || x || || || Certain || veg
|}

== 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]]

FOSS4G 2010 Breakout Sessions

2010-09-02T00:40:24Z

Wiki-Greenwood: /* Web Client (OpenLayers/GeoExt) */

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

back to [[FOSS4G 2010]]

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

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

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

'''Room allocation to be determined'''

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

==Timeslots Available==

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

Remember the Gala Dinner is scheduled at 20:00.

=Room Assignments=
==Rooms Available==

{|class="wikitable" border="1"
! width="150"|Room
! width="400"|Wednesday 08
! width="400"|Contact
|-
| Room 4 (75 pax)
|
|
|-
| Room 5 (250 pax)
|
|
|-
| Room 6 (320 pax)
|
|
|-
| Room 8 (100 pax)
|
|
|-
| Room 11 (78 pax)
|
|
|-
| Room 12 (90 pax)
|
|
|}

= Proposed Topics =

* Add yours below...

==Web Client (OpenLayers/GeoExt)==

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

'''Coming:'''

* Tim Schaub
* Eric Lemoine
* David Jonglez - for the first half, at least
* Florin Iosub
* Xurxo Méndez
* [[Ricardo Pinho|Ricardo Pinho]]
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Hugo Pereira
* [[Just van den Broecke|Just van den Broecke]]
* Sébastien Deleuze
* Richard Greenwood

==Spatial Databases BoF==

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

'''Coming:'''

* Paul Ramsey (PostGIS)
* Nicklas Avén (PostGIS)
* Brent Wood (NIWA)
* Peter Baumann (Jacobs University / rasdaman)
* Vincent Picavet (Oslandia/PostGIS)
* [[Nuno Guerreiro|Nuno Guerreiro]]
* Olivier Courtin (PostGIS)
* Hugo Pereira
* Volker Mische (CouchDB/GeoCouch)
* [[user:sebastian.ovide|Sebastián Ovide]]

==WPS BoF==

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

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

'''Who's coming:'''

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

==Sensor Web BoF==

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

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

'''Who's coming:'''

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

==Biodiversity/conservation projects and FOSS4G tools==

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

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

'''Coming:'''

* Javier de la Torre (Vizzuality)
* Brent Wood (NIWA)
* [[Markus Neteler]]
* [[User:jesus| Jorge de Jesus]] (Plymouth Marine Laboratory)
* [[User:Aghisla|Anne Ghisla]]
* Add your name here

==Spatial Data Infrastructure==

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

'''Who's coming:'''

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

==Virtualization and Cloud Computing BoF==

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

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

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

==Spatial OLAP==

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

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

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

==Flex Mapping (Alternatives to HTML)==

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

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

'''Coming:'''
* Sébastien Deleuze (OpenScales)
* Aurélien Barbier-Accary (OpenScales)
* Simon Lopez (OpenScales)
* Fabio Panettieri
* Marjorie Robert (if the session is planned on tuesday)
* Add your name here

David Jonglez - As discussed previously with other parties, it would be interesting to plan this session in an other time schedule in order to allow a maximum of interested persons already involved in other sessions to participate. What do you think planning this session on tuesday, the 7th evening ? (I'm shure we'll find a place !)

==QGIS user & developer meeting==

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

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

'''Coming:'''
* Marco Hugentobler
* [[User:Pirmin_Kalberer| Pirmin Kalberer]]
* Mathias Walker
* [[User:Vasile| Vasile Crăciunescu]]

FOSS4G2007 Session Chairs

2007-08-20T01:36:36Z

Wiki-Greenwood: /* 15:00 to 16:30 */

'''Back to [[FOSS4G2007]] ...'''

Session chairs serve as the "master of ceremonies" for one 90 minute session of presentations. Each session has three 25 minute presentations, with a 5 minute question-and-answer period after each. Chairs are expected to:
* introduce the speakers,
* ensure each speaker stays within his or her 30 minute combined presentations-plus-questions presentation limit,
* ensure the next presentation starts promptly as scheduled, and
* occasionally read off a few reminders and announcements at the end of the session.

Please add your name and email to one or more of the time slots below.

'''We need 5 session chairs for each time slot.'''

Check to ensure you are not presenting or teaching a lab during the session timeslot you are volunteering for.
([http://www.foss4g2007.org/program_overview/tuesday Tuesday Schedule,]
[http://www.foss4g2007.org/program_overview/wednesday Wednesday Schedule,]
[http://www.foss4g2007.org/program_overview/thursday Thursday Schedule])
If you have a particular room you want to chair, please note it in your entry.

= Tuesday =

== 13:00 to 14:30 ==
* Gary Sherman sherman@mrcc.com
* [[User:ajolma | Ari Jolma]]
* [[User:ianturton | Ian Turton]] View Royal - GeoRSS session

== 15:00 to 16:30 ==
* [[User:jlivni | Josh Livni]] (Saanich Room - REST stuff)
= Wednesday =

== 8:30 to 10:00 ==

== 10:30 to 12:00 ==
* [[User:Tbadard | Thierry Badard]] (Oak Bay 1)

== 13:00 to 14:30 ==

* Frank Warmerdam (Saanich)
* Tamas Szekeres (Lecture Theatre)

== 15:00 to 16:30 ==
* [[User:Greenwood | Richard Greenwood]] (Saanich)

= Thursday =

== 8:30 to 10:00 ==
* [[User:Tbadard | Thierry Badard]] (View Royal)
* [[User:mpg | Michael P. Gerlek]] (Lecture Theatre)

== 10:30 to 12:00 ==

* [[User:JoWalsh|Jo Walsh]] (Saanich)
* Frank Warmerdam (Lecture Theater)

= "On call" =
* [[User:mpg | Michael P. Gerlek]]
* [[User:venka | Venkatesh Raghavan]]

[[Category:FOSS4G]]
[[Category:FOSS4G2007]]

User:Greenwood

2007-08-20T01:33:59Z

Wiki-Greenwood:

* Location: Jackson Hole area, Wyoming, USA. 
* Occupation: owner of Greenwood Mapping, Inc. [http://www.greenwoodmap.com www.GreenwoodMap.com] 
* Focus: web map clients and coordinate systems. 
* Background: MapServer user since 2001.

FOSS4G2007 Session Chairs

2007-08-20T01:15:27Z

Wiki-Greenwood: /* 15:00 to 16:30 */

'''Back to [[FOSS4G2007]] ...'''

Session chairs serve as the "master of ceremonies" for one 90 minute session of presentations. Each session has three 25 minute presentations, with a 5 minute question-and-answer period after each. Chairs are expected to:
* introduce the speakers,
* ensure each speaker stays within his or her 30 minute combined presentations-plus-questions presentation limit,
* ensure the next presentation starts promptly as scheduled, and
* occasionally read off a few reminders and announcements at the end of the session.

Please add your name and email to one or more of the time slots below.

'''We need 5 session chairs for each time slot.'''

Check to ensure you are not presenting or teaching a lab during the session timeslot you are volunteering for.
([http://www.foss4g2007.org/program_overview/tuesday Tuesday Schedule,]
[http://www.foss4g2007.org/program_overview/wednesday Wednesday Schedule,]
[http://www.foss4g2007.org/program_overview/thursday Thursday Schedule])
If you have a particular room you want to chair, please note it in your entry.

= Tuesday =

== 13:00 to 14:30 ==
* Gary Sherman sherman@mrcc.com
* [[User:ajolma | Ari Jolma]]
* [[User:ianturton | Ian Turton]] View Royal - GeoRSS session

== 15:00 to 16:30 ==
* [[User:jlivni | Josh Livni]] (Saanich Room - REST stuff)
= Wednesday =

== 8:30 to 10:00 ==

== 10:30 to 12:00 ==
* [[User:Tbadard | Thierry Badard]] (Oak Bay 1)

== 13:00 to 14:30 ==

* Frank Warmerdam (Saanich)
* Tamas Szekeres (Lecture Theatre)

== 15:00 to 16:30 ==
* Richard Greenwood (Saanich)

= Thursday =

== 8:30 to 10:00 ==
* [[User:Tbadard | Thierry Badard]] (View Royal)
* [[User:mpg | Michael P. Gerlek]] (Lecture Theatre)

== 10:30 to 12:00 ==

* [[User:JoWalsh|Jo Walsh]] (Saanich)
* Frank Warmerdam (Lecture Theater)

= "On call" =
* [[User:mpg | Michael P. Gerlek]]
* [[User:venka | Venkatesh Raghavan]]

[[Category:FOSS4G]]
[[Category:FOSS4G2007]]

Choosing a Web Mapping Platform

2006-09-24T18:41:04Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide). This page focuses primarily on Open Source browser-based ''clients'' (not the servers).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* [http://docs.codehaus.org/display/MAP/Home MapBuilder]
* [http://www.mapbender.org/index.php/Main_Page Mapbender]
* [http://www.dmsolutions.ca/technology/chameleon.html Chameleon]
* [https://mapguide.osgeo.org/ MapGuide]
* [http://www.openlayers.org/ OpenLayers ]
* [http://ka-map.maptools.org/ ka-Map]
* [http://www.cartoweb.org/ CartoWeb ]

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI

Choosing a Web Mapping Platform

2006-09-24T18:23:40Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide). This page focuses primarily on browser-based ''clients'' (not servers).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* [http://docs.codehaus.org/display/MAP/Home MapBuilder]
* [http://www.mapbender.org/index.php/Main_Page Mapbender]
* [http://www.dmsolutions.ca/technology/chameleon.html Chameleon]
* [https://mapguide.osgeo.org/ MapGuide]
* [http://www.openlayers.org/ OpenLayers ]
* [http://ka-map.maptools.org/ ka-Map]
* [http://www.cartoweb.org/ CartoWeb ]

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI

Choosing a Web Mapping Platform

2006-09-24T18:12:36Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* MapBuilder http://docs.codehaus.org/display/MAP/HomeMapBuilder
* Mapbender http://www.mapbender.org/index.php/Main_Page
* Chameleon
* MapGuide
* OpenLayers
* ka-Map
* CartoWeb

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI

Choosing a Web Mapping Platform

2006-09-24T18:11:41Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* MapBuilder http://docs.codehaus.org/display/MAP/HomeMapBuilder
* Mapbender http://www.mapbender.org/index.php/Main_Page
* Chameleon
* MapGuide
* OpenLayers
* ka-Map
* CartoWeb

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI

Choosing a Web Mapping Platform

2006-09-24T18:10:37Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* MapBuilder http://docs.codehaus.org/display/MAP/HomeMapBuilder
* Mapbender
* Chameleon
* MapGuide
* OpenLayers
* ka-Map
* CartoWeb

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI

Choosing a Web Mapping Platform

2006-09-24T18:09:55Z

Wiki-Greenwood: /* Choosing a Web Mapping Platform for your Application */

== Choosing a Web Mapping Platform for your Application ==

There are a great many web mapping platforms available to someone starting a new project. If you are new to this world ... or perhaps have a different type of project that won't work with the platform that you are familiar with, this page should help you decide which platform is right for your project.

A web mapping platform is a toolkit that helps you build a web mapping application. It may or may not depend on a particular server technology (like MapServer or MapGuide).

Note that many of the platforms discussed below are very similar in most respects. There is a move afoot to consolidate some of the core components of these platforms into a single shared library ... which will further blur the distinctions.

The major web mapping platforms are (each needs to be linked to a separate page that describes the project in more detail, esp the benefits to a potential user):

* <a href="http://docs.codehaus.org/display/MAP/Home">MapBuilder</a>
* Mapbender
* Chameleon
* MapGuide
* OpenLayers
* ka-Map
* CartoWeb

I categorize these clients into two separate categories, each with two sub-categories ... this helps me sort out which platforms most closely match the type of application I am trying to build. At that point, I would go through the specific features of the contenders to figure out which one to actually use.

The two main categories are:

* How templates are implemented
* How maps are generated

=== Templates ===

In a web mapping platform, a template is simply the HTML that gets sent to the browser. All the web mapping platforms fall into one or both of the following sub-categories.

* Managed template. A managed template is one that the toolkit manages for you. The actual HTML is typically hidden from the application designer, and some sort of GUI interface is provided for setting up the look and feel of the application
* Unmanaged template. An unmanaged template is one that the toolkit uses, but doesn't manage for you. The actual HTML is hand-crafted by the application designer.

=== Maps ===

In a web mapping platform, maps seem to be used in two different ways (this is arguable for sure). The first is client-side. The second is server-side.

* Client Side. This type of platform uses pure OGC web services and manages the map and layer state entirely in the client.
* Server Side. This type of platform uses a server (MapServer or MapGuide) to generate the map, and relies primarily on the server's API to do so.

Undoubtedly, most platforms can do both. However, in my experience, each platform falls more into one of these categories due to its original architecture.

=== Where the projects ===

<pre>
managed | unmanaged
|
mapbender | mapbuilder
client | OpenLayers (2)
|
-----------
-----------------| WebMap.js |------------
-----------
|
| chameleon
server mapguide | ka-map (1)
| CartoWeb (3)
|
</pre>

(1) ka-Map is actually a client side app and can do client-side direct from WMS but its not the primary mechanism and the default install requires a server side component.

(2) OpenLayers can do server-side from ka-Map, but its not the primary mechanism

(3) HTML is actually totally separated from the code with a templating system. However the templating system is not managed through a GUI