Differences

This shows you the differences between two versions of the page.

--- agtek_-_leica_synergy_notes [2018/09/20 17:10]
mdransom
+++ agtek_-_leica_synergy_notes [2018/11/07 23:40] (current)
mikeclapp [KMZ Export support for ConX]
@@ Line 41: / Line 41: @@
   * With Upload to ConX set to Yes the unique part of the interface appears. With ConX the user has to:
-       * login/authenticate (can we cache the tokens/values? Are we doing a third party integration?)
+       * login/authenticate . The image matches the naming conventions of Conx ie Username. We have to display this everytime for changing but can store the remembered value if the user chooses to.(can we cache the tokens/values? Are we doing a third party integration?)
+       * {{::loginscreen.jpg?400|}}
        * Select the project (GET /api/one/v1/builders/{company uuid}/projects/?recursive=1) This is derivative from our existing project selection. It looks like creation of new projects is also API supported.
@@ Line 48: / Line 49: @@
        * Choose the unit and/or machine type. For example you might send a machine file to all the excavators or just a single named dozer. (A tree control with checkboxes organized by type then individual units might be an appropriate method.
        * Press Upload and Assign to start the uploading.
+**9-27-18 Apparently the New Project functionality was never implemented in the API. Leave the New project button out on the select Project Dialog for now. If they choose to implement it (I gave them use cases) we can add it back in to match the Access upload**
@@ Line 57: / Line 60: @@
 There's also a specification by machine type but that might be better represented by the tree referenced above.
+After meetings with the ConX guys it's apparent they're also going to want our KMZ outputs although they need to extend their KMZ reader to handle image overlays and the CData property sheet info. Besides adding ConX as an option the only to the data flow may be to ask the user to designate what they want to use it for (Background image, etc.) While ConX attempts to identify the data type coming into the system there are cases where the user supplying the data needs to designate it. That is not clear now and before we implement any interface to support it, we will need to be supplied the logical types.
@@ Line 104: / Line 109: @@
 Processing Drone data for photogrammetry
-API's for a roll your own construction version due beginning of 2019
+We have a version of Infinity in the office and it's fairly complex and probably more suitable for a surveyor at this point. Sort of a huge Swiss army knife that spans all of their sensors. Initial impressions it that the default values do excessive vertical filtering and we'll need to figure out which adjustment of many can be used to adjust it.
+I have no doubt this software does everything correctly but it is challenging. Too much so for the average US construction customer.
+API's for a roll your own construction version due beginning of 2019. 9-27-18 This turns out to be more about them creating a web interface for this functionality. I offered to look at early versions for suggestions on simplification. They're aiming this at the UAV market so it should be simpler.
@@ Line 115: / Line 126: @@
 Possible rebranding/renaming to Icon Office mobile for Leica customers?
+====== Earthmover Tracking points from ConX =======
+The M20 job has both AGTEK trackers and the ConX Earthmover Ipad on CAT801 for 10-12-2018. The Track under "Track - Location History" looks like a series of points representing a track. There was some question of whether we could read these as tracks. The more that I look at the data compared to the same track we captured I realize that the lines are probably just a vector between the pickup and dump points. If I try to pick any of those points on the screen it looks like it actually goes to the single points at the end of the lines. Frankly I'd represent them as an icon with matching numbers for load and dump because the vectors add to the busyness.
+====== KMZ Export support for ConX =======
+ConX currently has limited support for KMZ. They don't support the image overlay object which precludes them from displaying plan sheets or cut/fill colors. Their intention is to do so since they already support KMZ linework, placemarks(?) and closed polygons. It doesn't appear that they support any html view of the property sheets either.
+===== AGTEK Export of KMZ to ConX =====
+The interface challenge for export is that the KMZ export already has an export to Access option and our

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools