lot7 - dmt suite - release 20150331

23
7 DMT Suite – New version delivery This document describes the changes to the software. This new version is composed by: A new version of DMT Client version 3.2.2. This program must be installed by the users. New business rules defined and new quality controls applied. These rules were uploaded in the central database and will be automatically downloaded to the local computer when the user will start DMT Agent DMT Client installation procedure (Version 3.2.2) If DMT Client is not already install on the computer, run ‘Installation - DMT2015 Client V3.2.2.exe’ file. If DMT Client is already install (Version 3.1.0), the run ‘Update - DMT2015 Client V3.2.2.exe’ file. New installation procedure, i.e. DMT Client never installed on the computer Double click on file and follow installation procedure. Then, follow procedure describe in the DMT Client user guide in order to create a user (Chapter C1, page 27) and download the points’ sample. Upgrade procedure: Run the following procedure when DMT Client (version 3.1.0) is already installed on your computer. 1. Close DMT Client (version 3.1.0)

Upload: mihai-titanium

Post on 16-Sep-2015

6 views

Category:

Documents


3 download

DESCRIPTION

LOT7 - DMT Suite

TRANSCRIPT

DMT Suite New version delivery

This document describes the changes to the software. This new version is composed by: A new version of DMT Client version 3.2.2. This program must be installed by the users. New business rules defined and new quality controls applied. These rules were uploaded in the central database and will be automatically downloaded to the local computer when the user will start DMT AgentDMT Client installation procedure (Version 3.2.2)

If DMT Client is not already install on the computer, run Installation - DMT2015 Client V3.2.2.exe file. If DMT Client is already install (Version 3.1.0), the run Update - DMT2015 Client V3.2.2.exe file.New installation procedure, i.e. DMT Client never installed on the computerDouble click on file and follow installation procedure.Then, follow procedure describe in the DMT Client user guide in order to create a user (Chapter C1, page 27) and download the points sample.

Upgrade procedure:Run the following procedure when DMT Client (version 3.1.0) is already installed on your computer.1. Close DMT Client (version 3.1.0)2. Double click on file.3. Welcome window displays. Click on Next button

4. Select folder where is installed DMT Client (version 3.1.0). Click on OK button

5. The selected folder is displayed in the Select destination location window. Click on Next button.

6. Ready to install window displays. Click on Install button to start installation process.

7. Installation process is starting.

8. At the end, a final window displays. Click on Finish button.

9. Double click on DMT_Client.accdr file

10. DMT Client opens and the connection window displays. User can see on the bottom of the window the current version of DMT Client installed (3.2.2) and the associated metadata (V1.0.1). The last version of metadata is 1.0.7. Then, user must download the upgrade from the central server. Enter user login and password to connect.

11. Click on Agent button to start DMT Agent tool. DMT Agent starts and automatically requesting to the central server if new version of metadata was installed. Version 1.0.7 of the metadata is automatically downloaded.

12. At the end of the download process, DMT Client automatically detects the file and propose to the user to update the local DMT Client. Click on Yes button.

13. The upgrade process starts. At the end of the process, a confirmation message is displayed. Click on Ok button.

14. Connection window opens and on the bottom of the window is indicated the new version of metadata installed (V1.0.7). User can start data entry. All business rules defined in the version 1.0.7 will be applied during the automatic quality control.

This chapter describes updates related to the new DMT Client version 3.2.2.

DMT Client features Related version 3.2.2

#TypeFeatureDescription

1BugPoint tracking (log)Message was displayed when user was trying to open point tracking window. Corrected

2BugBy pass window: FilteringImpossible to filter by surveyor code. Corrected

3FeatureAdd user from connection windowButton to add a new user (request to the central server) is visible on Connection window. Possibility to initialize several surveyor from one DMT Client

4FeatureSave DMT Version and metadata used When user is saving a point, and running automatic quality control, the DMT Version used and the version of the quality control process is saved for the selected point. Better tracking of quality control, if business rules are updated during the project

5BugManage quality control and export process for a soil tripletImpossible to validate one point of the triplet, if at least an error was detected in one of the three points.

6FeatureQuestionnaire automatically filled-in according specific type of observationWhen user is entering type of observation and entered value is 5, 6 or 7, then not relevant values are filled-in.

7BugDefine DMT Client pathError observed when user was selecting new path is corrected. When functional administrator (CYLET00, CYLEF00, CYLE000) defines a new path, databases are copies in the destination folder. If a user select a new path, DMT Client is trying to connect on the database normally stored in this folder.

8BugUpdate type of additional photo from zoom windowOn write mode, it was not possible to update the type of additional photo when zooming on the photos. Corrected

9BugUnlock code buttonButton was not correctly displayed in some specific cases. Corrected

10FeatureButton resetA button reset was added on the data entry window. When, user clicks on it, questionnaire is re-initialized

11FeatureButton Up and down add in transect list boxClick on up or down buttons to move a transect code in the sequence

12FeatureTracking of quality control processWhen DMT Client is running automatic quality control, list of controls is displayed in the status bar, with the number of errors detected.

13FeatureDaily track not consistent with point locationDMT Client checks if the daily GPS track is in a 5 km radius around the point.

14BugManage photo file size higher than 3 MoPhoto resizer tool crashed DMT Client when loading photo (more than 3Mb). Corrected.

15FeatureAvoid two points registered at the same time by the same surveyorCheck if several points are not registered with the same date and time, for a given surveyor

16FeatureSurvey photo export at XC levelEven if photos were downloaded by XC, when point is exported (after validation) photos will not be transferred to the central server.

17BugClean tracking point table when DMT Client crashedWhen DMT Client crashes during data entry or automatic quality control process, end of process and associated point status is not saved. These values will be re-initialized in order to avoid blank data in the central database.

18FeatureAdd warning related to photosIf error is detected on EXIF data, a warning message is associated to the point

19FeaturePredefined comment for revisited pointIf point is revisited, the predefined comment AA08 is requested and date of first visit given in the free text field associated

20BugCOMDLG32.OCX automatically installed if not detected during installation process

New predefined codes - Related database version: 1.0.7

The table here below describes new predefined codes.TypeCodeDescription

Predefined commentsBG11BG11 BG Additional photo type 1 (Point access) not taken, precise

Predefined commentsBG12BG Additional photo type 2 (North/east rule) not taken, precise

Predefined commentsBG13BG Additional photo type 3 (Land cover) not taken, precise

Predefined commentsBG14BG Additional photo type 4 (Land use) not taken, precise

Predefined commentsBG15BG Additional photo type 5 (Transect) not taken, precise

Predefined commentsBG16BG Additional photo type 6 (soil) not taken, precise

Predefined commentsBG17BG Additional photo type 7 (water management) not taken, precise

Predefined commentsAA08Point revisited (insert date of previous visit)

Business rules (stored in central database) Related version: 1.0.7

The table here below describes additional controls implemented in central database version 1.0.7.

IDControl appliedError message associated

201555103Check if all the points of the triplets are currently stored in the local database. Normally this error should never appear.Soil triplet cannot be controlled. At least one of the point of the triplet was already exported

201591003Check if an additional photo, type Soil, was taken when the soil was collected. Normally soil label should be visible on this photoAdditional photo (point soil) required when soil sample taken (Photo label)

201591004If an additional photo, type soil, was taken, then predefined code BG16 cannot be registered by the user.If additional photo soil is taken, then comment BG16 not accepted

201561105Check beginning of the transect sequence when a point is photo-interpreted and no LC2 registered. Sequence should start by PI;LC1.When point is PI, transect should start by PI;LC1

201561106Check beginning of the transect sequence when a point is photo-interpreted and LC1 in artificial area (except A22) and no LC2 registered. Sequence should start by PI;A.When point is PI and LC1 like A (except A22), transect should start by PI;A

201561107Check beginning of the transect sequence when a point is photo-interpreted and LC1 = A22 and no LC2 registered. Sequence should start by PI;62 or PI;63.When point is PI and LC1 = A22, transect should start by PI;62 or PI;63

201561108Check beginning of the transect sequence when a point is photo-interpreted and LC1 & LC2 registered. Sequence should start by PI;LC1;LC2.When point is PI and LC1 LC2 registered, then transect should start by PI;LC1;LC2

201561109Check beginning of the transect sequence when a point is photo-interpreted and LC1 like A (except A22) & LC2 registered. Sequence should start by PI;A;LC2.When point is PI and LC1 like A (not A22) and LC2 registered (Not 8), then transect should start by PI;A;LC2

201561110Check beginning of the transect sequence when a point is photo-interpreted and LC1 = A22 & LC2 registered. Sequence should start by PI;62;LC2 or PI;63;LC2.When point is PI and LC1 = A22 and LC2 registered (Not 8), then transect should start by PI;62;LC2 or PI;63;LC2

201561104Check beginning of the transect sequence when LC1 = A13 or A30 & LC2 registered. Transect sequence starts by A;LC2Transect sequence should start by A;LC2 when LC1 = A13 or A30

201591005Check if additional photo, type 2 (North/East observation), was taken, when point observed to the North or East.Additional photo type 2 (North/East rule) required when direction of observation to the North or East

201591006Check if additional photo, type 3 Land cover, was taken, when a second land cover like Bxx, Cxx, Dxx, Exx was registeredAdditional photo type 3 (Land cover) required when LC2 like Bxx, Cxx, Dxx, Exx

201591007Check if additional photo, type 4 water management, was taken, when irrigation and drainage were found in the field.Additional photo type 4 (Water management) required when irrigation and drainage registered

201591008Check if additional photo, type 5 transect, was taken, when a part or all of the transect was PI.Additional photo type 5 (Transect) required when PI or X found in the transect sequence

201591009When an additional photo, type 2 (Direction of observation), was taken, then comment BG12 cannot be registered by the userIf additional photo type 2 is taken, then comment BG12 not accepted

201591010When an additional photo, type 3 (land cover), was taken, then comment BG13 cannot be registered by the userIf additional photo type 3 is taken, then comment BG13 not accepted

201591011When an additional photo, type 7 (water management), was taken, then comment BG17 cannot be registered by the userIf additional photo type 7 is taken, then comment BG17 not accepted

201591012When an additional photo, type 5 (transect), was taken, then comment BG15 cannot be registered by the userIf additional photo type 5 is taken, then comment BG15 not accepted

201591013Comment BG11, additional photo related to the point access not taken, cannot be registered if the point was reached by the surveyor (Additional photo not mandatory)Comment BG11 not accepted when Type of observation =1

201591014Comment BG12, additional photo type 2 not taken, cannot be registered if the direction of observation was to the point (Additional photo not mandatory)Comment BG12 not accepted when Direction of observation = 1

201591015Comment BG13, additional photo type 3 not taken, cannot be registered if LC2 = 8 or Axx, Gxx, Fxx, Hxx (Additional photo not mandatory)Comment BG13 not accepted when LC2 = 8 or Axx or Gxx or Fxx or Hxx

201591016Comment BG14, additional photo type 4 not taken, cannot be registered if no irrigation and drainage found in the field (Additional photo not mandatory)Comment BG17 not accepted when presence of irrigation not 4

201591017Comment BG15, additional photo type 5 not taken, cannot be registered if no PI, X or Z code registered in the transect sequence (Additional photo not mandatory)Comment BG15 not accepted when no PI, X or Z codes found in the transect sequence

201591018Check if when an additional photo is registered, the type of photo is specifiedType of additional photo cannot be empty.

201522015When a point is photo-interpreted, only code Bx1 or Bx2 are accepted as LC1, if the land cover in B categoryIf point is photo interpreted, then LC1 Bx1 or Bx2 accepted if crop is B category

2015101012Check if a free text comment was given by the user, if a predefined comment ended by 99 is registeredFree text comment is requested when comment code like x99 is registered

2015101013Check if a free text comment was given by the user, if a predefined comment like BG1x is registered. This free text explain the reason why the additional photo was not takenFree text comment is requested when comment code like BG1x is registered

2015120002Check if the daily track loaded is within 5 km around the pointDaily track loaded is not related to the point area. Please check the track loaded

2015101014Free text comment, with date of the first visit, is requested when comment code AA08 is registered

201575001Warning message registered when error in exif data (photo P)Please check photo P Exif data

201575002Warning message registered when error in exif data (photo N)Please check photo N Exif data

201575003Warning message registered when error in exif data (photo E)Please check photo E Exif data

201575004Warning message registered when error in exif data (photo S)Please check photo S Exif data

201575005Warning message registered when error in exif data (photo W)Please check photo W Exif data

201575006Warning message registered when error in exif data (photo C)Please check photo C Exif data

201575007Warning message registered when error in exif data (photo L)Please check photo L Exif data

201575008Warning message registered when error in exif data (photo I)Please check photo I Exif data

201575009Warning message registered when error in exif data (photo T)Please check photo T Exif data

2015120003Check several points surveyed at the same timeSeveral points surveyed at the same time. Please, check start and end time

Quality check carried out on point validation (Version 1.0.7)

IDError message

201500000Date or type of observation not recorded. The automatic quality control will not be executed. Point rejected

201511001Date of survey not consistent with beginning and end of the survey period defined.

201511002End time expected after start time.

201511003Slot not allowed

201511004A comment like BFx is required when the duration is higher than one hour or during less than 15 minutes

201511005A comment like BEx is required when the car park position is not recorded

201511007Observation type cannot be 7, if point not declared by Eurostat as Ex-ante point

201511008Observation type 7 mandatory, if point declared by Eurostat as Ex-ante point

201511100Field required

201512001When the surveyor went to the field, then observation GPS projection system 8

201512002A comment is required (AA*, BA*, BB*) when the observation type (question 7) is 2 or 4

201512003Inconstency between fields 7 (Type of observation) and field 14 (distance to the point) declared. If Question 7 = 1, then value in field 14 must be lower or equal to 100

201512004Inconstency between fields 7 (Type of observation) and field 14 (distance to the point) declared. If Question 7 = 2, then value in field 14 must be higher than 100

201513001A comment like BEx is required when a problem with the GPS is observed

201513002If GPS problem observed (question 8 = 2) then fields 9 and 11 equal 88.888888, field 10 equals 8 and fields 12 to 14 equals 8888

201513003When GPS coordinate system equal 1 (WGS84), Value 88.888888 not accepted for fields 9 and 11, value 8 not accepted for field 10 and value 8888 not accepted for fields 12 to 14

201513004Please check altitude entered in the field 12 (altitude entered higher than 1500 m)

201513005Please, check the value entered in the field 13 - GPS precision. Entered value higher than 50 m

201513006The distance of the point cannot be greater than the double of precision + calculated distance or less than calculated distance - the double of precision

201514001Comment like Abxx and/or Acxx required when ditance of observation higher than 100 m

201514002Comment like Abxx and/or Acxx required when point is photointerpreted

201514003Comment like Abxx and/or Acxx required when point is not observed and PI not possible

201521001A comment like BC is required when the North or East direction of observation is done

201521002If the point is observed (Field 7 from 1 to 3), the observation direction (Field 17) cannot be equal to Not relevant

201521003If the point is not observed (Field 7 value higher than 3), the observation direction (Field 17) is Not relevant

201521004If the point is observed (Field 7 from 1 to 3), the radius of observation (Field 18) cannot be equal to Not relevant

201521005If the point is not observed (Field 7 value higher than 3), the radius of observation (Field 18) is Not relevant

201521006Inconsistency between land cover codes entered and radius of observation declared

201521008If the point is observed (Field 7 from 1 to 3), the plot area (Field 19) cannot be equal to Not relevant

201521009If the point is not observed (Field 7 value higher than 3), the plot area (Field 19) is Not relevant

201521010Height of trees at the moment of the survey (Field 26) is not relevant according to the plot area (field 19) registered

201521011If plot area >0.5 (Field 19>1) and LC1 or LC2 like CXX, D10 or E10, then height of trees at the moment of the survey (Field 26) is requested

201521012If plot area >0.5 (Field 19>1) and LC1 or LC2 not like CXX, D10 or E10, then height of trees at the moment of the survey (Field 26) is not relevant (value 8)

201521013Height of trees at maturity (Field 27) is not relevant according to the plot area (field 19) registered

201522001Please check land cover 1 and land cover 2 codes. Association not allowed

201522002Association LC1 - LU1 not accepted

201522003Association LC 1 or LC2 with LU2 not accepted

201522004Value 8 not accepted for land cover 1 (Field 20), when the point is observed (Field 7 from 1 to 3)

201522005Land cover 1 (Field 20) not relevant, when the point is not observed (Field 7 from 4 to 6 or 8)

201522006Land cover 2 (Field 23) not relevant, when the point is not observed (Field 7 from 4 to 6 or 8)

201522007Association LC1 - LC1 plant species not accepted

201522008Association LC2 - LC2 plant species not accepted

201522009The land cover code 1 (Field 20) entered is not valid

201522010The land cover code 2 (Field 23) entered is not valid

201522011The percentage of land cover 1 (Field 22)is required when a Land cover code LC1 is recorded (Field 20)

201522012The percentage of land cover 2 (Field 25)is required when a Land cover code LC2 is recorded (Field 23)

201522013The percentage of land cover 2 (Field 25)is not relevant when the Land cover code LC2 is not recorded (Field 23)

201522014The percentage of land cover 1 (Field 22)is not relevant when the Land cover code LC1 is not recorded (Field 20)

201522015If point is photo interpreted, then LC1 Bx1 or Bx2 accepted if crop is B category

201523001Height of trees at the moment of the survey (Field 26) is not relevant according the type of observation (Field 7)

201523002Height of trees at maturity (Field 27) is not relevant according the type of observation (Field 7)

201523003Width of feature (Field 28) is not relevant according the type of observation (Field 7)

201523004Height of trees at maturity must be higheror equal to the height of trees at the moment of the survey

201523005When field height of trees at maturity (Field 27) is 2 (>=5m), then field Width of feature (Field 28) is not relevant

201523006If height of trees at maturity equal 2 (>=5m), then width of feature is required (Field 28 8)

201531001LU1 - LU2 association not authorized

201532001Field 35, signs of grazing visible is mandatory if LC1 like Bxx or Cxx or Dxx or Exx or Fxx or Hxx

201532002Field 35, signs of grazing visible is not relevant (8) if LC1 not like Bxx or Cxx or Dxx or Exx or Fxx or Hxx

201532003Field 36 is mandatory if type of observation (Field 7) is 1, 2 3 or 7

201532004Field 36 is not relevant if type of observation (Field 7) is 4, 5 or 6

201532005Field 37 (Special remarks on LC or LU) is mandatory if type of observation (Field 7) is 1, 2 3 or 7

201532006Field 37 (Special remarks on LC or LU) is not relevant if type of observation (Field 7) is 4, 5 or 6

201542100Sum of INSPIRE land cover classes cannot be over 100

201542101If LC 1 like Cxx, Dxx, Exx, Fxx, then sum of inspire code expected to 100

201542102If LC not C and not D and not E and not F, then inspire code not relevant, and sum = 0

201542201If LC1 = F10, then more than 90% has to be declared in consolidated bare surface field (INSPIRE)

201542202If LC1 = F20, then more than 90% has to be declared in unconsolidated bare surface field (INSPIRE)

201542203If LC1 = F30, then more than 90% has to be declared in lichens and mosses field (INSPIRE)

201542204If LC1 = F40, then more than 90% has to be declared in unconsolidated bare surface field (INSPIRE)

201542205If LC1 like C1*, C2* or C3*, then more than 10% has to be declared in coniferous + broadleaved forest field (INSPIRE)

201542206If LC1 = C10, then more than 10% has to be declared in broadleaved forest field (INSPIRE) and less than 25% of broadleaved covered by coniferous

201542207If LC1 = C10, then more than 10% has to be declared in broadleaved forest field (INSPIRE)

201542208If LC1 = C20 or C21 or C22, then more than 10% has to be declared in coniferous forest field (INSPIRE)

201542209If LC1 = C20 or C21 or C22, then more than 10% has to be declared in coniferous forest field (INSPIRE) and less than 25% of coniferous area registered covered by broadleaved

201542210If LC1 = C31 or C32 or C33, then more than 10% has to be declared in broadleaved + coniferous forest field (INSPIRE) and between 25% and 75% of broadleaved and coniferous areas registered covered by coniferous and broadleaved

201542211If LC1 = C31 or C32 or C33, then more than 10% has to be declared in broadleaved + coniferous forest field (INSPIRE) and between 25% and 75% of broadleaved and coniferous areas registered covered by coniferous and broadleaved

201542212If LC1 = D10, then more than 10% has to be declared in shrubs field (INSPIRE) and coniferous + broadleaved distribution equal 5

201542213If LC1 = D20, then more than 10% has to be declared in shrubs field (INSPIRE) and coniferous + broadleaved distribution equal to 0

201542214If LC1 = E10, then more than 10% has to be declared in herbaceous plants field (INSPIRE) and coniferous + broadleaved distibution equal 5 and shrubs under or equal to 10

201542215If LC1 = E20 or E30, then more than 10% has to be declared in herbaceous plants field (INSPIRE) and coniferous + broadleaved distribution equal 0 and shrubs distribution under or equal to 5

201552001If LU1 or LU2 is U111 or U112, then field 46, presence of water management, cannot be not relevant (8)

201552002If LU1 and LU2 is not U111 or U112, then field 46, presence of water management, is not relevant (8)

201552003If water management not relevant or no visible, then type of irrigation is not relevant (8)

201552004If water management not relevant or no visible, then source of irrigation is not relevant (8)

201552005If water management not relevant or no visible, then delivery system is not relevant (8)

201552006If presence of water management (field 46 = 1 to 4), then type of irrigation is required (value 8 not accepted)

201552007If presence of water management (field 46 = 1 to 4), then source of irrigation is required (value 8 not accepted)

201552008If presence of water management (field 46 = 1 to 4), then delivery system is required (value 8 not accepted)

201552501If point belongs to soil triplet, then field 50 4

201552502If point not belongs to soil triplet, then field 50 = 4

201552701If soil taken, then soil label (field 51) is relevant (8888)

201552702If soil taken, then field signs of ploughing is relevant (field 528888)

201552703If soil taken, then field percentage of residual crop is relevant (field 538)

201552704If soil taken, then field percentage of stones is relevant (field 548)

201552705If soil is not taken, then soil label is not relevant (field 51=8888)

201552706If soil is not taken, then field signs of ploughing is not relevant (field 52=8)

201552707If soil is not taken, then field percentage of residual crop is not relevant (field 53=8)

201552708If soil is not taken, then field percentage of stones is not relevant (field 54=8)

201553001Comment CA05 to CA07 or CA99 required when soil cannot be taken

201553002Comment like CA not accepted when no sample needed or already taken on another point

201553003Comment CA05, CA06, CA07 not accepted when soil taken

201553004Comment CA01 to CA04 or CA08 not accepted when soil not taken

201555101Inconsistency in soil collection. Please check field 50 for the three points related to the soil triplet

201555102Soil triplet cannot be controlled. At least one of the point of the triplet was not yet entered in DMT Client

201555103Soil triplet cannot be controlled. At least one of the point of the triplet was already exported

201555500At least one error detected during the quality control of the triplet (not related to the soil). Please, correct the relevant point. The point cannot be validated

201561001Transect sequence is not relevant (Field 56 = 8) when type of observation is 4 or 5 or 6

201561002Transect sequence must start by PI code when the point is photo-interpreted (Type of observation 3 or 7)

201561003Transect sequence must end by PI code when the point is ex-ante photo-interpreted (Type of observation = 7)

201561004Wrong number of codes (PI and PI) recorded in the transect sequence

201561005In the transect, codes Bx must be used inside PI

201561006X code only accepted at the end of the transect sequence

201561100Transect sequence must start by the LC1 code

201561101When land cover code is A22, the transect sequence must start by 62 or 63

201561102According to the land use code (LC1), the transect sequence should start by A code

201561103Transect sequence should start by LC1;LC2 according to the land cover codes entered

201561104Transect sequence should start by A;LC2 when LC1 = A13 or A30

201561105When point is PI, transect should start by PI;LC1

201561106When point is PI and LC1 like A (except A22), transect should start by PI;A

201561107When point is PI and LC1 = A22, transect should start by PI;62 or PI;63

201561108When point is PI and LC1 LC2 registered, then transect should start by PI;LC1;LC2

201561109When point is PI and LC1 like A (not A22) and LC2 registered (Not 8), then transect should start by PI;A;LC2

201561110When point is PI and LC1 = A22 and LC2 registered (Not 8), then transect should start by PI;62;LC2 or PI;63;LC2

201562001Duplicated code on the transect sequence

201562002Transect length must be equal to 250 m

201562005In the transect sequence, Bx code can be used if transect partially or fully photo-interpreted

201562006In the transect sequence, codes like B1x to B8x are not accepted inside a photo-interpreted sequence

201563001Comment DA09 or DA3x or DA99 required when X code in transect sequence

201563002Comment DA09 or DA3x not accepted when X code not in transect sequence

201563003Comment DA01 to DA08 or DA99 required when PI code in transect sequence

201563004Comment DA01 to DA08 not accepted when PI code not found in transect sequence

201570001Comment like BG required when photo P not taken

201570002Comment like BG required when photo C not taken

201570003Comment like BG required when photo N not taken

201570004Comment like BG required when photo E not taken

201570005Comment like BG required when photo S not taken

201570006Comment like BG required when photo W not taken

201570007Comment like BG required when photo I not taken

201570008Comment like BG required when photo T not taken

201570009Comment like BG required when photo soil (L) not taken

201570010Comment BG01, BG02, BG03, BG04 not accepted when all requested photos were taken

201571001When type of observation 1 or 2, then photo P cannot be not relevant (8)

201571002When type of observation 1 or 2 or 3, then photo N cannot be not relevant (8)

201571003When type of observation 1 or 2 or 3, then photo E cannot be not relevant (8)

201571004When type of observation 1 or 2 or 3, then photo S cannot be not relevant (8)

201571005When type of observation 1 or 2 or 3, then photo W cannot be not relevant (8)

201572001If land cover code in B or C or D or E, then crop photo must be taken

201572002If land cover code in A or F or G or H, then crop photo is not relevant

201573001If Visible water management, then Photo I cannot be not relevant

201573002If no visible water management, then Photo I is not relevant

201573003If water management not relevant, then Photo I is not relevant

201573004If soil taken, then Photo soil (L) cannot be not relevant

201573005If soil not taken, then Photo soil (L) is not relevant

201580001Visual QC comment status 1 (waiting feedback) expected when point rejected by quality controller

201580002Visual QC comment status 1 (waiting feedback) not accepted when point accepted by quality controller

201591001Additional photo (point access) required when type of observation 2 or 3 or 4

201591002Additional photo (point soil) required when soil sample cannot be taken

201591003Additional photo (point soil) required when soil sample taken (Photo label)

201591004If additional photo soil is taken, then comment BG16 not accepted

201591005Additional photo type 2 (North/East rule) required when direction of observation to the North or East

201591006Additional photo type 3 (Land cover) required when LC2 like Bxx, Cxx

201591007Additional photo type 7 (Water management) required when irrigation and drainage registered

201591008Additional photo type 5 (Transect) required when PI or X found in the transect sequence

201591009If additional photo type 2 is taken, then comment BG12 not accepted

201591010If additional photo type 3 is taken, then comment BG13 not accepted

201591011If additional photo type 7 is taken, then comment BG17 not accepted

201591012If additional photo type 5 is taken, then comment BG15 not accepted

201591013Comment BG11 not accepted when Type of observation =1

201591014Comment BG12 not accepted when Direction of observation = 1

201591015Comment BG13 not accepted when LC2 = 8 or Axx or Gxx or Fxx or Hxx

201591016Comment BG17 not accepted when presence of irrigation not 4

201591017Comment BG15 not accepted when no PI, X or Z codes found in the transect sequence

201591018Type of additional photo cannot be empty.

2015101000Please check LC changes between previous and current campaign

2015101001Please check LU changes between previous and current campaign

2015101002When a rare LC changes is observed, at least one of the following comment is requested : BP08 or BP11 OR BP12 OR BP99

2015101003When a rare LU changes is observed, at least one of the following comment is requested : BP09 or BP11 OR BP12 OR BP99

2015101004Different location than in previous campaign

2015101005Comment like BA or BP01 or BP02 or BP03 or BP04 or BP99 is expected if different location than in previous campaign

2015101006Comment like BCxx not accepted when Field 17 (Direction of observation) is on the point

2015101007Comment like BP05, BP06, BP07 and BP99 is required when direction of observation is different than in previous campaign

2015101008Comment BP05, BP06, BP07 not accepted when direction of observation is the same than in previous campaign

2015101009Comment like BP08 not accepted when a normal land cover changes is observed

2015101010Comment like BP09 not accepted when a normal land use changes is observed

2015101011Comment like BP11 or BP12 not accepted when a normal land cover and land use changes are observed

2015101012Free text comment is requested when comment code like x99 is registered

2015101013Free text comment is requested when comment code like BG1x is registered

2015120001Comment like BE requested when track file not found for the selected point

2015120002Daily track loaded is not related to the point area. Please check the track loaded.

2015101014Free text comment, with date of the first visit, is requested when comment code AA08 is registered

201575001Please check photo P Exif data

201575002Please check photo N Exif data

201575003Please check photo E Exif data

201575004Please check photo S Exif data

201575005Please check photo W Exif data

201575006Please check photo C Exif data

201575007Please check photo L Exif data

201575008Please check photo I Exif data

201575009Please check photo T Exif data

2015120003Several points surveyed at the same time. Please, check start and end time