GvSIG GSoC 2014 Ideas

2014-03-20T16:54:51Z

Wiki-Csanchez: /* SHP format support for gvSIG Mini */

Use this page to jot down and develop any good idea for the [[Google Summer of Code 2014]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[GvSIG GSoC 2013 Ideas|2013]], [[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__

== Add OpenCL support with Aparapi for Geoprocessing in gvSIG desktop ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Cèsar Ordiñana
* '''Possible student''': Paula Navarro

[https://code.google.com/p/aparapi/ Aparapi] is a library which allows Java developers to take advantage of the compute power of GPU and APU devices by executing data parallel code fragments on the GPU rather than being confined to the local CPU. It does this by converting Java bytecode to OpenCL at runtime and executing on the GPU, if for any reason Aparapi can't execute on the GPU it will execute in a Java thread pool.

Large amounts of geographic data-processing might be involved in the execution of a geoprocess. And many geoprocessing algorithms are suitable to be converted to parallel code, allowing for much better execution performance and capacity.

The objective would be to integrate the Aparapi library in gvSIG, so it might be used in the development of new parallel geoprocessing algorithms which take advantage of current GPUs. Also some geoprocesses would have to be developed or converted to use the Aparapi library to check the benefits and the proper operation of the idea.

== Port Network Analysis Extension to gvSIG 2.x branch ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': [[User:Fpenarru| Francisco José Peñarrubia]]
* '''Possible students''': David Pinheiro, Vicente Caballero, Sandeep Kumar, Dragos Dragomir

Port gvSIG Network Analysis Extension from 1.12 release to the new 2.x branch.

Network Analysis extension allows to calculate routes, service areas, origin - destination matrices, connectivity analysis... It supports speeds for several vehicles, barriers, turn costs, etc.

Improvement: Use GraphHopper [http://graphhopper.com/] library to use new algorithm Contraction Hierarchies (much faster) when calculating routes.

Skills needed: Java, Eclipse development. Some notions about Maven would be interesting.

== OGR library support for gvSIG Mini ==

* '''Product''': gvSIG Mini
* '''Possible mentor''': Daniel Gastón, Carlos Sánchez
* '''Possible student''': Vanessa Maria Martínez

'''1. Introduction'''

By integrating the OGR library into gvSIG Mini we could get access several vector formats including the widespread SHP, GML, KML format so much demanded by the gvSIG Mini users. OGR offers us the perfect platform to implement demanding format transformations and the corresponding file format outputs as many desktop GIS application already 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 and provide full support to the SHP format. The implementation is intended to be done in a way future formats supports are easily developed.

== Add XLS file format support to gvSIG Desktop 2.x ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Joaquín del Cerro
* '''Possible student''': Manuel Madrid

The management of alphanumeric information contained in tables is a critical question of spatial analysis, but often the desktop GIS applications are not as powerful as a spreadsheet application for this kind of tasks, so having the possibility of transfering data between both types of applications would be very useful.

Microsoft Excel is a poweful and widely used spreadsheet application tradicionaly used by many GIS users for managing alphanumeric data. Unfortunately from the version 2007 on, this application stopped supporting dBase file format (.DBF), which is the most common table file format used by GIS applications.

The idea is about adding to gvSIG Desktop support of XLS file format (Microsoft Excel Spreadsheet) by implementing a new data provider in order to facilitate the data transfer between Microsoft Excel and gvSIG.

The provider will support multiple spreadsheets files reading and mono-spreadsheet files writing.

== Geoprocesses Access from the Scripting Framework in gvSIG Desktop 2.x ==

* '''Product''': gvSIG Desktop
* '''Possible mentor''': Joaquín del Cerro
* '''Possible student''': Óscar Martínez Olmos

Since the last version, you can write your own Python scripts inside gvSIG 2.x using the new Scripting Framework. Now, when you create your script, you have a lot of functions available, but you don't have access to the Geoprocesses that already exist in gvSIG.

The idea is extend the capabilities of this module and create the link between Scripting and Geoprocesses for have access to powerfool tools, who can be even more usefull when you use it inside your own script. ArcPy (ArcGIS) have a similar funcion, with gvsig, you will call one geoprocess in your script with a code similar like this:

Gvsig_Disolve("layer1.shp","AREA",0,0,fields, "C:/gvsig/disolve.shp")

Also, if a have time, i would like to incorporate the option to insert scripts inside the gvSIG Model Builder, you could create greater tasks.

== Idea template ==

* '''Product''': gvSIG Desktop/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 2010 Ideas

2010-03-26T13:57:11Z

Wiki-Csanchez: /* gvSIG Desktop */

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

== gvSIG Mobile ==

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

OSGeo - User contributions [en]

GvSIG GSoC 2014 Ideas

GvSIG GSoC 2010 Ideas