November 4th, 2016 was a day to remember, as Autodesk had just released a 16.2 revision to Civil3D that provided what initially appeared to be some useful improvements to the Civil3D API (Application Programming Interface). A couple years before (11-29-2014) we had requested several improvements to the API to allow the creation and editing of FeatureLines on a level similar to polylines.
As we investigated further we come to realize that it fell far short of what we had requested, especially in two areas (in order of importance).
- Vertex editing still could not be accomplished. There is no SetPiPoint method and the combination of DeletePiPoint and InsertPiPoint cannot be used to change (all) the points. Since there is no INDEX parameter on these they are of limited use anyway?
- You still could not create a new FeatureLine. The only method available is to create a database resident polyline (in a separate transaction) then convert it to a FeatureLine. Perhaps an overload to the FeatureLine.Create function that accepts the Point Collection and optionally the bulge data?
Little did we know that was the last time Autodesk would even attempt to improve the .NET API, even though holes remained in areas (like Parcels & Catchments) big enough to drive a 40-ton rock truck into. This brings us to the sad point where the title of this post (and this image) fits.
There was a time (especially in the beginning) when Autodesk listened closely to third party developers and actively recruited their contributions. Even through the times when Autodesk chose to include (or buy) functionality they provided, third party developers pushed on with new improvements and the hope of a richer environment (API) where that could fill the holes left by the giants footsteps.
While that hope remains for now on standard AutoCAD (and the maturing clones), it’s time to give up on the Civil3D API. Pay our last respects because … it’s dead.