Search results

From Wiki.OSArch

Page title matches

Page text matches

  • ...cation MicroMVD]], [[Revit geolocation]], [[ArchiCAD geolocation]] & [[IFC geolocation]]. [[Category:Geolocation]]
    238 bytes (26 words) - 16:45, 11 January 2021
  • ...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) - 10:29, 18 August 2022
  • #REDIRECT [[Revit IFC geolocation]]
    35 bytes (4 words) - 06:45, 23 December 2020
  • #REDIRECT [[ArchiCAD IFC geolocation]]
    38 bytes (4 words) - 06:44, 23 December 2020
  • #REDIRECT [[Talk:ArchiCAD IFC geolocation]]
    43 bytes (5 words) - 06:44, 23 December 2020
  • #REDIRECT [[Talk:Revit IFC geolocation]]
    40 bytes (5 words) - 06:45, 23 December 2020
  • #REDIRECT [[MicroMVDs for exchange requirements/Geolocation MicroMVD]]
    70 bytes (7 words) - 07:21, 28 July 2022
  • #REDIRECT [[Talk:Revit setup for OpenBIM/Revit IFC geolocation]]
    64 bytes (9 words) - 06:39, 31 January 2022
  • #REDIRECT [[Revit setup for OpenBIM/Revit IFC geolocation]]
    59 bytes (8 words) - 06:39, 31 January 2022
  • #REDIRECT [[Industry Foundation Classes (IFC)/IFC geolocation]]
    63 bytes (7 words) - 10:27, 26 July 2022
  • #REDIRECT [[IFC - Industry Foundation Classes/IFC geolocation]]
    63 bytes (8 words) - 06:21, 28 July 2022
  • I suggest that the generic about ifc geolocation be moved to https://wiki.osarch.org/index.php?title=IFC_geolocation [[User:
    197 bytes (29 words) - 06:44, 23 December 2020
  • I suggest that the generic about ifc geolocation be moved to https://wiki.osarch.org/index.php?title=IFC_geolocation [[User:
    244 bytes (38 words) - 06:39, 31 January 2022
  • ...cord metric units correctly for the geolocation map conversion. This makes geolocation useless.
    1 KB (182 words) - 15: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) - 07: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) - 04: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) - 00: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) - 07: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) - 10:04, 17 January 2023
  • =Geolocation / Model far from origin=
    3 KB (410 words) - 06:40, 31 January 2022

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