OSGeo - User contributions [en]

Geoservices REST API

2013-05-09T08:15:23Z

Wiki-Psanxiao:

This wiki page aims to collate community concerns related to the proposed acceptance of the "Geoservices REST API" becoming an OGC standard. It is being collaboratively edited, targeting completion before the end of May 2013.

= Open Letter to OGC and voting members =

''Please don't edit this "Open Letter" statement, comments and discussion should go below.''

May 2013

We, the undersigned, have concerns that approving the "Geoservices REST API" as an OGC standard, would have detrimental impacts on interoperability within the spatial industry.

We strongly urge that the proposed "Geoservices REST API", as it stands in May 2013, be rejected as an OGC standard.

People have listed different reasons for concern. They are described below.

== Signed ==
''Please add your name here if you agree with the above statement. Include name, work title (if appropriate), very brief title/involvement in OSGeo if appropriate. (Link to OSGeo profile if appropriate). You may sign as a group, such as the Project Steering Committee of XXX project if you wish, or as Your Name on behalf of YYY company.''

* [[User:camerons|Cameron Shorter]], Geospatial Solutions Director at [http://lisasoft.com LISAsoft], core contributor & coordinator of [http://live.osgeo.org OSGeo-Live]
* [[User:Woodbri|Stephen Woodbridge]], Director of [http://imaptools.com iMaptools.com], Contributor and/or PSC of [http://mapserver.org Mapserver], [http://pgrouting.org/ pgRouting], [http://www.pagcgeo.org/ PAGC], and [http://www.postgis.org/ PostGIS]
* [[User:rouault|Even Rouault]], Geospatial developer, OSGeo Charter Member, core contributor and PSC member of [http://gdal.org GDAL/OGR], contributor of [http://mapserver.org Mapserver], [http://trac.osgeo.org/proj/ PROJ.4], [http://trac.osgeo.org/geotiff/ libgeotiff], [http://shapelib.maptools.org/ shapelib], [http://www.remotesensing.org/libtiff/ libtiff]
* Gerhard Triebnig, Managing Director at [http://eox.at EOX IT Services GmbH]
* [[User:pcreso|Brent Wood]], Environmental Information Delivery Programme Leader, NIWA, New Zealand. OGC member, Aust/NZ OSGEO chapter member, NZOSS Council member
* [[User:Schpidi|Stephan Meissl]], CTO at [http://eox.at EOX IT Services GmbH], contributor to [http://mapserver.org Mapserver], PSC chair of [http://eoxserver.org EOxServer]
* [[User:ticheler|Jeroen Ticheler]], Director of [http://geocat.net GeoCat], project founder and PSC chair of [http://geonetwork-opensource.org GeoNetwork opensource]
* [[User:Just|Just van den Broecke]], Director at [http://www.justobjects.nl Just Objects], contributor to [http://heron-mc.org Heron Mapping Client], secretary of [http://osgeo.nl OSGeo Dutch Local Chapter], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:milovanderlinden|Milo van der Linden]], member at [http://www.opengeogroep.nl OpenGeoGroep]
* [[User:surveyor|Landon Blake]], GIS Department Manager/Land Surveyor at [http://www.ksninc.com KSN], OSGeo California Chapter Board Representative.
* [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com/ Mapgears], core contributor and PSC member of [http://mapserver.org Mapserver] and [http://gdal.org GDAL/OGR]. Former OGC TC member and involved in the implementation of several OGC WxS services specs in MapServer.
* [[User:blammo|Bob Basques]], GIS Systems Developer at the City of Saint Paul, MN. [http://gis.ci.stpaul.mn.us Public Works GIS (GISmo)], Technical Director at [http://www.sharedgeo.org SharedGeo], OSGeo Charter Member, OSGeo TCMUG local chapter member, Co-founder and PSC member of [http://www.geomoose.org GeoMoose] project.
* [[User:vehrka|Pedro-Juan Ferrer Matoses]], PM at Omnium Strategic Intelligence, Spain, OSGeo Charter Member, OSGeo Spanish Local Chapter Liaison officer.
* Bevan Rudge, Director Lucion Limited, IT Advisor at Conservation Strategy Fund, Esri client
* [[User:Delawen|María Arias de Reyna]], software engineer at [http://geocat.net GeoCat], Spain, member of OSGeo Spanish Local Chapter.
* [[User:Aghisla|Anne Ghisla]], OSGeo Board Member, Italy, member of OSGeo Italian Local Chapter.
* [[User:Michogar|Micho Garcia]], Freelance and member of [http://geomati.co geomati.co], Spain, member of Spanish Local Chapter
* [[User:Madi|Margherita Di Leo]], OSGeo Charter Member, Italy
* [[Jorge Sanz]], GIS Consultant at [http://www.prodevelop.es Prodevelop], OSGeo Charter Member, OSGeo Spanish Local Chapter Member, Spain
* [[Pablo Sanxiao]], CTO and co-founder at [http://www.icarto.es iCarto], OSGeo Spanish Local Chapter Member, Spain

= Concerns =
--- DRAFT ____

''Please add concerns as bullet points below. Try to be concise. Where appropriate, link to external web pages (such as email achieves)''

== Summary ==
As at May 2013, OGC members have been asked to decide whether to accept the "GeoServices REST API" as an OGC standard. This is a contentious issue, with many people arguing that introduction of the “GeoServices REST API” will have costly, far reaching, negative impacts on interoperability, and significantly tarnish the OGC's reputation as a champion of interoperability.

The key points of contention revolve around the fact that the proposed "GeoServices REST API" does not build upon or extend existing OGC standards, but rather addresses similar requirements using an alternative API. In particular, the overlap and/or duplication of existing standards is widespread: OGC's core standards of WMS, WMTS, WFS, SE/SLD, WCS, CS/W are all duplicated to a significant extent. This defeats the purpose of having standards in the first place.

Duplication of standards will likely result in a combination of the following:
# The cost to application developers, systems integrators, testers and sponsors to support all relevant OGC standards will be substantially increased.
# Consequently, organisations and/or applications may choose to only support one standard, or only support one standard fully.
# Sponsors (such as governments) who require compliance with OGC standards will discover that applications don't communicate together, due to applications supporting different OGC standards that essentially do the same thing.
# This will result in a diminished importance of OGC, as the "OGC standards" stamp of approval will not equate interoperability.
# After a while, in order to solve interoperability issues, a respected international organisation or program will likely take the initiative to mandate one standard as the preferred standard for all agencies to follow. To date, the OGC has provided this leadership.
# One standard taking prominance over the other will likely lead to the other being neglected or deprecated, resulting in many OGC compliant systems becoming legacy systems in the process. This should be considered an undesirable outcome for a standards organisation. Backward compatibility to the existing WxS standards is important in this respect.
# Given backwards compatibility with the ESRI Restful implementation is mandated, this is not an Open Standard, and should not be ratified as if it was.

== Political Concerns ==

* Adopting the standard will expose the OGC to a strong suspicion of acting as a rubber stamp organization under ESRI weight, and will be detrimental to its recognized position as a reference organization for geospatial standards.
* It is a dubious practice that a standardization organisation promotes competing standards, without explicitely obsoleting (or at least recommending) some of them. How is a new comer to the industry supposed to select the appropriate standard if several ones share the same scope : WFS or GeoServices REST API Feature Service, WMS or GeoServices REST API Map Service, etc. ?

== Commercial Concerns ==

* Promoting standards from an existing implementation made by a single vendor leads to an obvious bias in competition.
* Supporting multiple overlapping standards greatly reduces usability while it increases complexity and cost of development and maintenance.
* Many SME's have invested in supporting existing OGC standards in their products. They will be forced to choose the standards they support (and can explain), resulting in decreased interoperability, confusion and frustration for clients.
* Confusing customers with new, overlapping OGC standards will lower the credibility of companies and of OGC, reducing business opportunities.

== Technical Concerns ==

* The Geoservices REST API overlaps in large proportion with existing OGC standards such as WMS, WCS, WFS, WMTS, CSW, with no effort made to reconcile with those standards.
* The standardization of WKT for Spatial reference systems is unfortunately currently quite weak in OGC standards. Geoservices REST API is tied with ESRI's version of WKT, which is not properly specified in the Geoservices REST API documents, and is known to be incompatible with other OGC documents, which will lead to a larger confusion. See the following [[http://lists.opengeospatial.org/pipermail/requests/2012-July/000166.html comment]] for more details on this issue.
* The Geoservices REST API is not particularly RESTful - it's a thinly disguised service call, not an address space for RESTful objects that can be operated on.

== Methodological Concerns ==

* No public response (nor private to the authors of the comments) has been made to the various comments sent on the OGC Requests mailing list in [[http://lists.opengeospatial.org/pipermail/requests/2012-July/date.html July 2012]] and [[http://lists.opengeospatial.org/pipermail/requests/2012-August/date.html August 2012]] during the 30 day public comments period.
* The Geoservices REST API can not be amended (other than editorial changes in the specification document), because of a requirement of backward compatibility with ESRI implementation. Consequently, the standard is unlikely to improve, or its evolution will be only lead by ESRI.
* OGC standards normally require interoperability experiments and a richer process to ratify a standard such as this one. No explanation has been forthcoming as to why a simplified process is appropriate in this case.

= History =

Todo: please expand
* Explain how this standard came to be
* Based on Arc GIS Server API
* Attempted but failed to go through OGC fast track process
* Recent voting history: refer to: http://lists.osgeo.org/pipermail/discuss/2013-May/011602.html

= References =
Todo: Link to key external docs, such as the proposed standards

[[Category: OGC]]
[[Category: Standards]]

GvSIG Report 2012

2013-04-18T11:22:51Z

Wiki-Psanxiao: Created page with "'''Key Accomplishments (Include Information on Software Releases Here)''' * Release of gvSIG Desktop 1.12 (25/09/2012). * Release of gvSIG Desktop 2.0 RC 3 (27/12/2012) * Rel..."

'''Key Accomplishments (Include Information on Software Releases Here)'''

* Release of gvSIG Desktop 1.12 (25/09/2012).
* Release of gvSIG Desktop 2.0 RC 3 (27/12/2012)
* Release of gvSIG Batoví 1.0 RC2 for secundary school (16/05/2012) & RC3 for primary school (28/08/2012).
* Google Summer of Code 2012 participation.

'''Events'''

* 8th International gvSIG Conference (Spain) 11/2012 (http://www.gvsig.org/web/community/events/jornadas-gvsig/8as/)
* 3as Jornadas Brasileiras de gvSIG (Brazil) 10/2012 (http://www.gvsig.org/web/community/events/jornadas-brasileiras/2012/)
* 4as Jornadas de Latinoamérica y Caribe de gvSIG (Uruguay) 09/2012 (http://www.gvsig.org/web/community/events/jornadas-lac/2012/inicio/view?set_language=es)
* 2as Jornadas Argentinas de gvSIG (Argentina) 09/2012 (http://www.gvsig.org/web/community/events/jornadas-argentina/2012/)
* 1as Jornadas Chilenas de gvSIG (Chile) 06/2012 (http://www.gvsig.org/web/community/events/jornadas-chile/2012/)
* 1-я встреча пользователей gvSIG в России (Russia) 05/2012 (http://www.gvsig.org/web/community/events/russian-conference/2012/)

'''Presentations at other conferences'''

* 1er Congreso Latinoamericano de Catastro (Bolivia).
* Jornadas Técnicas “El Valor estratégico de la información territorial” (Spain)
* Taza GIS (Morocco)
* FOSS-CE (Czech Republic)

'''Articles'''

Many papers that include gvSIG were published in scientific journals and conference proceedings in 2012: https://gvsig.org/web/docusr/divulgacion/articulos/2012-1/

'''Opportunities to Help'''

There many ways to participate in the gvSIG project, with different levels of involvement, like:

* Participating on the mailing lists, for users as well as developers, in may languages.

* Testing the application.

* Doing translations of the gvSIG user interface, user and developer documentation and the gvSIG portal.

* Writing articles and use cases.

* Developing new addons.

You can find more information in the following page: http://www.gvsig.org/web/community/participate

'''Outlook for Next Year'''

* Release of gvSIG Desktop 2.0
* Events (Latin American, International,...)

GvSIG GSoC 2013 Ideas

2013-04-05T11:04:15Z

Wiki-Psanxiao:

Use this page to jot down and develop any good idea for the [[Google Summer of Code 2013]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.

__TOC__

== Integrating OGR library into gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[Daniel Gastón]]
* '''Possible student''': [[User:csanchez|Carlos Sánchez]]

'''1. Introduction'''

By integrating the OGR library into gvSIG Mini we could get not only access to read the several vector formats it supports, but also write outputs and perform transformations between them as many desktop GIS application do.

'''2. Background'''

At this moment, gvSIG gets access to a reduced list of file formats and transformations.

'''3. The idea'''

The main idea behind this project is about integrating the OGR library into gvSIG Mini. The OGR library provides several capabilities for simple features vector data; however it should be mentioned that OGR is also part of the GDAL source tree, so that by integrating OGR we do integrate GDAL as well, getting access to GDAL raster capabilities(for future developments). This proposal improves the application interoperability, and in general terms, the supported range of geoprocesses and transformations.

Once the solution is adapted and compiled, we would proceed to adapt and connect the full OGR data model with the data model gvSIG works with. In this way it is expected to have a proper visualization no matter on which fileformat is intended to be used.

== Add raster format to scripting in gvSIG ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Nacho Brodín
* '''Possible student''': Sandeep Kumar

Expand the capabilities of Jython scripting in gvSIG 2.0 so that it works not only with vector data, but also raster data.

== Extend algorithm providers in SEXTANTE ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''':
* '''Possible student''':

Extend the algorithm providers of SEXTANTE with GDAL, Orfeo Toolbox, etc.

== Idea template ==

* '''Product''': gvSIG Desktop/gvSIG Mobile/gvSIG Mini
* '''Possible mentor''': if applicable
* '''Possible student''': if applicable

Write your idea here... Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi imperdiet condimentum leo sit amet scelerisque. Aliquam placerat, dolor non egestas gravida, tellus felis viverra dui, a scelerisque dolor leo in nulla. Suspendisse pharetra lacus vitae lacus mollis dapibus dignissim metus varius. Nullam scelerisque, elit sit amet ornare commodo, tortor enim consectetur est, eget imperdiet leo augue eget felis. Vivamus nec justo tellus, nec semper ante. Etiam et dolor urna. Nullam non augue in lacus auctor laoreet eget non erat. Integer id justo id magna commodo malesuada. Maecenas tincidunt ipsum nec erat fringilla posuere. Sed ante sapien, posuere non euismod tincidunt, fermentum sollicitudin quam. Aenean metus lacus, viverra ut hendrerit eu, interdum vitae turpis.

[[Category:Google Summer of Code]][[Category:gvSIG]]

GvSIG GSoC 2013 Ideas

2013-04-05T11:04:00Z

Wiki-Psanxiao:

GvSIG GSoC 2013 Ideas

2013-03-27T12:16:55Z

Wiki-Psanxiao:

Use this page to jot down and develop any good idea for the [[Google Summer of Code 2013]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.

__TOC__

== Integrating OGR library into gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[Daniel Gastón]]
* '''Possible student''': [[User:csanchez|Carlos Sánchez]]

'''1. Introduction'''

By integrating the OGR library into gvSIG Mini we could get not only access to read the several vector formats it supports, but also write outputs and perform transformations between them as many desktop GIS application do.

'''2. Background'''

At this moment, gvSIG gets access to a reduced list of file formats and transformations.

'''3. The idea'''

The main idea behind this project is about integrating the OGR library into gvSIG Mini. The OGR library provides several capabilities for simple features vector data; however it should be mentioned that OGR is also part of the GDAL source tree, so that by integrating OGR we do integrate GDAL as well, getting access to GDAL raster capabilities(for future developments). This proposal improves the application interoperability, and in general terms, the supported range of geoprocesses and transformations.

Once the solution is adapted and compiled, we would proceed to adapt and connect the full OGR data model with the data model gvSIG works with. In this way it is expected to have a proper visualization no matter on which fileformat is intended to be used.

== Add raster format to scripting in gvSIG ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Nacho Brodín
* '''Possible student''': Sandeep Kumar

Expand the capabilities of Jython scripting in gvSIG 2.0 so that it works not only with vector data, but also raster data.

== Idea template ==

* '''Product''': gvSIG Desktop/gvSIG Mobile/gvSIG Mini
* '''Possible mentor''': if applicable
* '''Possible student''': if applicable

Write your idea here... Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi imperdiet condimentum leo sit amet scelerisque. Aliquam placerat, dolor non egestas gravida, tellus felis viverra dui, a scelerisque dolor leo in nulla. Suspendisse pharetra lacus vitae lacus mollis dapibus dignissim metus varius. Nullam scelerisque, elit sit amet ornare commodo, tortor enim consectetur est, eget imperdiet leo augue eget felis. Vivamus nec justo tellus, nec semper ante. Etiam et dolor urna. Nullam non augue in lacus auctor laoreet eget non erat. Integer id justo id magna commodo malesuada. Maecenas tincidunt ipsum nec erat fringilla posuere. Sed ante sapien, posuere non euismod tincidunt, fermentum sollicitudin quam. Aenean metus lacus, viverra ut hendrerit eu, interdum vitae turpis.

[[Category:Google Summer of Code]][[Category:gvSIG]]

GvSIG GSoC 2013 Ideas

2013-03-25T21:12:28Z

Wiki-Psanxiao:

Use this page to jot down and develop any good idea for the [[Google Summer of Code 2013]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.

__TOC__

== Integrating OGR library into gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[Daniel Gastón]]
* '''Possible student''': [[User:csanchez|Carlos Sánchez]]

'''1. Introduction'''

By integrating the OGR library into gvSIG Mini we could get not only access to read the several vector formats it supports, but also write outputs and perform transformations between them as many desktop GIS application do.

'''2. Background'''

At this moment, gvSIG gets access to a reduced list of file formats and transformations.

'''3. The idea'''

The main idea behind this project is about integrating the OGR library into gvSIG Mini. The OGR library provides several capabilities for simple features vector data; however it should be mentioned that OGR is also part of the GDAL source tree, so that by integrating OGR we do integrate GDAL as well, getting access to GDAL raster capabilities(for future developments). This proposal improves the application interoperability, and in general terms, the supported range of geoprocesses and transformations.

Once the solution is adapted and compiled, we would proceed to adapt and connect the full OGR data model with the data model gvSIG works with. In this way it is expected to have a proper visualization no matter on which fileformat is intended to be used.

== Add raster format to scripting in gvSIG ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Nacho Brodín
* '''Possible student''':

Expand the capabilities of Jython scripting in gvSIG 2.0 so that it works not only with vector data, but also raster data.

== Idea template ==

* '''Product''': gvSIG Desktop/gvSIG Mobile/gvSIG Mini
* '''Possible mentor''': if applicable
* '''Possible student''': if applicable

Write your idea here... Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi imperdiet condimentum leo sit amet scelerisque. Aliquam placerat, dolor non egestas gravida, tellus felis viverra dui, a scelerisque dolor leo in nulla. Suspendisse pharetra lacus vitae lacus mollis dapibus dignissim metus varius. Nullam scelerisque, elit sit amet ornare commodo, tortor enim consectetur est, eget imperdiet leo augue eget felis. Vivamus nec justo tellus, nec semper ante. Etiam et dolor urna. Nullam non augue in lacus auctor laoreet eget non erat. Integer id justo id magna commodo malesuada. Maecenas tincidunt ipsum nec erat fringilla posuere. Sed ante sapien, posuere non euismod tincidunt, fermentum sollicitudin quam. Aenean metus lacus, viverra ut hendrerit eu, interdum vitae turpis.

[[Category:Google Summer of Code]][[Category:gvSIG]]

GvSIG GSoC 2013 Ideas

2013-03-04T14:55:33Z

Wiki-Psanxiao:

GvSIG GSoC 2013 Ideas

2013-03-04T14:55:16Z

Wiki-Psanxiao:

GvSIG GSoC 2013 Ideas

2013-03-04T14:54:40Z

Wiki-Psanxiao: Created page with "Use this page to jot down and develop any good idea for the Google Summer of Code 2012 program with gvSIG project. Please, use the gvSIG mailing lists for discussion and chec..."

Use this page to jot down and develop any good idea for the [[Google Summer of Code 2012]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[GvSIG GSoC 2012 Ideas|2012]],[[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.

__TOC__

== Idea template ==

* '''Product''': gvSIG Desktop/gvSIG Mobile/gvSIG Mini
* '''Possible mentor''': if applicable
* '''Possible student''': if applicable

Write your idea here... Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi imperdiet condimentum leo sit amet scelerisque. Aliquam placerat, dolor non egestas gravida, tellus felis viverra dui, a scelerisque dolor leo in nulla. Suspendisse pharetra lacus vitae lacus mollis dapibus dignissim metus varius. Nullam scelerisque, elit sit amet ornare commodo, tortor enim consectetur est, eget imperdiet leo augue eget felis. Vivamus nec justo tellus, nec semper ante. Etiam et dolor urna. Nullam non augue in lacus auctor laoreet eget non erat. Integer id justo id magna commodo malesuada. Maecenas tincidunt ipsum nec erat fringilla posuere. Sed ante sapien, posuere non euismod tincidunt, fermentum sollicitudin quam. Aenean metus lacus, viverra ut hendrerit eu, interdum vitae turpis.

[[Category:Google Summer of Code]][[Category:gvSIG]]

I Geoinquietos Nacional

2013-01-24T17:16:42Z

Wiki-Psanxiao:

Primer encuentro nacional de los diferentes grupos locales, a celebrar durante las Jornadas de SIG Libre de Girona.
Disponemos de 1 hora para montar algo. El plan por el momento es hacer un par de "ignite talks" y después una mesa redonda con la participación de los diferentes grupos locales, donde compartir experiencias e ideas entre todos.

==Ignite Talks==

* Víctor Olaya - geogit
* Ignite 2
* ...

==Mesa Redonda grupos Locales==

Grupos participantes confirmados:

* Geoinquietos Barcelona
* Geoinquietos Valencia
* Geoinquietos Zona Norte
* Geoinquietos Madrid
* Geoinquietos Cantabria

I Geoinquietos Nacional

2013-01-24T15:42:12Z

Wiki-Psanxiao:

Primer encuentro nacional de los diferentes grupos locales, a celebrar durante las Jornadas de SIG Libre de Girona.
Disponemos de 1 hora para montar algo. El plan por el momento es hacer un par de "ignite talks" y después una mesa redonda con la participación de los diferentes grupos locales, donde compartir experiencias e ideas entre todos.

==Ignite Talks==

* Ignite 1
* ...

==Mesa Redonda grupos Locales==

Grupos participantes confirmados:

* Geoinquietos Barcelona
* Geoinquietos Valencia
* Geoinquietos Zona Norte
* Geoinquietos Madrid
* Geoinquietos Cantabria

I Geoinquietos Nacional

2013-01-24T15:41:56Z

Wiki-Psanxiao: Created page with "Primer encuentro nacional de los diferentes grupos locales, a celebrar durante las Jornadas de SIG Libre de Girona. Disponemos de 1 para montar algo. El plan por el momento es ha..."

Primer encuentro nacional de los diferentes grupos locales, a celebrar durante las Jornadas de SIG Libre de Girona.
Disponemos de 1 para montar algo. El plan por el momento es hacer un par de "ignite talks" y después una mesa redonda con la participación de los diferentes grupos locales, donde compartir experiencias e ideas entre todos.

==Ignite Talks==

* Ignite 1
* ...

==Mesa Redonda grupos Locales==

Grupos participantes confirmados:

* Geoinquietos Barcelona
* Geoinquietos Valencia
* Geoinquietos Zona Norte
* Geoinquietos Madrid
* Geoinquietos Cantabria

Category:Eventos

2013-01-24T15:35:10Z

Wiki-Psanxiao:

__NOTOC__
En esta categoría se listan todas las páginas relacionadas con eventos vinculados a [[OSGeo-es]]

{| border=0 align="top"
|- valign="top"
| width="50%" |
== 2012 ==

* [[I Geoinquietos Nacional]]

| width="50%" |
== 2011 ==

* [[ESRI UC 2011 Madrid]]
* [[7th gvSIG Conference Valencia]]

|- valign="top"
| width="50%" |

== 2010 ==

* [[6th gvSIG Conference]]
* [[IV Congreso SL de la CV|IV Congreso de Software Libre de la CV]]
* [[FOSS4G2010]]
* [[2as Jornadas LAC de gvSIG]]
* [[OSGeo en la UPM 2010]]
* [[III Encuentro ASOLIF de Empresas de Software Libre]]
* [[4th Jornadas de SIG Libre OSGeo Spanish in Girona]]
* [http://barcampvalencia.com/ 2a Barcamp Valencia] Presentación sobre [http://www.slideshare.net/xurxosanz/open-layers-por-qu-no-poner-un-mapa-en-tu-web OpenLayers]
| width="50%" |

== 2009 ==

*[http://www.gvsig.org/web/community/events/jornadas-lac/2009 1as Jornadas LAC de gvSIG] / Presentación sobre [http://gvsig-desktop.forge.osor.eu/downloads/pub/events/jornadas-lac/1as-jornadas-lac/reports/osgeo-es.odp OSGeo-ES]
*[[5th gvSIG Conference]]
*[[Curso IDE UPM09|Curso IDEs UPM09]]
*Presentación OSGeo Foro Innovación
*[http://barcampvalencia.com/ 1a Desconferencia BarCamp Valencia] Presentación sobre [https://svn.osgeo.org/osgeo/community/presentations/20090725-barcamp-valencia/01_OSGeo_ES_vBarCamp.odp OSGeo-ES]
*III Jornadas de SIG Libre 2009
*[[OSGeo en Informatica 2009]]
|- valign="top"
| width="50%" |

== 2008 ==

* [[4th gvSIG Conference]]
* [[OSGeo en 4th gvSIG Conference]]
* [[II Jornadas de SIG Libre 2008]]
* [[OSGeo Spanish in Girona]]
* XXI International Geodetic Students Meeting, Valencia - Presentación sobre [https://svn.osgeo.org/osgeo/community/presentations/20080505-Valencia-IGSM/osgeo.odp OSGeo] y [https://svn.osgeo.org/osgeo/community/presentations/20080505-Valencia-IGSM/gvsig.odp gvSIG]
* 10º Encontro de Utilizadores de Informação Geográfica, Lisboa
|
== 2007 ==

* [[3rd gvSIG Conference]]
* [[2nd Jornadas de SIG Libre: OSGeo Spanish in Girona]]
|}

[[Category:Español]]

GvSIG GSoC 2011 Ideas

2011-02-08T10:11:27Z

Wiki-Psanxiao: /* Import / Export data from Epanet */

[[Category:Google Summer of Code]][[Category:gvSIG]]__TOC__

== gvSIG Desktop ==

=== Import / Export data from Epanet ===

Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]

The idea is to define a layer model suitable to be exported to Epanet's .inp file, and a geoprocess to export this model to Epanet. So, we will need to define pipes, wells, valves, depots and so on in gvSIG, analize connectivity and then export to Epanet. From Epanet, to analyze and modify the network and then export the network again to gvSIG. So, the main tasks are: '' Define layer model '', '' Create a geoprocess exporter to .INP'' , '' Create a geoprocess importer back to gvSIG ''.

=== New features for NavTable ===

Proposed mentor: [[User:psanxiao | Pablo Sanxiao]]

* '''Migrating NavTable to gvSIG 2.0''': This includes a good separation between interface and data access.
* '''Making NavTable will be able to modify the table schema''': it would be possible to add, erase and modify attributes, its order, the visibility and alias for the field name.
* '''New attribute table based on NavTable''': Creating a new gvSIG's attribute table based on NavTable to view data all together as in te current one but included the NavTable features of navigation, selection, filtered, etc... and some new improvements.

== gvSIG Mobile ==

== gvSIG Mini ==

User:Psanxiao

2011-01-18T08:56:21Z

Wiki-Psanxiao:

I'm Technical Engineer in Computer Sciences, involved in the Free Software World since 2005.

I've been participating in the [http://gnome.org GNOME] community as developer and maintainer of the [http://projects.gnome.org/gtranslator gtranslator] project and
also as member of the [http://foundation.gnome.org GNOME Foundation]

Since early 2009 I was working at [http://www.cartolab.es CartoLab] (Cartographic Engineering Laboratory of University of A Coruña) as a developer of GIS applications. Some examples:

* [http://navtable.forge.osor.eu NavTable]
* [http://forge.osor.eu/projects/opencadtools/ OpenCADTools]

In June, 2010 I created, with other six members of CartoLab, a new free software company called [http://www.icarto.es iCarto] to work in GIS applied to Civil Engineering and Cooperation for Development.

===Contact===

:IRC nick: psanxiao
:Jabber: psanxiao AT jabberes DOT org
:mail: psanxiao AT icarto DOT es

User:Psanxiao

2010-05-18T07:40:06Z

Wiki-Psanxiao:

I'm Technical Engineer in Computer Sciences, involved in the Free Software World since 2005.

I've been participating in the [http://gnome.org GNOME] community as developer and maintainer of the [http://projects.gnome.org/gtranslator gtranslator] project and
also as member of the [http://foundation.gnome.org GNOME Foundation]

Since early 2009 I'm working at [http://www.cartolab.es CartoLab] (Cartographic Engineering Laboratory of University of A Coruña) as a developer of GIS applications. Some examples:

* [http://navtable.forge.osor.eu NavTable]
* [http://forge.osor.eu/projects/opencadtools/ OpenCADTools]

===Contact===

:IRC nick: psanxiao
:Jabber: psanxiao AT jabberes DOT org
:mail: psanxiao AT cartolab DOT es

GvSIG GSoC 2010 Ideas

2010-03-29T16:07:06Z

Wiki-Psanxiao:

[[Category:Google Summer of Code]][[Category:gvSIG]]__TOC__

There's been a [http://n2.nabble.com/Google-Summer-of-Code-2010-td4790531.html#a4790531 general call] for ideas, mentors and students a gvSIG mailing list. If you have an idea, please feel free to add it here, as much detailed as possible. If you have any doubt, please refer to the general [[Google Summer of Code 2010]] main wiki page or [[Jorge Sanz]].

== gvSIG Desktop ==

Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]

* '''Import / Export data from Epanet''': The idea is to define a layer model suitable to be exported to Epanet's .inp file, and a geoprocess to export this model to Epanet. So, we will need to define pipes, wells, valves, depots and so on in gvSIG, analize connectivity and then export to Epanet. From Epanet, to analyze and modify the network and then export the network again to gvSIG. So, the main tasks are: '' Define layer model '', '' Create a geoprocess exporter to .INP'' , '' Create a geoprocess importer back to gvSIG ''.

Proposed mentor: [[User:csancehz | Carlos Sánchez Periñán]]

* '''KML 2.2 support for gvsig-gpe''': gvsig-gpe is a library for reading and writing data based on the GML format, through the use of events. It does not depend on any geometry data model, providing the raw data to the application. Initially developed for the GML format, it supports readers and writers for KML 2.1 formats. The project consist on develop a new plugin org.gvsig.gpe.kml2 for gvsig-gpe or complete the existing one adding the new KML 2.2 specification. The event's handled by the API also can be extended to support the Google KML file symbology referenced.
Summary:
-''Add new KML 2.2 tags specification to the reader into org.gvsig.gpe.kml''
-''Add the new updated KML 2.2 writer too''
-''Add new events to store other KML information or lauch it to the user''
OSOR gvsig-gpe repository [https://www.osor.eu/projects/gvsig-gpe]

Proposed mentor: [[User:benducke | Benjamin Ducke]]

* '''Support for SQLite3/SpatiaLite''': SQlite3 [http://www.sqlite.org] is a cross-plattform, fast and simple file-based DBMS. Currently, gvSIG has nothing to offer for those users that want to have a fully functional and fast desktop DBMS backend, without having to install (and manage) a full client/server system. SQlite3 could ideally fill that gap, being a far superior alternative to DBF and ODBC. SQlite3 can also store geometries (WKB and WKT) in an OGC-conformant manner. The GDAL/OGR driver page for SQLite3 details how this should be done. In addition, the SpatiaLite [http://www.gaia-gis.it/spatialite/] project provides optimized geometry storage plus topological SQL query functions. This looks very much like the emerging open source standard to replace those awful Shapefiles. Quantum GIS and OpenJUMP already have direct support for it and this makes having it in gvSIG all the more important. Much code could be borrowed from OpenJUMP, which is also Java based and already has working SQlite/SpatiaLite support. This should be implemented for gvSIG 2.0, as the data storage model has changed fundamentally in this code branch.

Work plan:
-''Add an SQLite3 driver for plain tables''
-''Add support for SpatiaLite vector layers (read and write)''

Proposed mentor: [[User:nachouve | Nacho Varela]]

* '''Sync gvSIG view with gmaps/osm...''': Create a gvSIG extension that allows to open an integrated web browser and show geographic info from google maps, openstreetmap, etc.. synchronized with the current view (zoom, pan, etc).

Proposed mentor: [[User:psanxiao | Pablo Sanxiao]]

* '''New fetaures for NavTable''': Implement new features for [http://navtable.forge.osor.eu NavTable]: modify the table schema to make possible add, erase and modify attributes and also choose which ones will be shown in NavTable and which won't, order records by attributes, creating a system to separate the GUI of the personalized forms based in Xml (maybe using thinlet, abeille...)

== gvSIG Mobile ==

* '''Add support of WMS-C and other tile services like OSM'''

* '''Add support of Versioned WFS:''' http://geoserver.org/display/GEOS/Versioning+WFS+-+Extensions

* '''Fill shapes with holes efficiently'''

== gvSIG Mini ==

Proposed mentor: [[Alberto Romeu]]

[http://www.gvsigmini.com gvSIG Mini] is a free mobile map viewer of several layers sources (OSM, WMS, WMS-c) which at the moment is able to consume [http://wiki.openstreetmap.org/wiki/YOURS YOURS routing service] and [http://wiki.openstreetmap.org/wiki/Name_finder NameFinder service] (also weather, twitter services, etc.).

gvSIG Mini is currently being developed by [http://www.prodevelop.es Prodevelop]. There are two versions: for Android and J2ME (CLDC/MIDP 2.0). Students are free to select which version of gvSIG Mini want to develop for or use a subset of the Java API compatible between Android and J2ME to build a library and then make the connectors needed for both versions.

* '''Add support to read GPX files (POIs, tracklogs, routes)''': The application should be able to read/parse files in GPX format, convert the data into the gvSIG Mini geometries model (points and lines) and draw the information on a new layer.

* '''Add support to write GPX files (POIs, tracklogs, routes)''': The application should be able to write files in GPX format to store POIs, tracklogs and routes with the information provided by the GPS.

* '''Design an API to make easy integrate gvSIG Mini in other applications''': For the Android version gvSIG Mini should be able to react to some Intent actions sent by other applications. For the J2ME version this project consists in decouple the mapping library from the UI.

* '''Integrate gvSIG Mini with social services''': Currently gvSIG Mini is able to send the GPS location of the device to the user twitter account. We'd like to improve the social skills of gvSIG Mini, so the application should be able to look for location information into the user's followers tweets and draw picture symbols on the proper locations over the map. This symbols should be contextable so, pressing on them the user should be able to send a message to the account of the user represented by the symbol.

* '''Build a POI editor using the OSM API''': Design a friendly interface to point locations on the map and edit the properties needed to store the location as a POI on the OSM database using its API.

'''We are open to new ideas!'''

User:Psanxiao

2010-03-29T16:04:22Z

Wiki-Psanxiao:

GvSIG GSoC 2010 Ideas

2010-03-29T16:01:46Z

Wiki-Psanxiao:

[[Category:Google Summer of Code]][[Category:gvSIG]]__TOC__

There's been a [http://n2.nabble.com/Google-Summer-of-Code-2010-td4790531.html#a4790531 general call] for ideas, mentors and students a gvSIG mailing list. If you have an idea, please feel free to add it here, as much detailed as possible. If you have any doubt, please refer to the general [[Google Summer of Code 2010]] main wiki page or [[Jorge Sanz]].

== gvSIG Desktop ==

Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]

* '''Import / Export data from Epanet''': The idea is to define a layer model suitable to be exported to Epanet's .inp file, and a geoprocess to export this model to Epanet. So, we will need to define pipes, wells, valves, depots and so on in gvSIG, analize connectivity and then export to Epanet. From Epanet, to analyze and modify the network and then export the network again to gvSIG. So, the main tasks are: '' Define layer model '', '' Create a geoprocess exporter to .INP'' , '' Create a geoprocess importer back to gvSIG ''.

Proposed mentor: [[User:csancehz | Carlos Sánchez Periñán]]

* '''KML 2.2 support for gvsig-gpe''': gvsig-gpe is a library for reading and writing data based on the GML format, through the use of events. It does not depend on any geometry data model, providing the raw data to the application. Initially developed for the GML format, it supports readers and writers for KML 2.1 formats. The project consist on develop a new plugin org.gvsig.gpe.kml2 for gvsig-gpe or complete the existing one adding the new KML 2.2 specification. The event's handled by the API also can be extended to support the Google KML file symbology referenced.
Summary:
-''Add new KML 2.2 tags specification to the reader into org.gvsig.gpe.kml''
-''Add the new updated KML 2.2 writer too''
-''Add new events to store other KML information or lauch it to the user''
OSOR gvsig-gpe repository [https://www.osor.eu/projects/gvsig-gpe]

Proposed mentor: [[User:benducke | Benjamin Ducke]]

* '''Support for SQLite3/SpatiaLite''': SQlite3 [http://www.sqlite.org] is a cross-plattform, fast and simple file-based DBMS. Currently, gvSIG has nothing to offer for those users that want to have a fully functional and fast desktop DBMS backend, without having to install (and manage) a full client/server system. SQlite3 could ideally fill that gap, being a far superior alternative to DBF and ODBC. SQlite3 can also store geometries (WKB and WKT) in an OGC-conformant manner. The GDAL/OGR driver page for SQLite3 details how this should be done. In addition, the SpatiaLite [http://www.gaia-gis.it/spatialite/] project provides optimized geometry storage plus topological SQL query functions. This looks very much like the emerging open source standard to replace those awful Shapefiles. Quantum GIS and OpenJUMP already have direct support for it and this makes having it in gvSIG all the more important. Much code could be borrowed from OpenJUMP, which is also Java based and already has working SQlite/SpatiaLite support. This should be implemented for gvSIG 2.0, as the data storage model has changed fundamentally in this code branch.

Work plan:
-''Add an SQLite3 driver for plain tables''
-''Add support for SpatiaLite vector layers (read and write)''

Proposed mentor: [[User:nachouve | Nacho Varela]]

* '''Sync gvSIG view with gmaps/osm...''': Create a gvSIG extension that allows to open an integrated web browser and show geographic info from google maps, openstreetmap, etc.. synchronized with the current view (zoom, pan, etc).

Proposed mentor: [[User:psanxiao | Pablo Sanxiao]]

* '''New fetaures for NavTable''': Implement new features for NavTable: modify the table schema to make possible add, erase and modify attributes and also choose which ones will be shown in NavTable and which won't, order records by attributes, creating a system to separate the GUI of the personalized forms based in Xml (maybe using thinlet, abeille...)

== gvSIG Mobile ==

* '''Add support of WMS-C and other tile services like OSM'''

* '''Add support of Versioned WFS:''' http://geoserver.org/display/GEOS/Versioning+WFS+-+Extensions

* '''Fill shapes with holes efficiently'''

== gvSIG Mini ==

Proposed mentor: [[Alberto Romeu]]

[http://www.gvsigmini.com gvSIG Mini] is a free mobile map viewer of several layers sources (OSM, WMS, WMS-c) which at the moment is able to consume [http://wiki.openstreetmap.org/wiki/YOURS YOURS routing service] and [http://wiki.openstreetmap.org/wiki/Name_finder NameFinder service] (also weather, twitter services, etc.).

gvSIG Mini is currently being developed by [http://www.prodevelop.es Prodevelop]. There are two versions: for Android and J2ME (CLDC/MIDP 2.0). Students are free to select which version of gvSIG Mini want to develop for or use a subset of the Java API compatible between Android and J2ME to build a library and then make the connectors needed for both versions.

* '''Add support to read GPX files (POIs, tracklogs, routes)''': The application should be able to read/parse files in GPX format, convert the data into the gvSIG Mini geometries model (points and lines) and draw the information on a new layer.

* '''Add support to write GPX files (POIs, tracklogs, routes)''': The application should be able to write files in GPX format to store POIs, tracklogs and routes with the information provided by the GPS.

* '''Design an API to make easy integrate gvSIG Mini in other applications''': For the Android version gvSIG Mini should be able to react to some Intent actions sent by other applications. For the J2ME version this project consists in decouple the mapping library from the UI.

* '''Integrate gvSIG Mini with social services''': Currently gvSIG Mini is able to send the GPS location of the device to the user twitter account. We'd like to improve the social skills of gvSIG Mini, so the application should be able to look for location information into the user's followers tweets and draw picture symbols on the proper locations over the map. This symbols should be contextable so, pressing on them the user should be able to send a message to the account of the user represented by the symbol.

* '''Build a POI editor using the OSM API''': Design a friendly interface to point locations on the map and edit the properties needed to store the location as a POI on the OSM database using its API.

'''We are open to new ideas!'''

User:Psanxiao

2010-03-29T14:40:25Z

Wiki-Psanxiao: New page: I'm Technical Engineer in Computer Sciences, involved in the Free Software World since 2005. I've been participating in the [http://gnome.org GNOME] community as developer and maintainer ...

GvSIG GSoC 2010 Ideas

2010-03-29T14:23:45Z

Wiki-Psanxiao:

[[Category:Google Summer of Code]][[Category:gvSIG]]__TOC__

There's been a [http://n2.nabble.com/Google-Summer-of-Code-2010-td4790531.html#a4790531 general call] for ideas, mentors and students a gvSIG mailing list. If you have an idea, please feel free to add it here, as much detailed as possible. If you have any doubt, please refer to the general [[Google Summer of Code 2010]] main wiki page or [[Jorge Sanz]].

== gvSIG Desktop ==

Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]

* '''Import / Export data from Epanet''': The idea is to define a layer model suitable to be exported to Epanet's .inp file, and a geoprocess to export this model to Epanet. So, we will need to define pipes, wells, valves, depots and so on in gvSIG, analize connectivity and then export to Epanet. From Epanet, to analyze and modify the network and then export the network again to gvSIG. So, the main tasks are: '' Define layer model '', '' Create a geoprocess exporter to .INP'' , '' Create a geoprocess importer back to gvSIG ''.

Proposed mentor: [[User:csancehz | Carlos Sánchez Periñán]]

* '''KML 2.2 support for gvsig-gpe''': gvsig-gpe is a library for reading and writing data based on the GML format, through the use of events. It does not depend on any geometry data model, providing the raw data to the application. Initially developed for the GML format, it supports readers and writers for KML 2.1 formats. The project consist on develop a new plugin org.gvsig.gpe.kml2 for gvsig-gpe or complete the existing one adding the new KML 2.2 specification. The event's handled by the API also can be extended to support the Google KML file symbology referenced.
Summary:
-''Add new KML 2.2 tags specification to the reader into org.gvsig.gpe.kml''
-''Add the new updated KML 2.2 writer too''
-''Add new events to store other KML information or lauch it to the user''
OSOR gvsig-gpe repository [https://www.osor.eu/projects/gvsig-gpe]

Proposed mentor: [[User:benducke | Benjamin Ducke]]

* '''Support for SQLite3/SpatiaLite''': SQlite3 [http://www.sqlite.org] is a cross-plattform, fast and simple file-based DBMS. Currently, gvSIG has nothing to offer for those users that want to have a fully functional and fast desktop DBMS backend, without having to install (and manage) a full client/server system. SQlite3 could ideally fill that gap, being a far superior alternative to DBF and ODBC. SQlite3 can also store geometries (WKB and WKT) in an OGC-conformant manner. The GDAL/OGR driver page for SQLite3 details how this should be done. In addition, the SpatiaLite [http://www.gaia-gis.it/spatialite/] project provides optimized geometry storage plus topological SQL query functions. This looks very much like the emerging open source standard to replace those awful Shapefiles. Quantum GIS and OpenJUMP already have direct support for it and this makes having it in gvSIG all the more important. Much code could be borrowed from OpenJUMP, which is also Java based and already has working SQlite/SpatiaLite support. This should be implemented for gvSIG 2.0, as the data storage model has changed fundamentally in this code branch.

Work plan:
-''Add an SQLite3 driver for plain tables''
-''Add support for SpatiaLite vector layers (read and write)''

Proposed mentor: [[User:nachouve | Nacho Varela]]

* '''Sync gvSIG view with gmaps/osm...''': Create a gvSIG extension that allows to open an integrated web browser and show geographic info from google maps, openstreetmap, etc.. synchronized with the current view (zoom, pan, etc).

Proposed mentor: [[User:psanxiao | Pablo Sanxiao]]

* '''New fetaures for NavTable''': Implement new features for NavTable: modify the table schema to make possible add, erase and modify attributes and also choose which ones will be shown in NavTable and which won't, order records by attributes,
creating a system to separate the GUI of the personalized forms based in Xml (maybe using thinlet, abeille...)

== gvSIG Mobile ==

* '''Add support of WMS-C and other tile services like OSM'''

* '''Add support of Versioned WFS:''' http://geoserver.org/display/GEOS/Versioning+WFS+-+Extensions

* '''Fill shapes with holes efficiently'''

== gvSIG Mini ==

Proposed mentor: [[Alberto Romeu]]

[http://www.gvsigmini.com gvSIG Mini] is a free mobile map viewer of several layers sources (OSM, WMS, WMS-c) which at the moment is able to consume [http://wiki.openstreetmap.org/wiki/YOURS YOURS routing service] and [http://wiki.openstreetmap.org/wiki/Name_finder NameFinder service] (also weather, twitter services, etc.).

gvSIG Mini is currently being developed by [http://www.prodevelop.es Prodevelop]. There are two versions: for Android and J2ME (CLDC/MIDP 2.0). Students are free to select which version of gvSIG Mini want to develop for or use a subset of the Java API compatible between Android and J2ME to build a library and then make the connectors needed for both versions.

* '''Add support to read GPX files (POIs, tracklogs, routes)''': The application should be able to read/parse files in GPX format, convert the data into the gvSIG Mini geometries model (points and lines) and draw the information on a new layer.

* '''Add support to write GPX files (POIs, tracklogs, routes)''': The application should be able to write files in GPX format to store POIs, tracklogs and routes with the information provided by the GPS.

* '''Design an API to make easy integrate gvSIG Mini in other applications''': For the Android version gvSIG Mini should be able to react to some Intent actions sent by other applications. For the J2ME version this project consists in decouple the mapping library from the UI.

* '''Integrate gvSIG Mini with social services''': Currently gvSIG Mini is able to send the GPS location of the device to the user twitter account. We'd like to improve the social skills of gvSIG Mini, so the application should be able to look for location information into the user's followers tweets and draw picture symbols on the proper locations over the map. This symbols should be contextable so, pressing on them the user should be able to send a message to the account of the user represented by the symbol.

* '''Build a POI editor using the OSM API''': Design a friendly interface to point locations on the map and edit the properties needed to store the location as a POI on the OSM database using its API.

'''We are open to new ideas!'''

GvSIG GSoC 2010 Ideas

2010-03-29T13:40:42Z

Wiki-Psanxiao:

[[Category:Google Summer of Code]][[Category:gvSIG]]__TOC__

There's been a [http://n2.nabble.com/Google-Summer-of-Code-2010-td4790531.html#a4790531 general call] for ideas, mentors and students a gvSIG mailing list. If you have an idea, please feel free to add it here, as much detailed as possible. If you have any doubt, please refer to the general [[Google Summer of Code 2010]] main wiki page or [[Jorge Sanz]].

== gvSIG Desktop ==

Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]

* '''Import / Export data from Epanet''': The idea is to define a layer model suitable to be exported to Epanet's .inp file, and a geoprocess to export this model to Epanet. So, we will need to define pipes, wells, valves, depots and so on in gvSIG, analize connectivity and then export to Epanet. From Epanet, to analyze and modify the network and then export the network again to gvSIG. So, the main tasks are: '' Define layer model '', '' Create a geoprocess exporter to .INP'' , '' Create a geoprocess importer back to gvSIG ''.

Proposed mentor: [[User:csancehz | Carlos Sánchez Periñán]]

* '''KML 2.2 support for gvsig-gpe''': gvsig-gpe is a library for reading and writing data based on the GML format, through the use of events. It does not depend on any geometry data model, providing the raw data to the application. Initially developed for the GML format, it supports readers and writers for KML 2.1 formats. The project consist on develop a new plugin org.gvsig.gpe.kml2 for gvsig-gpe or complete the existing one adding the new KML 2.2 specification. The event's handled by the API also can be extended to support the Google KML file symbology referenced.
Summary:
-''Add new KML 2.2 tags specification to the reader into org.gvsig.gpe.kml''
-''Add the new updated KML 2.2 writer too''
-''Add new events to store other KML information or lauch it to the user''
OSOR gvsig-gpe repository [https://www.osor.eu/projects/gvsig-gpe]

Proposed mentor: [[User:benducke | Benjamin Ducke]]

* '''Support for SQLite3/SpatiaLite''': SQlite3 [http://www.sqlite.org] is a cross-plattform, fast and simple file-based DBMS. Currently, gvSIG has nothing to offer for those users that want to have a fully functional and fast desktop DBMS backend, without having to install (and manage) a full client/server system. SQlite3 could ideally fill that gap, being a far superior alternative to DBF and ODBC. SQlite3 can also store geometries (WKB and WKT) in an OGC-conformant manner. The GDAL/OGR driver page for SQLite3 details how this should be done. In addition, the SpatiaLite [http://www.gaia-gis.it/spatialite/] project provides optimized geometry storage plus topological SQL query functions. This looks very much like the emerging open source standard to replace those awful Shapefiles. Quantum GIS and OpenJUMP already have direct support for it and this makes having it in gvSIG all the more important. Much code could be borrowed from OpenJUMP, which is also Java based and already has working SQlite/SpatiaLite support. This should be implemented for gvSIG 2.0, as the data storage model has changed fundamentally in this code branch.

Work plan:
-''Add an SQLite3 driver for plain tables''
-''Add support for SpatiaLite vector layers (read and write)''

Proposed mentor: [[User:nachouve | Nacho Varela]]

* '''Sync gvSIG view with gmaps/osm...''': Create a gvSIG extension that allows to open an integrated web browser and show geographic info from google maps, openstreetmap, etc.. synchronized with the current view (zoom, pan, etc).

== gvSIG Mobile ==

* '''Add support of WMS-C and other tile services like OSM'''

* '''Add support of Versioned WFS:''' http://geoserver.org/display/GEOS/Versioning+WFS+-+Extensions

* '''Fill shapes with holes efficiently'''

== gvSIG Mini ==

Proposed mentor: [[Alberto Romeu]]

[http://www.gvsigmini.com gvSIG Mini] is a free mobile map viewer of several layers sources (OSM, WMS, WMS-c) which at the moment is able to consume [http://wiki.openstreetmap.org/wiki/YOURS YOURS routing service] and [http://wiki.openstreetmap.org/wiki/Name_finder NameFinder service] (also weather, twitter services, etc.).

gvSIG Mini is currently being developed by [http://www.prodevelop.es Prodevelop]. There are two versions: for Android and J2ME (CLDC/MIDP 2.0). Students are free to select which version of gvSIG Mini want to develop for or use a subset of the Java API compatible between Android and J2ME to build a library and then make the connectors needed for both versions.

* '''Add support to read GPX files (POIs, tracklogs, routes)''': The application should be able to read/parse files in GPX format, convert the data into the gvSIG Mini geometries model (points and lines) and draw the information on a new layer.

* '''Add support to write GPX files (POIs, tracklogs, routes)''': The application should be able to write files in GPX format to store POIs, tracklogs and routes with the information provided by the GPS.

* '''Design an API to make easy integrate gvSIG Mini in other applications''': For the Android version gvSIG Mini should be able to react to some Intent actions sent by other applications. For the J2ME version this project consists in decouple the mapping library from the UI.

* '''Integrate gvSIG Mini with social services''': Currently gvSIG Mini is able to send the GPS location of the device to the user twitter account. We'd like to improve the social skills of gvSIG Mini, so the application should be able to look for location information into the user's followers tweets and draw picture symbols on the proper locations over the map. This symbols should be contextable so, pressing on them the user should be able to send a message to the account of the user represented by the symbol.

* '''Build a POI editor using the OSM API''': Design a friendly interface to point locations on the map and edit the properties needed to store the location as a POI on the OSM database using its API.

'''We are open to new ideas!'''