<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Schedule out what is already in the database &amp;quot;Offset from Host&amp;quot;&amp;quot; in Revit Structure Forum</title>
    <link>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14210120#M52404</link>
    <description>&lt;P&gt;A practical abutment workflow&lt;/P&gt;&lt;P&gt;For bridge families, I would separate the data into two groups.&lt;/P&gt;&lt;P&gt;1. Design/control data&lt;/P&gt;&lt;P&gt;These are parameters that should drive the family:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Abutment reference RL&lt;/LI&gt;&lt;LI&gt;Skew angle&lt;/LI&gt;&lt;LI&gt;Chainage or station&lt;/LI&gt;&lt;LI&gt;Offset from alignment&lt;/LI&gt;&lt;LI&gt;Abutment type&lt;/LI&gt;&lt;LI&gt;Bearing arrangement&lt;/LI&gt;&lt;LI&gt;Wall height&lt;/LI&gt;&lt;LI&gt;Foundation thickness&lt;/LI&gt;&lt;LI&gt;Element mark&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These should be shared parameters where they must be scheduled or tagged.&lt;/P&gt;&lt;P&gt;2. Derived setting-out data&lt;/P&gt;&lt;P&gt;These are values calculated from the actual geometry:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Easting&lt;/LI&gt;&lt;LI&gt;Northing&lt;/LI&gt;&lt;LI&gt;RL&lt;/LI&gt;&lt;LI&gt;Top RL&lt;/LI&gt;&lt;LI&gt;Bottom RL&lt;/LI&gt;&lt;LI&gt;Left and right extents&lt;/LI&gt;&lt;LI&gt;Bearing centre coordinates&lt;/LI&gt;&lt;LI&gt;Foundation corner coordinates&lt;/LI&gt;&lt;LI&gt;Host or level offset&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These should not be manually typed. They should be calculated automatically and written to schedulable parameters by Dynamo or, preferably for production, a Revit add-in.&lt;/P&gt;&lt;P&gt;Avoiding the “dead field” problem&lt;/P&gt;&lt;P&gt;The dangerous part of the current workflow is not the existence of additional parameters. It is that the parameters can become&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;stale without any visible warning&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;A robust implementation should include fields such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Coordinate Status&lt;/LI&gt;&lt;LI&gt;Last Coordinate Update&lt;/LI&gt;&lt;LI&gt;Updated By&lt;/LI&gt;&lt;LI&gt;Model Revision&lt;/LI&gt;&lt;LI&gt;Geometry Changed&lt;/LI&gt;&lt;LI&gt;QA Check&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The process should be:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Model the abutment and control it with the design parameters.&lt;/LI&gt;&lt;LI&gt;Run an automated coordinate extraction routine.&lt;/LI&gt;&lt;LI&gt;Write the calculated results to shared parameters.&lt;/LI&gt;&lt;LI&gt;Display the status in the schedule.&lt;/LI&gt;&lt;LI&gt;Prevent issue of drawings if any element is marked&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Needs Update&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Unverified.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;A Dynamo script can perform the extraction and update process. It should be run manually at controlled milestones rather than continuously, because an uncontrolled automatic script can create unexpected changes in a production model. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule XYZ Shared Coordinates of Elements&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a larger design office, a purpose-built add-in is generally safer because it can handle different element location types, report failures, apply shared-coordinate transformations, and provide a validation report. Commercial tools already demonstrate that this type of scheduleable coordinate extraction is technically feasible. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule Coordinates of Setting-Out Points Fast!&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;+ 1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use defined setting-out points—not just the family origin&lt;/P&gt;&lt;P&gt;For an abutment, “coordinate” needs a precise definition. It could refer to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Family insertion point&lt;/LI&gt;&lt;LI&gt;Abutment centreline&lt;/LI&gt;&lt;LI&gt;Bearing centre&lt;/LI&gt;&lt;LI&gt;Front-left corner&lt;/LI&gt;&lt;LI&gt;Back-left corner&lt;/LI&gt;&lt;LI&gt;Foundation corner&lt;/LI&gt;&lt;LI&gt;Alignment intersection&lt;/LI&gt;&lt;LI&gt;A survey setting-out point&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The best bridge-specific approach is to embed named reference markers in the family—for example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ABT-01-CL&lt;/LI&gt;&lt;LI&gt;ABT-01-BRG-01&lt;/LI&gt;&lt;LI&gt;ABT-01-BRG-02&lt;/LI&gt;&lt;LI&gt;ABT-01-FOUND-01&lt;/LI&gt;&lt;LI&gt;ABT-01-FOUND-02&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Constrain these markers to the relevant geometry. When the abutment changes, the markers move with it. The automation then reads their coordinates and writes them to fields such as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;X1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Y1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Z1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;X2,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Y2, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Z2. This is much more reliable than manually entering four sets of corner coordinates. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule Coordinates of Setting-Out Points Fast!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recommended schedule structure&lt;/P&gt;&lt;P&gt;A setting-out schedule might contain:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;Field Purpose &lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Abutment Mark&lt;/TD&gt;&lt;TD&gt;Identifies the element&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Point ID&lt;/TD&gt;&lt;TD&gt;Identifies the reference point&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Easting&lt;/TD&gt;&lt;TD&gt;Shared-coordinate X value&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Northing&lt;/TD&gt;&lt;TD&gt;Shared-coordinate Y value&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;RL&lt;/TD&gt;&lt;TD&gt;Reduced level&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Point Type&lt;/TD&gt;&lt;TD&gt;Centreline, bearing, corner, etc.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Coordinate Status&lt;/TD&gt;&lt;TD&gt;Current, stale, or failed&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Last Updated&lt;/TD&gt;&lt;TD&gt;QA traceability&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN class=""&gt;Exportar&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN class=""&gt;Copiar&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;For native Revit schedules, these values need to exist as parameters. Revit’s built-in coordinate data cannot simply be added to every schedule as universal calculated fields. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;General Features &amp;gt; Tools &amp;gt; Extract Coordinate - CADtools Revit&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;+ 1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What Autodesk should add&lt;/P&gt;&lt;P&gt;The requested feature should be broader than just adding X, Y, and Z fields. Native Revit should provide scheduleable, category-independent access to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Project-coordinate Easting and Northing&lt;/LI&gt;&lt;LI&gt;Shared-coordinate Easting and Northing&lt;/LI&gt;&lt;LI&gt;Elevation/RL&lt;/LI&gt;&lt;LI&gt;Top, centre, and bottom elevations&lt;/LI&gt;&lt;LI&gt;Offset from host&lt;/LI&gt;&lt;LI&gt;Offset from level&lt;/LI&gt;&lt;LI&gt;Location point and location curve&lt;/LI&gt;&lt;LI&gt;Coordinates of nominated family reference points&lt;/LI&gt;&lt;LI&gt;Coordinates of nested shared components&lt;/LI&gt;&lt;LI&gt;Linked-model coordinates&lt;/LI&gt;&lt;LI&gt;Coordinate-system identification&lt;/LI&gt;&lt;LI&gt;A stale-data or model-change warning&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The critical requirement is that the schedule should identify&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;which reference point and coordinate system&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;generated each value. Otherwise, a coordinate may be numerically correct but unsuitable for setting out.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jul 2026 17:49:04 GMT</pubDate>
    <dc:creator>jose_Miquelao</dc:creator>
    <dc:date>2026-07-23T17:49:04Z</dc:date>
    <item>
      <title>Schedule out what is already in the database "Offset from Host""</title>
      <link>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14201043#M52327</link>
      <description>&lt;P&gt;I find it frustrating that I need to keep figuring out workarounds to schedule out data that is already used to drive elements in my model.&lt;BR /&gt;I work in Transport / Bridges, and we always need coordinates and levels on drawings&lt;BR /&gt;The data is there but I can't get them added to native Revit schedules. This causes errors and lots of double handling to get things on drawings and reported to other parties&lt;BR /&gt;&lt;BR /&gt;Why do we still not have the ability to schedule out coordinates and offset from host / Levels form all categories&lt;BR /&gt;in today's example I build a Abutment I easily control RL for by input of a single RL, but it is impossible to schedule it out to a drawing!!!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Please Autodesk none of the engineers I work for care about my frustrations anymore and the tool is not making my life any easier.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Mario_LeRoux_0-1784149314527.png" style="width: 400px;"&gt;&lt;img src="https://forums.autodesk.com/t5/image/serverpage/image-id/1651094iFD8C96EF023D40EE/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Mario_LeRoux_0-1784149314527.png" alt="Mario_LeRoux_0-1784149314527.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Now I need to imbed additional elements, add dummy fields, populate said fields, and schedule out dead crap to drawings that will be a RFI in 3 days because someone forgot to update a dead field after making a change.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2026 21:03:46 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14201043#M52327</guid>
      <dc:creator>Mario_LeRoux</dc:creator>
      <dc:date>2026-07-15T21:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: Schedule out what is already in the database "Offset from Host""</title>
      <link>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14210120#M52404</link>
      <description>&lt;P&gt;A practical abutment workflow&lt;/P&gt;&lt;P&gt;For bridge families, I would separate the data into two groups.&lt;/P&gt;&lt;P&gt;1. Design/control data&lt;/P&gt;&lt;P&gt;These are parameters that should drive the family:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Abutment reference RL&lt;/LI&gt;&lt;LI&gt;Skew angle&lt;/LI&gt;&lt;LI&gt;Chainage or station&lt;/LI&gt;&lt;LI&gt;Offset from alignment&lt;/LI&gt;&lt;LI&gt;Abutment type&lt;/LI&gt;&lt;LI&gt;Bearing arrangement&lt;/LI&gt;&lt;LI&gt;Wall height&lt;/LI&gt;&lt;LI&gt;Foundation thickness&lt;/LI&gt;&lt;LI&gt;Element mark&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These should be shared parameters where they must be scheduled or tagged.&lt;/P&gt;&lt;P&gt;2. Derived setting-out data&lt;/P&gt;&lt;P&gt;These are values calculated from the actual geometry:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Easting&lt;/LI&gt;&lt;LI&gt;Northing&lt;/LI&gt;&lt;LI&gt;RL&lt;/LI&gt;&lt;LI&gt;Top RL&lt;/LI&gt;&lt;LI&gt;Bottom RL&lt;/LI&gt;&lt;LI&gt;Left and right extents&lt;/LI&gt;&lt;LI&gt;Bearing centre coordinates&lt;/LI&gt;&lt;LI&gt;Foundation corner coordinates&lt;/LI&gt;&lt;LI&gt;Host or level offset&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These should not be manually typed. They should be calculated automatically and written to schedulable parameters by Dynamo or, preferably for production, a Revit add-in.&lt;/P&gt;&lt;P&gt;Avoiding the “dead field” problem&lt;/P&gt;&lt;P&gt;The dangerous part of the current workflow is not the existence of additional parameters. It is that the parameters can become&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;stale without any visible warning&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;A robust implementation should include fields such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Coordinate Status&lt;/LI&gt;&lt;LI&gt;Last Coordinate Update&lt;/LI&gt;&lt;LI&gt;Updated By&lt;/LI&gt;&lt;LI&gt;Model Revision&lt;/LI&gt;&lt;LI&gt;Geometry Changed&lt;/LI&gt;&lt;LI&gt;QA Check&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The process should be:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Model the abutment and control it with the design parameters.&lt;/LI&gt;&lt;LI&gt;Run an automated coordinate extraction routine.&lt;/LI&gt;&lt;LI&gt;Write the calculated results to shared parameters.&lt;/LI&gt;&lt;LI&gt;Display the status in the schedule.&lt;/LI&gt;&lt;LI&gt;Prevent issue of drawings if any element is marked&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Needs Update&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Unverified.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;A Dynamo script can perform the extraction and update process. It should be run manually at controlled milestones rather than continuously, because an uncontrolled automatic script can create unexpected changes in a production model. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule XYZ Shared Coordinates of Elements&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a larger design office, a purpose-built add-in is generally safer because it can handle different element location types, report failures, apply shared-coordinate transformations, and provide a validation report. Commercial tools already demonstrate that this type of scheduleable coordinate extraction is technically feasible. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule Coordinates of Setting-Out Points Fast!&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;+ 1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use defined setting-out points—not just the family origin&lt;/P&gt;&lt;P&gt;For an abutment, “coordinate” needs a precise definition. It could refer to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Family insertion point&lt;/LI&gt;&lt;LI&gt;Abutment centreline&lt;/LI&gt;&lt;LI&gt;Bearing centre&lt;/LI&gt;&lt;LI&gt;Front-left corner&lt;/LI&gt;&lt;LI&gt;Back-left corner&lt;/LI&gt;&lt;LI&gt;Foundation corner&lt;/LI&gt;&lt;LI&gt;Alignment intersection&lt;/LI&gt;&lt;LI&gt;A survey setting-out point&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The best bridge-specific approach is to embed named reference markers in the family—for example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ABT-01-CL&lt;/LI&gt;&lt;LI&gt;ABT-01-BRG-01&lt;/LI&gt;&lt;LI&gt;ABT-01-BRG-02&lt;/LI&gt;&lt;LI&gt;ABT-01-FOUND-01&lt;/LI&gt;&lt;LI&gt;ABT-01-FOUND-02&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Constrain these markers to the relevant geometry. When the abutment changes, the markers move with it. The automation then reads their coordinates and writes them to fields such as&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;X1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Y1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Z1,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;X2,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Y2, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Z2. This is much more reliable than manually entering four sets of corner coordinates. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;Revit Snippet: Schedule Coordinates of Setting-Out Points Fast!&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recommended schedule structure&lt;/P&gt;&lt;P&gt;A setting-out schedule might contain:&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;Field Purpose &lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Abutment Mark&lt;/TD&gt;&lt;TD&gt;Identifies the element&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Point ID&lt;/TD&gt;&lt;TD&gt;Identifies the reference point&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Easting&lt;/TD&gt;&lt;TD&gt;Shared-coordinate X value&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Northing&lt;/TD&gt;&lt;TD&gt;Shared-coordinate Y value&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;RL&lt;/TD&gt;&lt;TD&gt;Reduced level&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Point Type&lt;/TD&gt;&lt;TD&gt;Centreline, bearing, corner, etc.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Coordinate Status&lt;/TD&gt;&lt;TD&gt;Current, stale, or failed&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Last Updated&lt;/TD&gt;&lt;TD&gt;QA traceability&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN class=""&gt;Exportar&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN class=""&gt;Copiar&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;For native Revit schedules, these values need to exist as parameters. Revit’s built-in coordinate data cannot simply be added to every schedule as universal calculated fields. &amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;SPAN class=""&gt;General Features &amp;gt; Tools &amp;gt; Extract Coordinate - CADtools Revit&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;+ 1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What Autodesk should add&lt;/P&gt;&lt;P&gt;The requested feature should be broader than just adding X, Y, and Z fields. Native Revit should provide scheduleable, category-independent access to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Project-coordinate Easting and Northing&lt;/LI&gt;&lt;LI&gt;Shared-coordinate Easting and Northing&lt;/LI&gt;&lt;LI&gt;Elevation/RL&lt;/LI&gt;&lt;LI&gt;Top, centre, and bottom elevations&lt;/LI&gt;&lt;LI&gt;Offset from host&lt;/LI&gt;&lt;LI&gt;Offset from level&lt;/LI&gt;&lt;LI&gt;Location point and location curve&lt;/LI&gt;&lt;LI&gt;Coordinates of nominated family reference points&lt;/LI&gt;&lt;LI&gt;Coordinates of nested shared components&lt;/LI&gt;&lt;LI&gt;Linked-model coordinates&lt;/LI&gt;&lt;LI&gt;Coordinate-system identification&lt;/LI&gt;&lt;LI&gt;A stale-data or model-change warning&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The critical requirement is that the schedule should identify&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;which reference point and coordinate system&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;generated each value. Otherwise, a coordinate may be numerically correct but unsuitable for setting out.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2026 17:49:04 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14210120#M52404</guid>
      <dc:creator>jose_Miquelao</dc:creator>
      <dc:date>2026-07-23T17:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: Schedule out what is already in the database "Offset from Host""</title>
      <link>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14212744#M52406</link>
      <description>&lt;P&gt;Thanks for the detailed answer &lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/19001131"&gt;@jose_Miquelao&lt;/a&gt;. Hope most of this has not been AI generated:)&amp;nbsp;&lt;BR /&gt;Looks like I already do what has been suggested here. This does not remove frustration with a BIM software that won't provide proper access to the basic building blocks of the information required to document and drive placement of elements natively&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 26 Jul 2026 19:58:01 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/revit-structure-forum/schedule-out-what-is-already-in-the-database-quot-offset-from/m-p/14212744#M52406</guid>
      <dc:creator>Mario_LeRoux</dc:creator>
      <dc:date>2026-07-26T19:58:01Z</dc:date>
    </item>
  </channel>
</rss>

