Keeping ESRI Honest

Friends of LASzip and LAZ, it has come to my attention (from more than one source) that a certain company East of LA has started to more aggressively promote their proprietary LiDAR format known as the “LAZ clone” (more hereherehere and here but also read the comments) by approaching individual stake holders of the LiDAR community. Trying to convince others to drop support of the open source LASzip compression for LiDAR management, server, and storage in favour of the proprietary “LAZ clone”, said company resorts – if needed – to bad-mouthing the LAZ format with made up arguments that attack the suitability of LASzip for “professional” use.

It appears the LiDAR lock-in PR campaign is now in full swing despite of my repeated attempts to reach out to said company for creating a joint LAS 1.4 compressor that avoids fragmenting the LiDAR data market. And I may just be hearing back about a tiny tip of the drink-the-koolaid iceberg PR. This seems to mark the start of the “clone wars” that we at rapidlasso tried to avoid … (-;

laz_clonesOne way to engage the Empire is to draw them out from the darkness into full technical transparency. After all, the only argument for why the “LAZ clone” had to be created was that LAZ lacks a “particular feature” for efficient employment in the cloud, yet the question what this “particular feature” was has always been dodged (because we would have happily added it to LAZ).

How can you help?

  1. Tell us about any “LAZ clone” campaigs you hear about. Especially those targetting stake holders.
  2. Attend LiDAR training events and Webinars by ESRI that may be “teaching” the unsuspecting newbies to lock their LiDAR into the zLAS format as part of a “smart management strategy” and
    – record any arguments made for the “LAZ clone” or against LAZ so we can publically defute them
    – keep them honest by making your unwillingness to drink the koolaid on zLAS known as early as possible.
    – ask tough questions and disrupt with a strong technical critique on the user-unfriendly and vendor lock-in nature of a closed proprietary format soon as they “teach” the LAS to zLAS conversion
  3. Educate folks about the difference between open LAZ and propietary zLAS.

You may comment below (also anonymously) or email us at ‘honestesri@rapidlasso.com‘ if you have any (juicy?) details about “LAZ clone” campaigns or on video or live training courses where it was “taught” to lock-up the LiDAR into zLAS during an initial “optimization” step …

Geoinformatics magazine interviews rapidlasso

Eric van Rees, the editor of the Geoinformatics magazine, met with rapidlasso GmbH at INTERGEO 2013 in Essen to have a quick chat about LAStools, LASzip, and PulseWaves as well as our LiDAR processing toolboxes for ArcGIS and QGIS.

Geoinformatics magazine interviews rapidlasso

In the three-page article we talk about the beginnings of rapidlasso’s software, about when and how the company got started, about our various open and closed source products, and about current projects. The interview was published in the most recent October/November edition of the Geoinformatics magazine that was distributed in print at the SPARELMF 2013 conference in Amsterdam this week. If you did not get a copy you can read the online version of the magazine here.

Can you copyright LiDAR?

UPDATE: The situation has changed. Make sure you also read this.

A few weeks ago, I wanted to demonstrate how geometric compression can shorten download times for online dissemination of 3D archeological artifacts. The demo failed. My web page was gone. The web admin told me later that he had to delete it after receiving an email from a director at CyArk stating that I was “[…] hosting unauthorized content from CyArk […] ” and that “[…] Dr. Isenburg gained unauthorized access to our information and the re-posted it to his webpage […]”. Bummer. Unintentionally, I had become “the raider of the CyArk”. A point plunderer. A LiDAR looter. A scan scrounger. A laser pirate … arrr … (-;

How did I fall so low? After reading this LiDAR news article about CyArk’s new online 3D viewer I invested serious time into understanding their content delivery system and suggested how to shorten download times as I had done a lot of prior research on this particular topic (see this, this, this or this page). So, I created several interactive java-based web pages for them to demonstrate how – with some quantization, simple prediction, and clever scripting – more web-efficient 3D content might be possible. I did these experiments with their data sets to allow an apples-to-apples comparison: a point model (Ti’kal) and a mesh model (Mount Rushmore).

cyark_mount_rushmore_small

After a long technical exchange the person at CyArk suddenly demanded that I take down the compressed content. I was surprised and asked why I should have to delete these illustrative examples on 3D compression that represented a significant investment in volunteered time and energy.

Me: “What you mean with take down? Delete it from my webpages? But I am using it as a purely educational example for scanner precision and coordinate resolution. I am not promoting it in any context that would interfere with the mission of CyArk. I do not quite follow the imperative here. Aren’t you a non-profit site dedicated to science and education? And anyone could download those points clouds from your site just the way I did it. It’s not rocket science … (-:”

Person at CyArk: “And, yes, to clarify my request, I would like you to delete any content from your server or webpages. Sorry if I was vague. Thanks!”

Me: “I believe I am in accordance with both Ben (Kacyra)’s vision and the creative commons license with my educational use of the 3D content (see http://archive.cyark.org/copyright). Is there something I am missing?”

I considered myself well informed about CyArk’s mission on providing open access to 3D data for research, education, and virtual tourism through various media such as Wikipedia and Ben Kacyra’s visionary TED talk. I assumed that my creative commons argument had resonated because I did not hear back from them. I only realized that CyArk was not interested in explaining their licensing but simply had my pages removed when I tried to access this demo.

A few days ago I saw Tom Greaves, executive director at CyArk, commenting “Sweeeet use of CyArk data.” on their blog entry which describes the creation of a sugary fudge replica of Ti’kal – the very same data set that I had been using – for the launch event of a new sugar series by British-based multinational agribusiness Tate & Lyle.

Tik’al Fudge Cake made with golden caster sugar, over 80 cm tall

I like to have fun with LiDAR and appreciate the educational factor of such events. Yet I wonder whether the Guatemalan people would be that much happier to see their ancient cultural heritage presented as a piece of cake to promote a new line of sugars than to see it used as a demo on how to Web-optimize 3D content … (-;

I took this as an opportunity to – once more – inquire about the creative commons license of CyArk and I finally received an answer from Tom.

Dear Dr. Isenburg,

Please understand that only some of […]     […] have any questions.

Sincerely,
Tom Greaves

Executive Director
CyArk

Unfortunately Tom did “not recall giving” me his “permission to publish” his “private correspondence” as he pointed out shortly after this blog article went live, so I had to remove the reprint of his email. It essentially said that much of the data collected by CyArk remains property of the site owners and that Cake for Breakfast obtained permission to use the 3D scan as the secret ingredient for their Mayan bake job.

copyright cartoon

After inquiring with Tom “So which models are creative commons and which not?” I quickly got the surprising response from Tom that: “None of our 3D point cloud is available under Creative Commons. Only some of the 2D image data is covered by this.

Now this is certainly not what I had been reading into their press releases and news articles. The data-generous openness in access to 3D data that is advertised for example on their mission statement: “Digital Preservation is ‘Preserving cultural heritage sites through collecting, archiving and providing open access to data created by 3D laser scanning, digital modeling, and other state-of-the-art technologies,’ the CyArk Mission.” is apparently not the practiced reality.

So I asked in my LAStools user forum about the experiences of others: What are the most and least permitting licenses for such data and what do they mean in practice? How do I know what is open and what not? Can you help clarifying what “creative commons” licensing means and what it allows and forbids so I don’t violate anyone’s license in the future. This sparked discussions with interesting outcomes:

  1. the creative commons (non-commercial) license is useless
    The folks behind @OpenAccessArch picked up the story to provide their view of the particularities of the creative commons (non-commercial) license used by CyArk in a long blog post titled “Creative Commons Non-commercial A Cruel Joke.
  2. it is in general not possible to copyright a LiDAR scan
    Doug Rocks-Macqueen from @OpenAccessArch also started the fundamental discussion whether it is even possible to copyright a LiDAR scan in the first place. Apparently not – at least not for an object whose copyright has already expired and for details read this message thread. His closing argument was that in this legal battle between Meshwerks, Inc. and Toyota Motor Sales U.S.A., Inc. the Court of Appeals affirmed the district court’s opinion that “3D models of physical objects, if faithfully and accurately representing the original, are not original enough to warrant copyright protection.”
  3. do not engage in open-washing … (-:
    In CyArk’s defense it needs to be said that there is probably a collision between their vision and the contract terms specified by the different site owners that they have to respect in order to get the permission to scan a site. What is lacking are clear terms of use in their communications and proper protection mechanisms. The academic pioneers of 3D scanning at Stanford university had to deal with similar issues during their Digital Michelangelo Project and created ScanView: a secure client / server rendering system that permits users to examine 3D models, but not extract the underlying data. In summary: do not claim your data is open and allow access to it when it is not.

With all the publicity I was worried that my little rabble rousing might be perceived as disruptive instead of constructive by the community until someone reassured me that: “I think we’re all quite happy that the discussion is happening. Between you and me, CyArk have a reputation as being rather less open with their data than their publicity would suggest.” … (-;

Martin @rapidlasso

PS: Be aware that all comments to this article will be considered “creative commons”. Or maybe not … (-;

cyark_tikal_sugarcubes_400The (loosely related) image shown above was obtained here and is courtesy of CyArk. I assume this use is allowed under their copyright and does not violate the creative commons (non-commercial) license … (-;

Addendum (May 1st, 2013): As a result of this article CyArk not only updated their copyright notice to exclude point clouds from the Creative Commons license but also added a very clear data use policy statement.