New rules for the Topology Framework in gvSIG Desktop

Project
Title: New rules for the Topology Framework in gvSIG Desktop.

Student: Mauro Carlevaro.

Mentors: Óscar Martínez, Mario Carrera Rodriguez, Alfred de Jager and Francisco Peñarrubia.

Repository: Link to GitHub repository.

Brief Description
A new topology toolbox. This tool will provide a group of integrity rules that will check the validation of the geometries relationship in the data. A new topology data model can be created for each project. This toolbox provide a new set of tools to navigate, find and fix validation errors different from each topology rule. Right now, there are just a few topology rules implemented with a limited actions. This project will analize, implement and optimize a new set of rules that will be incorporated to this framework. This tools can be created in Java or in Jython through the Scripting composer tool.

State of the Project Before GSoC.
Only a few topology rules have been implemented until now, the most of them are still pending to be developed.

The addition that the project bring to the software.
A new set of topology rules for vector datasets validation and fixing is implemented, which improve and expand the existing before.

Deliverables
A new set of topology rules for vector datasets validation/fixing, that will improve and expand the existing one:
 * Must be coincident with.
 * Must be covered by endpoint of.
 * Points must be covered by line.
 * Must be properly inside polygons
 * Contains point.
 * Contains one point.

Pre-Bonding Period (March 25th - April 9th)

 * Set up working environment, choose tools to be used in the project and set up repository.
 * Familiarize more deeply with the community.
 * Review and learn as much as possible about Python, Jython and Java.
 * Test the topology plugin and study the code of some rules that are already made.

Community Bonding Period (May 6th - May 27th)

 * Familiarize more deeply with the code, with the mentors of the project and with the documentation.
 * Study the Topology Framework API.
 * Study the algorithm for a correct implementation according to the established rules.
 * Set up the development environment.
 * Interact with mentors, introduce myself to the community and actively get involved in the discussion.
 * Set up the wiki page to keep track of weekly progress.
 * Introduce myself and the project on OSGeo's SOC mailing list.
 * Improve in the creation of scripts

First Evaluation Period (May 27th - June 23rd)
√ Define all the required, all the corresponding Classes and Objects. √ Define the interactions. √ Topological rule: Must be coincident with. √ Weekly report.
 * Week 1 (May 27th - June 2nd)

√ Topological rule: [https://github.com/Maureque/TopologyRuleMustBeCoincidentWithPoint Must be coincident with. Topological rule integration with the topology framework.] √ Test and debug the developed code. √ Weekly report.
 * Week 2 (June 3rd - June 9th)

√ Study of the rule. Complete analysis of names, descriptions, solution to be performed, actions, solution per action and all the requeriments following the steps established in the document: Topology Rules for gvSIG Desktop: Development guide. √ Topological rule: Must be covered by endpoint of. File structure to perform the integration with the topology framework. √ Test and document more thoroughly. √ Weekly report. √ Topological rule: [https://github.com/Maureque/TopologyRuleMustBeCoveredByEndpointOfPoint Must be covered by endpoint of. Code developed.] √ Test and debug the developed code. √ Document the entire process. √ Weekly report.
 * Week 3 (June 10th - June 16th)
 * Week 4 (June 17th - June 23rd)

June 24th (beginning)- June 28th (deadline).

 * √ Submit Evaluations.

Second Evaluation Period (June 24th - July 21st)
√ Study of the rule. Complete analysis of names, descriptions, solution to be performed, actions, solution per action and all the requirements following the steps established in the document: Topology Rules for gvSIG Desktop: Development guide. √ Topological rule: Points must be covered by line. √ Add in the rule of week 1: Must be coincident with, the corresponding study to work with multipoint layers. √ Test and debug the developed code. √ Document the entire process. √ Weekly report.
 * Week 5 (June 24th - June 30th)

√ Topological rule: Points must be covered by line. - Optimize algorithms. √ Test and debug the developed code. √ Improve documentation explaining how the rules work when the layers are multipart. √ In-depth study of the code, and implementation with multipart geometries. √ Implementation study with 2D, 2DM and 3D geometries. √ Document the entire process. √ Weekly report.
 * Week 6 (July 1st - July 7th)

- Study of the rule. Complete analysis of names, descriptions, solution to be performed, actions, solution per action and all the requirements following the steps established in the document: Topology Rules for gvSIG Desktop: Development guide. - Topological rule: Must be properly inside polygons. - Optimize algorithms. - Test and debug the developed code. - Document the entire process. - Weekly report.
 * Week 7 (July 8th - July 14th)

- Topological rule: Must be properly inside polygons. - Test and debug the developed code. - Document the entire process. - Weekly report.
 * Week 8 (July 15th - July 21st)

July 22nd (beginning)- July 26th (deadline).

 * Submit Evaluations.

Third Evaluation Period (July 22nd - August 18th)
- Study of the rule. Complete analysis of names, descriptions, solution to be performed, actions, solution per action and all the requeriments following the steps established in the document: Topology Rules for gvSIG Desktop: Development guide. - Topological rule: Contains point. - Test, debug and improve the developed code. - Document the entire process. - Weekly report.
 * Week 9 (July 22nd - July 28th)

- Study of the rule. Complete analysis of names, descriptions, solution to be performed, actions, solution per action and all the requeriments following the steps established in the document: Topology Rules for gvSIG Desktop: Development guide. - Topological rule: Contains point. - Topological rule: Contains one point. - Test, debug and improve the developed code. - Document the entire process. - Weekly report.
 * Week 10 (July 29th - August 4th)

- Topological rule: Contains one point. - Make further changes in the code to improve the functionality. - Improve existing documentation. - Weekly report.
 * Week 11 (August 5th - August 11th)

- Make further changes in the code to improve the functionality. - Improve existing documentation. - Weekly report.
 * Week 12 (August 12th - August 18th)

- Submit Final work product and evaluations.
 * August 19th (beginning)- August 26th (deadline).

Weekly Reports
Section for listing the links to the weekly reports.
 * COMMUNITY BONDING PERIOD (May 6th – May 27th).
 * Report Week 1 (May 27th to June 2nd).
 * Report Week 2 (June 3rd to June 9th).
 * Report Week 3 (June 10th to June 16th).
 * Report Week 4 (June 17th to June 23rd).
 * Report Week 5 (June 24th to June 30th).
 * Report Week 6 (July 1st to July 7th).
 * Report Week 7 (July 8th to July 14th).
 * Report Week 8 (July 15th to July 21st).
 * Report Week 9 (July 22nd to July 28th).
 * Report Week 10 (July 29th to August 4th).
 * Report Week 11 (August 5th to August 11th).
 * Report Week 12 (August 12th to August 18th).

Testing Plan
The objective of the Testing Plan is to find errors from early stages of development. To achieve this, the development it is tested in each sprint, therefore, it will be carried out throughout the development of the project. At the end of each sprint a test version of the project is available.

Tests will be carried out with different types of amounts, features and entities in the layers.

White box and black box testing were carried out.

Black box. The study is carried out from the point of view of the inputs and outputs. The internal structure, design and implementation of the item being tested is not known to the tester.

White box. The purpose is to check the execution flows in each unit. The tester chooses different input values to examine the possible execution flows and make sure that the correct output values are returned. It is a method of software testing that tests internal structures.

The tests provide valuable information to define the quality of the product in each sprint and check which ones must be fixed.

Student Information
Country: Uruguay

School and Degree:
 * Technological University (UTEC, Fray Bentos, Uruguay), Student of Bachelor of IT (2019-2022).
 * University of Engineering (ORT, Montevideo, Uruguay), Programmer Analyst (2014-2018).
 * University of Engineering (UdelaR, Montevideo, Uruguay), Cartographic Technician (2013-2016).

Computing experience
I have been working as a web developer and implementing geographic information systems. The technologies that i work with daily are: Java, Python, MySQL, PostgreSQL/PostGIS, Apache Tomcat and GeoServer.

GIS experience as a user
I have experience using gvSIG and QGIS. Thematic cartography course (Uruguay edition), dictated by The National Geographic Institute and the National Geographic Information Center of Spain. 40 hours duration. Participation in the webinar “gvSIG applied to wildlife and protected natural spaces", on October 14, 2014, made by MundoGEO and Asociación gvSIG, with 60 minutes duration.

GIS programming

 * Colombana, Carlos. 5th gvSIG Uruguay Conference. Material of the lecture and workshop "Scripting: Exprimiendo / Extendiendo gvSIG", 2018. [online]. Available: http://www.gvsig.com/es/eventos/jornadas-uruguay/2018/comunicaciones/-/asset_publisher/zAf8UO2Aurwr/content/taller-2-scripting-exprimiendo-extendiendo-gvsig?
 * Scripting in gvSIG. I learned about scripting studying the material of the “Introduction to Scripting in gvSIG 2.1” (2014 ed.) MOOC, this course was offered by the gvSIG Association. This course was useful for me as started point to continue practicing. Available: https://blog.gvsig.org/2014/10/30/curso-introduccion-a-scripting-en-gvsig-2-1-en-espanol-gratuito/