Edit QGIS Plugin Rev2

1. Script 1: Generate layers: Generate standardized layers before the user connects the vertices, with pre-defined fields and styles (points, lines and polygons). 2. Script 2: Import points: read from the raw table of GPS points collected in the field, with transformation of the data into a vector layer (shapefile) of georeferenced points. Note: it is necessary to determine the type of point: (m = milestone, p = point, v = virtual) for future filters by attributes. 3. Script 3: Define limits: The script opens the editing of the line type layer and activates the add function (a facility for lay beginners). Here the user will click on the vertices, of the point layer imported in script 2. 4. Script 4: Generate perimeters: generate polygons from the vertices generated in Script 2 or lines generated manually by the user connecting the vertices. The vertices of the polygon will be ordered from the most northerly point and oriented clockwise. Verification and removal of duplicate vertices will be performed. After the polygons are generated, the user will manually fill in the property data fields that each generated polygon represents, and will also manually create confronting lines in an additional layer, when necessary. 5. Script 5: generate memorial: the plugin should fill in the field of "confrontants" of pre-existing polygons (generated in Script 3), from neighborhood analysis as well as fill in the vertex data from the point layer, inserting fields. For each line connecting 2 vertices of a polygon, the information of the confrontant will be filled in as follows (in order of priority): A. The. with the data of the polygon that has a segment (edge) in common with the line or B. with the line data drawn manually by the user and that is concomitant with the segment connecting the vertices. C. If no pre-defined polygons or confronting lines are found, the field will be left empty. 6. Script 6: generate ods spreadsheet: cross layers of the polygons of interest and facing and export spreadsheet (ods, txt, csv) with information from each vertex (one tab per polygon): A. GPS data (read in Script 2): vertex, E / long, sigma E, N / lat, sigma N, H, sigma H, positioning method. B. Property data (filled in manually by the user after executing the Script 3): type of limit, CNS, registration, descriptive. C. Fine adjustment of the vertexes in relation to the GPS reference point layer. 7. Script 7: generate letter of consent: the script will read the data already generated so far and make an individualization for the neighboring side of the parcel 8. Script 8: export the data: export data of layers and points in format (xls, dxf and kml), having options to choose which layers will be exported, being able to be filtered by attributes (vertex type, limit type, etc.) 9. Script 9: import the data: A. of an ods spreadsheet, csv (predefined template), pdf memorial, txt files. B. of a spreadsheet or own txt generated from the plugin itself and generated by another user. 10. Script 10: import sigef: The plugin will connect to the site: [login to view URL] and will download a portion from its code, provided by the user, redesigning it with all the parcel information. 11. Script 11: check overlap: the program will connect through a WFS connection and will check if there is an overlap by downloading the neighboring parcels. 12. Script 12: generate stamp: this option will be to fill in information previously entered by the user in the fields of a stamp of the plant 13. Script 13: check for errors: use native qgis scripts to check duplicate points or even wrongly clicked lines and polygons layers, as the imported vertices will be the reference layer. 14. Script 14: query data: we will create a database with extra information to make it easier to use. 15. Script 15: other functions: I want to implement the checking of municipal limits in the future, importing vector layers from other files or databases. (this is a combined price)