-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
confusion with datetime and LAS spec #36
Comments
So I just learned that "creation_year" and "creation_doy" are actually referring to the production time and not the aquisition time (see ASPRSorg/LAS#138). In this case I think populating |
hi @wiesehahn yeah the LAS creation date is ambiguous unfortunately... It would be better to try to extract the datetime information from individual points, but then probably use start/end datetime rather than a single datetime, given that a single file may be composed of multiple swaths from different dates or weeks. Maybe this could be done with an extra command line option, and by default use just the header info. |
populating So personally I would be definitely in favor of populating Then it would just be of question how to define |
datetime
is defined aswhich is also assumed for vpc creation
However I am unsure if this is what "creation_year" and "creation_doy" are defined as (see ASPRSorg/LAS#148)
there it simply says
And from my experience this is what providers populate it with, the date at which the file was created after inital processing, so usually this is days to month later than the aquisition date.
In my understanding the definition is unclear and the implementation here is correct, however I am not sure.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: