OSGeo - User contributions [en]

GvSIG GSoC 2013 Ideas

2013-05-02T18:59:46Z

Wiki-Aromeu: /* Integrating OGR library into gvSIG Mini */

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''':
* '''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.

== Create a title block from the library in the Layout of gvSIG ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': [[User:vcaballero|Vicente Caballero]]
* '''Possible student''': [[Violeta Carlos]]

'''1. Introduction'''

GvSIG as GIS desktop thick client, it seems a viable and free, but limited in terms of Layout, so I plan to improve the use of the Layout of this application to extend the functionality of gvSIG Layouts, add to a library of configurable title blocks (this functionality is required through the mailing list of users of gvSIG).

The aim is to reduce repetitive and tedious work of creating title blocks in the designs, which is so limited in the current version of gvSIG. It will be possible to configure the text, images, divisions, size, font ... and save them with a owner format (GVB) for storage and use in any other Layout in gvSIG.

'''2. Background'''

From the point of view of the end user, the Layout of the desing process is very important part of any GIS solution, since it is eventually represent how the information on the role that ends up being the way in representing most GIS operations or CAD we do.

'''3. The idea'''

Once we have defined the library and several title block available, we will be able to select for different Layouts you want and whether it was created with the appropriate parameters, we can even customize.

The plugin will provide gvSIG the ability to save the title block as separate elements with a owner format and reusing the same libraries that use gvSIG to save your files (Castor), such as: "GVP", "gvt" and "gvl."

This list of formats extensions gvSIG would add "GVB" referring to the items title block.

The plugin will provide a basic library and title block created by default, which may be adding data and can be customized to be used directly by users.

== Design and implement an API for tiled vectorial support of POIProxy ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[User:aromeu|Alberto Romeu]]
* '''Possible student''': [[Arturo Argilés]]

'''1. Introduction'''

Currently there are plenty of services that provide geo-located data: Twitter, Buzz, Panoramio, Flickr, Wikipedia, YouTube, LastFM, Minube, Foursquare, etc. All of them have things in common (Use of a REST API, JSON as a format for responses, ...) and several different behaviours. [https://github.com/alrocar/POIProxy POIProxy] is a server that fills the gap between all that services and a map client.

'''2. Background'''

A similar idea was proposed in 2011 and ended up with the development of POIProxy, but gvSIG Mini still lacks support to load POIProxy layers or provide geocoding and reverse geocoding, that makes gvSIG Mini less atractive to the general public.

'''3. The idea'''

The idea consists in create a brand new POIProxy client based on gvSIG Mini that will provide access to a set of geo-location services.

Technically this project pretends to provide gvSIG Mini with a simple API to support POIProxy services. The API will offer transparent support to load a geo-located service, make requests as the user navigates the map, cache data (into memory and disk in standard GeoJSON) to speed up the data-load, and build the user interfaces to show extra data, such as additional info, media (images, video), etc.

The user will have the chance to load one or more POIProxy layers that will make requests to geo-location services as the user navigates the map. That functionality will offer social and contextual information related to the location of the user.

On the other hand, gvSIG Mini lacks of a geocoding and reverse-geocoding service. POIProxy could be a good candidate to provide those services.

Recently the OGC has contributed a new standard, [http://openpoi.ogcnetwork.net/ OpenPOI]. It will be nice, during the summer, add support to this standard in POIProxy so that gvSIG Mini could become a client of OpenPOI.

== 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-05-02T18:59:26Z

Wiki-Aromeu:

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''':
* '''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.

== Create a title block from the library in the Layout of gvSIG ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': [[User:vcaballero|Vicente Caballero]]
* '''Possible student''': [[Violeta Carlos]]

'''1. Introduction'''

GvSIG as GIS desktop thick client, it seems a viable and free, but limited in terms of Layout, so I plan to improve the use of the Layout of this application to extend the functionality of gvSIG Layouts, add to a library of configurable title blocks (this functionality is required through the mailing list of users of gvSIG).

The aim is to reduce repetitive and tedious work of creating title blocks in the designs, which is so limited in the current version of gvSIG. It will be possible to configure the text, images, divisions, size, font ... and save them with a owner format (GVB) for storage and use in any other Layout in gvSIG.

'''2. Background'''

From the point of view of the end user, the Layout of the desing process is very important part of any GIS solution, since it is eventually represent how the information on the role that ends up being the way in representing most GIS operations or CAD we do.

'''3. The idea'''

Once we have defined the library and several title block available, we will be able to select for different Layouts you want and whether it was created with the appropriate parameters, we can even customize.

The plugin will provide gvSIG the ability to save the title block as separate elements with a owner format and reusing the same libraries that use gvSIG to save your files (Castor), such as: "GVP", "gvt" and "gvl."

This list of formats extensions gvSIG would add "GVB" referring to the items title block.

The plugin will provide a basic library and title block created by default, which may be adding data and can be customized to be used directly by users.

== Integrating OGR library into gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[User:aromeu|Alberto Romeu]]
* '''Possible student''': [[Arturo Argilés]]

'''1. Introduction'''

Currently there are plenty of services that provide geo-located data: Twitter, Buzz, Panoramio, Flickr, Wikipedia, YouTube, LastFM, Minube, Foursquare, etc. All of them have things in common (Use of a REST API, JSON as a format for responses, ...) and several different behaviours. [https://github.com/alrocar/POIProxy POIProxy] is a server that fills the gap between all that services and a map client.

'''2. Background'''

A similar idea was proposed in 2011 and ended up with the development of POIProxy, but gvSIG Mini still lacks support to load POIProxy layers or provide geocoding and reverse geocoding, that makes gvSIG Mini less atractive to the general public.

'''3. The idea'''

The idea consists in create a brand new POIProxy client based on gvSIG Mini that will provide access to a set of geo-location services.

Technically this project pretends to provide gvSIG Mini with a simple API to support POIProxy services. The API will offer transparent support to load a geo-located service, make requests as the user navigates the map, cache data (into memory and disk in standard GeoJSON) to speed up the data-load, and build the user interfaces to show extra data, such as additional info, media (images, video), etc.

The user will have the chance to load one or more POIProxy layers that will make requests to geo-location services as the user navigates the map. That functionality will offer social and contextual information related to the location of the user.

On the other hand, gvSIG Mini lacks of a geocoding and reverse-geocoding service. POIProxy could be a good candidate to provide those services.

Recently the OGC has contributed a new standard, [http://openpoi.ogcnetwork.net/ OpenPOI]. It will be nice, during the summer, add support to this standard in POIProxy so that gvSIG Mini could become a client of OpenPOI.
== 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-25T11:27:14Z

Wiki-Aromeu:

GvSIG GSoC 2013 Ideas

2013-03-25T11:26:32Z

Wiki-Aromeu: /* Integrating OGR library into gvSIG Mini */

GvSIG GSoC 2013 Ideas

2013-03-25T11:23:23Z

Wiki-Aromeu:

GvSIG GSoC 2012 Ideas

2012-03-30T08:44:02Z

Wiki-Aromeu:

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 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.

__TOC__

== Create a gvSIG plugin for drinking water analysis and management. ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': [[User:Fpenarru|Francisco José Peñarrubia]]
* '''Possible student''': if applicable

The analysis part will be done with Epanet's help (http://www.epa.gov/nrmrl/wswrd/dw/epanet.html).

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 test data integrity (with Network Analysis Extension) and then export to Epanet.

From Epanet, the user will be able 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 (we can start from an ongoing work) , Create a geoprocess importer back to gvSIG.

After having the network already balanced in gvSIG, we will develop some methods in order to manage the daily operation of the network. (See possible leaks, see wich pipes or valves need to be replaced, etc).

== Create a solver for the Traveling Salesman and Vehicle Routing Problems ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': [[User:Fpenarru|Francisco José Peñarrubia]]
* '''Possible student''': [[User:davidpinh|David Pinheiro]]

'''The problem''': The Vehicle Routing Problem (VRP), as the well known Traveling Salesman Problem (TSP), is an Optimization problem whose goal is to determine the optimal set of routes to be performed by a fleet of vehicles (in the case of the TSP, just one vehicle) to serve (picking or delivering goods) a given set of costumers. It has plenty of application areas such as distribution and logistics, solid waste collection, passenger transportation …

'''The solution''': These are hard NP-complete problems. Therefore, for reasonable sized problems, only heuristic (and meta-heuristic) methods are viable in a solution search.

'''The proposed work''': The development of a solver for the TSP and VRP on top of the Network Extension. The work should address not only the simple VRP but one or more of its most popular variants, like the Capacitated VRP (CVRP) or others.
The suggested project will continue a MSc thesis that the proposed student is taking and which has already leaded to a Java library with the goal of solving VRP (and TSP) using Genetic Algorithms (http://code.google.com/p/metavrp) and a prototype of a solver on top of GvSIG’s Network extension (http://code.google.com/p/vrp-for-gvsig-network-extension).

== Adding GPS survey capabilities to gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': [[User:Alrocar|Alberto Romeu]]
* '''Possible student''': <Enter your name here>

{| border="0" cellspacing="5" cellpadding="5" align="center"
| [[Image:gvsig-mini.png]]
|valign="top" | ''Storing GPS coordinates in a well-known vector format is a powerful professional-oriented feature, currently unavailable in gvSIG Mini. The suggested output format is SHP due to its popularity.''
|}

==== Suggested simplest version ====

* There will be a ''Start Survey'' button which will create an in-memory vector layer in gvSIG Mini using its geometry model (this has nothing to do with the output format yet).
* At any moment, the user will be able to push an ''Export'' button to create a vector data file in the device's SD card with the current set of coordinates. The suggested output format is [http://en.wikipedia.org/wiki/Shapefile ESRI Shapefile]. Alternatives: GML, GPX, Sqlite, GeoJSon, etc.
* It is also important to let the user associate some values to each feature (attributes). In order to establish the attribute names and types and perhaps valid values, you could simply use a properties file (attributes.properties) so the implementation will be easier. I'm thinking about something like:

<pre>
ELEMENT=STRING;TREE,ROCK,HOLE,POOL
SIZE=STRING;LARGE,MEDIUM,SMALL
COMMENT=STRING
</pre>

* The geometry type will be POINT to make the implementation easier.

In this simplest version, gvSIG Mini will write a vector data file but will not necessarily be able to read it. If you choose SHP as the output format, you might use the shapefile writer available in gvSIG and gvSIG Mobile or use some other GIS library to perform the export operation (GeoTools, etc).

==== Suggested improvements ====

* Implement also the import option to let the user open the resulting vector data file.
* Let the user choose LINE or POLYGON as the geometry type of the new vector layer. This will make the application more sophisticated, as it will be necessary to think about a user-friendly way to finish the current feature and start a new one.

== Add tests and educational games support to gvSIG Educa/Batoví ==

* '''Product''': gvSIG Batoví/Educa (gvSIG desktop 2.0)
* '''Possible mentor''': Cèsar Ordiñana
* '''Possible student''': Nadal Francisco

==== gvSIG Educa ====

'''gvSIG Educa''' is an adaptation of the gvSIG Desktop project as an education tool, mainly for subjects with a geographic component.

The main objective of gvSIG Educa is to be applied to teach territory analysis and comprehension. It may be used not only for geography matters, but also for any matter which uses the territorial component, like history, economics, natural sciences, sociology, ...

gvSIG Educa makes learning an easier task, as it allows students to interact with the information, through the use of thematic maps, tests and educational games.

==== gvSIG Batoví ====

'''gvSIG Batoví''' is the origin project for gvSIG Educa. It is a project driven by the Ministerio de Transporte y Obras Públicas (MTOP) of the República Oriental del Uruguay, developed by the gvSIG Association and the Facultad de Ingeniería de la Universidad de la República (UdelaR). Its main objective is to allow using gvSIG Educa in education through the Plan Ceibal project (Uruguay).

The project is ending the first stage, with the following outcomes:

* gvSIG plugins for building and visualizing thematic maps.

* A gvSIG Batoví distribution and installer for the Plan Ceibal computers, which are OLPC computes distributed to all the secondary education students in the public schools of Uruguay.

* A thematic maps viewer application, to be used in the Plan Ceibal computers for the elementary education.

==== Objectives ====

The objective would be to extend the thematic maps support already available to allow to design and play tests and educational games, to be used in geography and maps learning. The main tasks to perform would be:

* Extend the thematic maps editor plugin to allow to create tests and educational games.

* Extend the thematic maps viewer plugin to play tests and educational games created through the previous plugin.

* Add support for some types of tests and games like:

** Localization of place names through the selection of geographic shapes.

** Localization of geographic shapes through the selection of place names.

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