OSGeo - User contributions [en]

Ottawa Chapter/tutorials

2009-04-15T14:03:17Z

Wiki-Dsampson: /* Grass Tutorial */

== List of GRASS Tutorials ==

=== Tutorial 1: GRASS in a Nutshell ===
Source: [[Image:Grass6_nutshell2005.pdf]]

=== Tutorial 2: GRASS and a GPS (historical) ===
Source: [[Image:Ottawa_Chapter_Tutorial_2_GPS_and_GRASS.pdf]]

=== Tutorial 3: Building Ottawa GRASS Location ===
Source: [[Image:Ottawa_Chapter_Tutorial_3_Building_Ottawa.pdf]]

=== Tutorial 4: Building_National_Framework GRASS Location ===
Source: [[Image:Ottawa_Chapter_Tutorial_4_Building_National_Framework.pdf ]]

=== Tutorial 5: Raster Elevation Data in GRASS===
Source: [[Ottawa_Chapter/tutorials/Raster_elevation | Raster Elevation Data in GRASS ]]

==Tutorial Input==
This section is designed to help solicit input to creation and execution of out tutorials

===Grass Tutorial===
This is an area to get input in structuring our upcoming GRASS tutorial

Date: TBD (Spring/summer 2009)
Location: Carleton University(?)
Time: Evening

Purpose:
* Introduce users to the GRASS desktop GIS
* Access basic GRASS functions through

Participant Requests
* eg. Have fun and deliver an informative tutorial [[User:Dsampson|Dave Sampson]]
* enter your request here

==Tutorial Ideas==
Tutorial Title: QGIS Plugins
Presenter: Dave Sampson
Date (TBD):
Purpose:
* Introduce the user to QGIS
* Demonstrate various plugins
** finding them
** Choosing them
** installing them
* Create simple Python based plugin (eg Hello world, plot a point)

Tutorial title: FOSS4G GPS Capturing
presenter: Dave Sampson
Date:
* Day 1: Weekend
* Day 2: Weeknight (unless we can access a computer lab on the weekend)
Purpose:
* demonstrate the use of GPS and FOSS4G tools in capturing and sharing
** waypoints
** tracks
** routes

Ottawa Chapter/tutorials

2009-04-15T14:01:42Z

Wiki-Dsampson:

== List of GRASS Tutorials ==

=== Tutorial 1: GRASS in a Nutshell ===
Source: [[Image:Grass6_nutshell2005.pdf]]

=== Tutorial 2: GRASS and a GPS (historical) ===
Source: [[Image:Ottawa_Chapter_Tutorial_2_GPS_and_GRASS.pdf]]

=== Tutorial 3: Building Ottawa GRASS Location ===
Source: [[Image:Ottawa_Chapter_Tutorial_3_Building_Ottawa.pdf]]

=== Tutorial 4: Building_National_Framework GRASS Location ===
Source: [[Image:Ottawa_Chapter_Tutorial_4_Building_National_Framework.pdf ]]

=== Tutorial 5: Raster Elevation Data in GRASS===
Source: [[Ottawa_Chapter/tutorials/Raster_elevation | Raster Elevation Data in GRASS ]]

==Tutorial Input==
This section is designed to help solicit input to creation and execution of out tutorials

===Grass Tutorial===
This is an area to get input in structuring our upcoming GRASS tutorial

Date: TBD (Spring/summer 2009)
Location: Carleton University(?)
Time: Evening

Purpose:
* Introduce users to the GRASS desktop GIS
* Access basic GRASS functions through

==Tutorial Ideas==
Tutorial Title: QGIS Plugins
Presenter: Dave Sampson
Date (TBD):
Purpose:
* Introduce the user to QGIS
* Demonstrate various plugins
** finding them
** Choosing them
** installing them
* Create simple Python based plugin (eg Hello world, plot a point)

Tutorial title: FOSS4G GPS Capturing
presenter: Dave Sampson
Date:
* Day 1: Weekend
* Day 2: Weeknight (unless we can access a computer lab on the weekend)
Purpose:
* demonstrate the use of GPS and FOSS4G tools in capturing and sharing
** waypoints
** tracks
** routes

Ottawa Chapter

2009-04-15T13:47:59Z

Wiki-Dsampson: /* Chairs */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July 2007 meeting turn out (more or less).]]

 
Date: April '''9''', 2009 (note change of date, if you previously read April 2) 
Time: 6:00 PM
 
Location: [http://foxandfeather.ca The Fox and Feather] pub, in Fox 2 back room on the top floor (all the way to the top flight of stairs, then turn right and go into the smaller room with the TV in the corner).

 [http://maps.google.com/maps?f=q&q=283+Elgin+Street,+Ottawa,+ON+K2P+1M1+Canada&ie=UTF8&om=1 283 Elgin Street (at Somerset W)] Ottawa, Canada K2P 1M1 phone # - (613) 233-2219

Topic:
 
 Business Items:

* Introductions
* What are your OSGeo issues today?
* Informal discussion (aka Eat, Drink, Be Merry). 
   

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

A Powerpoint presentation reporting on our chapter's formation and first year of activity is available for download in its original [http://cemml.carleton.ca/osgeo_files/local-chap.ppt full version], or the [http://cemml.carleton.ca/osgeo_files/OttLocal-chap_condensed.ppt condensed form] created to squeeze into a tighter time constraint.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTos
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

=== Chairs ===

* 2008 - present Ottawa chapter co-chairs: [[User:smitch|Scott Mitchell]] and Philippe Vachon
* 2006 - 2008 Ottawa chapter co-chairs: [[User:Dsampson|Dave Sampson]] and [[User:jmckenna|Jeff McKenna]]
* 2005 - 2006 OGUG Chair: [[User:Dsampson|Dave Sampson]]
* 2003 - 2006 OMSUG Chair: [[User:jmckenna|Jeff McKenna]]

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]
[[Category:Canada]]

OSGeo Cartographic Engine

2008-05-02T18:29:05Z

Wiki-Dsampson: /* Other Worflow Models */

== Motivation ==

There are plans for new/rewritten cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects, while this project focuses on standard libraries or command line utilities.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement -- for example, collision management based on rotated extent rectangles. Also, collision management against line and polygon and point features. Provision for prioritized set of text placement rules, first one to prevent collision wins.
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)
* parse and print map (geovisualization) description files

This paper might be worth looking at: [http://utpjournals.metapress.com/content/b584484743vk910g/ Extended Cartographic Interfaces for Open Distributed Processing]

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

What about the possibility of exporting SVG and using Inkscape for cartographic styling and design? Inkscape is written in C++ and already has a wealth of vector graphics functionality. You could also consider using Scribus for map layout. I believe Scribus is also written in C++. Why implement the great functionality that already exists in open source programs?

Coming from the Web Mapping angle it will be interesting to be able to acquire OGC WMS maps with a pixel sizes < 0.28 mm (which is the current standard of ~ 72 or 90 dpi). This option has been suggested as a change request and is currently being discussed. It will allow to compose high resolution print maps also using OGC WMS.

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language. Please keep in mind that this is underlying library, not the graphical user interface.

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?

* Stylization
** ...

* Symbology
** [http://www.iho.shom.fr/PUBLICATIONS/download.htm#special S-52 standard for nautical chart (ENC) symbology] and cartography from the [http://www.iho.shom.fr/ International Hydrographic Bureau]
:: [http://openev.cvs.sourceforge.net/openev/contrib/S52/ GPL library implementing the S-52 standard] (OpenEV)

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] (LGPL.C++)

* Output:
** Postscript/PDF output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver] (GPL, C)
*** [http://sourceforge.net/projects/geofunctions GeoFunctions]: Geographic XML to PDF. Not sure what specific code, but the project leaders might have some insight.
** PNG output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver] (GPL, C)
*** See AGG below
** CAIRO output
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/cairodriver CAIRO driver] (GPL, C)
*** [http://cairographics.org/ Cairo Graphics Library] (LGPL or MPL)
** [Mapnik http://mapnik.org/] is a Free Toolkit for developing mapping applications.

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in) and large format (eg 34 x 44in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* [[OSGeo map symbol set|Symbols library]]
* Separate cartographic and geographic representation (eg changes to carto does not affect geo).
* Generalization on-the-fly, based on current scale.
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF
** Postscript (need for directly sending files to printers)
** SVG
* Layout Functionality
* Text-based configuration file that applications can output to or humans can manually hack/script
* Common, interoperable data file input options

==Layout Functionality==
===Design Modeling===
Issues of layout will always be important in creating the final cartographic product. Layout templating such as that used in Natural Resources Canada's (NRCAN) Cartographic Design Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13).

Perhaps we can learn from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus could allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

=== XML and PDF===
OSGEO might be able to get behind the [http://sourceforge.net/projects/geofunctions Geo Functions] project. "Geo Functions is an open-source library of XSLT-2 / XQuery functions, templates, stylesheets and classes devoted to the processing of geographic data in XML." I understand that the original purpose of the project is to produce PDF maps from XML based data.

==Potential Components==
Breaking the end goal into some components will help to recognise which area(s) there is greatest need. There seems to be at least four primary components to the proposal.

=== Style & Layout Configuration Standards ===
* Specifications for styling of features and layout of a map composition
* Could re-use existing approaches where applicable (e.g. SLD, WMC, MapServer Mapfile, OGR Feature Styles)
* Specifications to be used in map definition/configuration files

=== Graphical Style & Layout Editor ===
* To create styles interactively
* To define map layout
* Could be stand-alone
* Could be adopted as part of another application
* Saves a style/layout definition document according to above standards

=== Graphical Map Composition Editor ===
* Implemented by existing applications (e.g. GRASS, QGIS, etc.)
* Sets up pointers to data layers
* Assigns styles definitions to the layers
* Applies layout definition to maps
* Outputs a map composition configuration file

=== Rendering Engine ===
* Stand-alone application (no GUI)
* Reads standard map composition configuration file
* Reads and applies the required style/layout definition documents
* Outputs final graphics to specific files

=== Libraries ===
* Sets of libraries could be created to implement parts of the above sections
* Add more here...

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library
* [http://cairographics.org/ Cairo] graphics library - vector, text and raster input, various output including Postscript
* [http://schemas.opengis.net/se/1.1.0/ OpenGIS Symbology Encoding Schema] A language for describing coverage and feature styles

== Worflow ==

By working from the end product to a workflow might let us identify specific libraries to help with each task in the workflow required to produce a map. Edit at will.

* read geo data
** geometries
** projection
** metadata (if required)
* apply styling
** feature to style coding
* Cartographic edits
** overide some of the geometry if required (eg roads don't run through lakes)
* manual edits / retouching
* Produce other cartographic edits objects
** create suround
** create grids
** create legend
** create scale bar
** create north arrow
** Copyright notices from text file or DB
** Licensing notices from text fiel or DB
* Other
** Output size

=== Other Worflow Models ===
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 Generic GRASS-GMT Workflow]
* [http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview Quality Digital Cartography with GMT and GRASS]

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
* [[User:Tmitchell|Tyler Mitchell]]
* [[User:reholl|Robert Hollingsworth]]
* [[User:Wolf|Wolf Bergenheim]]: v.label.sa developer
* [[User:HamishBowman|Hamish Bowman]]: ps.map developer
* [[User:GAruta|Giuseppe Aruta]]: Geologist
* [[User:Roy|Roy Braam]]: Software Engineer
* Ionut Iosifescu
* [[User:ajolma|Ari Jolma]]: Wants to go ahead with Cairo
* [[User:vasile|Vasile Crăciunescu]]
* [[User:Peterrushforth|Peter Rushforth]]
* [[User:Turban|Bjorn Sandvik]]: thematicmapping.org
* [[User:JoCook| Jo Cook]]

== See also ==

* [[OSGeo map symbol set]]

[[Category: Software Stack]]

OSGeo Cartographic Engine

2008-05-02T18:21:05Z

Wiki-Dsampson: /* Worflow */

== Motivation ==

There are plans for new/rewritten cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects, while this project focuses on standard libraries or command line utilities.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement -- for example, collision management based on rotated extent rectangles. Also, collision management against line and polygon and point features. Provision for prioritized set of text placement rules, first one to prevent collision wins.
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)
* parse and print map (geovisualization) description files

This paper might be worth looking at: [http://utpjournals.metapress.com/content/b584484743vk910g/ Extended Cartographic Interfaces for Open Distributed Processing]

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

What about the possibility of exporting SVG and using Inkscape for cartographic styling and design? Inkscape is written in C++ and already has a wealth of vector graphics functionality. You could also consider using Scribus for map layout. I believe Scribus is also written in C++. Why implement the great functionality that already exists in open source programs?

Coming from the Web Mapping angle it will be interesting to be able to acquire OGC WMS maps with a pixel sizes < 0.28 mm (which is the current standard of ~ 72 or 90 dpi). This option has been suggested as a change request and is currently being discussed. It will allow to compose high resolution print maps also using OGC WMS.

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language. Please keep in mind that this is underlying library, not the graphical user interface.

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?

* Stylization
** ...

* Symbology
** [http://www.iho.shom.fr/PUBLICATIONS/download.htm#special S-52 standard for nautical chart (ENC) symbology] and cartography from the [http://www.iho.shom.fr/ International Hydrographic Bureau]
:: [http://openev.cvs.sourceforge.net/openev/contrib/S52/ GPL library implementing the S-52 standard] (OpenEV)

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] (LGPL.C++)

* Output:
** Postscript/PDF output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver] (GPL, C)
*** [http://sourceforge.net/projects/geofunctions GeoFunctions]: Geographic XML to PDF. Not sure what specific code, but the project leaders might have some insight.
** PNG output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver] (GPL, C)
*** See AGG below
** CAIRO output
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/cairodriver CAIRO driver] (GPL, C)
*** [http://cairographics.org/ Cairo Graphics Library] (LGPL or MPL)
** [Mapnik http://mapnik.org/] is a Free Toolkit for developing mapping applications.

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in) and large format (eg 34 x 44in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* [[OSGeo map symbol set|Symbols library]]
* Separate cartographic and geographic representation (eg changes to carto does not affect geo).
* Generalization on-the-fly, based on current scale.
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF
** Postscript (need for directly sending files to printers)
** SVG
* Layout Functionality
* Text-based configuration file that applications can output to or humans can manually hack/script
* Common, interoperable data file input options

==Layout Functionality==
===Design Modeling===
Issues of layout will always be important in creating the final cartographic product. Layout templating such as that used in Natural Resources Canada's (NRCAN) Cartographic Design Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13).

Perhaps we can learn from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus could allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

=== XML and PDF===
OSGEO might be able to get behind the [http://sourceforge.net/projects/geofunctions Geo Functions] project. "Geo Functions is an open-source library of XSLT-2 / XQuery functions, templates, stylesheets and classes devoted to the processing of geographic data in XML." I understand that the original purpose of the project is to produce PDF maps from XML based data.

==Potential Components==
Breaking the end goal into some components will help to recognise which area(s) there is greatest need. There seems to be at least four primary components to the proposal.

=== Style & Layout Configuration Standards ===
* Specifications for styling of features and layout of a map composition
* Could re-use existing approaches where applicable (e.g. SLD, WMC, MapServer Mapfile, OGR Feature Styles)
* Specifications to be used in map definition/configuration files

=== Graphical Style & Layout Editor ===
* To create styles interactively
* To define map layout
* Could be stand-alone
* Could be adopted as part of another application
* Saves a style/layout definition document according to above standards

=== Graphical Map Composition Editor ===
* Implemented by existing applications (e.g. GRASS, QGIS, etc.)
* Sets up pointers to data layers
* Assigns styles definitions to the layers
* Applies layout definition to maps
* Outputs a map composition configuration file

=== Rendering Engine ===
* Stand-alone application (no GUI)
* Reads standard map composition configuration file
* Reads and applies the required style/layout definition documents
* Outputs final graphics to specific files

=== Libraries ===
* Sets of libraries could be created to implement parts of the above sections
* Add more here...

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library
* [http://cairographics.org/ Cairo] graphics library - vector, text and raster input, various output including Postscript
* [http://schemas.opengis.net/se/1.1.0/ OpenGIS Symbology Encoding Schema] A language for describing coverage and feature styles

== Worflow ==

By working from the end product to a workflow might let us identify specific libraries to help with each task in the workflow required to produce a map. Edit at will.

* read geo data
** geometries
** projection
** metadata (if required)
* apply styling
** feature to style coding
* Cartographic edits
** overide some of the geometry if required (eg roads don't run through lakes)
* manual edits / retouching
* Produce other cartographic edits objects
** create suround
** create grids
** create legend
** create scale bar
** create north arrow
** Copyright notices from text file or DB
** Licensing notices from text fiel or DB
* Other
** Output size

=== Other Worflow Models ===
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 Generic GRASS-GMT Workflow]

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
* [[User:Tmitchell|Tyler Mitchell]]
* [[User:reholl|Robert Hollingsworth]]
* [[User:Wolf|Wolf Bergenheim]]: v.label.sa developer
* [[User:HamishBowman|Hamish Bowman]]: ps.map developer
* [[User:GAruta|Giuseppe Aruta]]: Geologist
* [[User:Roy|Roy Braam]]: Software Engineer
* Ionut Iosifescu
* [[User:ajolma|Ari Jolma]]: Wants to go ahead with Cairo
* [[User:vasile|Vasile Crăciunescu]]
* [[User:Peterrushforth|Peter Rushforth]]
* [[User:Turban|Bjorn Sandvik]]: thematicmapping.org
* [[User:JoCook| Jo Cook]]

== See also ==

* [[OSGeo map symbol set]]

[[Category: Software Stack]]

OSGeo map symbol set

2008-04-14T20:05:30Z

Wiki-Dsampson: /* Symbol Availability */

== Motivation ==

The [[OSGeo Cartographic Library]] and all software projects obviously need a free map symbol set.

== Available Material ==

* Free map symbol sets from GFOSS.it: [http://www.gfoss.it/drupal/simboli Simboli cartografici]
* Free [http://grass.osgeo.org/wiki/IconSymbols map icons] from GRASS
* ...

== Other Technology==
Microsoft has a [http://www.aaronlerch.com/blog/2007/09/01/symbol-server-transaction-manager/ symbol server]

== Symbol Availability ==
{| class="wikitable"
|-
! Symbol
! GFOSS.it
! GRASS
! OSGEO
|-
| '''Community'''
|
|
|-
| School
|
|
| NA
|-
| Recreation Centre
|
|
| NA
|-
| '''Emergency Services'''
|
|
|-
| Hospital
|
|
| NA
|-
| Police station
|
|
| NA
|-
| Fire station
|
|
| NA
|-
| Ambulance
|
|
| NA
|-
| '''Basic'''
|
|
| NA
|-
| Arrow
|
| yes
| NA
|-
| Box
|
| yes
| NA
|-
| Circle
|
| yes
| NA
|-
| '''Extras'''
|
|
| NA
|-
| Compass
|
| Yes
| NA
|-
| Airport
|
| Yes
| NA
|-
| Target
|
| yes
| NA
|-
| Dive Flag
|
| yes
| NA
|-
| '''Transportation'''
|
|
|
|-
| Information Centre
|
|
| NA
|-
| Bus Stop
|
|
| NA
|-
| Picnic Area
|
|
| NA
|}

== Interested people ==

* [[User:Neteler|Markus Neteler]]
* [[User:Dsampson|Dave Sampson]]

[[Category: Software Stack]]
[[Category: Public Geospatial Data Committee]]

OSGeo map symbol set

2008-04-14T20:01:07Z

Wiki-Dsampson: Symbol Availability

== Motivation ==

The [[OSGeo Cartographic Library]] and all software projects obviously need a free map symbol set.

== Available Material ==

* Free map symbol sets from GFOSS.it: [http://www.gfoss.it/drupal/simboli Simboli cartografici]
* Free [http://grass.osgeo.org/wiki/IconSymbols map icons] from GRASS
* ...

== Other Technology==
Microsoft has a [http://www.aaronlerch.com/blog/2007/09/01/symbol-server-transaction-manager/ symbol server]

== Symbol Availability ==
{| class="wikitable"
|-
! Symbol
! GFOSS.it
! GRASS
! OSGEO
|-
| '''Community'''
|
|
|-
| School
|
|
| NA
|-
| Recreation Centre
|
|
| NA
|-
| '''Emergency Services'''
|
|
|-
| Hospital
|
|
| NA
|-
| Police station
|
|
| NA
|-
| Fire station
|
|
| NA
|-
| Ambulance
|
|
| NA
|-
| '''Basic'''
|
|
| NA
|-
| Arrow
|
| yes
| NA
|-
| Box
|
| yes
| NA
|-
| Circle
|
| yes
| NA
|-
| '''Extras'''
|
|
| NA
|}

== Interested people ==

* [[User:Neteler|Markus Neteler]]
* [[User:Dsampson|Dave Sampson]]

[[Category: Software Stack]]
[[Category: Public Geospatial Data Committee]]

OSGeo map symbol set

2008-04-14T19:40:46Z

Wiki-Dsampson:

OSGeo map symbol set

2008-04-14T19:37:56Z

Wiki-Dsampson: /* Interested people */

OSGeo Cartographic Engine

2008-04-14T19:10:10Z

Wiki-Dsampson: Added workflow section

== Motivation ==

There are plans for new/rewritten cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects, while this project focuses on standard libraries or command line utilities.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement -- for example, collision management based on rotated extent rectangles. Also, collision management against line and polygon and point features. Provision for prioritized set of text placement rules, first one to prevent collision wins.
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

What about the possibility of exporting SVG and using Inkscape for cartographic styling and design? Inkscape is written in C++ and already has a wealth of vector graphics functionality. You could also consider using Scribus for map layout. I believe Scribus is also written in C++. Why implement the great functionality that already exists in open source programs?

Coming from the Web Mapping angle it will be interesting to be able to acquire OGC WMS maps with a pixel sizes < 0.28 mm (which is the current standard of ~ 72 or 90 dpi). This option has been suggested as a change request and is currently being discussed. It will allow to compose high resolution print maps also using OGC WMS.

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language. Please keep in mind that this is underlying library, not the graphical user interface.

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide, [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] and [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?
* Stylization
** ...
* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)
* Output:
** Postscript/PDF output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver] (GPL, C)
*** [http://sourceforge.net/projects/geofunctions GeoFunctions]: Geographic XML to PDF. Not sure what specific code, but the project leaders might have some insight.
** PNG output:
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver] (GPL, C)
*** See AGG below
** CAIRO output
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/cairodriver CAIRO driver] (GPL, C)
*** [http://cairographics.org/ Cairo Graphics Library] (LGPL or MPL)
** [Mapnik http://mapnik.org/] is a Free Toolkit for developing mapping applications.

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in) and large format (eg 34 x 44in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* symbols library
* Seprate cartographic and geographic representation (eg changes to carto does not affect geo).
* Generalization on-the-fly, based on current scale.
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF
** Postscript (need for directly sending files to printers)
** SVG
* Layout Functionality
* Text-based configuration file that applications can output to or humans can manually hack/script
* Common, interoperable data file input options

==Layout Functionality==
===Design Modeling===
Issues of layout will always be important in creating the final cartographic product. Layout templating such as that used in Natural Resources Canada's (NRCAN) Cartographic Design Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13).

Perhaps we can learn from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus could allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

=== XML and PDF===
OSGEO might be able to get behind the [http://sourceforge.net/projects/geofunctions Geo Functions] project. "Geo Functions is an open-source library of XSLT-2 / XQuery functions, templates, stylesheets and classes devoted to the processing of geographic data in XML." I understand that the original purpose of the project is to produce PDF maps from XML based data.

==Potential Components==
Breaking the end goal into some components will help to recognise which area(s) there is greatest need. There seems to be at least four primary components to the proposal.

=== Style & Layout Configuration Standards ===
* Specifications for styling of features and layout of a map composition
* Could re-use existing approaches where applicable (e.g. SLD, WMC)
* Specifications to be used in map definition/configuration files

=== Graphical Style & Layout Editor ===
* To create styles interactively
* To define map layout
* Could be stand-alone
* Could be adopted as part of another application
* Saves a style/layout definition document according to above standards

=== Graphical Map Composition Editor ===
* Implemented by existing applications (e.g. GRASS, QGIS, etc.)
* Sets up pointers to data layers
* Assigns styles definitions to the layers
* Applies layout definition to maps
* Outputs a map composition configuration file

=== Rendering Engine ===
* Stand-alone application (no GUI)
* Reads standard map composition configuration file
* Reads and applies the required style/layout definition documents
* Outputs final graphics to specific files

=== Libraries ===
* Sets of libraries could be created to implement parts of the above sections
* Add more here...

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library
* [http://cairographics.org/ Cairo] graphics library - vector, text and raster input, various output including Postscript

== Worflow ==

By working from the end product to a workflow might let us identify specific libraries to help with each task in the workflow required to produce a map. Edit at will.

* read geo data
** geometries
** projection
** metadata (if required)
* apply styling
** feature to style coding
* Cartographic edits
** overide some of the geometry if required (eg roads don't run through lakes)
* manual edits / retouching
* Produce other cartographic edits objects
** create suround
** create grids
** create legend
** create scale bar
** create north arrow
** Copyright notices from text file or DB
** Licensing notices from text fiel or DB
* Other
** Output size

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
* [[User:Tmitchell|Tyler Mitchell]]
* [[User:reholl|Robert Hollingsworth]]
* Wolf Bergenheim
* [[User:HamishBowman|Hamish Bowman]]: ps.map developer & evangelist
* [[User:GAruta|Giuseppe Aruta]]: Geologist
* [[User:Roy|Roy Braam]]: Software Engineer
* Ionut Iosifescu
* [[User:ajolma|Ari Jolma]]: Wants to go ahead with Cairo
* [[User:vasile|Vasile Crăciunescu]]
* [[User:Peterrushforth|Peter Rushforth]]

[[Category: Software Stack]]

OSGeo Cartographic Engine

2008-04-07T16:38:51Z

Wiki-Dsampson: /* Existing code to be recycled */

== Motivation ==

There are plans about new cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language:

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide, [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] and [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?
* Stylization:
* Postscript/PDF output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver]
** [http://sourceforge.net/projects/geofunctions GeoFunctions]: Geographic XML to PDF. Not sure what specific code, but the project leaders might have some insight.

* PNG output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver]
** See AGG below
** [http://cairographics.org/ Cairo Graphics Library]

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* symbols library
* Seprate cartographic and geographic representation (eg changes to carto does not affect geo)
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF
** Postscript (need for directly sending files to printers)
* Layout Functionality
* Text-based configuration file that applications can output to or humans can manually hack/script
* Common, interoperable data file input options

==Layout Functionality==
===Design Modeling===
Issues of layout will always be important in creating the final cartographic product. Layout templating such as that used in Natural Resources Canada's (NRCAN) Cartographic Design Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13).

Perhaps we can learn from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus vcould allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

=== XML and PDF===
OSGEO might be able to get behind the [http://sourceforge.net/projects/geofunctions Geo Functions] project. "Geo Functions is an open-source library of XSLT-2 / XQuery functions, templates, stylesheets and classes devoted to the processing of geographic data in XML." I understand that the original purpose of the project is to produce PDF maps from XML based data.

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
* [[User:Tmitchell|Tyler Mitchell]]

[[Category: Software Stack]]

Talk:OSGeo Cartographic Engine

2008-04-07T15:27:49Z

Wiki-Dsampson: removed my discussion post. All content hacked into wiki

OSGeo Cartographic Engine

2008-04-07T15:25:04Z

Wiki-Dsampson: added design modeling and xml/pdf section

== Motivation ==

There are plans about new cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language:

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide, [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] and [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?
* Stylization:
* Postscript/PDF output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver]
* PNG output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver]
** See AGG below
** [http://cairographics.org/ Cairo Graphics Library]

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* symbols library
* Seprate cartographic and geographic representation (eg changes to carto does not affect geo)
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF
* Layout Functionality

==Layout Functionality==
===Design Modeling===
Issues of layout will always be important in creating the final cartographic product. Layout templating such as that used in Natural Resources Canada's (NRCAN) Cartographic Design Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13).

Perhaps we can learn from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus vcould allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

=== XML and PDF===
OSGEO might be able to get behind the [http://sourceforge.net/projects/geofunctions Geo Functions] project. "Geo Functions is an open-source library of XSLT-2 / XQuery functions, templates, stylesheets and classes devoted to the processing of geographic data in XML." I understand that the original purpose of the project is to produce PDF maps from XML based data.

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
[[Category: Software Stack]]

OSGeo Cartographic Engine

2008-04-07T15:15:30Z

Wiki-Dsampson: /* End User Needs */

== Motivation ==

There are plans about new cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language:

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide, [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] and [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?
* Stylization:
* Postscript/PDF output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver]
* PNG output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver]
** See AGG below
** [http://cairographics.org/ Cairo Graphics Library]

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* symbols library
* Seprate cartographic and geographic representation (eg changes to carto does not affect geo)
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF / GeoPDF

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
[[Category: Software Stack]]

OSGeo Cartographic Engine

2008-04-07T15:15:10Z

Wiki-Dsampson: added some user requirements

== Motivation ==

There are plans about new cartographic tools (map composer) for QGIS, as well as for GRASS. We suggest to develop a joint library for the various functions which could be shared across GRASS, QGIS and other projects with bindings to Qt, Python etc. The GUI part will be done within the individual software projects.

== Functionality ==

Shared functions may include

* class breaks (various algorithms)
* histogram analysis
* color ramps
* RGB and possibly CYMK support (aka color transformations) etc.
* Algorithms for intelligent label placement
* Symbology management
* map surround
* legend
* cartographic templates (ie. predefined map styles)

== Programming Language ==

* C? C++?

Perhaps we could implement the core in C++, but provide a high level C API for applications and environments wanting to drive the library. C++ is a strong implementation language, but presenting a C API to the outside world reduces complexity calling from other languages or compiler versions and reduces "interface fragility".

* Python bindings?

There has been talk on the [http://gmt.soest.hawaii.edu/ GMT] mailing list about Python bindings to the core C API. Since GMT already has a wealth of routines for plotting directly to PS|EPS format files, this route may give developers a great head-start. There has been [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 some work] on the integration of GRASS and GMT in the past, with [http://grass.gdf-hannover.de/wiki/GRASS_AddOns several user-submitted modules].

== Output Formats ==

What output formats do we want to target. I think at the core this question comes down to whether we want to render everything to a raster format or whether we wish to preserve linework, and text in non-raster form. That is, whether output output is a raster format, or a raster+vector+text format like postscript/pdf.

If a cartographic product is the objective, I think selection of an output format like PDF makes a lot of sense, but it does make interactive composition more complicated and it is possible we have limited pdf/postscript development expertise in our developer community (the GMT developers may be of help here...).

== Existing code to be recycled ==

There will be code in GRASS, QGIS, the Python Cartographic Library (http://zcologia.org/cartography) and other sources which could be integrated (check license compatibility). Please indicate precisely where to find the source code, license, programming language:

* Label placement code:
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)
* Color management:
** MapGuide, [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] and [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)
** OpenJump ?
* Stylization:
* Postscript/PDF output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/ps/ps.map ps.map] (Postscript output) and [http://trac.osgeo.org/grass/browser/grass/trunk/lib/psdriver PS driver]
* PNG output:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver]
** See AGG below
** [http://cairographics.org/ Cairo Graphics Library]

* Class breaks:
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)

== End User Needs ==
* Print to small format medium (eg 8.5in x 11in, 11in x 14in)
* Interactive layout
* High quality printing
* Storage of cartographic symbolizing
* symbols library
* Seprate cartographic and geographic representation (eg changes to carto does not affect geo)
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)
* Multiple export formats
** Geotiff
** PNG
** PDF /

== Technologies ==

* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik).
* Freetype - text management and rendering library

== License ==

It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.

== Interested people ==

* [[User:Neteler|Markus Neteler]] (proposer)
* Horst Düster
* [[User:Landa|Martin Landa]]
* [[User:MarcoHugentobler|Marco Hugentobler]]
* Frank Warmerdam
* [[User:Adiez|Agustin Diez]]
* [[User:mlennert|Moritz Lennert]]
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist
[[Category: Software Stack]]

Talk:OSGeo Cartographic Engine

2008-04-07T13:49:54Z

Wiki-Dsampson: New page: ~~~~ Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations. One of their biggest needs is the ability to print maps off in t...

[[User:Dsampson|Dsampson]] 09:49, 7 April 2008 (EDT)

Currently I am working to get a Search and Rescue (SAR) volunteer group into some OS geo for their field operations.

One of their biggest needs is the ability to print maps off in the field from a regular printer (8.5x11in or 11x14in) sheets.

I am of course using GRASS and QGIS and some basic carto features we would be able to use are

1. Printing from a georefed PDF or GeoTiff 
2. Miniature maps with borders, scale, UTM Grid 
3. Printing from vector and raster combined data 
4. Simple color schemes 
5. Printing to "recreation paper" (eg Tyvek) 

[[User:Dsampson|Dsampson]] 09:49, 7 April 2008 (EDT)

Two things to consider include how the data is represented and how the style rules are stored.

These questions might influence the model for designing the cartographic library. For instance should we consider separating the geographic representation from the cartographic representation. This may be similar as to ESRI's cartographic layer. A great concept. This way multiple clients or uses can be achieved from the same growing and changing data sources.

Furthermore, for the representations there is also the layout (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf#page=13). Perhaps we can learn lots from the desktop publishing world from the likes of the Scribus project (http://www.scribus.net/). Maybe being able to export a certain portion to scribus to handle some the major layout hurdles. A link between the cartographic library and scribus vcould allow for auto generation of some layout features and text such as changing declination, Projection info, and others.

Second, is the rule based approach. Natural Resource Canada (NRCAN)publishes their Cartographic Specifications (http://ess.nrcan.gc.ca/pubs/carto/downloads/design_specs.pdf). Could these be stored in a database or XML format that can be applied to multiple maps?

OSGeo Cartographic Engine

2008-04-07T13:37:01Z

Wiki-Dsampson: /* Interested people */

OSGeo Cartographic Engine

2008-04-07T13:36:27Z

Wiki-Dsampson: /* Interested people */

OSGeo Cartographic Engine

2008-04-07T13:32:42Z

Wiki-Dsampson: /* Interested people */

Commercial Services

2008-02-19T20:57:32Z

Wiki-Dsampson:

''The Open Source Geospatial Foundation is a non profit organization and does not provide commercial services.''

= Commercial use of OSGeo Software =
There are excellent preconditions to use [[Free Software | Free]] and [[Open Source]] Software packages in [[Business]] contexts. To make most effective use of software (regardless of licensing style) it can be helpful to hire commercial service providers. They can deliver solutions, support and service in time and through regular contracts. In larger environments and complex infrastructures it is normal to hire specialists to look after the network infrastructure, perform database tuning, customize software or consult on the architecture. This applies to both proprietary and Free and Open Source Software.

OSGeo does not provide these services itself but has set up a [[Service Provider Directory]] to make this information available to businesses and organizations in need of professional services and with a budget to afford them.

= [[FOSS]] Business Models =
[[FOSS]] Business Models models are identical to those of any other IT enterprise. The only element which is missing is selling license usage rights through the proprietary licensing model. [[Professional Support]] and services provided by companies around the world comprise:

* Training, Workshops, Know-how dissemination
* Installation, Maintenance
* Consultation
* Customization of interfaces and features
* Implementation of new features
* Support and Hotline at all availability levels
* Research and Development
* ''add your source of income''

Depending on the focus of the enterprise the business model can combine any of the above types.

= Business Ready Software =
Ready-to-use software is sometimes called COTS (Commercial Off The Shelf) software. There are several packages within OSGeo and the Free and Open Source community at large that can be used right off the shelf (but does not ship in shrink-wrap packages). Others like libraries, services or other infrastructure components need to be installed and configured individually, sometimes in large and highly complex or productive environments. Some such structures need to be maintained on a daily basis, for example if security requirements (Confidentiality, Availability, Integrity) are exceptionally high. Free and Open Source Geospatial software is used in allof these contexts and is just as diverse as are the needs.

Graduated OSGeo Software has gone through the [[Incubation Process]] and thus proven to follow the guidelines that have been set up to ensure several soft factors that a software ''project'' cannot always provide out of itself. These include legally clean code licenses and use of external libraries, a functioning community and truly open governance and decision structure. Additionally some technical requirements have been defined as being minimal to a healthy project like the use of a code repository, bug tracking environment and support mechanism, most often through mailing lists.

[[Category:Advocacy]]

Business

2008-02-19T20:54:58Z

Wiki-Dsampson: /* Studies */

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

=Business Resources=
these are some resources for companies or individual contractors to better understand FOSS4G business models

==Studies==
A listing of various studies in FLOSS and FOSS4G

* Report by e-Cology Corporation on its [http://www.e-cology.ca/canfloss/report/ study of open source software (OSS) in Canada], which was contracted out by the Government of Canada

== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Business

2008-02-19T20:54:48Z

Wiki-Dsampson: /* Studies */

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

=Business Resources=
these are some resources for companies or individual contractors to better understand FOSS4G business models

==Studies==
A listing of various studies in FLOSS and FOSS4G

* Report by e-Cology Corporation on its [http://www.e-cology.ca/canfloss/report/ | study of open source software (OSS) in Canada], which was contracted out by the Government of Canada

== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Business

2008-02-19T20:54:32Z

Wiki-Dsampson: /* Studies */

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

=Business Resources=
these are some resources for companies or individual contractors to better understand FOSS4G business models

==Studies==
A listing of various studies in FLOSS and FOSS4G

* Report by e-Cology Corporation on its [[http://www.e-cology.ca/canfloss/report/ | study of open source software (OSS) in Canada]], which was contracted out by the Government of Canada

== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Business

2008-02-19T20:54:01Z

Wiki-Dsampson:

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

=Business Resources=
these are some resources for companies or individual contractors to better understand FOSS4G business models

==Studies==
* report by e-Cology Corporation on its [[http://www.e-cology.ca/canfloss/report/ | study of open source software (OSS) in Canada]], which was contracted out by the Government of Canada
== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Business

2008-02-19T20:53:31Z

Wiki-Dsampson:

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

=Business Resources=
these are some resources for companies or individual contractors to better understand FOSS4G business models

==Studies==
* report by e-Cology Corporation on its [[http://www.e-cology.ca/canfloss/report/ | study of open source software (OSS) in Canada]], which was contracted out by the Government of Canada

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Business

2008-02-19T20:50:59Z

Wiki-Dsampson:

=Definition=
Business means ''being busy'' sometimes with the connotation of ''making money''. If you need to know more precisely you might want to check the [http://en.wikipedia.org/wiki/Business Wikipedia article on Business] and please always consider viewing it from several perspectives to thoroughly understand.

== OSGeo's Service Provider Directory ==
In many cases [[Professional Support]] will help to speed up using and operating any kind of software environment. In some cases [[Commercial Services]] will be required to get something done in time. To make information about service providers who offer both professional and or commercial support more accessible to potential users and businesses OSGeo maintains a [[Service Provider Directory]].

Feel free to add your [[Commercial Services]] or company to this directory or use it to search for service providers near your location or with special skills you are in need for.

== OSGeo and Business ==
OSGeo is '''not''' a business club. Instead it aims at being a not-for-profit[1] organization. Nonetheless a lot of the software, training and geospatial data is produced, maintained and enhanced by commercial enterprises. Services are offered around [[Free Software]] and [[Open Source]] for pay, which again is a commercial activity.

[1] ...which is a stupid conflict in English legal talk because obviously everybody makes a profit from OSGeo's existence.

[[Category:Advocacy]]

Ottawa Chapter

2008-01-14T15:33:13Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: January - 17 
Time: 6pm 
Location: Fox and Feather (regular Room) [http://maps.google.ca/maps?q=fox+feather++Ottawa+On+ca MAP] 
Presentation:
* TBD
 
Business Items:

* General Discussion
* Upcoming events
* TBD
* Eat, Drink, Be Merry. 

== Report on December 12's meeting: ==

* We held an introductory workshop on GRASS and GRASS/QGIS integration, using the most recent "stable release" versions of GRASS and QGIS. We forgot to count heads while everyone was still there, but 9-10 people participated, helping to debug a new tutorial Scott Mitchell is developing. The [http://cemml.carleton.ca/osgeo_files/tutdoc.pdf tutorial document is available here].
 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

A Powerpoint presentation reporting on our chapter's formation and first year of activity is available for download in its original [http://cemml.carleton.ca/osgeo_files/local-chap.ppt full version], or the [http://cemml.carleton.ca/osgeo_files/OttLocal-chap_condensed.ppt condensed form] created to squeeze into a tighter time constraint.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

Powerpoint

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]
[[Category:Canada]]

Ottawa Chapter

2008-01-14T15:32:01Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: January - 17 
Time: 6pm 
Location: Fox and Feather (regular Room) [http://maps.google.ca/maps?q=615+Booth+Street++Ottawa+On+ca MAP] 
Presentation:
* TBD
 
Business Items:

* General Discussion
* Upcoming events
* TBD
* Eat, Drink, Be Merry. 

== Report on December 12's meeting: ==

* We held an introductory workshop on GRASS and GRASS/QGIS integration, using the most recent "stable release" versions of GRASS and QGIS. We forgot to count heads while everyone was still there, but 9-10 people participated, helping to debug a new tutorial Scott Mitchell is developing. The [http://cemml.carleton.ca/osgeo_files/tutdoc.pdf tutorial document is available here].
 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

A Powerpoint presentation reporting on our chapter's formation and first year of activity is available for download in its original [http://cemml.carleton.ca/osgeo_files/local-chap.ppt full version], or the [http://cemml.carleton.ca/osgeo_files/OttLocal-chap_condensed.ppt condensed form] created to squeeze into a tighter time constraint.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

Powerpoint

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]
[[Category:Canada]]

Ottawa Chapter

2008-01-14T15:31:45Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: January - 17 
Time: 6pm 
Location: Fox and Feather (regular Room) [http://maps.google.ca/maps?q=615+Booth+Street++Ottawa+On+ca title]MAP 
Presentation:
* TBD
 
Business Items:

* General Discussion
* Upcoming events
* TBD
* Eat, Drink, Be Merry. 

== Report on December 12's meeting: ==

* We held an introductory workshop on GRASS and GRASS/QGIS integration, using the most recent "stable release" versions of GRASS and QGIS. We forgot to count heads while everyone was still there, but 9-10 people participated, helping to debug a new tutorial Scott Mitchell is developing. The [http://cemml.carleton.ca/osgeo_files/tutdoc.pdf tutorial document is available here].
 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

A Powerpoint presentation reporting on our chapter's formation and first year of activity is available for download in its original [http://cemml.carleton.ca/osgeo_files/local-chap.ppt full version], or the [http://cemml.carleton.ca/osgeo_files/OttLocal-chap_condensed.ppt condensed form] created to squeeze into a tighter time constraint.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

Powerpoint

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]
[[Category:Canada]]

Ottawa Chapter

2008-01-14T14:42:41Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: January - 17 
Time: 6pm 
Location: Fox and Feather (regular Room) 
Presentation:
* TBD
 
Business Items:

* General Discussion
* Upcoming events
* TBD
* Eat, Drink, Be Merry. 

== Report on December 12's meeting: ==

* We held an introductory workshop on GRASS and GRASS/QGIS integration, using the most recent "stable release" versions of GRASS and QGIS. We forgot to count heads while everyone was still there, but 9-10 people participated, helping to debug a new tutorial Scott Mitchell is developing. The [http://cemml.carleton.ca/osgeo_files/tutdoc.pdf tutorial document is available here].
 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

A Powerpoint presentation reporting on our chapter's formation and first year of activity is available for download in its original [http://cemml.carleton.ca/osgeo_files/local-chap.ppt full version], or the [http://cemml.carleton.ca/osgeo_files/OttLocal-chap_condensed.ppt condensed form] created to squeeze into a tighter time constraint.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

Powerpoint

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]
[[Category:Canada]]

OSGeo:Community Portal

2007-10-20T14:31:55Z

Wiki-Dsampson: /* News */ added Canadian Chapter page creation

Lets see whether the village pump is going to get some good use. Add discussions, gossip, news here. Don't know how to or why? Read the help on [[Getting Started]].

Or chat in IRC: [irc://irc.freenode.net/#osgeo #osgeo]

== News ==
''Newest on top''
* [[Canada]] chapter is looking for interested individuals (October, 2007)
* [[Board Election 2007]] nomination possible until July 19th, 2007 Voting tentatively starts July 23rd
* [[New Member Nominations]] possible until June 3rd, 2007.
* [[Mapbender Development Sprint Spring 07]]
* [http://grass.itc.it/announces/announce_grass621.html GRASS GIS 6.2.1 Released] (12 December 2006)
* Somewhat belated [[Intergeo 2006 Report]] with pictures and details on how to organize such an event
* [http://www.directionsmag.com/press.releases/index.php?duty=Show&id=15020 GRASS GIS 6.1.0 released] (11 August 2006)
* [http://mail.osgeo.org/servlets/ReadMsg?list=discuss&msgNo=696 Ottawa, Canada Local chapter discussion meeting] (July 20, 2006)
* [http://www.directionsmag.com/press.releases/?duty=Show&id=13648&trv=1 GRASS GIS 6.0.2 released] (February 22, 2006)
* [[OSGEO Icons and Humor]] (content warning)
* [http://www.mapbender.org/index.php/Mapbender_2.2.3_for_download Mapbender 2.2.3 avaliable for download] Learn more about it at the [[FOSSGIS 2006]] conference in Bonn, Germany.

Canada

2007-10-20T14:20:24Z

Wiki-Dsampson: Added Representation by prov/terr

There are many people involved in OSGeo who are from [http://atlas.nrcan.gc.ca/site/english/maps/reference/national/can_political_e/referencemap_image_view Canada]. This page is to try to gather interest in establishing a nation-wide OSGeo chapter. The [[Ottawa]] Local Chapter has focused on the nation's capital, and other cities are sure to have particular smaller groups of interest as well.

= Mission =

= Objectives =
* Support development of local OSGEO chapters
* Support National Geomatics events to promote FOSS4G and OSGEO
* Organize National Geomatics events to promote FOSS4G and OSGEO
* Participate in National Geomatics events to promote FOSS4G and OSGEO

= Resources =
* Starting a local Chapter
* [[Local Chapter Guidelines]]
* [[Proposed Membership Rules]]
* [[Interest Groups]]
* [[Like Minded Regional Organizations]]
* [[One Organizational Model]]
* [[International Outreach]]

= Representation (Prov/Terr) =
A good goal would be for full representation across the country. Please change the list as we add missing representation. Either a group or single individual can be considered a representation. Next to the abbreviation we can list regional chapters that are also represented in this group. A regional chapter is not required for representation but can help network people to local activities.
== Present ==
* BC: [[British Columbia Chapter]],
* ON: [[Ottawa Chapter]],
* QC:
* MB:
* PEI:

== Absent ==
* NL
* NS
* NB
* AB
* NW
* NU

= Interested Individuals =
* [[User:Tmitchell | Tyler Mitchell]], [http://osgeo.org OSGeo], [http://tinyurl.com/295q2l Williams Lake], [http://atlas.nrcan.gc.ca/site/english/maps/reference/provincesterritories/british_columbia/referencemap_image_view British Columbia]

* [[User:Dpatton | Dave Patton]], CIS and [http://www.confluence.org Degree Confluence Project], [http://tinyurl.com/2tnkda Victoria], [http://atlas.nrcan.gc.ca/site/english/maps/reference/provincesterritories/british_columbia/referencemap_image_view British Columbia]

* [[User:Dsampson | Dave Sampson]], [[Ottawa_Chapter | Ottawa Chapter]]

* [http://www.kralidis.ca/ Tom Kralidis], Charter Member, Toronto, ON

*[[User:Smitch | Scott Mitchell]], [[Ottawa_Chapter | Ottawa Chapter]], [http://www.carleton.ca/geography Carleton University], [[GRASS | GRASS project (PSC)]]

* [[User:Madair | Mike Adair]], [[Ottawa_Chapter | Ottawa Chapter]], Charter member, [[Mapbuilder | MapBuilder project]], DM Solutions Group

* [[User:Dmorissette | Daniel Morissette]], [http://www.mapgears.com/ Mapgears], Chicoutimi, QC

* [[User:Mleslie | Mark Leslie]], [http://www.lisasoft.com/ LISAsoft], Sydney, [http://atlas.nrcan.gc.ca/site/english/maps/reference/international/oceania/referencemap_image_view AU] (but I'm still Canadian)

* [[User:MapperBob | Bob Bruce]] [http://www.gov.mb.ca/conservation/geomatics/ Province of Manitoba], [http://www.hwps.ca HWPS], Winnipeg, Manitoba. Interests: MapServer, QGIS, uDig, [http://mli.gov.mb.ca/ Manitoba Land Initiative (MLI)], [http://mlidata.gov.mb.ca/WPMLI Manitoba Land Initiative (MLI) Webmap], [http://mlidata.gov.mb.ca/wms/request.aspx MLI WMS Server]

* [[User:Tbadard | Thierry Badard]], [[Conference_Committee | Conference Committee]], [[Francophone | Francophone Chapter]], [http://geosoa.scg.ulaval.ca/fr Laval University (Centre for Research in Geomatics) ], Quebec City, QC

* [[User:Sanderson | Ken Sanderson]], [http://www.rockies.ca/ Miistakis Institute], Hope River, PEI

* [[User:Aleroux | Alexandre Leroux]], [http://eer.cmc.ec.gc.ca/index_e.php Canadian Meteorological Centre] and [http://slashgeo.org Slashgeo], Montreal, Qc

* [[User:swallbridge | Shawn Wallbridge]] Hobbyist, [http://www.synack-hosting.com SynAck Hosting], Winnipeg, Manitoba.

= Links =
[[Category:Local Chapters]]
[[Category:Canada]]

Canada

2007-10-09T13:11:50Z

Wiki-Dsampson: Added resources section

Canada

2007-10-09T13:08:56Z

Wiki-Dsampson: /* Objectives */ Added two points

Canada

2007-10-09T13:04:42Z

Wiki-Dsampson: /* Interested Individuals */

Ottawa Chapter

2007-08-28T19:32:20Z

Wiki-Dsampson: new business item

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: September 6 
Time: 6pm 
Location: Fox and Feather Pub (upstairs, small room) 
Address: 283 Elgin Street (at Maclaren St) 
[http://maps.google.ca/maps?f=q&hl=en&q=fox+and+feather+ottawa&ie=UTF8&z=12&ll=45.422793,-75.72361&spn=0.134701,0.244789&om=1&iwloc=A map]
 
 
Presentation:
The State of GDAL (tentative) 
Presenter: Frank Warmerdam 
 
Business Items:
* Present your local chapter at FOSS4G
* TBA 
* Eat, Drink, Be Merry 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]

Ottawa Chapter

2007-08-28T19:32:01Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==
[[Image:OSGeo_July_Meeting.jpg|thumb|right|The July meeting turn out (more or less).]]

Date: September 6 
Time: 6pm 
Location: Fox and Feather Pub (upstairs, small room) 
Address: 283 Elgin Street (at Maclaren St) 
[http://maps.google.ca/maps?f=q&hl=en&q=fox+and+feather+ottawa&ie=UTF8&z=12&ll=45.422793,-75.72361&spn=0.134701,0.244789&om=1&iwloc=A map]
 
 
Presentation:
The State of GDAL (tentative) 
Presenter: Frank Warmerdam 
 
Business Items:
* Present you local chapter at FOSS4G
* TBA 
* Eat, Drink, Be Merry 

== Mailing List ==

You can [http://lists.osgeo.org/mailman/listinfo/Ottawa_users subscribe] and review the
[http://lists.osgeo.org/pipermail/ottawa_users archive] of Ottawa_users@lists.osgeo.org.

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Additionally you might want to consider adding <nowiki>[[Category:Ottawa Chapter]]</nowiki> to all pages tagging them for the [http://wiki.osgeo.org/index.php/Special:Categories Wiki Categories]. Then add that category to the <nowiki>[[Category:Local Chapters]]</nowiki> and have a category of categories. Or just go have some more beer.

[[Category:Local Chapters]]

Journal Volume 2 Ottawa Local Chapter

2007-07-04T18:23:30Z

Wiki-Dsampson: /* Authors */

THIS IS A DRAFT
----
==Article Guidelines==

from TylerM:

"Think of it as a bulletin board for sharing pieces of news with the worldwide OSGeo community or inviting others to join in your work.

I invite you to contribute a short summary of the sorts of things your group has been working on. The Journal will be published (digitally) by August, but if you want to contribute an article we will need it by July 6th."
----
==Article Draft==

===Background===

The Ottawa Local Chapter of OSGeo was formed in July 2006 in Ottawa, Ontario, Canada. The group is a union of two previously existing groups: the Ottawa GRASS Users Group (OGUG) formed in June 2005, and the Ottawa MapServer Users Group (OMSUG) formed in winter 2003. Both groups were already very active in the FOSS4G community, with OGUG continuing development and use of the Public Geodata License in english (http://cemml.carleton.ca:8080/OGUG/pgl), and OMSUG hosting the 2004 Open Source GIS Conference in Ottawa (http://www.omsug.ca/osgis2004/). The Ottawa OSGEO Chapter was formed by the combination of those original two groups, but also includes active local users and developers of at least the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and MapServer.

===Mission===
The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

===Chapter Co-Chairs===
* Dave Sampson, Natural Resources Canada
* Jeff McKenna, DM Solutions Group

===Current Activities===
Meeting approximately once a month, the Chapter regularly enjoys presentations and discussions on various FOSS4G subjects, as well as refreshments. Recent presentation topics include the Nunaliit Atlas Framework (http://nunaliit.org/), as well as GeoServer's functionality (http://www.geoserver.org/).

===Important Links===
* [http://lists.osgeo.org/mailman/listinfo/Ottawa_users mailing list]
* [http://wiki.osgeo.org/index.php/Ottawa_Chapter home page]

==Authors==
* [[User:jmckenna|Jeff McKenna]]
* [[User:dsampson|Dave Sampson]]

User:Dsampson

2007-07-04T18:22:32Z

Wiki-Dsampson:

Dave Sampson currently works with [http://maps.nrcan.gc.ca/index_e.php Centre for Topographic Information] at Natural Resources Canada and is actively contributing to OSGeo.

* User of [[GRASS]]
* OSGEO Education
* OSGEO Data

Other open Source GIS
* Promoter and user of PGAC
* Implementing open source technologies

User:Dsampson

2007-07-04T18:20:03Z

Wiki-Dsampson:

Dave Sampson currently works with [http://maps.nrcan.gc.ca/index_e.php Centre for Topographic Information] at Natural Resources Canada and is actively contributing to OSGeo.

* User of [[GRASS]]
* Promoter and user of PGAC
* OSGEO Education
* Implementing open source technologies
*

Journal Volume 2 Ottawa Local Chapter

2007-07-04T18:15:35Z

Wiki-Dsampson: /* Authors */

Journal Volume 2 Ottawa Local Chapter

2007-07-04T18:13:58Z

Wiki-Dsampson: updated OGUG history, added reference to OSGEO ottaw chapter in closing sentence

Ottawa Chapter

2006-12-04T14:15:32Z

Wiki-Dsampson:

== Next Meeting ==

Date: Thursday December 7 
Time: 6pm 
Location: Fox and Feather ? TBConfirmed... 
Address: 
Map: 
 
Presentation: 
''OSGeo Executive Director, Tyler Mitchell'' 
* Meet and greet
* General OSGEO Discussion
 
Business Items:
* TBA 
* Eat, Drink, Be Merry 

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and broadening our collective focus to include all OSGeo projects, catering to any interested users or developers in the Ottawa (National Capital Region) area. We are now officially designated as an OSGeo chapter.

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

The Ottawa Chapter of OSGeo was formed by the combination of those original two groups, but also includes active local users and developers of at LEAST the following OSGeo projects: GDAL/OGR, GRASS, Mapbuilder, MapGuide, and Mapserver.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Ottawa Chapter

2006-10-11T14:33:48Z

Wiki-Dsampson: /* Chapter Resources */

== Next Meeting ==

Date: Thursday November 2 
Time: 6:pm 
Location: TBA 
 
Presentation: TBA 
 
Business Items:
* TBA 
* Eat, Drink, Be Mary 

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and operating as an OSGeo local chapter in the Ottawa (National Capital Region) area. While not yet officially designated as an OSGeo chapter, we are "in formation".

The Ottawa Chapter of OSGEO is formed by the combination the local active communities of three OSGEo projects: Mapserver, GRASS and Mapbuilder

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

[[Ottawa_Chapter/associations| Various associations related to Geospatial ]]:

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Ottawa Chapter

2006-10-11T14:33:37Z

Wiki-Dsampson: Add Association section lin

Ottawa Chapter

2006-10-06T12:23:31Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==

Date: Thursday November 2 
Time: 6:pm 
Location: TBA 
 
Presentation: TBA 
 
Business Items:
* TBA 
* Eat, Drink, Be Mary 

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and operating as an OSGeo local chapter in the Ottawa (National Capital Region) area. While not yet officially designated as an OSGeo chapter, we are "in formation".

The Ottawa Chapter of OSGEO is formed by the combination the local active communities of three OSGEo projects: Mapserver, GRASS and Mapbuilder

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Ottawa Chapter/Admin/meetings/100506

2006-10-06T12:18:44Z

Wiki-Dsampson:

Thursday Oct 5 
6pm 
Clock Tower Brew Pub 
575 Bank Street 
Ottawa, ON K1S 5L7 
(613) 233-7849 

[http://www.google.ca/maps?num=50&hl=en&hs=JhR&lr=&client=firefox-a&rls=org.mozilla:en-US:official&q=clock+tower+brew+pub&near=Ottawa,+ON&sa=X&oi=local&ct=title Map]

* Report on aproval by the OSGEO Board for our local chapter (Frank W)
* Presentation on Community Map Builder (Mike Adair)
* Eat Drink and be merry!

Ottawa Chapter

2006-10-06T12:18:26Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and operating as an OSGeo local chapter in the Ottawa (National Capital Region) area. While not yet officially designated as an OSGeo chapter, we are "in formation".

The Ottawa Chapter of OSGEO is formed by the combination the local active communities of three OSGEo projects: Mapserver, GRASS and Mapbuilder

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets

Ottawa Chapter/Admin

2006-10-06T12:17:35Z

Wiki-Dsampson: /* Meetings */

== Executive Members==
Chair: Dave Sampson
Co-Chair: Jeff McKenna

== Meetings ==



[[Ottawa_Chapter/Admin/meetings/072006 | July 20 2006]] 
[[Ottawa_Chapter/Admin/meetings/083106 | August 31 2006]] 
[[Ottawa_Chapter/Admin/meetings/100506 | October 6 2006]] 

== Chapter Navigation ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.

Ottawa Chapter

2006-10-03T16:08:11Z

Wiki-Dsampson: /* Next Meeting */

== Next Meeting ==

Thursday Oct 5 
6pm 
Clock Tower Brew Pub 
575 Bank Street 
Ottawa, ON K1S 5L7 
(613) 233-7849 

[http://www.google.ca/maps?num=50&hl=en&hs=JhR&lr=&client=firefox-a&rls=org.mozilla:en-US:official&q=clock+tower+brew+pub&near=Ottawa,+ON&sa=X&oi=local&ct=title Map]

* Report on aproval by the OSGEO Board for our local chapter (Frank W)
* Presentation on Community Map Builder (Mike Adair)
* Eat Drink and be merry!

== About Ottawa OSGEO ==

The OGUG (Ottawa Grass Users Group) and OMSUG (Ottawa Map Server Users Group) have had a preliminary joint meeting and decided to pursue merging and operating as an OSGeo local chapter in the Ottawa (National Capital Region) area. While not yet officially designated as an OSGeo chapter, we are "in formation".

The Ottawa Chapter of OSGEO is formed by the combination the local active communities of three OSGEo projects: Mapserver, GRASS and Mapbuilder

The Ottawa MapServer Users Group (OMSUG) began meeting during the winter of 2003. With a strong local user base in Ottawa, representing many diverse users and developers, these meetings provide a unique opportunity for members to meet and discuss how MapServer is being leveraged in Ottawa and ways we can work together to grow its use in the region.

OGUG formed in June of 2005 as a network of GIS practitioners interested in incorporating or replacing their proprietary GIS workflow with Open Source GIS Solutions. OGUG aimed to be a central body of knowledge and expertise for the GRASS GIS Community in the Ottawa area.

=== Mission ===

The OSGeo Ottawa Chapter exists to provide support for local users of Open Source Geospatial software, and to promote the goals and projects of the Open Source Geospatial Foundation. The Chapter is focused on the National Capital Region around Ottawa with face to face meetings providing networking, support and educational opportunities to the local members.

=== Objectives ===
* Monthly face to face meetings
** Networking
** Presentations
** Workshops and Tutorials
** User to user support
** Job Opportunities
** HowTo's
* Colaborative Projects
** Documentation
** Local Data Sets
** Supporting OSGEO projects at large
* Regional Events
** Conference
** Demonstrations
* Communication
** Active mailing List
** Content Rich Wiki
** Outreach to local Geo community
** Documented Activities

== Chapter Sections ==
[[Ottawa_Chapter | Ottawa Chapter Home]]:
The WIKI Home Page for the Ottawa OSGEO Chapter.


[[Ottawa_Chapter/Admin | Chapter Admin]]:
Information of interest to the chapter at large concerning meetings, events, charter,etc.

[[Ottawa_Chapter/MAPSERVER | MapServer]]:
Information of interest to local MAPSERVER users (including old OMSUG content)

[[Ottawa_Chapter/GRASS | GRASS]]:
Information of interest to local GRASS users (including old OGUG content)

[[Ottawa_Chapter/MAPBUILDER | MapBuilder]]:
Information of interest to local MAPBUILDER users


[[Ottawa_Chapter/Directory | Local Chapter Directory]]:
Listing of companies, people, universities and government departments involved with or using OSGeo projects

[[Ottawa_Chapter/Media | Ottawa OSGEO Media Coverage]]:
Links or snippets of media featuring activities of Ottawa OSGeo from various Sources

== Chapter Resources ==
[[Ottawa_Chapter/data | Data]]:
Free and open data created by local chapter members

[[Ottawa_Chapter/tutorials | Tutorials]]:
Tutorials supporting related FOSS4G projects

[[Ottawa_Chapter/links | Related Links]]:
A Clearing House of related links

== Contributing to this wiki ==
=== How To Write WIKI ===
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Page Naming Conventions ===
Since the whole wiki uses a flat file structure instead of a directory structure there is a need to organize the pages relavant to our chapter's activities. To get this wiki area started I chose a simple page structure format

PREFIX:
To keep the site clean and to make it easier to locate all WIKI pages connected with the Ottawa Chapter please not the appropriate prefix. Use this prefix when creating new pages.

Prefix= Ottawa_Chapter

The logic:
* Ottawa_Chapter_(Project Area)_(Topic)_(Sub Topic)

Examples: 
* Ottawa_Chapter_OSGEO_meetings_072106
* Ottawa_Chapter_GRASS_Datasets