Difference between revisions of "GvSIG GSoC 2011 Ideas"
Jump to navigation
Jump to search
(created stub page for gvSIG GSoC participation for 2011) |
|||
| Line 10: | Line 10: | ||
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 ''. | 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 Mobile == | ||
Revision as of 02:11, 8 February 2011
gvSIG Desktop
Import / Export data from Epanet
Proposed mentor: 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 .
Proposed mentor: 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.