OSGeo - User contributions [en]

Nordic

2011-04-13T21:10:07Z

Wiki-Turban:

= OSGeo Nordic chapter =

This is a first try at getting the Nordic users to get to know each other and who is doing what, the goal is to create a formal OSGeo Nordic chapter. From this point onwards, the page will be in any of the Scandinavian languages (Swedish, Danish or Norwegian).

== Aktiviteter og prosjekter ==

[[Nordic:inspire WMS|INSPIRE compliant VewServices]]

== Potensielle medlemsnasjoner ==

Denne OSGeo gruppen er ment for de [http://en.wikipedia.org/wiki/Nordic_countries nordiske landene]

*Norge
*Danmark
*Sverige
*Finland
*Island

== Språk ==

Norsk, dansk og svensk vil være offisielle arbeidsspråk for et nordisk OSGeo chapter.

Om engelsk skal tillates eller ikke kan være opp til gruppen, etter hvert som den formes, å bestemme. Å tillate engelsk muntlig og skriftlig i gruppen vil nok være fornuftig, men muligens ikke som offisielt språk.

== Målsetting ==

Hovedhensikten med et nordisk OSGeo chapter er å skape en felles arena der de nordiske landene kan samarbeide om bruk av fri geoprogramvare. De nordiske landene har mange felles utfordringer og burde derfor kunne trekke veksler på hverandres erfaringer. Noen hovedoppgaver landene har felles og står overfor er:

*Implementering av [http://inspire.jrc.ec.europa.eu/ INSPIRE] tjenester
**View Services
**Download Services
*Metadatakatalog
*En robust og effektiv nasjonal geografisk infrastruktur

Et [http://beta.geonorge.no/wiki/index.php/Main_Page nordisk initiativ] er allerede opprettet for utvikling av [http://www.osgeo.org/geonetwork GeoNetwork Opensource] programvaren, der medlemslandene deler på kostnadene ved utvikling og deler kildekoden og funksjonaliteten som utvikles. Denne måten å gjennomføre utvikling på er effektivt for alle, og kostnadene reduseres. Etableringen av et nordisk OSGeo chapter er et forsøk på å utvide dette samarbeidet til å gjelde flere programvarekomponenter, og forankre samarbeidet i en større helhet som OSGeo.

'''OSGeo gruppen bør ha et teknisk fokus og samarbeidet i gruppen skal ha fokus på teknologisk utvikling''' for å løse felles problemstillinger. Kunnskapsdeling om hvordan man kan utnytte FOSS4G programvareporteføljen bør være en viktig del av OSGeo Nordic chapter. Erfaringer aktører i hver enkelt nasjon har gjort, er viktig for at de andre nasjonene fortere å kunne nå sine egne mål.

Generell utveksling av kompetanse og erfaring på teknisk nivå.

== Organisering ==

TBD

Kommersielle aktører er velkommen til å delta i gruppen på like vilkår som alle andre.

=== Mailingliste ===

19.10.2010: Interessen for gruppen begynner nå å bli så stor at Statens kartverk vil ta kontakt med OSGeo, og presenteret behovet for en dedikert mailingliste for OSGeo Nordic Chapter.

'''25.10.2010: Mailinglisten er etablert :) Meld deg på her - http://lists.osgeo.org/mailman/listinfo/nordic'''

=== Interessenter ===

Hvis du er interessert å delta i en nordisk OSGeo gruppe, vennligst fyll inn personlig innformasjon i tabellen under. Hvis du i tillegg er interessert i å bidra til å forme gruppen, skriv Ja/Nei/Kanskje i feltet ''bidra til organisering''.

<br> ''Tips: Bruk Rich Editor (valg rett over redigeringsboksen) for enklere redigering av tabellen.''

<br>

{| cellspacing="4" cellpadding="4" align="left" style="width: 742px; height: 606px;"
|-
! align="center" scope="col" style="background: none repeat scroll 0% 0% rgb(240, 240, 240);" | '''Navn'''
! align="center" scope="col" style="background: none repeat scroll 0% 0% rgb(240, 240, 240);" | '''Nasjonalitet'''
! align="center" scope="col" style="background: none repeat scroll 0% 0% rgb(240, 240, 240);" | '''Arbeidsgiver'''
! align="center" scope="col" style="background: none repeat scroll 0% 0% rgb(240, 240, 240);" | '''Lokasjon'''
! align="center" scope="col" style="background: none repeat scroll 0% 0% rgb(240, 240, 240);" | '''Bidra til organisering'''
|-
| [[User:Kripal|Pål Kristensen]]
| Norsk
| Statens kartverk
| Hønefoss, Norge
| Ja
|-
| [[User:Relet|Thomas Hirsch]]
| Annet
| Statens kartverk
| Hønefoss, Norge
| Nei
|-
| [[User:Dybrol|Rolf Dybdal]]
| Norsk
| Statens kartverk
| Hønefoss, Norge
| Ja
|-
| [[User:Trondmm|Trond Michelsen]]
| Norsk
| Meteorologisk institutt
|
| Ja
|-
| [[User:Geira|Geir Aalberg]]
| Norsk
| Meteorologisk institutt
|
| Ja
|-
| [[User:Arneke|Arne Kepp]]
| Annet
| Infinite Loop AS
|
| Ja
|-
| [http://wiki.osgeo.org/wiki/User:Demartino Jørgen Larsen de Martino]
| Dansk
| Kort og matrikelstyrelsen
|
| Nej
|-
| [[User:Julian Hollingbery|Julian Hollingbery]]
| Dansk
| Kort og matrikelstyrelsen
|
| Nej
|-
| [[User:Morpl|Morten Lindegaard]]
| Dansk
| Kort og Matrikelstyrelsen
| København, Danmark
| Nej
|-
| [[User:Jolni|Jonas Lund Nielsen]]
| Dansk
| Kort og Matrikelstyrelsen
| København, Danmark
| Nej
|-
| [[User:Martin.Hvidberg|Martin Hvidberg]]
| Dansk
| Aarhus Universitet, Danmarks Miljøundesøgelser
| Roskilde, Danmark
| Nej
|-
| [[User:Runarbe|(Stein) Runar Bergheim]]
| Norsk
| AVINET
|
| Ja
|-
| [[User:Halset|Tore Halset]]
| Norsk
| Electronic Chart Centre
| Stavanger, Norge
| Ja
|-
| [[User:Ragnvald|Ragnvald Larsen]]
| Norsk
| Direktoratet for Naturfovaltning
| Trondheim, Norge
| Ja
|-
| [[User:Bgrotan|Bjørn Ove Grøtan]]
| Norsk
| Norges geologiske undersøkelse
| Trondheim, Norge
| Ja
|-
| [[User:MichaelOstling|Michael Östling]]<span class="Apple-tab-span" style="white-space: pre;">[[User:MichaelOstling| ]]</span>
| Svensk
| MetaGIS AB
| Falun, Sverige
| Nej
|-
| [[User:Fredper|Fredrik Persäter]]
| Svensk
| Lantmäteriet
| Kiruna, Sverige
| Nej
|-
| [[User:Tellett|Tom Ellett von Brasch]]
| Engelsk
| Statens kartverk
| Hønefoss, Norge
| Nej
|-
| [[User:Nicklas|Nicklas Avén]]
|
|
| Våler i Solør, Norge
| Nej
|-
| [[User:Gisassistans|Anders Söderman]]
| Svensk
| Firma GISassistans
| Stockholm, Sverige
| Ja, gärna.
|-
| [[User:Frodewj|Frode Wiseth Jørgensen]]
| Norsk
| AVINET
| Trondheim, Norge
| Ja
|-
| [[User:Sverre|Sverre Iversen]]
| Norsk
| Norges geologiske undersøkelse
| Trondheim, Norge
| Ja
|-
| [[User:JonasHolmberg|Jonas Holmberg]]
| Svensk
| Sveriges geologiska undersökning (SGU)
| Uppsala, Sverige
| Nej
|-
| [[User:Esisa|Espen Isaksen]]
| Norsk
| Institutt for Skog og Landskap
| Ås, Norge
| Nei
|-
| [[User:Arnfra|Frank Arntsen]]
| Norsk
| Statens kartverk
| Norge
|
Ja

|-
| [[User:Jkylmaaho|Jani Kylmäaho]]
| Engelsk
| Lantmäteriverket
| Finland
| Nej
|-
| [[User:Turban|Bjørn Sandvik]]
| Norsk
| NRK
| Norge
| Ja

|}

Nordic

2011-04-13T21:09:05Z

Wiki-Turban:

OSGeo Cartographic Engine

2008-04-26T17:06:49Z

Wiki-Turban: /* Interested people */

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

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

== See also ==

* [[OSGeo map symbol set]]

[[Category: Software Stack]]

User:Turban

2008-04-08T16:46:34Z

Wiki-Turban:

'''Bjorn Sandvik'''

I’m working as a project manager at United Nations Association (UNA) of Norway, - currently on study leave to undertake a master's in Geography Information Science (GIS) at University of Edinburgh.

* [http://blog.thematicmapping.org Blog]

User:Turban

2008-04-08T16:44:29Z

Wiki-Turban: New page: '''Bjorn Sandvik''' * [http://blog.thematicmapping.org Blog]

'''Bjorn Sandvik'''

* [http://blog.thematicmapping.org Blog]