CWRS DigiPhase Leiras

7/28/2019 CWRS DigiPhase Leiras

1/20

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

11

CWRS DigiPhase Extension under ARC GIS

Contents:

1 The tasks of the application.......................................................................................................... 12 Setting the CWRS DigiPhase Extension and logging in ........ ......... .......... ........... ........... ......... ..... 1

2.1 Installing, and starting to use ................................................................................................. 23 Tools and their use ....................................................................................................................... 44 Steps of the work in summary ...................................................................................................... 75 Error and obvious error (OE) codes used...................................................................................... 76 Digitising the parcels, or QC of already digitized parcels ......... .......... .......... ......... .......... .......... . 11

6.1 Some special cases appeard during digitising......... .......... ........... ......... ......... ........... ......... ... 117 Linking the digitized parcels to the claim data.......... ......... ........... ........... ......... .......... .......... ...... 11

7.1 Some special cases appeard during linking .......................................................................... 138 Cases and examples of the block maps and the farmers parcel drawings....... ......... .......... .......... . 13

1 The tasks of the applicationThis application is made for digitizing the parcels from the blokmaps attached to the area aidclaims, linking the polygons to the claim data and finding and coding the anomalies and obviouserrors found.The input data are:

The block maps of the farmers, scanned, as part of the claim, with the drawings of theparcels. 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 theusers. Received_Map_Files table used for registering the scanned blockmap images.


2/20



22

Digitized_Declared_Parcels_curent table the feature class used for registering the declaredparcels. AR_ZABRANI blockmap of the test data.

The Received_Map_Files table contains the links of the scanned and rectified blockmaps with theparcels drawing on them. The links must be valid, to be able to work with the extension. Aftercoping 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.batDigiPhaseExtension.regUninstallDigiPhase.regCWRSenv.regDigiPhaseExtension.dll

Starting the INSTALL.bat will complete all the registration procedure. The user only has to say OKfor the question asked.

The installing process create 3 environmental variable:APIA_CATALOG - the name of the APIA databaseCWRS_CATALOG - the name of the CWRS databaseCWRS_PROVIDER - the name of the SQL Server instance

In the CWRSenv.reg file the administrator can modify this values before the installation. Modifyonly the red characters!!!

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\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 makesthat in the System dialog's advanced tab.

After the installation you must restart the computer!


3/20



33

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 theArcGIS extension, and the components. This bat file use the information of theUninstallDigiPhase.reg file.

To use the extension you should set after the installation process in the Tools menu / Extensions theCwRS DigiPhase Extension.

To click in and out the toolbar is possible in the Customize window. The toolbar can not bereached, 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


4/20



44

waste of time to build it up again and again.


5/20



55

3 Tools and their useThe 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 bechanged 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) loadingautomatically, 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 sameMapFile_IDs in the parcel table. In linking phase: if you select a parcel, the program colors (lightblue) that MapID cells in the parcel table, which parcels get the same mapID.


6/20



66

Yellow = always means some kind of selectionyellow 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 isvisible 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 1 st image related to that is uploaded andzoomed into the middle of the window automatically.

2.DigiPhase BackMap Control tool: if a block is processed, the next image is automaticallydownloaded 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 newparcel, 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. Theimages (scanned blockmaps) related to the CRF are listed in the table on the bottom. To follow withthe work of the blocks is a one direction procedure but you can step back if it is needed.

After choosing a CRF, the 1 st 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 BackMapTool.

5.

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

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


7/20



77

area in the dockable window.After setting the values, and pushing the Apply, the values are written into the record of the editedpolygon. Saving is done at stop editing, as the user chooses it. Undo/Redo can't be used for sketchand attribute editing When you stop the editing a query message appears, and you can select savingor cancelling the edits.

Only one character can be set into the Subparcel filed, one from the standard English 25, no specialcharacters 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 isdeleted with pressing the null in the right upper corner of the attribute setting palette. After this, anew attribute can be set.

In case of obvious error codes: OBV1, OBV2 or OBV3 the SIRSUP And the PB ID can bechanged, 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 usethe REFRESH PARCEL button. Do not forget this else the parcel might not be linked, because itis 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.


8/20



88

7.Stop Editing: closing the editing session. Save Edits from the Editor menu can be, andrecommended to be used. Maybe it should be automatic with certain timing! Closing editing closesautomatically 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 + LINKING1. logging in, opening the 1 st map of the farmer (the application lists the CRFs in the combobox, 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 thedatabase.. shortly the versioning should be switched off. In the Edit/target the targetedediting layer should be set, if it is not saved in the mxd, save it. You can start editing if theeditor toolbar is opened.3. digitizing the polygon4. capturing the attributes: parcel, sub parcel, sketch error code (if needed, the no is the defaultvalue), 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 thesketch error code and the remark, and after these DIGI OK. If any correction is needed, editingis 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 theNEXT, 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 lastlinked row will remain with yellow color on the last records.9. RECORD LINKING link the records manually, witch could not been linkedautomatically. These for sure has some problem, so correct the parcel or sub parcel number orthe 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 MISSINGPARCEL.10. FINISH CRF, if the CRF is completed, and can be deleted from your list. It goes for theCAPI. If you push the NEXT the CRF will be kept assigned to you, and you can look back to it.The 1 st 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 theparcel + sub parcel number, a manual link will be made, or the data is wrong, so no link can beallocated.The CwRS contractor is not obliged to correct the data, only in certain cases witch we call OE. Inall 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.


9/20



99

SKETCHfield

Coduri refereitoare la schitahartii blocurilor fizice

OBV_LPIS Eroare evident corectat cu

date LPISLimitele parcelei nu sunt intotalitate desenate de fermier,dar cu limitele blocului se poatedesena o parcela agricoladeplina, iar numarul este bun.

Obvious error corrected with SIPA data

by the interpretaor. The boundary of theparcel is not totally drawn by thefarmer, but the block boundary makes ita full agricultural parcel, and thenumber is OK.

EPN Eroare num r parcel Numarul parcelei nu este lizibil sau nu poate fi inteles in totalitate, se ia numarul care este legat de parcela.

Error parcel number and/or cropcode The parcel number is not readable,or not exisiting, or not clearlyunderstandable which number is relatedto the parcel.

MPN Lips

num

r parcel

Nu exista numarul parcelei care sa faca legatura cu parcela.

Missing parcel number and/or cropcode There is no parcel number relatedto the parcel.

PBM Lips parte din parcel dincauza terminarii hrii bloculuiParcela care este legata in modcorect cu datele din cerere, cuun numar si un cod de culturabun, dar schita nu e completapentru ca blocul sau suprafatatotala a parcelei nu este vizibila

pe harta cu blocurile fizice.

Missing part of the parcel because theend of the block map Parcel which isOK as linking to the claim data, havingan OK parcel number and crop code, butthe drawing is not complete because thefull block or the full area is not visibleon the block map.

EAP Parcel agricol gre it Nu sunt clare limitele parcelelor,desenele nu contin o suprafata continua care poate fi o singura cultura.

Erroneous agricultural parcel Notunderstandable parcel boundaries, thedrawing are not formulating acontinuous area, which can be a singlecrop.

E1 Orice alt problem referitoarela desen, care nu sunt definite incazurile anterioare. Observatii siexplicatii scrise sunt necesare inacest caz.

Any other kind of drawing problem,which are not defined above .Writtenobservation and explanation isnecessary in this case.

E1_SAPS Subparcelele cu refereire la o singuraparcela SAPS nu sunt adiacente:numerotarea subparcelelor nu estecorecta, ar trebui sa aiba numerediferite pt parcela. (ex 1a nu este lipitade 1b, corect ar fi 1a si 2a).

the different sub parcels related to oneSAPS parcel are not continuous, so theparcel numbering is not correct, itshould have different parcel numbers.


10/20



11

E1_cir Numarul de bloc fizic este incercuit decatre fermier, cu semnificatia ca iiapartine intregul bloc (fermierii au fostsfatuiti sa procedeze astfel). In acestcaz, la digitizare se copiaza limitablocului izic.

The block ID was circled by the farmer,clearly meaning that he claimed the fullblock (because the farmers were advisedlike that) . The digitizer copies theboundary of the PB.

E1_X Nu exista nici o limita desenata ce saingradeasca o parcela, in schimb,pozitia parcelei este marcata cu un X,iar numarul de parcela si cel al bloculuifizic sunt corespunzatoare. Sedigitizeaza un poligon ce sa incadrezeX-ul si se aplica codul E1X.

There is no parcel boundary digitized,but an X shows the position of theparcel and the parcel and block ID isOK. Small square is digitized around theX + the E1X code.

E2_nob Parcela este desenata intr-o zonaunde nu exista nici un bloc fizic indatele SIPA.

the parcel is drawn in an area where noPB is existing in the SIPA data with theblock ID

ASS.field

Coduri referitoare la asociereacu schita cererii de sprijin

OBV1 Erori evidente 1Lips numr parcel pe harta deblocuri, in cazul in care doar unnumar lipseste pe harta si parcelapoate fi doar una dintre parcelelelistate in cerere nefiind posibilanici o alta solutie.

Obvious error 1 Missing parcelnumber on the map, in case only onenumber is missing on the map, and theparcel can only be one parcel amongthe parcels listed in the claim, no otherpossible solution occurs.

OBV2 Erori evidente 2Lipseste ID-ul blocului sau acestanu este total vizibil pe harta, darse regaseste in cerere si parcelapoate fi doar o singura parceladin cerere, nefiind posibila nici oalta solutie.

Obvious error 2 There is no block ID,or the block ID is not fully visible inthe map, but the block ID is existingin the SIPA and in the claim data, andthe parcel can only be one parcel inthe claim, no other possible solutionoccurs.


11/20



11

OBV3 Erori evidente 3Erori care nu apar mai sus, darpot fi corectate cu o solutie clarasi unica. Observatii si explicatiiscrise sunt necesare in acest cazExemple:Parcela poate fi localizata pebaza suprafetei din cerere sau cuimaginile orto, care arata limiteleparcelei, chiar daca ele nu au fostdesenate de fermier. In acest caznu pot exista diferente mai maride 20% in ceea ce privestesuprafata ce apare in cerere fatade suprafata determinata folosindimaginea orto.

Suprafata parcelei este exact lafel ca si suprafata neta a bloculuisi este o singura parcela in bloc,chiar daca limitele nu au fostdesenate.

Obvious error 3 Errors not describedabove, but can be corrected with aclear, one-way solution. Writtenobservation and explanation isnecessary in this case. Examples: heparcel can be located based on thearea claimed and with the orthoimage, which shows the parcelboundary, even the parcel boundary isnot drawn by the farmer. In this casethere can not be more then 20%difference between the area of theparcel on the claim and the area on theortho image. The area of the parcel isexactly the same as the net area of theblock, and there is only one parcel in

the block, even the boundary is notdrawn.

MP Parcel lips :Nu exist pe hart nici un desende parcel n leg tur cu dateledin cerere.

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

P+ Parcel extra:Desen clar de parcel , fr leg tur cu date din cerere.

Extra parcel Parcel drawing, which isunderstandable, but having no claimdata related.THE PARCEL IS NOT LINKED

E2 Orice alt problem referitoare laleg tura dintre datele din cerere i poligoanele digitizate aleparcelelor, altele dect celedefinite mai sus. n acest caz suntnecesare observaii i explicaiiscrise

Any other kind of problem, linkingthe claim data to the digitized parcelpolygons, which are not definedabove. Written observation andexplanation is necessary in this case.In case of E2 THE PARCEL ISNOT LINKED! If you can find thelink, the OBV3 should be applied.

E1_crop Numarul parcelei (numarulparcelei+ codul subparcelei) esteutilizat de doua sau mai multe oriin cerere, deci nu poate fi facutanici o legatura intre cerere siparcela.

the parcel number: parcel number +subparcel code is used twice or morein the claim, so no clear link can bemade between the claim data and theparcel sketchTHE PARCEL IS NOT LINKED


12/20



11

E2_block Parcela este desenata in alt blocfizic decat cel specificat indeclaratie; sau numarul de blocfizic lipseste din declaratie.

the parcel is drawn in an other PBthen it is in the claim, or the block IDis missing from the claimTHE PARCEL IS LINKED, butbefore changing the PB ID to theright one, it can not be processed inthe right PB during the CAPI phase

6 Digitising the parcels, or QC of already digitized parcelsThis phase can be the initial to start with, a correction during the linking phase, or a change isnecessary 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 bedigitized again, at the step of the roght CRF they belong to.

7 Linking the digitized parcels to the claim dataThe 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 andthe SIPA data any modification is possible, so the link can be created. This will lead to somekind of OE codes.

If the user starts linking (automatic or record linking) the application check the values of each claimrecord, and not link that records which are not contain any of SIRSUP, block, parcel, subparcelvalues.If you started the "Linking", you can't select different Map by clicking on an element of MapTableor using the Back, or Next arrows on the button bar. If you select a digitized parcel the Map will beselected automatically.


13/20



11

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 theOperatorCRFAssignement 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, theapplication 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"tstart 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 digitizedo 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 inthe shape file


14/20



11

The green color symbolizes in the MapDigiStatus column if the Maps are completed or not. Theyellow 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 1 st 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 parcelstable, with light blue in the block column. If the given parcel can not be seen in the part of the tableactually 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 markedwith 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 1 st Sirsup column the actually selected record. Records selected with yellow in


15/20



11

the last column was selected in the previous selection. This can help the reconstruction of theprevious 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 MissingParcel, 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, andthen 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, andthe parcel can be linked only manually. If you link it manually, the parcel and/or subparcel shouldnot 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, 1 st check the SYPSUP form theblockmap, and the PB ID. If it does not fot to the claim data, give E2_block code to the parcel, andlink it to the right parcel and sub parcel ID, if that one is unique in the claim. These erroneousparcels will not be found in the block during the CAPI, so they will get an outside the block codeduring the CAPI phase.3 IF the PB number is correct, and only one parcel is existing in the PB, even not clear parceland/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 maptable 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 apolygon, witch has already a linked parcel.


16/20



11

9 Cases and examples of the block maps and the farmersparcel drawings

CASE 1:

The farmer made a drawing on an area of the block map, where no nominated (with ID) physicalblock is existing.

APPLIED SOLUTION: The drawing of the agricultural parcel is valid, we digitize it if the parcelID 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 theproject.

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 berecounted 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 claimdatabase.

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 isOK, 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 WRONGIMAGE NAME button-

CASE 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:


17/20



11

The farmer made his drawing on blockmap, witch was copied from an already used map withthe drawing of an other farmer. It is visible, because the 1 st farmers drawing is black&white,the actual ones are red, and the parcel number of the 1 st one is masked out.

APPLIED SOLUTION: Only work with the red ones, digitize it, and do not do anything with theother 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 anOE, if it is the only problematic parcel of the farmer.


18/20



11

APPLIED SOLUTION: Code: EPN Error parcel number and/or crop code The parcelnumber is not readable, or not exisiting, or not clearly understandable which number isrelated 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:


19/20



11

APPLIED SOLUTION: Digitize the the 7A and 7B : code E1_SAPS: the diffrent subparcelsrelated 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, theparcels 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/orcrop 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, sono ID or any relation to surrounding an area.


20/20



CASE 11:

One or 2 parcels????

APPLIED SOLUTION: Because the line, dividing the drawing to 2 parcels is not cut, we take it asan 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.

CWRS DigiPhase Leiras

Documents

Transcript of CWRS DigiPhase Leiras