CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd

d 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

CWRS DigiPhase Extension under ARC GIS

Contents:
1 The tasks of the application .......................................................................................................... 1 2 Setting the CWRS DigiPhase Extension and logging in ............................................................... 1 2.1 Installing, and starting to use ................................................................................................. 2 3 Tools and their use ....................................................................................................................... 4 4 Steps of the work in summary ...................................................................................................... 7 5 Error and obvious error (OE) codes used...................................................................................... 7 6 Digitising the parcels, or QC of already digitized parcels ........................................................... 11 6.1 Some special cases appeard during digitising....................................................................... 11 7 Linking the digitized parcels to the claim data............................................................................ 11 7.1 Some special cases appeard during linking .......................................................................... 13 8 Cases and examples of the block maps and the farmers parcel drawings..................................... 13

1 The tasks of the application

This application is made for digitizing the parcels from the blokmaps attached to the area aid claims, linking the polygons to the claim data and finding and coding the anomalies and obvious errors found. The input data are: The block maps of the farmers, scanned, as part of the claim, with the drawings of the parcels. The digital claim data. You can find the living discussion here: http://www.gauss.ro:10012/CAPIFORUM/ please use the topic dedicated for the digi phase questions: questions in the method and the use of the error codes, and the SW bogs are in a separated topic.

2 Setting the CWRS DigiPhase Extension and logging in

The files required for using the extension are located in the sample geodatabase: OperatorDigiAssignment table used for registering the work packages distributed to the users. Received_Map_Files table used for registering the scanned blockmap images.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc Digitized_Declared_Parcels_curent table the feature class used for registering the declared parcels. AR_ZABRANI blockmap of the test data.

The Received_Map_Files table contains the links of the scanned and rectified blockmaps with the parcels drawing on them. The links must be valid, to be able to work with the extension. After coping the images to a directory, with the given directory structure, the actual path should be set. There is only one test operator in the OperatorDigiAssignment stable: operator1 try with that.

2.1

Installing, and starting to use

The isnstallation kit contains 5 files: _INSTALL.bat _UNINSTALL.bat DigiPhaseExtension.reg UninstallDigiPhase.reg CWRSenv.reg DigiPhaseExtension.dll Starting the INSTALL.bat will complete all the registration procedure. The user only has to say OK for the question asked. The installing process create 3 environmental variable: APIA_CATALOG - the name of the APIA database CWRS_CATALOG - the name of the CWRS database CWRS_PROVIDER - the name of the SQL Server instance In the CWRSenv.reg file the administrator can modify this values before the installation. Modify only the red characters!!!

REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "APIA_CATALOG"="APIA_DB" "CWRS_CATALOG"="CWRS07_SCT" "CWRS_PROVIDER"="SERVERBD2OLD\\SQLSERVER2005

The administrator can modify the environmental variables after the installation too. He can makes that in the System dialog's advanced tab. After the installation you must restart the computer! 2

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

The DigiPhaseExtension.reg contains information needs for the registration of ArcGIS components. This file mustn't be modified! The package contains the _UNINSTALL.bat file. You can start it if you want to uninstall the ArcGIS extension, and the components. This bat file use the information of the UninstallDigiPhase.reg file. To use the extension you should set after the installation process in the Tools menu / Extensions the CwRS DigiPhase Extension.

To click in and out the toolbar is possible in the Customize window. The toolbar can not be reached, until the extension is not clicked in.

Saving the the MapDokumentum- mxd is making the workflow management more convenient. If the necessary files had been already uploaded it is better to safe by the user in an mxd, because is a 3

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc waste of time to build it up again and again.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

3 Tools and their use

The application uses a Toolbar, and a communication window inserted into a Dockable Windowba, witch can be adjusted from the Toolbar. Toolbar:

The numbers in the dockable window are the farmer registry numbers (CRF). The CERf can be changed here. You can move between the maps of a farmer with the use of the < > arrows. As logging in the application and the first CRF's first map (and the CRF's connected data) loading automatically, and displaying.When you do a logging in the application, that select all the CRFs, which are denoted to you, the program automatically select the first and open that one. Dialog:

In digitizing phase: if you select a Map, the program colors ( light blue), the cells of the same MapFile_IDs in the parcel table. In linking phase: if you select a parcel, the program colors (light blue) that MapID cells in the parcel table, which parcels get the same mapID.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc Yellow = always means some kind of selection yellow Select the 1st column: always means select, and the value is the one selected for use. yellow select in last column: the parcel was in work last time. blue in the left table = information about parcels in the same block blue in the right table = claim record that contains missing parcel value 1. Little man icon: for setting the user, after that the CRF list selected for that particular user is visible in the combo box next to. No other user could be set like defined in the SDE connection. After setting the user (logging in ) the first CRF, and the 1st image related to that is uploaded and zoomed into the middle of the window automatically. 2. DigiPhase BackMap Control tool: if a block is processed, the next image is automatically downloaded and zoomed into the middle with this tool. If you zoomed into the image, before jumping to the next one, this tool zooms to the actual image in full central view again, to be able to check, if there is any parcel not digitized yet. The block ID is changing, when the new map appears, and stays until the Next or the Back map jumping. When the user edited the attributes of a new parcel, but the changes wasn't Apply, the BackMap and the NextMap tools are disabled. 3. Scrolling list, the Combo: choose the CRF you want to work with from the scrolling list. The images (scanned blockmaps) related to the CRF are listed in the table on the bottom. To follow with the work of the blocks is a one direction procedure but you can step back if it is needed. After choosing a CRF, the 1st image related to the CRF is uploaded and zoomed into the middle of it automatically. 4. DigiPhase NextMap Control tool: the explanation of this tool is readable at the 2-nd BackMap Tool.

5. Start Editing: start the editing process. Same as the Start Editing in the standard Editor toolset, witch one is a living possibility as well. If only the standard files are uploaded, you do not need to set editing area, but in case other feature classes are in the mxd, you must set for workspace the data you work on (setting the Target feature class).

6. DigiPhase Sketch Tool: normal polygon editing tools. After closing the edit session of a polygon with a double click, the attribute communication panel is activated. It is created on the left-lower 6

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc area in the dockable window. After setting the values, and pushing the Apply, the values are written into the record of the edited polygon. Saving is done at stop editing, as the user chooses it. Undo/Redo can't be used for sketch and attribute editing When you stop the editing a query message appears, and you can select saving or cancelling the edits. Only one character can be set into the Subparcel filed, one from the standard English 25, no special characters and no numbers. Only numbers are accepted into the Parcel field. If the code set in the code list is not good, and the operator wants to change it, the previous record is deleted with pressing the null in the right upper corner of the attribute setting palette. After this, a new attribute can be set. In case of obvious error codes: OBV1, OBV2 or OBV3 the SIRSUP And the PB ID can be changed, but both are compulsory. In case of codes EPN and MPN the Association code and/or the Sketch code can be empty. The application automatically sets the target layer (DDPC). If a parcel is digitized, or deleted use the REFRESH PARCEL button. Do not forget this else the parcel might not be linked, because it is not on the table appearing. The user can not be editing a new parcel before the saving attributes.

The Apply command lock the dialog box until creating a new parcel polygon.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc 7. Stop Editing: closing the editing session. Save Edits from the Editor menu can be, and recommended to be used. Maybe it should be automatic with certain timing! Closing editing closes automatically the attribute communication window. 8. Add Data button: the regular Add Data, but faster to reach from here.

4 Steps of the work in summary

DIGITIZING + LINKING 1. logging in, opening the 1st map of the farmer (the application lists the CRFs in the combo box, on the DigiPhase toolbar, and opening the first) 2. start editing with the digi toolbar In the Editor menu/options the Edit a version of the database.. shortly the versioning should be switched off. In the Edit/target the targeted editing layer should be set, if it is not saved in the mxd, save it. You can start editing if the editor toolbar is opened. 3. digitizing the polygon 4. capturing the attributes: parcel, sub parcel, sketch error code (if needed, the no is the default value), remark (only if needed) 5. APPLY Deleting a parcel: selecting by the regular select feature tool and delete. Operator must use the 'Refresh parcels' button (under the parcel table) after deleting a parcel! 6. DIGI OK in case the digitization was already done, controlling the boundary, adding the sketch error code and the remark, and after these DIGI OK. If any correction is needed, editing is possible with the BACK TO FALSE. If the polygon needs a change, start editing + digitizing + stop editing. In the editing mode the attributes of the parcels can not be changed. 7. START LINKING, if no claim data is available, push the FINISH CRF, if you use the NEXT, the CRF will be kept assigned to you, and you can look back to it. 8. AUTOMATED LINKING all the linked data will be colored with green, and the last linked row will remain with yellow color on the last records. 9. RECORD LINKING link the records manually, witch could not been linked automatically. These for sure has some problem, so correct the parcel or sub parcel number or the block ID as obvious error, if possible, and then link it manually, or start again the automatic, if not possible, assign the error code. If the claim data has no parcel, push the MISSING PARCEL. 10. FINISH CRF, if the CRF is completed, and can be deleted from your list. It goes for the CAPI. If you push the NEXT the CRF will be kept assigned to you, and you can look back to it. The 1st block map of the next CRF will be loaded into.

5 Error and obvious error (OE) codes used

In case of parcels, witch are not linked automatically to the claim row based on the block ID and the parcel + sub parcel number, a manual link will be made, or the data is wrong, so no link can be allocated. The CwRS contractor is not obliged to correct the data, only in certain cases witch we call OE. In all the other cases the error codes will show the potential problems of the claim or the block map. OE and the other errors found will be reported to APIA. 8

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

SKETCH field OBV_LPIS

Coduri refereitoare la schita hartii blocurilor fizice Eroare evident corectat cu date LPIS Limitele parcelei nu sunt in totalitate desenate de fermier, dar cu limitele blocului se poate desena o parcela agricola deplina, iar numarul este bun. Eroare numr parcel Numarul parcelei nu este lizibil sau nu poate fi inteles in totalitate, se ia numarul care este legat de parcela. Lips numr parcel Nu exista numarul parcelei care sa faca legatura cu parcela. Lips parte din parcel din cauza terminarii hrii blocului Parcela care este legata in mod corect cu datele din cerere, cu un numar si un cod de cultura bun, dar schita nu e completa pentru ca blocul sau suprafata totala a parcelei nu este vizibila pe harta cu blocurile fizice. Parcel agricol greit Nu sunt clare limitele parcelelor, desenele nu contin o suprafata continua care poate fi o singura cultura. Orice alt problem referitoare la desen, care nu sunt definite in cazurile anterioare. Observatii si explicatii scrise sunt necesare in acest caz.
Subparcelele cu refereire la o singura parcela SAPS nu sunt adiacente: numerotarea subparcelelor nu este corecta, ar trebui sa aiba numere diferite pt parcela. (ex 1a nu este lipita de 1b, corect ar fi 1a si 2a).

Obvious error corrected with SIPA data by the interpretaor. The boundary of the parcel is not totally drawn by the farmer, but the block boundary makes it a full agricultural parcel, and the number is OK. Error parcel number and/or crop code The parcel number is not readable, or not exisiting, or not clearly understandable which number is related to the parcel. Missing parcel number and/or crop code There is no parcel number related to the parcel. Missing part of the parcel because the end of the block map Parcel which is OK as linking to the claim data, having an OK parcel number and crop code, but the drawing is not complete because the full block or the full area is not visible on the block map.

EPN

MPN

PBM

EAP

Erroneous agricultural parcel Not understandable parcel boundaries, the drawing are not formulating a continuous area, which can be a single crop. Any other kind of drawing problem, which are not defined above .Written observation and explanation is necessary in this case. the different sub parcels related to one SAPS parcel are not continuous, so the parcel numbering is not correct, it should have different parcel numbers.

E1

E1_SAPS

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc E1_cir
Numarul de bloc fizic este incercuit de catre fermier, cu semnificatia ca ii apartine intregul bloc (fermierii au fost sfatuiti sa procedeze astfel). In acest caz, la digitizare se copiaza limita blocului izic.

The block ID was circled by the farmer, clearly meaning that he claimed the full block (because the farmers were advised like that) . The digitizer copies the boundary of the PB. There is no parcel boundary digitized, but an X shows the position of the parcel and the parcel and block ID is OK. Small square is digitized around the X + the E1X code. the parcel is drawn in an area where no PB is existing in the SIPA data with the block ID

E1_X

Nu exista nici o limita desenata ce sa ingradeasca o parcela, in schimb, pozitia parcelei este marcata cu un X, iar numarul de parcela si cel al blocului fizic sunt corespunzatoare. Se digitizeaza un poligon ce sa incadreze X-ul si se aplica codul E1X. Parcela este desenata intr-o zona unde nu exista nici un bloc fizic in datele SIPA.

E2_nob

ASS. field OBV1

Coduri referitoare la asocierea cu schita cererii de sprijin Erori evidente 1 Lips numr parcel pe harta de blocuri, in cazul in care doar un numar lipseste pe harta si parcela poate fi doar una dintre parcelele listate in cerere nefiind posibila nici o alta solutie. Erori evidente 2 Lipseste ID-ul blocului sau acesta nu este total vizibil pe harta, dar se regaseste in cerere si parcela poate fi doar o singura parcela din cerere, nefiind posibila nici o alta solutie. Obvious error 1 Missing parcel number on the map, in case only one number is missing on the map, and the parcel can only be one parcel among the parcels listed in the claim, no other possible solution occurs. Obvious error 2 There is no block ID, or the block ID is not fully visible in the map, but the block ID is existing in the SIPA and in the claim data, and the parcel can only be one parcel in the claim, no other possible solution occurs.

OBV2

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc OBV3 Erori evidente 3 Erori care nu apar mai sus, dar pot fi corectate cu o solutie clara si unica. Observatii si explicatii scrise sunt necesare in acest caz Exemple: Parcela poate fi localizata pe baza suprafetei din cerere sau cu imaginile orto, care arata limitele parcelei, chiar daca ele nu au fost desenate de fermier. In acest caz nu pot exista diferente mai mari de 20% in ceea ce priveste suprafata ce apare in cerere fata de suprafata determinata folosind imaginea orto. Suprafata parcelei este exact la fel ca si suprafata neta a blocului si este o singura parcela in bloc, chiar daca limitele nu au fost desenate. Parcel lips: Nu exist pe hart nici un desen de parcel n legtur cu datele din cerere. Parcel extra: Desen clar de parcel, fr legtur cu date din cerere. Obvious error 3 Errors not described above, but can be corrected with a clear, one-way solution. Written observation and explanation is necessary in this case. Examples: he parcel can be located based on the area claimed and with the ortho image, which shows the parcel boundary, even the parcel boundary is not drawn by the farmer. In this case there can not be more then 20% difference between the area of the parcel on the claim and the area on the ortho image. The area of the parcel is exactly the same as the net area of the block, and there is only one parcel in the block, even the boundary is not drawn.

MP

Missing parcel There is no parcel drawing on the map related to the claim data. THE PARCEL IS NOT LINKED

P+

E2

E1_crop

Extra parcel Parcel drawing, which is understandable, but having no claim data related. THE PARCEL IS NOT LINKED Orice alt problem referitoare la Any other kind of problem, linking the claim data to the digitized parcel legtura dintre datele din cerere polygons, which are not defined i poligoanele digitizate ale above. Written observation and parcelelor, altele dect cele definite mai sus. n acest caz sunt explanation is necessary in this case. necesare observaii i explicaii In case of E2 THE PARCEL IS scrise NOT LINKED! If you can find the link, the OBV3 should be applied. the parcel number: parcel number + Numarul parcelei (numarul parcelei+ codul subparcelei) este subparcel code is used twice or more utilizat de doua sau mai multe ori in the claim, so no clear link can be made between the claim data and the in cerere, deci nu poate fi facuta parcel sketch nici o legatura intre cerere si parcela. THE PARCEL IS NOT LINKED

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc E2_block Parcela este desenata in alt bloc fizic decat cel specificat in declaratie; sau numarul de bloc fizic lipseste din declaratie. the parcel is drawn in an other PB then it is in the claim, or the block ID is missing from the claim THE PARCEL IS LINKED, but before changing the PB ID to the right one, it can not be processed in the right PB during the CAPI phase

6 Digitising the parcels, or QC of already digitized parcels

This phase can be the initial to start with, a correction during the linking phase, or a change is necessary in the QC phase. It can be done at any step.

6.1

Some special cases appeard during digitising

1. If no blockmap behind the parcel digitized, delete the parcels, from that CRF, because they are probably related to an other farmer, but the name of the file is not correct. These will be digitized again, at the step of the roght CRF they belong to.

7 Linking the digitized parcels to the claim data

The linking is made on farmer / dossier level, so the declared parcels of one dossier are visible. If all the digitization is good, the parcels will be linked to the claim data. There are 2 ways of managing this link: Automated linking, based on the block ID, that parcel and the sub parcel number Manual linking, can be used all the time, but necessary in case based on the claim data and the SIPA data any modification is possible, so the link can be created. This will lead to some kind of OE codes. If the user starts linking (automatic or record linking) the application check the values of each claim record, and not link that records which are not contain any of SIRSUP, block, parcel, subparcel values. If you started the "Linking", you can't select different Map by clicking on an element of MapTable or using the Back, or Next arrows on the button bar. If you select a digitized parcel the Map will be selected automatically.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

The STOP Linking button (enable the map table, disable the claim tools), the user can do editing, and after the stop edit the start linking can be pushed to continue the linking. If you finish a CRF, you can push the "Finish CRF" button, the CRF will be deleted from the OperatorCRFAssignement table, and reselect the CRF list. After this operation the firsth element of the list opens automatically. In the table on the right hand no edit process is available. You can use the NEXT button along the list of the CRFs, and when you saw the last CRF, the application ask you: "Do you want restart at the beginning?" In case a CRF hasn"t claims the user can Finish the CRF. When a CRF hasn"t claims the user can"t start linking.

DIGI OK / NO DIGI buttons are enabled both, when MapStatus is false: DIGI OK is usable if any parcel is digitized. The DIGI OK"s map tip contains the code from the Digitization field NO DIGI is usable if no any parcel is digitized. If it is pressed, it is possible to give a remark, what is the reason of the nodigi. The reasons can be the followings: o SHITA: if no drawing, no number made by the farmer is available on the map at all. o SCAN: if the scan is erroneous on a way, that the parcel sketches are not visible, so can not be digitized o DUBL: if the pb map is doubled and the parcel was digitized on the other one, put this code to the second image. In case the parcel was digitized on both, delete one of the parcels and put the code to the map. o SIPA: disconcordances between the numbering of the pb on the paper maps and in the shape file

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

The green color symbolizes in the MapDigiStatus column if the Maps are completed or not. The yellow color symbolizes the actual map selected. The meaning of the colors of the declaration table: YELLOW: the current selected record is shown by being yellow in the 1st column, (the SIRSUP). Yellow cells in the column shows, that this record was the one, selected before the actual selection. This can help the reconstruction of the previous action if necessary. BULE: If the user selects a blockmap, the related digitized parcels will be selected in the parcels table, with light blue in the block column. If the given parcel can not be seen in the part of the table actually visible, the window is scrolled automatically to the selected record. GREY: if the MapDigiStatus is true, the parcels related to the finished mapsheet will be marked with grey in the Id_Map column, helping to find the parcels related to the non-finalized map sheets. GREEN: the green color in the ObjectID filed shows the parcels already linked.

Meaning of the colors used in the claim table: YELLOW: shows in 1st Sirsup column the actually selected record. Records selected with yellow in 1

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc the last column was selected in the previous selection. This can help the reconstruction of the previous action if necessary. GREEN: the green color in the Block, Parcel, Subparcel fileds shows the parcels already linked. The polygon Id of the linked polygon (parcel) is seen in the id_ddpc filed. BLUE: parcels in the claim signed with an error code, mening that no parcel was linked, so Missing Parcel, are colored with blue in the Block, Parcel, Subparcel fields.

Tip: If you linked a parcel with manual record linking, and you want to unlink it, press MP, and then link with the one you would like.

7.1

Some special cases appeard during linking

1 In case of "MPN" sketch error, the user can add non-value for parcel and/or subparcel, and the parcel can be linked only manually. If you link it manually, the parcel and/or subparcel should not have to be filled up. It will show, that it was not there ont he map. 2 If the parcel is drawn in another PB, then in the claim, 1st check the SYPSUP form the blockmap, and the PB ID. If it does not fot to the claim data, give E2_block code to the parcel, and link it to the right parcel and sub parcel ID, if that one is unique in the claim. These erroneous parcels will not be found in the block during the CAPI, so they will get an outside the block code during the CAPI phase. 3 IF the PB number is correct, and only one parcel is existing in the PB, even not clear parcel and/or sub-parcel number on the map, it can be linked with an OBV1 code. 4 If the number of parcel do not correspond, no way of linking it. 5 The previously captured attributes, called Georeferencing_notes, Digi_notes are in the map table are visible, if any of this is existing. 6 The P+ and the MPN is automatically deleted, if you link these parcels. 7 In case of APN and MPN the parcel and/or subparcel can be empty = nodata. 8 The double link is not allowed! It is not possible to link a parcel from the claim data to a polygon, witch has already a linked parcel.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

9 Cases and examples of the block maps and the farmers parcel drawings
CASE 1: The farmer made a drawing on an area of the block map, where no nominated (with ID) physical block is existing. APPLIED SOLUTION: The drawing of the agricultural parcel is valid, we digitize it if the parcel ID and the block ID is good, and the data fits to the claim data. The OBV_2 is registered. The parcel is OK, goes for CAPI. Summary report to the APIA + proposal for avoiding the problem is needed at the end of the project. CASE 2: The SAPS parcel is not continuous, so the parcel parcel number is not correct. APPLIED SOLUTION: Digitize both, and give E1_SAPS code to both polygon. Back to APIA for correction, needs a report to generate. The parcel and sub parcel number must be recounted by APIA and changed in the IACS claim database. CASE 3: The parcel number: order number + crop code is used twice or more in the claim, so no clear link can be made between the claim data. APPLIED SOLUTION: E1_crop code: Back to APIA for correction, needs a report to generate. The parcel and sub parcel number must be recounted by APIA and changed in the IACS claim database. CASE 4: Wrong naming convention for the blokmap image files. APPLIED SOLUTION: If the parcel drawing is not in the targeted block, but the in the claim it is OK, and the right block is found in the SIPA data, the parcel is accepted, OBV2 code. If the file is named with the map sheet number, instead of the block ID. Press the WRONG IMAGE NAME buttonCASE 5: Not correct scanning, where part of the block map is missing. APPLIED SOLUTION: Code it, and send it back to APIA where to code? CASE 6: 1

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc The farmer made his drawing on blockmap, witch was copied from an already used map with the drawing of an other farmer. It is visible, because the 1st farmers drawing is black&white, the actual ones are red, and the parcel number of the 1st one is masked out.

APPLIED SOLUTION: Only work with the red ones, digitize it, and do not do anything with the other ones, if it clear, that the actual parcels are with red colors. CASE 7: Maybe a 7??? but basically not readable. By knowing the claim data it can turn to be an OE, if it is the only problematic parcel of the farmer.

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

APPLIED SOLUTION: Code: EPN Error parcel number and/or crop code The parcel number is not readable, or not exisiting, or not clearly understandable which number is related to the parcel. CASE 8: Big mess, not clear boundaries.

APPLIED SOLUTION: This case is accepted, because the 30A is an OK number, not duplicated, and the masked thing seems, that the farmer corrected his wrong numbering. CASE 9: All 3 parcels has an error codes:

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

APPLIED SOLUTION: Digitize the the 7A and 7B : code E1_SAPS: the diffrent subparcels related to one SAPS parcel are not continuous, so the parcel parcel numbering is not correct, it should have different parcel numbers. This case goes back to APIA for correction, the parcels must be recounted by APIA and changed in the IACS claim database. The parcel on the left from 7A will be digitized also + code MPN: Missing parcel number and/or crop code There is no parcel number related to the parcel. this is not an OE, Interpretator gives the code after digitising the parcel, prefixed values, and back to APIA for correction. CASE 10: Only one line, with no connection to any parcel, or number drawn.

APPLIED SOLUTION: Leave it out, until nothing to do with the task they needed to complete, so no ID or any relation to surrounding an area. 1

CwRS Romania 2007 GAUSS Parcel digitisation phase, Manual of the ArcGIS extension, Prepaired by the MSO Ltd 2007/11/12/, 16:11, CWRS_DigiPhase_leiras_v12_en.doc

CASE 11: One or 2 parcels????

APPLIED SOLUTION: Because the line, dividing the drawing to 2 parcels is not cut, we take it as an existing one. Digitise 2 parcels, one is the 19A, and the other gets a code: MPN. It can be an OE, based on the claim data. CASE 12: Boundary, under the correction ink?

APPLIED SOLUTION: Accept it, it is clear, that the number was corrected.