Embedded Files
GIS Pipe Inspection Gas/Water
Build as App Variant on Albion in C++.
Lead Architect and Solo Programmer, was Software Architect, Database Architecture and Design and UI designs and CAD Tooling features designs, user interaction design and implementation, Design of CAD themes and implementation. Developer, Programmed all supporting routines for functionary and alignment features. Wrote Documentation and Manual, had a new colleague checking documents for spelling, then bundled it into software and build installers using my existing revamped abstract installer builder for all applications variants and sent the final installer package to Pure in the USA.
Features:
- Interpreted all their various supplied Robotic Datasets and design an abstracted single format Database persistent storage schema for everything
- Generic Import Tools, Dialog Capture Robotic Dataset Configuration and mapping to abstracted format.
1. Existing Water/Gas Pipe line.
2. Robotic Inspection datasets, that would be overlayed and aligned to Best known GIS/Lat, Lon pipe route.
- GIS Visual generation algorithm, that would generate GIS Geometry for the Raw dataset.
Having different modes of alignment for compress/stretch, non adjustments left aligned.
Computed all the relative errors percentages and adjusted relative size length extra.
- GIS CAD alignment tooling, for constraining different pipe sections to know Lat, Long and existing pipe features. 3 hours versus 1 day estimate, followed by myself testing it in the USA together with the reset of the week having late nights to 2am in hotel + break to watch independence day fireworks rush at 5pm + Sat, for all 5/7 corner cases, which required identifying crash or bugs. To solve each required a re-write of the CAD tool relook at preparation of all data lookups and required projection loaded into a structure way to allow the CAD to be able have all data need to different permutation the tool be used in, i.e node align to another node within 3,2,1 segment of each other, start and end Majors, as well when skipping nodes and Major nodes start and ends of datasets.
- Grid display import errors, running in the background had a full Error Log roll up process, that could provide context and a list of imported record errors, to identify the issues, in case some later added field constraint or trigger, that could cause a record to not be imported(error), a grid would display with providing all the context to know which record and what the issues was, so could be fixed and re-imported.
Page updated
Google Sites
Report abuse