LASValidate fail report: file creation day should be between 1-152 not 186

[Mauro Assis]

I don´t understand this error message, as I supposed that the field should contain the number of days between 1/1 to the file creation date, that is, any value between 1 and 365/366 should be valid.

Tks in advance,

Mauro

[LAStools - efficient tools for LiDAR processing]

Hi Mauro,

please send a sample file and the full sample file text validation output.
The date may refer to the current year. No future dates are allowed.

Cheers,

Jochen @rapidlasso

[Mauro Assis]

This is the link to download file: https://we.tl/t-sHoMaP8LUJQNRHKE

Below, the lasvalidate output:

{
  "LASvalidator": {
    "version": "lasvalidate (260319) built with LAStools version 260326",
    "command_line": "lasvalidate64.exe -i I:\\Amazonia3D\\amazon-3d-lidar\\ENTREGAS\\ENTREGA_01\\1_Nuvem_de_Pontos\\NP_1418193.laz -odir . -ojson -report_per_file",
    "report": [
      {
        "file": {
          "name": "NP_1418193.laz",
          "path": "I:\\Amazonia3D\\amazon-3d-lidar\\ENTREGAS\\ENTREGA_01\\1_Nuvem_de_Pontos",
          "LAS_version": "1.4",
          "system_identifier": "Teledyne Optech Galaxy T500",
          "generating_software": "MapBiomas AM | SAI",
          "point_data_format": 7,
          "CRS": "SIRGAS 2000 / UTM zone 20S"
        },
        "summary": "fail",
        "details": {
          "fail": [
            {
              "variable": "file creation day",
              "note": "should be between 1-152 not 186"
            }
          ],
          "warning": [
            {
              "variable": "x offset",
              "note": "translation fluff: decimal digits of 509965.711971368233208 do not match scale factor 0.001"
            },
            {
              "variable": "y offset",
              "note": "decimal digits of 9228871.327246062457561 do not match scale factor 0.001"
            }
          ]
        }
      }
    ],
    "total": {
      "result": "fail",
      "details": {
        "pass": 0,
        "warning": 0,
        "fail": 1
      }
    }
  }
}

--
Download LAStools at
https://rapidlasso.de
Manage your settings at
https://groups.google.com/g/lastools/membership
---
You received this message because you are subscribed to the Google Groups "LAStools - efficient tools for LiDAR processing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lastools+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lastools/9df855b3-abf5-4c1e-a600-9b75495153dfn%40googlegroups.com.

[Jochen Rapidlasso]

Hi Mauro,

it's just as we suspected: the date is in the future. The maximum value for the current year is 152.

To crosscheck we use the file browser of laslook, where the file date is also shown decoded (here with our system setting of "dd.mm.yyyy"):

You can use lasinfo -i ... -auto_creation to fix the date to the current file creation date or 

    -set_creation_date [day] [year]     : set creation date to [day] [year]  

to fix this issue.

Cheers,

Jochen @rapidlasso

[Mauro Assis]

You were right! Anyway, the error message isn't very clear...

Tks!

 Mauro

To view this discussion visit https://groups.google.com/d/msgid/lastools/933749cd-26d0-4898-b0b4-9c22490d6dc2n%40googlegroups.com.

[Jochen Rapidlasso]

Hi Mauro,

we will refine the error message to make that a little clearer.

Cheers,

Jochen @rapidlasso