Difference between revisions of "GvSIG GSoC 2010 Ideas"

From OSGeo
Jump to navigation Jump to search
Line 5: Line 5:
 
Proposed mentor: [[User:fpenarru | Francisco José Peñarrubia]]
 
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. The idea is to define pipes, wells, valvels 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 ''.
+
* '''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 ''.
  
 
== gvSIG Mobile ==
 
== gvSIG Mobile ==

Revision as of 03:31, 24 March 2010

gvSIG Desktop

Proposed mentor: 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 .

gvSIG Mobile

gvSIG Mini

Proposed mentor: Alberto Romeu

gvSIG Mini is a free mobile map viewer of several layers sources (OSM, WMS, WMS-c) which at the moment is able to consume YOURS routing service and NameFinder service (also weather, twitter services, etc.).

gvSIG Mini is currently being developed by 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!