https://wiki.osgeo.org/w/api.php?action=feedcontributions&user=Wiki-MaksimS&feedformat=atomOSGeo - User contributions [en]2024-03-19T12:29:00ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=OSGeo_map_symbol_set&diff=27852OSGeo map symbol set2008-08-02T12:49:35Z<p>Wiki-MaksimS: /* Interested people */</p>
<hr />
<div>== Motivation ==<br />
<br />
The [[OSGeo Cartographic Library]] and all software projects obviously need a '''free''' map symbol set.<br />
<br />
== Available Material ==<br />
<br />
* Free map symbol sets from GFOSS.it: [http://www.gfoss.it/drupal/simboli Simboli cartografici]: trees, geology, meteorology and north arrows<br />
<br />
* Free [http://grass.osgeo.org/wiki/IconSymbols map icons] from GRASS: various symbols<br />
<br />
* [http://www.gpsdrive.de GpsDrive] and [http://www.openstreetmap.org OpenStreetMap] maintain a repository of c. '''''hundreds''''' of Point Of Interest (POI) rasterized and SVG symbol icons under a permissive OSS license. Things like "banks" and "hospitals" are very well covered.<br />
: see http://www.gpsdrive.de/development/map-icons/overview.en.shtml<br />
:: http://wiki.openstreetmap.org/index.php/Tags_to_Symbols_Mapping<br />
:: http://wiki.openstreetmap.org/index.php/Osmarender/Symbols<br />
<br />
* symbols for wildland fire are available from US Gov't: http://gis.nwcg.gov/gstop_symbol.html (public domain?)<br />
<br />
* ...<br />
<br />
== Other Technology==<br />
<br />
(please keep focus on free as in freedom technologies)<br />
<br />
Microsoft has a [http://www.aaronlerch.com/blog/2007/09/01/symbol-server-transaction-manager/ symbol server]<br />
<br />
<br />
<br />
== Symbol Availability ==<br />
{| class="wikitable"<br />
|-<br />
! Symbol<br />
! GFOSS.it<br />
! GRASS<br />
! OSGEO<br />
|-<br />
| '''Community''' <br />
| <br />
| <br />
|-<br />
| School <br />
| <br />
| <br />
| NA<br />
|-<br />
| Recreation Centre <br />
| <br />
| <br />
| NA<br />
|-<br />
| '''Emergency Services''' <br />
| <br />
| <br />
|-<br />
| Hospital <br />
| <br />
| <br />
| NA <br />
|-<br />
| Police station <br />
| <br />
| <br />
| NA<br />
|-<br />
| Fire station <br />
| <br />
| <br />
| NA <br />
|-<br />
| Ambulance <br />
| <br />
| <br />
| NA<br />
|-<br />
| '''Basic''' <br />
| <br />
| <br />
| NA<br />
|-<br />
| Arrow <br />
| <br />
| yes<br />
| NA<br />
|-<br />
| Box <br />
| <br />
| yes<br />
| NA<br />
|-<br />
| Circle<br />
| <br />
| yes<br />
| NA<br />
|-<br />
| '''Extras''' <br />
| <br />
| <br />
| NA<br />
|-<br />
| Compass <br />
| <br />
| Yes<br />
| NA<br />
|-<br />
| Airport <br />
| <br />
| Yes<br />
| NA<br />
|-<br />
| Target <br />
| <br />
| yes<br />
| NA<br />
|-<br />
| Dive Flag <br />
| <br />
| yes<br />
| NA<br />
|-<br />
| '''Transportation''' <br />
| <br />
| <br />
| <br />
|-<br />
| Information Centre <br />
| <br />
| <br />
| NA<br />
|-<br />
| Bus Stop <br />
| <br />
| <br />
| NA<br />
|-<br />
| Picnic Area <br />
| <br />
| <br />
| NA<br />
|}<br />
<br />
== Interested people ==<br />
<br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Dsampson|Dave Sampson]]<br />
* [[User:Landa|Martin Landa]]: GRASS developer<br />
* [[User:Wolf|Wolf Bergenheim]]<br />
* [[User:MaksimS|Maksim Sestic]]<br />
<br />
[[Category: Software Stack]]<br />
[[Category: Public Geospatial Data Committee]]</div>Wiki-MaksimShttps://wiki.osgeo.org/w/index.php?title=OSGeo_Cartographic_Engine&diff=27851OSGeo Cartographic Engine2008-08-02T12:47:33Z<p>Wiki-MaksimS: /* Interested people */</p>
<hr />
<div>== Motivation ==<br />
<br />
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.<br />
<br />
== Functionality ==<br />
<br />
Shared functions may include<br />
<br />
* class breaks (various algorithms)<br />
* histogram analysis<br />
* color ramps<br />
* RGB and possibly CYMK support (aka color transformations) etc.<br />
* 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.<br />
* Symbology management<br />
* map surround <br />
* legend<br />
* cartographic templates (ie. predefined map styles)<br />
* parse and print map (geovisualization) description files<br />
<br />
This paper might be worth looking at: [http://utpjournals.metapress.com/content/b584484743vk910g/ Extended Cartographic Interfaces for Open Distributed Processing]<br />
<br />
== Programming Language ==<br />
<br />
* C? C++?<br />
<br />
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".<br />
<br />
* Python bindings?<br />
<br />
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].<br />
<br />
== Output Formats ==<br />
<br />
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. <br />
<br />
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...).<br />
<br />
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?<br />
<br />
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.<br />
<br />
== Existing code to be recycled ==<br />
<br />
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.<br />
<br />
* Label placement code:<br />
** Mapserver [http://trac.osgeo.org/mapserver/browser/trunk/mapserver/maplabel.c labeling code] (MapServer License, C language)<br />
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.label.sa v.label.sa] (GPL, C language)<br />
* Color management:<br />
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/PlatformBase/Data/Color.cpp Color] (LGPL.C++)<br />
** OpenJump ?<br />
<br />
* Stylization<br />
** ...<br />
<br />
* Symbology<br />
** [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]<br />
:: [http://openev.cvs.sourceforge.net/openev/contrib/S52/ GPL library implementing the S-52 standard] (OpenEV)<br />
<br />
* Class breaks:<br />
** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/arraystats different algorithms for class breaks] (GPL, C)<br />
** MapGuide [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Server/src/Services/Feature/FeatureNumericFunctions.cpp CalculateDistribution] (LGPL.C++)<br />
<br />
* Output:<br />
** Postscript/PDF output:<br />
*** 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)<br />
*** [http://sourceforge.net/projects/geofunctions GeoFunctions]: Geographic XML to PDF. Not sure what specific code, but the project leaders might have some insight.<br />
** PNG output:<br />
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/pngdriver PNG driver] (GPL, C)<br />
*** See AGG below<br />
** CAIRO output<br />
*** GRASS [http://trac.osgeo.org/grass/browser/grass/trunk/lib/cairodriver CAIRO driver] (GPL, C)<br />
*** [http://cairographics.org/ Cairo Graphics Library] (LGPL or MPL)<br />
** [Mapnik http://mapnik.org/] is a Free Toolkit for developing mapping applications.<br />
<br />
== End User Needs ==<br />
* Print to small format medium (eg 8.5in x 11in, 11in x 14in) and large format (eg 34 x 44in)<br />
* Interactive layout<br />
* High quality printing<br />
* Storage of cartographic symbolizing<br />
* [[OSGeo map symbol set|Symbols library]]<br />
* Separate cartographic and geographic representation (eg changes to carto does not affect geo).<br />
* Generalization on-the-fly, based on current scale.<br />
* Rules based cartography stored in RDBMS (eg series 400 highways are blue with double lines)<br />
* Multiple export formats<br />
** Geotiff<br />
** PNG<br />
** PDF / GeoPDF<br />
** Postscript (need for directly sending files to printers)<br />
** SVG<br />
* Layout Functionality<br />
* Text-based configuration file that applications can output to or humans can manually hack/script<br />
* Common, interoperable data file input options<br />
* Customizable legend with Symbology representation (textures, object symbols, etc.)<br />
<br />
==Layout Functionality==<br />
===Design Modeling===<br />
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). <br />
<br />
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.<br />
<br />
=== XML and PDF===<br />
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.<br />
<br />
==Potential Components==<br />
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.<br />
<br />
=== Style & Layout Configuration Standards ===<br />
* Specifications for styling of features and layout of a map composition<br />
* Could re-use existing approaches where applicable (e.g. SLD, WMC, MapServer Mapfile, OGR Feature Styles)<br />
* Specifications to be used in map definition/configuration files<br />
<br />
=== Graphical Style & Layout Editor ===<br />
* To create styles interactively<br />
* To define map layout<br />
* Could be stand-alone<br />
* Could be adopted as part of another application<br />
* Saves a style/layout definition document according to above standards<br />
<br />
=== Graphical Map Composition Editor ===<br />
* Implemented by existing applications (e.g. GRASS, QGIS, etc.)<br />
* Sets up pointers to data layers<br />
* Assigns styles definitions to the layers<br />
* Applies layout definition to maps<br />
* Outputs a map composition configuration file<br />
<br />
=== Rendering Engine ===<br />
* Stand-alone application (no GUI)<br />
* Reads standard map composition configuration file<br />
* Reads and applies the required style/layout definition documents<br />
* Outputs final graphics to specific files<br />
<br />
=== Libraries ===<br />
* Sets of libraries could be created to implement parts of the above sections<br />
* Add more here...<br />
<br />
== Technologies ==<br />
<br />
* AGG (sophisticated rendering of vector/text graphics to raster format - used by MapServer, MapGuide, Mapnik). <br />
* Freetype - text management and rendering library<br />
* [http://cairographics.org/ Cairo] graphics library - vector, text and raster input, various output including Postscript<br />
* [http://schemas.opengis.net/se/1.1.0/ OpenGIS Symbology Encoding Schema] A language for describing coverage and feature styles<br />
<br />
== Workflow ==<br />
<br />
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.<br />
<br />
* read geo data<br />
** geometries<br />
** projection<br />
** metadata (if required)<br />
* apply styling<br />
** feature to style coding<br />
* Cartographic edits<br />
** overide some of the geometry if required (eg roads don't run through lakes)<br />
* manual edits / retouching<br />
* Produce other cartographic edits objects<br />
** create suround<br />
** create grids<br />
** create legend<br />
** create scale bar<br />
** create north arrow<br />
** Copyright notices from text file or DB<br />
** Licensing notices from text fiel or DB<br />
* Other<br />
** Output size<br />
<br />
=== Other Workflow Models ===<br />
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/561 Generic GRASS-GMT Workflow]<br />
* [http://169.237.35.250/~dylan/grass_user_group/#GMT_and_GRASS-overview Quality Digital Cartography with GMT and GRASS]<br />
<br />
== License ==<br />
<br />
It is proposed to license the OSGeo Cartographic Library under LGPL. The license needs to be GPL compliant.<br />
<br />
== Interested people ==<br />
<br />
* [[User:Neteler|Markus Neteler]] (proposer)<br />
* Horst Düster<br />
* [[User:Landa|Martin Landa]]: GRASS developer<br />
* [[User:MarcoHugentobler|Marco Hugentobler]]<br />
* Frank Warmerdam<br />
* [[User:Adiez|Agustin Diez]]<br />
* [[User:mlennert|Moritz Lennert]]<br />
* [[User:Dsampson | Dave Sampson]]: End User, Search and Rescue Maps,<br />
* [http://casoilresource.lawr.ucdavis.edu/drupal/node/38 Dylan Beaudette]: Soil Science Researcher, OSGeo evangelist<br />
* [[User:Tmitchell|Tyler Mitchell]]<br />
* [[User:reholl|Robert Hollingsworth]]<br />
* [[User:Wolf|Wolf Bergenheim]]: v.label.sa developer<br />
* [[User:HamishBowman|Hamish Bowman]]: ps.map developer<br />
* [[User:GAruta|Giuseppe Aruta]]: Geologist<br />
* [[User:Roy|Roy Braam]]: Software Engineer<br />
* Ionut Iosifescu<br />
* [[User:ajolma|Ari Jolma]]: Wants to go ahead with Cairo<br />
* [[User:vasile|Vasile Crăciunescu]]<br />
* [[User:Peterrushforth|Peter Rushforth]]<br />
* [[User:Turban|Bjorn Sandvik]]: thematicmapping.org<br />
* [[User:JoCook| Jo Cook]]<br />
* [[User:Mloskot|Mateusz Loskot]] (potential tester, contributor and user)<br />
* [[User:kotzino|Dimitris Kotzinos]]<br />
* [[User:drrho|Robert Barta]]: semantic aspects of visualisation<br />
* Giovanni Allegri: Environmental Geologist, (Web)GIS and RS Researcher<br />
* [[User:MaksimS|Maksim Sestic]]<br />
<br />
== See also ==<br />
<br />
* [[OSGeo map symbol set]]<br />
<br />
[[Category: Software Stack]]</div>Wiki-MaksimShttps://wiki.osgeo.org/w/index.php?title=Public_Geospatial_Data_Project&diff=13737Public Geospatial Data Project2007-04-11T14:03:15Z<p>Wiki-MaksimS: /* People interested in participating */</p>
<hr />
<div>There is an official [[Public Geospatial Data Committee|official foundation committee]] page which provides more detail on meetings and discussions.<br />
<br />
== Mission ==<br />
<br />
=== Promote the use of open geospatial formats ===<br />
Providing best-practise guidelines and examples for use of open and free standards for data (GML, WMS, WFS-T) and metadata (Dublin Core, RDF, ISO19115 through ISO19139).<br />
<br />
=== Promote public access to state-collected geodata ===<br />
<br />
Lead by example in demonstrating economic value and research activity generated by open access to public geographic information.<br />
<br />
=== Run a repository of open geodata ===<br />
A [[Geodata_Repository]] shall be hosted by the PGDP.<br />
Additionally, links to other open data repostories shall be collected.<br />
<br />
=== Present and explain licenses for public geodata ===<br />
The PGDP aims to collect licenses suitable for the publishing of public geodata. The license shall be presented along with a summary of its benefits and focus.<br />
<br />
== Approach ==<br />
<br />
After a [[Public Geospatial Data Committee Definition Phase|Definition phase]] this has become an official [[Committees|committee]] within [[Main Page|OSGeo]]. <br />
<br />
=== Working Groups ===<br />
<br />
At the [[Geodata Committee Meeting 20060322|first meeting of the geodata committee]] we decided to focus interest through three [[Working Groups]]:<br />
<br />
* A [[Geodata Discovery Working Group]] which would focus on indexing and search of data and metadata repositories.<br />
* A [[Geodata Packaging Working Group]] to look at creation and maintanance of really high quality and rich data packages to offer for educational purposes with software packages, with [[GRASS GIS]] in particular.<br />
* A [[Geodata Licensing Working Group]] to look into parallel licensing developments and to consult on guidelines for open licenses for geodata.<br />
<br />
=== Mailing List ===<br />
<br />
There is a public mailing list and [http://lists.osgeo.org/pipermail/geodata/ archive] for discussion of geodata activities within OSGeo at http://lists.osgeo.org/mailman/listinfo/geodata.<br />
<br />
=== Meetings ===<br />
<br />
This group is having regular meetings on IRC on the #osgeo channel on irc.freenode.net. At the moment this is happening on Thursdays at 16:00 UTC. [http://www.timeanddate.com/worldclock/fixedtime.html?year=2006&month=4&hour=16&min=0&sec=0 fixed time]<br />
<br />
See the [[Public Geospatial Data Committee|Geodata Committee]] page for more details on past meetings and upcoming agendas.<br />
<br />
=== People interested in participating ===<br />
<br />
* David Bitner <br />
* Allan Doyle <br />
* Florian Kindl <br />
* Pericles S. Nacionales <br />
* Markus Neteler <br />
* [[User:JoWalsh|Jo Walsh]]<br />
* [[User:Uchoa|Helton Uchoa]]<br />
* Aaron Racicot - Ecotrust - aaronr at ecotrust.org<br />
* Daniel Brookshier <br />
* Schuyler Erle <br />
* Jeff McKenna (DM Solutions)<br />
* Steve Coast <br />
* Mikel Maron <br />
* Alessandro Frigeri<br />
* David Blasby<br />
* [[User:kevinyam| Kevin Yam]]<br />
* [[User:putler|Dan Putler]]<br />
* [[User:Arnulf Christl|Arnulf Christl]]<br />
* Ned Horning<br />
* [[User:Nhv|Norman Vine]]<br />
* Colin Gowens<br />
* [[User:smaffulli|Stefano Maffulli]]<br />
* [[User:fbiasi|Frank Biasi]]<br />
* [[User:Ticheler|Jeroen Ticheler]]<br />
* Stefan Keller<br />
* [[User:Dsampson|Dave Sampson]]<br />
* [[User:kablukiw|Kevin Ward]]<br />
* [[User:JoCook|Jo Cook]]<br />
* Nick Black<br />
* [[User:Mloskot|Mateusz Loskot]]<br />
* Martin Spott<br />
* David Jonglez<br />
* [[User:dandye|Daniel Dye]]<br />
* [[User:MaksimS|Maksim Sestic]]<br />
* ''Please add yourself''<br />
<br />
=== Organizations to beneficially connect with ===<br />
<br />
* [http://www.eogeo.org EOGEO] <br />
* [http://www.openstreetmap.org/ OpenStreetMap Project] <br />
* [http://www.gsdi.org GSDI Association] <br />
* [http://topp.openplans.org The Open Planning Project]<br />
* [http://www.fgdc.gov Federal Geographic Data Committee]<br />
* [http://www.opengeospatial.org Open Geospatial Consortium]<br />
* [http://www.upct.org/ Un point c'est tout]<br />
<br />
=== Events ===<br />
<br />
Events where we can either promote our positions or are likely to run into like-minded individuals.<br />
<br />
* [http://www.asia-commons.net/ Asian Conference on the Digital Commons - April 18-20, 2006, Bangkok, Thailand]<br />
* [http://conferences.oreillynet.com/where2006/ Where 2.0 - June 13-14, 2006, San Jose, California, USA]<br />
* [http://www.foss4g2006.org/ FOSS4G2006 - Free And Open Source Software for Geoinformatics - September 12-15, 2006, Lausanne, Switzerland]<br />
<br />
== References ==<br />
<br />
=== Geo Data Repositories / Group Collection Projects ===<br />
* [http://www.openstreetmap.org/ OpenStreetMap Project]<br />
* [http://freeearthfoundation.com/ Free Earth Foundation]<br />
* [http://geobase.ca/ Canadian Base Data]<br />
* [http://geotorrent.org/ Various Free Datasets via Bittorrent]<br />
* [http://geodatacommons.umaine.edu/ GeodataCommons project at U. Maine]<br />
* [http://www.iscgm.org/cgi-bin/fswiki/wiki.cgi Global Map] - International Steering Committee for Global Mapping<br />
* [http://www.geonames.org Geonames.org] - Geonames is integrating geographical data such as names, altitude, population and others from various sources<br />
* [http://www.geo-one-stop.gov/ Geospatial One Stop]<br />
* [http://gcmd.nasa.gov/index.html Global Change Master Directory]<br />
* [http://conserveonline.org/workspaces/cons.geo.portal Conservation GeoPortal]<br />
* [http://datagateway.nrcs.usda.gov/ USDA:NRCS Geospatial Data Gateway] - Lots of good imagery<br />
* [http://www.fao.org/geonetwork FAO-UN GeoNetwork portal to spatial data and information]<br />
<br />
=== Geo Data Repository & Policy Research ===<br />
<br />
* [http://geodatacommons.umaine.edu/CGDPlone University of Maine Commons for Geographic Data]<br />
* [http://www.metrogis.org MetroGIS] [http://datafinder.org Datafinder] Twin Cities, MN Metro Area Public Agency Data Sharing Effort (includes section on benefits/testimonials from public geodata)<br />
* [http://www.gis.state.mn.us MN Governor's Council on Geographic Information]<br />
* [http://www.oasisnyc.org New York City Open Accessible Space Information System]<br />
* [http://www.mass.gov/mgis Massachusetts GIS]<br />
<br />
On the [[Geodata Repository]] page, a draft outline for OSGeo's own repository project is being prepared.<br />
<br />
=== Geo Data Policy Advocacy ===<br />
* [http://www.publicgeodata.org/ Public Geodata Project] (IRC: [irc://freenode/publicgeodata publicgeodata]) with the support of the Open Knowledge Foundation<br />
* [http://okfn.org/geo/manifesto.php Open Access to State-Collected Geospatial Data Manifesto]<br />
* [http://www.freeourdata.org.uk/ Free Our Data: Make taxpayers' data available to them] (United Kingdom)<br />
<br />
=== Open Access ===<br />
There are also more general open access movements, often aimed at scientific data, that could provide a venue for broadening awareness of the geo-specific issues.<br />
<br />
* [http://oa.mpg.de/openaccess-golm/index.html Berlin 4 Open Access - From Promise to Practice - March 29-31, 2006 Golm, Germany]<br />
* [http://oa.mpg.de/openaccess-berlin/berlindeclaration.html Berlin Declaration on Open Access to Knowledge in the Sciences and Humanities]<br />
* [http://www.conservationcommons.org/ Conservation Commons] - "The Conservation Commons is characterized by an underlying set of Principles which supports open access to, and in particular the fair use of, data and information related to the conservation of biodiversity." <br />
* [http://www.locusforums.org/forum/ The Locus Forum] - "The Locus Association is a trade association of private organisations working to increase opportunities and reduce barriers to fair trade between the public and private sector, particularly in the use of Public Sector Information."<br />
* [http://ppgis.iapad.org/ Public Participation GIS] - "<br />
<br />
== Further Reading ==<br />
* [http://technology.guardian.co.uk/weekly/story/0,,1736751,00.html Ordnance Survey challenged to open up] - 2006-03-23 article in the Guardian<br />
* [http://technology.guardian.co.uk/weekly/story/0,,1726229,00.html Give us back our crown jewels] - 2006-03-09 article in the Guardian<br />
* [http://www.directionsmag.com/article.php?article_id=2107&trv=1 Why Europe Needs to Provide its Own Public Geodata ] by Jo Walsh (Feb 15, 2006)<br />
* [http://www.systemed.net/blog/entry060311122655.html ShareAlike considered harmful for geodata] by Richard Fairhurst, a critique of GPL-like licensing situations with suggested LGPL-like model for distribution.<br />
* "Open Source Software for Spatial Data Infrastructure (FOSSDI)". SDIC submitted 2005 to INSPIRE/EU. <br> [http://mpa.itc.it/markus/papers/sdic_call_fossdi.pdf PDF with layout] | [http://inspire.jrc.it/ir/sdic_view_step1_only.cfm?id=2163 HTML without layout]<br />
* [http://mitworld.mit.edu/video/270/ Open Networks and Open Society: The Relationship between Freedom, Law, and Technology] - MIT World video featuring Hal Abelson, John Wilbanks, Creative Commons<br />
* [http://www.metrogis.org/documents/articles/index.shtml Articles] [http://www.metrogis.org/benefits/testimonials/index.shtml Testimonials] [http://www.metrogis.org/benefits/studies/index.shtml Studies] [http://www.metrogis.org/benefits/perf_measure/index.shtml Performance Measures] about [http://www.metrogis.org Metrogis], a collaboration for GIS data sharing in the Twin Cities, MN, USA</div>Wiki-MaksimS