Infrastructure Modeling DevBlog

Index - Autodesk Infrastructure Map Server(AIMS) API Training Materials

By Daniel Du

I am always asked where the AIMS API training materials are, actually they are posted to ADN Devblogs long time ago, you may find some of them by Google search. But they may scattered in different blog posts, for convenience, I compose this index, it just direct to each post:

 

DevTV and Code Sample: create temporary layer, feature editing

 

• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-1

• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-2
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-3
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-4
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-5
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-6
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-7
• Autodesk Infrastructure Map Server(AIMS) API Training content : Part-8

 

It maybe kind of out-dated as software versions are increasing, but the API should be compatible. If should be not difficult to apply them to new versions. Hope this helps some.

Change surface style with Civil 3D API

By Daniel Du

I was asked how to edit the style of surface in Civil 3D, for example, we need to change the color of contours. We can do it with Civil 3D UI by right clicking the surface object and choose “Edit surface style…” and switching to “Display” tab to show the dialogue as below:

This is code snippet demonstrating how to do it with API:

[CommandMethod("MyGroup", "SurfaceStyleExample", 
    "SurfaceStyleExample", CommandFlags.Modal)]
public void MyCommand() // This method can have any name
{
 
    Document doc = Application.DocumentManager.MdiActiveDocument;
    
    if (doc != null)
    {
        Editor ed = Application.DocumentManager
            .MdiActiveDocument.Editor;
 
        
 
        // select a tin surface
 
        PromptEntityOptions peo = new PromptEntityOptions(
          "\nSelect a tin surface: ");
        peo.SetRejectMessage("\nOnly Tin surface is accepted");
        peo.AddAllowedClass(typeof(TinSurface), true);
        PromptEntityResult per = ed.GetEntity(peo);
        if (per.Status != PromptStatus.OK) return;
 
        CivilDocument civilDoc = CivilApplication.ActiveDocument;
 
        using (Transaction trans = doc.TransactionManager
            .StartTransaction())
        {
            TinSurface surface = trans.GetObject(per.ObjectId, 
                OpenMode.ForRead) as TinSurface;
 
            //exclude invalid points
 
            surface.BuildOptions.ExecludeMaximumElevation = true;
            surface.BuildOptions.MaximumElevation = 5000;
            surface.BuildOptions.ExecludeMinimumElevation = true;
            surface.BuildOptions.MinimumElevation = 200;
 
            //set the Maximum Triangle Length
 
            surface.BuildOptions.MaximumTriangleLength = 200;
 
            //change the style
            ObjectId styleId;
            if (civilDoc.Styles.SurfaceStyles.Contains("Standard"))
            {
                styleId = civilDoc.Styles.SurfaceStyles["Standard"];
            }
            else
            {
                // create a new style called 'example style':
                styleId = civilDoc.Styles.SurfaceStyles
                    .Add("example style");
 
            }
            
            
 
            // modify the style
 
            SurfaceStyle surfaceStyle = styleId.GetObject(
                OpenMode.ForWrite) as SurfaceStyle;
 
            //countours smoothing 
 
            surfaceStyle.ContourStyle.SmoothContours = true;
            surfaceStyle.ContourStyle.SmoothingType 
                = ContourSmoothingType.AddVertices;
            surfaceStyle.ContourStyle.SmoothingFactor = 10;
 
            surfaceStyle.ContourStyle.MajorContourColorScheme 
                = ColorSchemeType.Rainbow;
 
            //Major contour, red
 
            surfaceStyle.GetDisplayStylePlan(
                SurfaceDisplayStyleType.MajorContour).Color 
                = Autodesk.AutoCAD.Colors.Color.FromRgb(255, 0, 0);
 
            //Major contour, layer 0
 
            surfaceStyle.GetDisplayStylePlan(
                SurfaceDisplayStyleType.MajorContour).Layer = "0";
 
            //Mainor contour, gree
 
            surfaceStyle.GetDisplayStylePlan(
                SurfaceDisplayStyleType.MinorContour).Color 
                = Autodesk.AutoCAD.Colors.Color.FromRgb(0, 255, 0);
 
            //Mainor contour, layer 0
 
            surfaceStyle.GetDisplayStylePlan(
                SurfaceDisplayStyleType.MajorContour).Layer = "0";
 
            // display major contours:
 
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .MajorContour).Visible = true;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .MinorContour).Visible = true;
 
            // turn off display of other items:
            
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .UserContours).Visible = false;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .Directions).Visible = false;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .Elevations).Visible = false;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .Slopes).Visible = false;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .SlopeArrows).Visible = false;
            surfaceStyle.GetDisplayStylePlan(SurfaceDisplayStyleType
                .Watersheds).Visible = false;
 
            //TODO: do the same for all model display settings as well
            //
 
 
            // assign the style to the first surface in the document:
           
            surface.StyleId = styleId;
 
            // commit the transaction
 
            trans.Commit();
 
            //rebuild the surface 
            surface.Rebuild();
        }
 
    }
 
 
 
}

 

This is how it looks like before editing:

And here is how it looks like after editing the surface contour style with major contour color to red and monor contour color to green.

Hope this helps.

Workaround for displacement of base map layer and dynamic layer

By Daniel Du

To improve viewing performance of Autodesk Infrastructure Map Server, you can set some layers into base layer group so that they can be rendering as tile. The tile size is 300*300 by default, which is defined in serverconfig.ini(in C:\Program Files\Autodesk\Autodesk Infrastructure Map Server 201x\Bin folder by default). 

 

[TileServiceProperties]
# *****************************************************************************
# T I L E  S E R V I C E
#
# Property Name                    Description
# -----------------------------------------------------------------------------
# RenderOnly                       Renders the tile only
#                                       0 = false and 1 = true
# TileCachePath                    Root path of the image tile cache
# TileColumnsPerFolder             Number of columns of tiles per folder
#                                       0 < Value <= 1000
# TileRowsPerFolder                Number of rows of tiles per folder
#                                       0 < Value <= 1000
# DefaultTileSizeX                 Width of generated tiles in pixels
#                                       50 < value <= 10000
# DefaultTileSizeY                 Height of generated tiles in pixels
#                                       50 < value <= 10000
# ImageFormat                      Image format for generated tiles
#                                       PNG, PNG8, GIF or JPG
# *****************************************************************************
RenderOnly                         = 0
TileCachePath                      =C:\Program Files\Autodesk\Autodesk Infrastructure Map Server 2014\Repositories\TileCache\
TileColumnsPerFolder               = 30
TileRowsPerFolder                  = 30
DefaultTileSizeX                   = 300
DefaultTileSizeY                   = 300
ImageFormat                        = PNG

 

You may find some issues if you are using flexible web layout when changing the default tile size, there is a displacement between base map layer and dynamic layer, it works fine in basic layout. Here is the workaround to fix this issue:

1. Open file fusionSF-compressed.js with NotePad. By default, the file is in C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 201x\www\fusion\lib

2. Find text ‘defaultSize:new OpenLayers.Size(300,300)’. There is only one occurrence.

3. Update (300,300) to the value that you defined on server side.

4. Clear the tile cache, the default folder is C:\Program Files\Autodesk\Autodesk Infrastructure Map Server 201x\Repositories\TileCache

5. Restart Map Server.

 

Hope this helps if you run into this issue.

Read coordinates of line features with Map 3D API

By Daniel Du

I am asked how to get the coordinates of each vertices from a line feature, for example, a line feature which is created from an AutoCAD polyline .

For an AutoCAD polyline which only contains lines, when it is converted to feature with Map 3D command “Create from Geometry”, the feature type will be MgCurveString which contains only one linear segments.

For AutoCAD polyline which contains arc, the feature after conversion will be several segments, including arc segments and linear segments.

 

Here is the code snippet:

using System;
using Autodesk.AutoCAD.Runtime;
using Autodesk.AutoCAD.ApplicationServices;
using Autodesk.AutoCAD.DatabaseServices;
using Autodesk.AutoCAD.Geometry;
using Autodesk.AutoCAD.EditorInput;
using Autodesk.Gis.Map.Platform.Interop;
using Autodesk.Gis.Map.Platform;
using OSGeo.MapGuide;
 
// This line is not mandatory, but improves loading performances
[assembly: CommandClass(typeof(GetFeatureType.MyCommands))]
 
namespace GetFeatureType
{
 
public class MyCommands
{
 
 
// Modal Command with localized name
[CommandMethod("getPolylineCoordinates")]
public void MyCommand() // This method can have any name
{
    Editor ed = Autodesk.AutoCAD.ApplicationServices.Application
        .DocumentManager.MdiActiveDocument.Editor;
 
    Transaction trans = Autodesk.AutoCAD.ApplicationServices.Application
        .DocumentManager.MdiActiveDocument.Database.TransactionManager
        .StartTransaction();
 
    using (trans)
    {
        // Get the Map Object
        AcMapMap currentMap = AcMapMap.GetCurrentMap();
 
        // Prompt user to Select Feature in Map
        PromptSelectionOptions psop = new PromptSelectionOptions();
        psop.MessageForAdding = "Select the FDO Feature in Map 3D to read Data : ";
        psop.SingleOnly = true;
        PromptSelectionResult psResult = ed.GetSelection(psop);
 
        if (psResult.Status == PromptStatus.OK)
        {
            SelectionSet selSet = psResult.Value;
 
            // Get Map Selectionset from AutoCAD SelectionSet
            MgSelectionBase mapSelBase = AcMapFeatureEntityService
                .GetSelection(selSet);
            AcMapLayer mapLayer = AcMapFeatureEntityService
                .GetLayer(psResult.Value[0].ObjectId);
 
            //Get the ID of the selected Parcel
            MgFeatureReader ftrRdr = mapSelBase.GetSelectedFeatures(
                mapLayer, mapLayer.FeatureClassName, false);
 
            while (ftrRdr.ReadNext())
            {
                MgClassDefinition cd = ftrRdr.GetClassDefinition();
 
                //the geomety property name maybe different for your 
                //data source 
                MgByteReader byteRdr = ftrRdr.GetGeometry("Geometry");
                MgAgfReaderWriter wtr = new MgAgfReaderWriter();
 
                MgGeometry geom = wtr.Read(byteRdr);
 
                if (geom is OSGeo.MapGuide.MgCurveString)
                {
                    var cs = geom as MgCurveString;
 
                    ed.WriteMessage("\n geo is MgCurveString.");
 
                    for (int i = 0, segmentCount = cs.Count; i < segmentCount; i++)
                    {
                        var seg = cs.GetSegment(i);
                        if (seg is MgArcSegment)
                        {
                            ed.WriteMessage("\nthis is an Arc Segment.");
                            var arcSeg = seg as MgArcSegment;
 
                            string msg = string.Format(
                                "\nstart point: x= {0}, y={1}",
                                arcSeg.StartCoordinate.X,
                                arcSeg.StartCoordinate.Y);
                            ed.WriteMessage(msg);
 
                            msg = string.Format(
                                "\ncontrol point  x= {0}, y={1}",
                                arcSeg.ControlCoordinate.X,
                                arcSeg.ControlCoordinate.Y);
                            ed.WriteMessage(msg);
 
                            msg = string.Format(
                                "\nend point: x= {0}, y={1}",
                                arcSeg.EndCoordinate.X,
                                arcSeg.EndCoordinate.Y);
                            ed.WriteMessage(msg);
                        }
                        if (seg is MgLinearSegment)
                        {
                            ed.WriteMessage("\nthis is a linear Segment.");
 
                            var linearSeg = seg as MgLinearSegment;
                            var interator = linearSeg.GetCoordinates();
                            while (interator.MoveNext())
                            {
                                var x = interator.GetCurrent().X;
                                var y = interator.GetCurrent().Y;
 
                                ed.WriteMessage(string.Format(
                                    "\n x = {0}, y={1} ", x, y));
                            }
                        }
 
                    }
                }
                if (geom is OSGeo.MapGuide.MgLineString)
                {
                    var ls = geom as MgLineString;
                    var interator = ls.GetCoordinates();
                    while (interator.MoveNext())
                    {
                        var x = interator.GetCurrent().X;
                        var y = interator.GetCurrent().Y;
 
                        ed.WriteMessage(string.Format(
                            "\n x = {0}, y={1} ", x, y));
                    }
 
                }
 
            }
        }
        trans.Commit();
    }
 
}
 
 
 
}
 
}

Intelligent landing page for AIMS/MapGuide Fusion Viewer

By Daniel Du

You may come across this post, implementing an intelligent landing page in AIMS/MapGuide Ajax viewer(Basic web layout), and I am also asked how to do it in Fusion viewer(flexible web layout). Actually the implemenation is pretty similar, as both Ajax Viewer and Fusion viewer share the same server side logic. Let’s take the first one as an example,zooming to specified view port by initial x, y and scale. If you have not read this post and the source code of the sample attached, please do it now, then come back to this one.

 

In the implementation of zooming to specified view port, it takes a copy of the basic WebLayout stored in the Library repository and changing the <CenterX/>, <CenterY/> and <Scale/> elements. The updated XML is written into the Session and is used as the target when the page is ultimately loaded. In fusion web layout, there are similar tags if you “use custom view”:

Let’s examine the xml of fusion weblayout with mapagent(http://localhost/mapserver2014/mapagent/), select resource –> GetResource Content

 

You will see the InitialView tag, which is similar with basic web layout. OK, with that, you can do the similar within basic weblayout, taking a copy of theflexible  WebLayout stored in the Library repository and changing the <CenterX/>, <CenterY/> and <Scale/> elements. The updated XML is written into the Session and is used as the target when the page is ultimately loaded.  Please refer to the source code in this post for detail.

 

Good luck!

Mark errors when doing mapclean in Map 3D

By Daniel Du

In Map 3D map clean tool, it marks the errors it finds.Here is an example to demonstrate how to use do it with API:

[CommandMethod("clean")]
public void DrawingCleanUp()
{
    string sGroupKeyword = "GROUP";
    string sErrorKeyword = "ERROR";
    string sYes = "YES";
    string sNo = "NO";

    int iGrpErrCnt = 0;
    Editor ed = Application.DocumentManager.MdiActiveDocument.Editor;

    Autodesk.Gis.Map.Topology.Variable cadAction =
        new Autodesk.Gis.Map.Topology.Variable();
    cadAction.LoadProfile(@"C:\MapCleanDemo\myClean.dpf");

    PromptKeywordOptions pkoCleanupType =
        new PromptKeywordOptions("Cleanup Type:");
    pkoCleanupType.Keywords.Add(
        sGroupKeyword, sGroupKeyword, sGroupKeyword, true, true);
    pkoCleanupType.Keywords.Add(
        sErrorKeyword, sErrorKeyword, sErrorKeyword, true, true);
    pkoCleanupType.AllowNone = true;

    PromptKeywordOptions pkoFixError = new PromptKeywordOptions("Fix?");
    pkoFixError.Keywords.Add(sYes, sYes, sYes, true, true);
    pkoFixError.Keywords.Add(sNo, sNo, sNo, true, true);
    pkoFixError.AllowNone = true;

    PromptResult pres = ed.GetKeywords(pkoCleanupType);
    if (pres.Status != PromptStatus.Cancel)
    {
        using (Autodesk.Gis.Map.Topology.TopologyClean cadCleanobj
            = new Autodesk.Gis.Map.Topology.TopologyClean())
        {
            cadCleanobj.Init(cadAction, null);

            cadCleanobj.Start();
            cadCleanobj.GroupNext();
            if (pres.StringResult.ToUpper().Equals(sErrorKeyword))
            {
                while (!cadCleanobj.Completed)
                {
                    iGrpErrCnt = cadCleanobj.GroupErrorCount;

                    ed.WriteMessage("\nGroup Error Count: " + iGrpErrCnt);
                    ed.WriteMessage("\n* Iterating over Errors.");

                    for (int i = 0; i < iGrpErrCnt; i++)
                    {
                        cadCleanobj.ErrorCur(i);
                        ed.WriteMessage("\n* Current Error (X: "
                            + Math.Round(cadCleanobj.ErrorPoint.X, 2)
                            + " Y: " + Math.Round(cadCleanobj.ErrorPoint.Y, 2) + ")");
                        cadCleanobj.ErrorDraw();

                        if (ed.GetKeywords(pkoFixError).StringResult.ToUpper().Equals(sYes))
                            cadCleanobj.ErrorFix();
                        else
                            cadCleanobj.ErrorMark();
                    }

                    cadCleanobj.GroupNext();
                }
            }
            else if (pres.StringResult.ToUpper().Equals(sGroupKeyword))
            {
                ed.WriteMessage("\nGroup Cleanup");
                ed.WriteMessage("\n* Iterating over Groups.");
                while (!cadCleanobj.Completed)
                {
                    iGrpErrCnt = cadCleanobj.GroupErrorCount;

                    ed.WriteMessage("\nGroup Error Count: " + iGrpErrCnt);

                    cadCleanobj.GroupDraw();

                    if (ed.GetKeywords(pkoFixError).StringResult.ToUpper().Equals(sYes))
                        cadCleanobj.GroupFix();
                    else
                        cadCleanobj.GroupMark();

                    cadCleanobj.GroupNext();
                }
            }
            else
                ed.WriteMessage("\n" + pres.StringResult + " is not a valid option.");

            cadCleanobj.End();
        }
    }
}

Autodesk Infrastructure Map Server(AIMS) API Training content : Part-8

By Daniel Du

We talked about Ajax Viewer, Fusion Viewer, actually Mobile Viewer is another important viewer, especially for those who want to view map data on mobile devices. The Mobile Viewer framework is a set of JavaScript classes, CSS files, images and icons designed to provide a compelling and intuitive interface for displaying Autodesk Infrastructure Map Server 2014 spatial content on the Apple iPhone, iPad, and iPod Touch. The OpenLayers mapping framework is used to handle many aspects of the map display and management. Several of the PHP scripts used by the Fusion framework are used unmodified in order to interact with the Infrastructure Map Server Web Tier API to perform such functions as session creation, map initialization, selection, and determination of feature properties. You do not need to download/install anything on your devices. 

In this chapter, we introduce Mobile Viewer itself and its API, we also talk about how to create a custom controls to extend the mobile viewer and how to debug, build and deploy it.  Please find the attached PPT and code samples, and Mobile Viewer Reference Guide section of the AIMS documents

Download Creating a Custom Control for Mobile Viewer

How to setup and run Mobile Viewer Sample.

Please note that the samples just demo how to create custom control, they are not fully tested, and you need to do more work to use them in your project.

 

1.      Install Apache Ant(http://ant.apache.org), and add to PATH environment variable.

2.      Copy C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www\MobileViewer To C:\MobileViewer_Dev

3.      Unpack MobileViewer2013.zip to  C:\MobileViewer_Dev and merge the contents. Here is the folder structure after merging :

4.      Setup the server side logic.

a)       Copy sample\ListSelectionAppDotnet to C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www\MobileViewer

b)       Convert virtual directory to web application in IIS, please make sure to use ASP.NET 4.0, an easy way is to use MapServer2013AppPool as application pool:

 

c)        Copy all dlls from C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www\mapviewernet\bin To C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www\MobileViewer\ListSelectionAppDotnet\bin

d)       Copy webconfig.ini from C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www  to C:\Program Files\Autodesk\Autodesk Infrastructure Web Server Extension 2013\www\MobileViewer\ListSelectionAppDotnet

 

5.      Start-> cmd to open command window:

a)       cd C:\MobileViewer_Dev (the folder contains build.xml)

b)       Ant

6.      Open Mobile viewer and test

a)       Open in browser

b)       Click “DevCampHelloWorld” button, and click on map;

c)        Click “DevCampShowMapInformation” button to show the map information

d)       Zoom in and select some features with multi-selection tool

e)       Click “ListSelection” button, to show the feature information of selected features.

 

 

ODTables.Item(tableName) does not work on Windows7/Vista?

By Daniel Du

Issue

I am migrating my Map 3D VBA application to .NET, but when I call ODTables.Item(strTableName), it always crashes AutoCAD on Windows 7/Vista, and it works well on WinXP.

Solution

You can use following workaround on Windows 7/Vista to solve this problem:

VB.NET:

<code_begin>
    Dim ODTbl As AutocadMAP.ODTable
    ODTbl = Nothing
    For index = 0 To ODTbls.Count - 1
       Debug.WriteLine( ODTbls.Item(index).Name.ToString())
       If (ODTbls.Item(index).Name.ToString() = TargetTable) Then
            ODTbl = ODTbls.Item(index)
        Exit For
       End If
    Next

<code_end>

VBA code:

<code_begin>
Public Sub GetMapApp()
Dim amap As AcadMap
Dim tbl As ODTable
Dim tbls As ODTables
Set amap = ThisDrawing.Application.GetInterfaceObject("AutoCADMap.Application")
Debug.Print amap.Projects.Count 

'' workaround
Set tbls = amap.Projects(ThisDrawing).ODTables

If (tbls.Count) > 0 Then
For Each tbl In tbls
If tbl.Name = "Building" Then ‘ set OD Table name here as per your data
Debug.Print tbl.Name
End If
Next
End If

End Sub

<code_end>

Autodesk Infrastructure Map Server(AIMS) API Training content : Part-7

By Daniel Du

We discussed Ajax Viewer API in chapter2, in this chapter, we will talk about Fusion Viewer API. Flexible web layouts are an alternative to the Ajax Viewer. Flexible web layouts make use of additional libraries and technologies for some functionality. At times it may be useful to refer to documentation for these libraries. See the following for more information:

• Fusion, the open source technology used by Flexible Web Layouts.
  http://trac.osgeo.org/fusion/wiki
• OpenLayers, a JavaScript library for displaying map data in a browser.
  http://www.osgeo.org/openlayers
• Jx, a JavaScript library for building UI components like dialogs.
  http://jxlib.org

In this chapter we will give you an introduction of fusion viewer, the components of fusion viewer, how it works and how to extend this fusion viewer. This document on wikihelp is very useful, I would suggestion you to go through it first and refer to our training materials below.  You may also find this DevTV useful as well.

Download EN_AIMS_API_Chapter_7

Autodesk Infrastructure Map Server(AIMS) API Training content : Part-6

By Daniel Du

This is second half of feature service, we will discuss updating, deleting and creating features with feature service.

A feature class contains one or more features. Each feature has a geometry that defines the spatial representation of the feature.Features will also generally have one or more properties that provide additional information. Feature class is a database-table-like structure, it contains properties corresponding to table columns. The properties can be geometry type, data type, raster type or object type. The most commonly used ones are geometry property and various data properties.  MgClassDefinition or MgPropertyDefinition classes are used to describe the schema of feature class.

To create a feature class, we need to build up the schema first by creating a MgClassDefinition and populate the property definition collection and add them to a MgPropertyDefinitionCollection which can be get from MgClassDefinition.GetProperties() method, next step is to create and set up schema with MgFeatureSchema class and the physical storage format. In AIMS, we can create file based schema like SDF, SHP file or SQLite.

Once the schema of feature source is created, we can add/delete/update some records(features) into it with MgInsertFeatures/MgDeleteFeatures/MgUpdateFeatures commands.  These commands accept MgPropertyCollection as parameter. MgPropertyCollection holds the property value used to update/insert a feature class. Finally we MUST call MgFeatureService.UpdateFeatures() to execute the commands(insert/delete/update) and commit the changes into feature source.

Let’s consider such a scenario, a user draws a feature(point, line or polygon)in browser with mouse and we’d like to save it into feature source. Firstly we need to get the coordinates of the feature, this process is called digitizing, it can be done with Ajax Viewer API or Fusion viewer API, please refer to this post for example of digitizing in fusion viewer.  After we getting the coordinate value of each vertex, we can create the geometry with MgGeometryFactory class.

If you examine the feature service API, you will notice that the constructor of MgGeometryProperty class need a parameter with MgByteReader type. In AIMS API, a geometry has 3 representations:

1. MgGeometry and its subclasses, it can be  created with MgGeometryFactory;
2. MyByteReader, which is used by feature service API;
3. AGF(Autodesk Geometry Format) text, it is a superset of WKT(Well known text);

The conversion between these 3 representations can be done by MgAgfReaderWriter or MgWktReaderWriter:

 

Following graph demos the process of inserting a feature into class, it can be found in Web Extension API reference. Please read this graph from bottom to top.

 

OK, now please find the attached PPT for more information about this chapter.

Download EN_AIMS_API_Chapter_6