You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no standard methodology for recording which LDP or other non standards the LAS file is meant to conform to.
Some possible standards that matter:
LAS revision
LAS Domain Profile (topobathy v1, topobathy v2, transmission lines, etc)
ASPRS 2014
ASPRS 2023 v1, v2, etc
USGS LDP v____
Standardizing these with a lookup table would require constant maintenance. Perhaps the best solution would be for the VLR content to be a null-terminated array of URLs? Or maybe LAS wiki page names to err on the safe side?
The text was updated successfully, but these errors were encountered:
I think an array that contained both a common (but not necessarily standardized) name and a URL would be good. Is there a common pattern for putting an array of strings in a VLR or EVLR?
What is the issue about?
Other
Issue description
There is currently no standard methodology for recording which LDP or other non standards the LAS file is meant to conform to.
Some possible standards that matter:
Standardizing these with a lookup table would require constant maintenance. Perhaps the best solution would be for the VLR content to be a null-terminated array of URLs? Or maybe LAS wiki page names to err on the safe side?
The text was updated successfully, but these errors were encountered: