Glue API: Visibility of Company Roster Explained
Happy Father's Day!

Identify Layout Points Coming from Total Station

Here is the first question that I received about Point Layout API.

Q. In the Glue API reference document, I see there are APIs for Point Layout. But it looks to me that they are points of a model only. Do we have any API to get point data coming from Total Station?  

A. The sample response in the documentation for getting points for a model includes the description of each item for a point data. But it does not include actual sample data nor more detailed information. Having a sample with real data might help understand where to look for to identify point coming from a total station. Below are two examples taken from an actual point data in JSON format. The first one shows data that came from a robotic total station. The second is from a model with points generated using Autodesk Point Layout: 

(1)  Example of point data from total station 

Sample Point Data from Total Station
      "id": "1g4bf4b8-0136-4ea6-9fb3-0c29f5382721",
      "created_by": "[email protected]",
      "created_date": "2015-06-19 17:13:57.533",
      "model_id": "81kjhd35-6cc1-446c-b14f-dd3cf3634b24",
      "point_id": "STK7010",
      "point_id_prefix": "STK",
      "point_number": "7010",
      "timestamp": "2015-06-19 17:13:57.000",
      "is_deleted": 0,
      "is_current_version": 1,
      "version_count": 1,
      "description": "east edge of  beam support",
      "x": 185.50102392,
      "y": 174.42560122,
      "z": 57.8104,
      "point_type": "",
      "point_role": "As Built",
      "capture_method": "BPL_Robot",
      "instrument": "Topcon LN-100",
      "device_id": "DC382AC0-549D-43F3-9695-9AD3300FE5F5",
      "notes": "",
      "status": 1,
      "from_pt": "2000",
      "ref_pt": "2001",
      "hi": 5.15,
      "ht": 7.0,
      "horiz": 87.39582335,
      "zenith": 89.45105574,
      "slope": 88.08772802


(2)  Example of point data from Navisworks + Point Layout model:

Sample Point Data from a Model
      "id": "rr8f898f-87e8-4872-9efc-e53b2e017cbb",
      "created_by": "[email protected]",
      "created_date": "2015-06-19 17:13:57.457",
      "model_id": "71e87d75-6dc1-446c-b14f-jj3cf8064b24",
      "point_id": "4016",
      "point_id_prefix": "",
      "point_number": "4016",
      "timestamp": "2015-06-19 17:13:57.000",
      "is_deleted": 0,
      "is_current_version": 1,
      "version_count": 1,
      "description": "Plumbing",
      "x": 191.74036539,
      "y": 172.17597998,
      "z": 57.8104,
      "point_type": "",
      "point_role": "Control Point",
      "capture_method": "APL_Model",
      "instrument": "",
      "device_id": "",
      "notes": "",
      "status": 1,
      "from_pt": "",
      "ref_pt": "",
      "hi": 0.0,
      "ht": 0.0,
      "horiz": 0.0,
      "zenith": 0.0,
      "slope": 0.0


As you can see, there is a “capture_method” property, which says “BPL_Robot” for the point coming from a total station through BIM 360 Layout, while “APL_Model” for the point from the model using Autodesk Point Layout. Notice properties “instrument” and “device_id” are defined in the point data from the total station, while the same properties in the model point have no value defined. 

While on this topic, you may wonder what some of abbreviations stand for. (I certainly did.) Here are a few clarifications I asked the product team:  

  • hi – Height of Instrument
  • ht – Height of Target
  • horiz – Horizontal angle

Another question is about determining when a point is updated. This is done by versioning. When an uploading a point, if an existing model_id/point_id is found, a new version of the point will be created. If no matching model_id/point_id is found, a first version of the point will be created.