Search results

From Wiki.OSArch

Page title matches

  • #REDIRECT [[MicroMVDs for exchange requirements/Geolocation MicroMVD]]
    70 bytes (7 words) - 11:21, 28 July 2022
  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. Feature: Geolocation
    5 KB (726 words) - 11:22, 28 July 2022
  • #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
  • #REDIRECT [[Industry Foundation Classes (IFC)/IFC geolocation]]
    63 bytes (7 words) - 14:27, 26 July 2022
  • 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
  • #REDIRECT [[Revit setup for OpenBIM/Revit IFC geolocation]]
    59 bytes (8 words) - 10:39, 31 January 2022
  • ...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 ==
    12 KB (1,678 words) - 04:56, 16 June 2022
  • #REDIRECT [[IFC - Industry Foundation Classes/IFC geolocation]]
    63 bytes (8 words) - 10:21, 28 July 2022
  • ...page by moving generic content from the [[Revit geolocation]] & [[ArchiCAD geolocation]] pages. ...enShell/blob/master/1.%20geolocation.ipynb Interactive Notebook explaining Geolocation]
    723 bytes (83 words) - 14:29, 18 August 2022

Page text matches

  • ...page by moving generic content from the [[Revit geolocation]] & [[ArchiCAD geolocation]] pages. ...enShell/blob/master/1.%20geolocation.ipynb Interactive Notebook explaining Geolocation]
    723 bytes (83 words) - 14:29, 18 August 2022
  • #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
  • #REDIRECT [[MicroMVDs for exchange requirements/Geolocation MicroMVD]]
    70 bytes (7 words) - 11:21, 28 July 2022
  • #REDIRECT [[Revit setup for OpenBIM/Revit IFC geolocation]]
    59 bytes (8 words) - 10:39, 31 January 2022
  • #REDIRECT [[IFC - Industry Foundation Classes/IFC geolocation]]
    63 bytes (8 words) - 10:21, 28 July 2022
  • #REDIRECT [[Industry Foundation Classes (IFC)/IFC geolocation]]
    63 bytes (7 words) - 14:27, 26 July 2022
  • ...cord metric units correctly for the geolocation map conversion. This makes geolocation useless.
    1 KB (182 words) - 19:19, 4 August 2022
  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. Feature: Geolocation
    5 KB (726 words) - 11:22, 28 July 2022
  • 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
  • ...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 ==
    12 KB (1,678 words) - 04:56, 16 June 2022
  • | 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) - 11:22, 28 July 2022
  • ...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,219 words) - 14:04, 17 January 2023
  • =Geolocation / Model far from origin=
    3 KB (410 words) - 10:40, 31 January 2022
  • ...MVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set.
    4 KB (642 words) - 11:22, 28 July 2022
  • * [[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
  • ...ew features compared to IFC2X3, such as improved geometry representations, geolocation support, and more element categories.
    7 KB (992 words) - 21:48, 14 February 2023
  • ...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,618 words) - 10:41, 31 January 2022
  • ...See [[IfcOpenShell code examples]]. Comes with many utility functions for geolocation, data extraction, IFC query filtering, and more.
    12 KB (1,645 words) - 10:09, 1 March 2024
  • ...IFC files. For example, many BIM authoring software packages do not handle geolocation properly and this can be fixed using the patch utility.
    17 KB (2,601 words) - 02:38, 6 July 2023

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