Search results

From Wiki.OSArch

Page title matches

  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. Feature: Geolocation
    5 KB (726 words) - 06:05, 7 April 2021
  • ...page by moving generic content from the [[Revit geolocation]] & [[ArchiCAD geolocation]] pages. {{Geolocation}}
    588 bytes (70 words) - 20:44, 11 January 2021
  • #REDIRECT [[ArchiCAD IFC geolocation]]
    38 bytes (4 words) - 10:44, 23 December 2020
  • #REDIRECT [[Revit IFC geolocation]]
    35 bytes (4 words) - 10:45, 23 December 2020
  • ...our project is primarily vertical, i.e. only one CRS is used, then setting geolocation data is relatively straightforward. If the project is primarily horizontal, == IFC2X3 Geolocation ==
    11 KB (1,582 words) - 19:09, 25 April 2021
  • This guide describes the process to meet the IFC geolocation MVD requirement from '''Archicad (versions 23 and 24)'''. ...the IFC4 schema meets the MVD requirement by locating the data in specific geolocation entities. While IFC 2x3 doesn't include these entities, it does still expor
    3 KB (495 words) - 08:04, 20 September 2021

Page text matches

  • ...page by moving generic content from the [[Revit geolocation]] & [[ArchiCAD geolocation]] pages. {{Geolocation}}
    588 bytes (70 words) - 20:44, 11 January 2021
  • #REDIRECT [[ArchiCAD IFC geolocation]]
    38 bytes (4 words) - 10:44, 23 December 2020
  • #REDIRECT [[Revit IFC geolocation]]
    35 bytes (4 words) - 10:45, 23 December 2020
  • ...cord metric units correctly for the geolocation map conversion. This makes geolocation useless.
    1 KB (178 words) - 02:23, 12 April 2021
  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. Feature: Geolocation
    5 KB (726 words) - 06:05, 7 April 2021
  • ...our project is primarily vertical, i.e. only one CRS is used, then setting geolocation data is relatively straightforward. If the project is primarily horizontal, == IFC2X3 Geolocation ==
    11 KB (1,582 words) - 19:09, 25 April 2021
  • This guide describes the process to meet the IFC geolocation MVD requirement from '''Archicad (versions 23 and 24)'''. ...the IFC4 schema meets the MVD requirement by locating the data in specific geolocation entities. While IFC 2x3 doesn't include these entities, it does still expor
    3 KB (495 words) - 08:04, 20 September 2021
  • | See the [[Geolocation MicroMVD]] for caveats related to federating geolocated data. | See the [[Geolocation MicroMVD]] for caveats related to federating geolocated data.
    3 KB (426 words) - 09:21, 20 March 2021
  • ...Topography</code> is exported as <code>IfcSite</code>, to allow for IFC2X3 geolocation to occur. ...itions to overcome shortcomings in the Autodesk version, in particular for geolocation and type vs instance parameter name clashes. Many of these parameters will
    8 KB (1,205 words) - 12:15, 19 July 2021
  • =Geolocation / Model far from origin=
    3 KB (406 words) - 08:29, 11 June 2021
  • * [[IFC geolocation|How georeferencing data is stored in IFC]] * [[Revit geolocation|How to geolocate models from Revit]]
    7 KB (1,027 words) - 09:17, 16 October 2021
  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set.
    4 KB (642 words) - 09:25, 20 March 2021
  • ...ew features compared to IFC2X3, such as improved geometry representations, geolocation support, and more element categories. However, IFC4 support is less promine
    4 KB (641 words) - 07:18, 3 May 2021
  • * [[IFC geolocation|¿Cómo IFC almacena datos de georeferencia?]] * [[Revit geolocation|¿Cómo geolocalizar modelos en Revit?]]
    8 KB (1,215 words) - 00:20, 12 January 2021
  • * [[Geolocation MicroMVD]]
    6 KB (859 words) - 23:38, 22 June 2021
  • ...ing your <code>IfcSite</code> object representation as detailed in [[Revit geolocation]], the procedure is slightly different. Do not implement both procedures si
    11 KB (1,616 words) - 10:46, 23 December 2020
  • ...See [[IfcOpenShell code examples]]. Comes with many utility functions for geolocation, data extraction, IFC query filtering, and more.
    8 KB (1,032 words) - 09:14, 17 June 2021
  • ...their quirks in their IFC files. Currently enabled for Revit’s lack of IFC geolocation and funny materials. This should help a lot of people who aren’t aware th ...tralasia co-founder @john.mitchell - it tests basic project attributes and geolocation for both IFC2X3 and IFC4.
    102 KB (15,906 words) - 02:31, 7 June 2021

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)