Difference between revisions of "GvSIG GSoC 2013 Ideas"
Wiki-Aromeu (talk | contribs) |
|||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 22: | Line 22: | ||
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. | 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 == | == Add raster format to scripting in gvSIG == | ||
* '''Product''': gvSIG Desktop | * '''Product''': gvSIG Desktop | ||
| − | * '''Possible mentor''': | + | * '''Possible mentor''': |
* '''Possible student''': Sandeep Kumar | * '''Possible student''': Sandeep Kumar | ||
| Line 39: | Line 38: | ||
Extend the algorithm providers of SEXTANTE with GDAL, Orfeo Toolbox, etc. | 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 == | == Idea template == | ||
Latest revision as of 10:59, 2 May 2013
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 2012, 2011, 2010, 2009 ideas pages for examples or reference.
Integrating OGR library into gvSIG Mini
- Product: gvSIG Mini
- Possible mentor: Daniel Gastón
- Possible student: 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: 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: 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. 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, 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.