our LPIS products (.csv) do contain less parcels then present in the declaration dataset. This is not expected, as the user manual states that both datasets should have the same number of parcels:
22.214.171.124 Output data
The preparation step generates a series of output files, which are used by the subsequent L4x processors.These outputs are described below. Standardized declaration dataset with quality flags. The first output is a postGIS layer. It contains the original declaration dataset information as well as the quality flags generated during the preparation step. It has the same number of lines (parcels) than the original LPIS / GSAA declaration dataset.It contains the following attribute fields (fields in orange are already present in the original declaration dataset) (Table 4-3).This information is also copied in a csv file, accessible in the folder /mnt/archive/lpis/site-name/
Still, in our example we get ~18K parcels in the LPIS product from ~19K parcels in the input data (another example yielded only 105K parcels from 140K).
I was looking at the parcels (size and form) that did not make it into the LPIS product. They seem very similar to the ones that did make it into the LPIS product.
Can you tell me about possible reasons why these parcels are excluded in the LPIS product?