Help
RSS
API
Feed
Maltego
Contact
Domain > www.libe57.org
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2014-08-28
216.34.181.97
(
ClassC
)
2024-08-28
216.105.38.10
(
ClassC
)
Port 80
HTTP/1.1 200 OKServer: nginxDate: Wed, 28 Aug 2024 10:32:57 GMTContent-Type: text/htmlContent-Length: 18572Connection: keep-alivevary: Accept-Encodingvary: Hostlast-modified: Tue, 18 Jun 2024 16:43:37 GMTetag: 488c-61b2cc8860040accept-ranges: bytescache-control: max-age3600expires: Wed, 28 Aug 2024 11:32:42 GMTx-from: sfp-ioweb82-2vary: Accept-Encoding !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN>html>head>meta http-equivContent-Type contenttext/html; charsetISO-8859-1> !-- libE57 reference implementation library -->title>libE57: Software Tools for Managing E57 files (ASTM E2807 standard)/title>meta namerobots contentindex,follow>meta namegooglebot contentindex,follow>meta nameslurp contentindex,follow>meta namemsnbot contentindex,follow>meta namekeywords contentASTM E2807, E57, 3D laser scanning, ASTM E2807 standard, E57 file format, point clouds, Beta Testing libE57 Library, Foundation API, Simple API and libe57>meta namedescription contentA compact, vendor-neutral format for storing point clouds, images, and metadata produced by 3D imaging systems, such as laser scanners.>meta nameResource-Type contentDocument>meta nameUsergroup contentPublic>meta nameDistribution contentGlobal>meta nameCoverage contentWorldwide>meta nameDate-Created-yyyymmdd content20090901>meta nameDate-PrevRevision-yyyymmdd content20100721>meta nameDate-Revision-yyyymmdd content20110715>link relstylesheet typetext/css hrefstyle.css>style typetext/css>/style>/head>body bottommargin0 leftmargin0 rightmargin0 topmargin0 backgroundimg/background.jpg>table cellpadding0 cellspacing0 height123 width100% border0>tbody>tr valigntop>!----- insert logo below ------------------------------------------>td>img srcimg/bluelogo.jpg alt height123 width587 border0>/td>!------------------------------------------------------------------>td width100% backgroundimg/topbg.jpg> /td>/tr>/tbody>/table>table cellpadding0 cellspacing0 height40 width100% border0>tbody>tr valigntop>td width100% backgroundimg/topbar.jpg> /td>/tr>/tbody>/table>table cellpadding0 cellspacing0 width100% border0>tbody>tr valigntop>td width201>span classstyle7>br> !----- menu, insert links below ------------------------------------------> » a hrefindex.html>Home/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefnews.html>News/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefhttp://www.linkedin.com/e/-tq0kkz-gqcgnrr5-38/vgh/4010954/>E57 User Group/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefdownload.html>Downloads/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefdata.html>Test Data/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefhttp://sourceforge.net/tracker/?group_id247438&atid1325620>Bugs/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefdocumentation.html>Documentation/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hreffeatures.html>Feature Categories/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefextensions.html>Extensions/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefexample.html>Example/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefpartners.html>Supporting Partners/a>br>img srcimg/menubar.jpg width201 height11 border0 alt>BR> » a hrefproducts.html>Supporting Products/a>BR>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hrefconsultants.html>Consultants/a>br>img srcimg/menubar.jpg alt height11 width201 border0>br> » a hreflicense.html>Licenses/a>/span>br>img srcimg/menubar.jpg alt height11 width201 border0>br>!-------------------------------------------------------------------------->/td>td width100%> table cellpadding10 cellspacing0 width100% border0> tbody>tr valigntop> td>!----- content, insert text and content below ------------------------------------------>h1>libE57: Software Tools for Managing E57 Files/h1> table cellpadding5 cellspacing0 width600 aligncenter bgcolor#ffaaa7 border2 bordercolor#000000> tbody>tr> td>p aligncenter>strong>Call for a new E57 Version 2.0 file format standard/strong>/p> p>We would like to request a new effort by a hrefhttp://www.astm.org/COMMIT/COMMITTEE/E57.htm>ASTM E57.11 Data Interoperability Committee/a> to update and create a new a hrefE57Version2.html>E57 Version 2.0 file format/a> standard. Anyone interested in jointing this effort should join the E57.11 Committee./p> nbsp> /nbsp>/td> /tr> /tbody>/table> h2>The E57 File Format/h2> p>The E57 file format is a compact, vendor-neutral formatfor storing point clouds, images, and metadata produced by 3D imagingsystems, such as laser scanners. The file format is specified by theASTM, an international standards organization, and it is documented inthe a hrefhttp://www.astm.org/Standards/E2807.htm>ASTM E2807/a> standard. The E57 format was developed by the Data Interoperability sub-committee of the a hrefhttp://www.astm.org/COMMIT/COMMITTEE/E57.htm>ASTM E57 Committee on 3D Imaging Systems/a>. An overview of the design and implementation of the E57 format can be found in the paper a hrefhttp://www.ri.cmu.edu/publication_view.html?pub_id6767>The ASTM E57 File Format for 3D Imaging Data Exchange/a>./p> h2>The libE57 Software/h2> p>The libE57 software is an open source implementation of the a hrefhttp://www.astm.org/Standards/E2807.htm>ASTM E2807/a> Standard Specification for 3D Imaging Data Exchange (known as theE57 format hereafter)in the C++ language. It is intended to lower the barrier to adoption ofthe standard and to provide a reference to compare other implementations against. It is not expected to be the only implementation, and it isnot intended to be the fastest possible implementation./p> p>The libE57 software consists of a library, supporting utilitiesand example programs, and documentation. The software includes twoseparate application programming interfaces (APIs) for reading, writing, and manipulating E57 files - the Foundation API and the Simple API. The Foundation API is a full-featured interface that operates at arelatively low-level, allowing control over all aspects of an E57 file,including custom extensions. The Simple API is a simplified interface(built on top of the Foundation API) that supports the most common usecases for reading and writing E57 files./p> p>The source code for the libE57 software can be a hrefhttp://www.libe57.org/download.html>downloaded/a> from this web site. Pre-built binaries are provided for a selection ofcompilers and operating systems (OSes). If there is no versionmatching your compiler/OS, it will be necessary to download the sourcecode and compile it yourself. Instructions for both uses are provided./p> h2>Frequently Asked Questions/h2> p classfaq>What is the relationship between the libE57 software and the ASTM E2807 standard?/p> p>The libE57 software is not part of the ASTM standard, nor are the APIs defined within the libE57 software part of the standard. Althoughthe developers of the software were involved in the development of theE57 format standard, the software is not sanctioned or approved in anyway by the ASTM. /p> p classfaq>Do I need a copy of the a hrefhttp://www.astm.org/Standards/E2807.htm>ASTM E2807/a> standard?/p> p>Yes. While it is possible to utilize some aspects of the software without reference to the standard, the standard is an essentialreference that is needed to make full use of the library. In particular, it would be difficult to effectively use the Foundation API withoutreference to the standard, which documents the names, data types, andmeanings of the data structures that compose an E57 file. /p> p>A copy of the latest draft version of the specification can be obtained by a hrefhttp://www.astm.org/COMMIT/COMMITTEE/E57.htm>joining the ASTM E57 committee/a> of the ASTM. The standard is available for purchase via the a hrefhttp://www.astm.org/Standards/E2807.htm>ASTM E2807/a> web site./p> p classfaq>Is the E57 format XML?/p> p>The E57 specification uses a subset of XML that has been extended to support efficient storage of large amounts of binary data. An E57file is encoded as a hierarchical tree structure, some of which isencoded in XML, and some of which is encoded in a binary format that isnot XML. The bulk of the data, including point data and images, isencoded in the binary sections for efficiency. Metadata, such as sensorpose information, is encoded in XML. The binary sections are notembedded in the XML section. Instead, they are located in separatesections of the file and referenced from the XML section./p> p classfaq>Is the E57 format extensible?/p> p> Yes. One of the greatest strengths of E57 is that it was designed to be readily extensible to accommodate new hardware innovations. Using the E57 extension mechanism, hardware developers can differentiate their products and incorporate new features by developing extensions that allow software developers to access additional technological innovations. These extensions provide E57 application developers with new features above and beyond the features specified in the E2807 standard. E57 extensions keep the format current with the latest innovations and technologies. /p> p>Here are some of the extension that have been defined.ul>li>a hrefE57_EXT_surface_normals.txt>NOR -- E57_EXT_surface_normals/a>/li>li>a hrefhttp://www.riegl.com/e57/rlms-extensions-2011.txt>RLMS -- E57_RIEGL_2011/a>/li>li>a hrefhttp://www.libe57.org/E57_LEICA_Camera_Distortion.txt>DIST -- E57_LEICA_Camera_Distortion/a>/li>li>a hrefhttp://www.libe57.org/E57_LEICA_Terrain_Classification.txt>CLASS -- E57_LEICA_Terrain_Classification/a>/li>li>a hrefhttp://www.libe57.org/E57_LEICA_Time_Bounds.txt>TIME -- E57_LEICA_Time_Bounds/a>/li>li>a hrefhttp://www.libe57.org/E57_ZF_InfraredTemperatureC.txt>IR -- E57_ZF_InfraredTemperatureC/a>/li>/ul>/p> p classfaq>What software products have native E57 support?/p> p> ul>a hrefhttp://www.3datdepth.com/?page_id1742>3D at Depth subsea LiDAR software suite/a>/ul> ul>a hrefhttp://www.allpointsystems.com/solutions-bridges.php>Allpoint Scan-time / Allpoint Insight / Allpoint Bridges V1.1.2/a>/ul> ul>a hrefhttp://www.artec3d.com/>Artec Studio V9.0/a>/ul> ul>a hrefhttp://apps.exchange.autodesk.com/ACD/List/Search?productlineACD&querye57&facet&collection>Point Cloud E57 Plug-in (x64,x32) for AutoCAD (Architecture/Mechanical/MEP/Civil 3D) 2013/a>/ul> ul>a hrefhttp://www.bentley.com/en-US/Products/MicroStation/>Bentley MicroStation V8i SS3/a>a hrefhttp://www.pointools.com/products.php> / Pointools Suite/a>/ul> ul>a hrefhttp://www.bluemarblegeo.com/products/global-mapper.php>Blue Marble Geographics Global Mapper v15.0/a>/ul> ul>a hrefhttp://www.calabiyausystems.com>CalabiYau LD3 Studio V6.0/a>/ul> ul>a hrefhttp://www.certainty3d.com>Certainty 3D TopoDOT V5.0/a>/ul> ul>a hrefhttp://www.danielgm.net/cc/>CloudCompare / ccViewer/a>/ul> ul>a hrefhttp://www.euclideon.com/products/converter>Euclideon Geoverse Convert/a>/ul> ul>a hrefhttp://www.faro.com/focus/us/software>Faro SCENE V5.0/a>/ul> ul>a hrefhttp://www.gexcel.homeip.net/Gexcel/Product_Information/R_REC_EN.pdf>Gexcel JRC 3D Reconstructor/a>/ul> ul>a hrefhttp://www.inovx.com/realitylinx.html>Inovx RealityLINx V5.6/a>/ul> ul>a hrefhttp://kubit-software.com/CAD/Products/PointCloud_Laser_Scanner_AutoCAD/laser_scanner_AutoCAD.php>Kubit PointSense/PointCloud/a>/ul> ul>a hrefhttp://www.leica-geosystems.com/en/Leica-Cyclone_6515.htm>Leica Cyclone V7.3.2 / CloudWorx CADD / VR point cloud plug-in/a>/ul> ul>a hrefhttp://www.maptek.com/products/i-site/i-site_studio.html>Maptek I-Site Studio/a>/ul> ul>a hrefhttp://www.optech.com/index.php/product/optech-ilris-scan/>Optech ILRIS Scan/a>/ul> ul>a hrefhttp://lastools.org>Rapidlasso LASTools/a>/ul> ul>a hrefhttp://www.rhino3d.com/download/rhino/5.0/import_e57>Rhinoceros 5.0 E57 File Import plug-in/a>/ul> ul>a hrefhttp://www.riegl.com/products/software-packages/riscan-pro/>Riegl RiScan PRO/a>/ul> ul>a hrefhttp://www.safe.com/>Safe FME 2013/a>/ul> ul>a hrefhttp://www.scalypso.com/>Scalypso Software Suite 2.4/a>/ul> ul>a hrefhttps://www.technet-gmbh.com/en/products/scantra/>Technet Scantra/a>/ul> ul>a hrefhttp://www.topconpositioning.com/products/software/office-applications/scanmaster>Topcon ScanMaster/a>/ul> ul>a hrefhttp://www.trimble.com/3d-laser-scanning/realworks.aspx?dtIDoverview&>Trimble RealWorks V7.2/a>/ul> ul>a hrefhttp://www.zf-laser.com/e_z_f_viewer.html>Z+F LaserControl V8.2/a>/ul> ul>...more coming.../ul> /p> p classfaq>What is the difference between E57 format and LAS?/p> p>The LAS format was developed by the American Society forPhotogrammetry and Remote Sensing (ASPRS) for the purpose of storingLIDAR point data. It is specifically geared toward the needs of theaerial sensing community, though the format can be utilized forterrestrial laser scanner data by ignoring the inapplicable fields. TheE57 format is intended to be a more general format that is well-suitedfor storing data across a variety of application domains. There are anumber of differences in the capabilities of the E57 format as comparedto the LAS format. The E57 format allows users to flexibly choose theinformation associated with each 3D point as well as the number of bitsused to represent the information. In contrast, LAS uses a pre-definedset of fixed-size record types that are specialized for aerial datacollection. The E57 format supports gridded data (i.e., data aligned inregular arrays), multiple coordinate systems (including Cartesian andspherical), embedded images from cameras, built in error detection, andgroupings of points into rows, columns, or user-defined groups. The E57format also defines an extension mechanism that allows users to developcustom capabilities that were not envisioned in the initial design ofthe standard. These extensions could be integrated into future versionsof the standard. Finally, the E57 format has an essentially unlimitedfile size and number of records (1.8E19 bytes in length), whereas theLAS format is limited to 4.2E9 records./p> p classfaq>How can I learn more about the E57 format?/p> p>A good starting point would be to read the overview paper entitled a hrefhttp://www.ri.cmu.edu/publication_view.html?pub_id6767>The ASTM E57 File Format for 3D Imaging Data Exchange/a>. The standard itself contains a much more detailed description. The standard is available for purchase via the a hrefhttp://www.astm.org/Standards/E2807.htm>ASTM E2807/a> web site. Finally, many subtle details of the standard can be best understood by looking at the a hrefhttp://www.libe57.org/documentation.html>API documentation/a>, a hrefhttp://www.libe57.org/example.html>examples/a>, and a hrefhttp://www.libe57.org/download.html>software/a> on this site. /p> p classfaq>Is there a mailing list available?/p> p>Yes, you can go to the a hrefhttps://lists.sourceforge.net/lists/listinfo/e57-3d-imgfmt-devel>subsciption page/a> to sign up. Currently there is only one list for users and developers since the traffic is not very high yet./p> p classfaq>Is there a user group?/p> p>Yes, to be part of the E57 user group join LinkedIn at a hrefhttp://www.linkedin.com/e/-tq0kkz-gqcgnrr5-38/vgh/4010954/>ASTM E57 Data Exchange Format Group/a>br> /p> p classfaq>How can I get involved?/p> p>Joining the ASTM E57.04 sub-committee and become involved in the on going discussions. You can also post to the working ASTM E57 sub-committee, send email to a hrefmailto:astm-e57-data-interoperability@googlegroups.com>astm-e57-data-interoperability@googlegroups.com./a>br> To subscribe to this group, send email to a hrefastm-e57-data-interoperability+subscribe@googlegroups.com>astm-e57-data-interoperability+subscribe@googlegroups.com./a>br> To unsubscribe from this group, send email to a hrefastm-e57-data-interoperability+unsubscribe@googlegroups.com>astm-e57-data-interoperability+unsubscribe@googlegroups.com./a>br>br> To see all the documents, meeting notes, and discussions of the ASTM E57 sub-committee visit a hrefhttp://groups.google.com/group/astm-e57-data-interoperability?hlen>http://groups.google.com/group/astm-e57-data-interoperability?hlen./a> or a hrefhttps://docs.google.com/leaf?id0B65WOJis2TflYWQ1MGUwNGEtODQzNi00NzEwLThmN2EtZGNjYTY2NDc0MGY1&hlen>e57-shared on Google Docs/a>br>br> /p> br> br> br> br> br> br> br> br> br> !---------------------------------------------------------------------------------------> br> br> br> br> br> br> br> br> br> br> br> br> br> br>/p>p aligncenter>This site is © Copyright 2010 E57.04 3D Imaging System File Format Committee, All Rights Reservedbr>a hrefhttp://www.steves-templates.com/ titleFree website templates classstyle2>Free web site templates/a>/p> /td> /tr> /tbody>/table>/td>/tr>/tbody>/table>/body>/html>
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]