OSGeo - User contributions [en]

INSPIRE

2008-08-28T11:26:27Z

Wiki-Roy: /* FIT/GAP analysis */

[http://eu-geoportal.jrc.it/ INSPIRE] is a European based approach at solving interoperability issues for gespatial data.

== Introduction (from http://eu-geoportal.jrc.it/) ==

''INSPIRE (Infrastructure for Spatial Information in Europe) is an initiative launched by the European Commission and developed in collaboration with Member States and accession countries. It aims at making available relevant, harmonized and quality geographic information to support formulation, implementation, monitoring and evaluation of Community policies with a territorial dimension or impact. INSPIRE intends to trigger the creation of a European spatial data infrastructure that delivers to the users integrated spatial information services linked by common standards and protocols.''

''The INSPIRE Geo-Portal is Europe's Internet access point for Spatial Data and Services. From there, you can search for spatial data, services, and organisations. ''

== OSGeo's involvement ==
There is no coordinated effort at involving OSGeo as an organization in the INSPIRE initiative but many OSGeo projects are already tied into processes and the emerging INSPIRE architecture. A formal meeting of OSGeo representatives with people (from JRC) involved in INSPIRE is planned for the end of 2007.

== FIT/GAP analysis ==
How good does Open Source GIS software fit into the INSPIRE picture? Can it be used as a software stack to build INSPIRE SDI's? It would be interesting to make a fit/gap analysis between what the INSPIRE standards require and what the OSGEO stack provides. Also, a plan could be made up to fill in the gaps (in time). The reasoning behind this is that the regular customers will not be able to make this analysis by themselves, so it would be good to have something written up. Ofcourse this is an ongoing effort as not many of the standards are final as yet, and most are still in draft.

Who is interested in collaborating in such a fit/gap analysis?
* Bart van den Eijnden
* Dirk Frigne

== See also ==

* [[FOSS SDIC]]

[[Category: Standards]]

INSPIRE

2008-08-25T07:27:26Z

Wiki-Roy: /* FIT/GAP analysis */

[http://eu-geoportal.jrc.it/ INSPIRE] is a European based approach at solving interoperability issues for gespatial data.

== Introduction (from http://eu-geoportal.jrc.it/) ==

''INSPIRE (Infrastructure for Spatial Information in Europe) is an initiative launched by the European Commission and developed in collaboration with Member States and accession countries. It aims at making available relevant, harmonized and quality geographic information to support formulation, implementation, monitoring and evaluation of Community policies with a territorial dimension or impact. INSPIRE intends to trigger the creation of a European spatial data infrastructure that delivers to the users integrated spatial information services linked by common standards and protocols.''

''The INSPIRE Geo-Portal is Europe's Internet access point for Spatial Data and Services. From there, you can search for spatial data, services, and organisations. ''

== OSGeo's involvement ==
There is no coordinated effort at involving OSGeo as an organization in the INSPIRE initiative but many OSGeo projects are already tied into processes and the emerging INSPIRE architecture. A formal meeting of OSGeo representatives with people (from JRC) involved in INSPIRE is planned for the end of 2007.

== FIT/GAP analysis ==
How good does Open Source GIS software fit into the INSPIRE picture? Can it be used as a software stack to build INSPIRE SDI's? It would be interesting to make a fit/gap analysis between what the INSPIRE standards require and what the OSGEO stack provides. Also, a plan could be made up to fill in the gaps (in time). The reasoning behind this is that the regular customers will not be able to make this analysis by themselves, so it would be good to have something written up. Ofcourse this is an ongoing effort as not many of the standards are final as yet, and most are still in draft.

Who is interested in collaborating in such a fit/gap analysis?
* Bart van den Eijnden
* Dirk Frigne
* Roy Braam

== See also ==

* [[FOSS SDIC]]

[[Category: Standards]]

Roy Braam

2008-08-14T07:07:57Z

Wiki-Roy:

Software Engineer specialized in building webbased open source Geographic Information Systems and related software. Works for B3partners, a open source software company.

<tt>[[Category:OSGeo Member]][[Category:Nederland]]

User:Roy

2008-08-14T07:06:46Z

Wiki-Roy: Redirecting to Roy Braam

#REDIRECT [[Roy_Braam]]

Roy Braam

2008-08-14T07:05:50Z

Wiki-Roy:

Roy Braam

2008-08-14T07:04:40Z

Wiki-Roy: Redirecting to User:Roy

#REDIRECT [[User:Roy]]

Roy Braam

2008-08-14T07:00:51Z

Wiki-Roy:

"http://wiki.osgeo.org/wiki/Roy"

<tt>[[Category:OSGeo Member]]

User:Roy

2008-08-14T06:59:01Z

Wiki-Roy:

Software Engineer specialized in building webbased open source Geographic Information Systems and related software. Works for B3partners, a open source software company.

Roy Braam

2008-08-14T06:57:43Z

Wiki-Roy: New page: Software Engineer specialized in building webbased open source Geographic Information Systems and related software. Works for B3partners, a open source software company.

Software Engineer specialized in building webbased open source Geographic Information Systems and related software. Works for B3partners, a open source software company.

User:Roy

2008-08-14T06:46:06Z

Wiki-Roy:

Working for B3partners as a Software Engineer.
Specialized in Open Source Geographic Information Systems and related things.

Nederlands

2008-06-20T07:09:07Z

Wiki-Roy: /* Interested Individuals */

{{Languages}}
= Mailing list =

Discussions in the Dutch language can be held at:
[[http://lists.osgeo.org/mailman/listinfo/dutch]]
This is also the page to sign up for this mailinglist.

= Interested Individuals =
* [[User:Taatuut | Emil Zegers]]
* [[User:bartvde | Bart van den Eijnden]]
* [[User:ticheler | Jeroen Ticheler]]
* [[User:WimDeHaas | Wim de Haas]]
* [[User:dirkf | Dirk Frigne]]
* [[User:milovanderlinden | Milo van der Linden]]
* [[User:roybraam| Roy Braam]]

= Links =
[[Category:Nederland]] [[Category:European Network]]

OSGeo Cartographic Engine

2008-04-09T09:35:13Z

Wiki-Roy: /* 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)

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

== 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
** ...
* 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)

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

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

== 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
[[Category: Software Stack]]

User:Roy

2008-04-09T09:34:01Z

Wiki-Roy: New page: Working for B3partners as a Software Engineer. Specialized in Geographic Information Systems

Working for B3partners as a Software Engineer.
Specialized in Geographic Information Systems