-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Source commit: 2e89e8f Nikola version: 8.3.0
- Loading branch information
Unknown
committed
Apr 23, 2024
1 parent
ca1f426
commit 93ea1cf
Showing
23 changed files
with
96 additions
and
96 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Dion Moult)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/dion-moult.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:48:00 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenShell to parse IFC files with Python</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-to-parse-ifc-files-with-python/</link><dc:creator>Dion Moult</dc:creator><description><blockquote> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Dion Moult)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/dion-moult.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:53:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenShell to parse IFC files with Python</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-to-parse-ifc-files-with-python/</link><dc:creator>Dion Moult</dc:creator><description><blockquote> | ||
| <p>IFC is the ISO standard format for storing BIM data. IfcOpenShell is a project that has a Python library that allows you to parse IFC files...</p> | ||
| </blockquote> | ||
| <p><a href="https://thinkmoult.com/using-ifcopenshell-parse-ifc-files-python.html">Continue reading on thinkmoult.com</a></p></description><guid>https://academy.ifcopenshell.org/posts/using-ifcopenshell-to-parse-ifc-files-with-python/</guid><pubDate>Tue, 12 Feb 2019 09:14:00 GMT</pubDate></item></channel></rss> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Emiel van Strien)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/emiel-van-strien.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:48:00 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenshell and pythonOCC to generate cross sections directly from an IFC file</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-pythonocc-to-generate-cross-sections-directly-from-an-ifc-file/</link><dc:creator>Emiel van Strien</dc:creator><description><div><p>[This article contains several snippets of source code for illustration purposes, the full source code can be downloaded at the bottom]</p> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Emiel van Strien)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/emiel-van-strien.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:53:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenshell and pythonOCC to generate cross sections directly from an IFC file</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-pythonocc-to-generate-cross-sections-directly-from-an-ifc-file/</link><dc:creator>Emiel van Strien</dc:creator><description><div><p>[This article contains several snippets of source code for illustration purposes, the full source code can be downloaded at the bottom]</p> | ||
| <p>Section information can be used for multiple purposes. This example is the first part of a project in which the aim is to be able to directly send information to a large 3D concrete printer. This printer will be able to print concrete buildings on a 1:1 scale on a building site. The goal is to control the printer directly from an IFC model. Since the printer will print one layer at a time, the first step is to derive section information from an IFC file. This is what this tutorial is about. As an example of the information that can be deduced from a section, the area that needs to be printed is calculated.</p> | ||
| <p>This example builds upon some of the concepts in "Using IfcOpenShell and pythonOCC to construct new geometry" and uses the same model of a simple house, called <a href="http://blog.ifcopenshell.org/2012/11/say-hi-to-ifcopenhouse.html">IfcOpenHouse</a>.</p> | ||
| <p><a href="https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-pythonocc-to-generate-cross-sections-directly-from-an-ifc-file/">Read more…</a> (6 min remaining to read)</p></div></description><category>IfcOpenShell</category><category>python</category><category>PythonOCC</category><guid>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-pythonocc-to-generate-cross-sections-directly-from-an-ifc-file/</guid><pubDate>Wed, 04 Mar 2015 03:39:00 GMT</pubDate></item></channel></rss> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Francisco Navarrete Mandly)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/francisco-navarrete-mandly.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:48:00 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenShell and C++ to generate Alignments through the IFC 4x1 schema</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-c%2B%2B-to-generate-alignments-through-the-ifc-4x1-schema/</link><dc:creator>Francisco Navarrete Mandly</dc:creator><description><div><p><em>IfcOpenShell</em> has an <a href="https://github.com/IfcOpenShell/IfcOpenShell/tree/master/src/ifcexpressparser#readme">EXPRESS parser and code generator</a> that generates code for the various IFC schemas. As part of the source code repository comes pre-generated code for the two widely used versions IFC2X3 and IFC4. But arbitrary schemas can be fed into the parser to provide support for other schemas at compile time. This post highlights the process of generating code for other schemas and talks about the recent developments within the IFC Alignment project._</p> | ||
| <?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IfcOpenShell Academy (Posts by Francisco Navarrete Mandly)</title><link>https://academy.ifcopenshell.org/</link><description></description><atom:link href="https://academy.ifcopenshell.org/authors/francisco-navarrete-mandly.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 <a href="mailto:thomas@aecgeeks.com">Thomas Krijnen</a> </copyright><lastBuildDate>Tue, 23 Apr 2024 14:53:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using IfcOpenShell and C++ to generate Alignments through the IFC 4x1 schema</title><link>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-c%2B%2B-to-generate-alignments-through-the-ifc-4x1-schema/</link><dc:creator>Francisco Navarrete Mandly</dc:creator><description><div><p><em>IfcOpenShell</em> has an <a href="https://github.com/IfcOpenShell/IfcOpenShell/tree/master/src/ifcexpressparser#readme">EXPRESS parser and code generator</a> that generates code for the various IFC schemas. As part of the source code repository comes pre-generated code for the two widely used versions IFC2X3 and IFC4. But arbitrary schemas can be fed into the parser to provide support for other schemas at compile time. This post highlights the process of generating code for other schemas and talks about the recent developments within the IFC Alignment project._</p> | ||
| <p><img alt="Illustration of an alignment as exchanged in IFC" src="https://academy.ifcopenshell.org/images/alignment.png"></p> | ||
| <p><a href="https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-c%2B%2B-to-generate-alignments-through-the-ifc-4x1-schema/">Read more…</a> (2 min remaining to read)</p></div></description><category>C++</category><category>EXPRESS</category><category>IfcOpenShell</category><guid>https://academy.ifcopenshell.org/posts/using-ifcopenshell-and-c%2B%2B-to-generate-alignments-through-the-ifc-4x1-schema/</guid><pubDate>Sun, 21 May 2017 08:03:00 GMT</pubDate></item></channel></rss> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.