A proprietary format is a file format of a company, organization, or individual
In contrast an open format is a file format that is published and free to be used by everybody.
--
--
You are subscribed to "The LAS room - a friendly place to discuss the the LAS or LAZ formats" for those who want to see LAS or LAZ succeed as open standards. Go on record with bug reports, suggestions, and concerns about current and proposed specifications.
Visit this group at http://groups.google.com/group/lasroom
Post to this group with an email to las...@googlegroups.com
Unsubscribe by email to lasroom+u...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "The LAS room - a friendly place to discuss the LAS and LAZ formats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lasroom+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The GUID is infinitely useful.
It is guaranteed to be unique across the universe of all GUIDs.
You can generate one using any of a number of on-line GUID generators.
Remember, no one need know anything at all about the GUID so long as the same GUID is used for all files in a project.
Thus if a GUID is properly assigned to a project, all data within that project (all the way down to single points) can be uniquely identified.
Lewis Graham
--
Download LAStools at
http://lastools.org
http://rapidlasso.com
Be social with LAStools at
http://facebook.com/LAStools
http://twitter.com/LAStools
http://linkedin.com/groups/LAStools-4408378
Manage your settings at
http://groups.google.com/group/lastools/subscribe
--
GUIDs are unique by construction – that’s the entire purpose of the invention of GUIDs. They solve the problem of uniqueness without the need for centralized arbitration.
If you create a GUID (using a proper GUID generator which, again, does not require a lookup of precreated GUIDs), the chances of creating a duplicate are less than the chance you get hit in the head by a meteorite.
We envisioned these as being used (in LAS) for managing data while still “near” the sensor. For example, I could tag a bunch of LAS files that came from the same sortie with a GUID and then tag the related metadata (such as the trajectory) with that same GUID. It is an optional field in the LAS header and can be freely used for project management schemes.
We did not envision the GUID as being particularly useful once data hit the exploitation phase (for example, a county government taking delivery of some LAS data). Once you have merged, at the tile level, a bunch of individual LAS files, the individual point tracking requires a local catalog (which can be stored in a VLR of the LAS file). I am not aware of any implementations of this.
Thus the GUID is primarily used in production management. It is particularly useful in multi-sensor, multi-contractor projects.
Regards,
Lewis
Lewis Graham
Here is an on-line generator:
Second part – she must have duplicated a doppelganger’s GUID…..
Regards,
Lewis
Lewis Graham
AirGon LLC, small UAS Solutions
GeoCue Group
9668 Madison Blvd., Suite 202
Madison, AL USA 35758
01-256-461-8289
Hello,
okay. I am adding an option to lasinfo called '-set_GUID' that takes in a hexastring. That said, there is still an issue with endian-ness. The GUIDs seem to be defined as big endian [1] but the LAS specification states all fields are little endian [2]. Hence, I am not even sure the current way these strings are reported by lasinfo has been correct all these years.Are all GUIDs reported by lasinfo in the wrong byte order? I am admittingly much more knowledgable about grilling SQUIDs than being grilled over GUIDs ... (-;
--
I, too, am interested to know how LAStools, LP360, TerraSolid, GeoCue, and similar tools implement this.Also added lasroom back to this email chain.Evon
After a close read of the spec, I'm getting the impression that it was originally intended to follow with the Microsoft-style of UUIDs, as described on the Wikipedia page.
<image.png>
lasinfo -i myfile.las -set_GUID F794F8A4-A23E-421E-794D-725031306A6F