Ply files download

Feb 22, Added a. May 29, Jan 1, Added -OO note. Apr 14, View code. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Neither the name of the David Beazley or Dabeaz LLC may be used to endorse or promote products derived from this software without specific prior written permission. How to Use PLY consists of two files : lex.

For example: from. About Python Lex-Yacc www. Releases 3 tags. Packages 0 No packages published. Input Arguments collapse all filename — File name character vector string scalar. Note This function only supports PCD file formats saved in version 0.

Output Arguments collapse all ptCloud — Object for storing point cloud pointCloud object. Object for storing point cloud, returned as a pointCloud object that contains the following PLY or PCD fields: Location property, stores the x , y , and z values. Color property, stores the red, green, and blue values.

Normal property, stores the normal vectors for each point. Intensity property, stores the grayscale intensity for each point.

You have a modified version of this example. Do you want to open this example with your edits? Some notable features include the fact that its implemented entirely in Python and it uses LALR 1 parsing which is efficient and well suited for larger grammars. PLY is extremely easy to use and provides very extensive error checking. It is compatible with both Python 2 and Python 3. Feb 15, Jan 31, Aug 31, Oct 2, Apr 26, Feb 18, Oct 11, However, exactly what constitutes a "valid" file isn't obvious, since there doesn't seem to be a single complete and consistent description of the PLY format.

Even the "authoritative" Ply. Where can comments appear in the header? It appears that in all the "official" examples, all comments immediately follow the "format" line, but the language of the document neither places any such restrictions nor explicitly allows comments to be placed anywhere else.

Thus, it isn't clear whether comments can appear anywhere in the header or must immediately follow the "format" line. At least one popular reader of PLY files chokes on comments before the "format" line.

Another ambiguity is names: what strings are allowed as PLY element and property names? This may not be such a big deal, though: although names are theoretically arbitrary, in practice, the majority of PLY element and property names probably come from a small finite set "face", "x", "nx", "green", etc. A more serious problem is that the PLY format specification appears to be inconsistent regarding the syntax of property definitions.

In some examples, it uses the syntax. The specification explicitly states that lines in the header must end with carriage returns, but this rule doesn't seem to be followed by anyone, including the C-language PLY implementation by Greg Turk, the author of the format. Here, we stick to common practice and output Unix-style line endings with no carriage returns but accept any line ending style in input files. Examples beyond the scope of this document and the tests are in the examples directory.

May 3, Feb 7, Mar 22, Oct 9, Dec 26, Jul 28, Feb 28, Apr 19, Download the file for your platform. If you're not sure which to choose, learn more about installing packages. Warning Some features may not work without JavaScript. Please try enabling it if you encounter problems. Search PyPI Search. Latest version Released: May 3, Navigation Project description Release history Download files.