• System.Object
  • ThinkGeo.MapSuite.Routing.RoutingTransactionBuffer

RoutingTransactionBuffer()

• This is the class constructor.

• This is the default constructor and is typically not used.

RoutingTransactionBuffer(Dictionary<String,RouteSegment>,Collection<String>,Dictionary<String,RouteSegment>)

• N/A

• N/A

• addBuffer
  • Type:Dictionary<String,RouteSegment>
  • Description:N/A

• deleteBuffer
  • Type:Collection<String>
  • Description:N/A

• editBuffer
  • Type:Dictionary<String,RouteSegment>
  • Description:N/A

Clear()

• N/A

• This method will clear all the items in AddBuffer, EditBuffer and DeleteBuffer.

• Type:Void
• Description:None.

AddRouteSegment(RouteSegment)

• N/A

• None

• Type:Void
• Description:None

• routeSegment
  • Type:RouteSegment
  • Description:This parameter represents the RouteSegment you are adding to the transaction buffer.

DeleteRouteSegment(String)

• N/A

• This does not remove a RouteSegment from the TransactionBuffer but rather it add a “to be deleted record”. In this way when the TransactionBuffer if processed we know what records need to be deleted.

• Type:Void
• Description:None

• featureId
  • Type:String
  • Description:This parameter represents the unique feature Id for the specific RouteSegment being passed in.

UpdateFeature(RouteSegment)

• N/A

• None

• Type:Void
• Description:None

• routeSegment
  • Type:RouteSegment
  • Description:This parameter represents the RouteSegment to be updated.

ToString()

• N/A

• N/A

• Type:String
• Description:N/A

Equals(Object)

• N/A

• N/A

• Type:Boolean
• Description:N/A

• obj
  • Type:Object
  • Description:N/A

GetHashCode()

• N/A

• N/A

• Type:Int32
• Description:N/A

GetType()

• N/A

• N/A

• Type:Type
• Description:N/A

Finalize()

• N/A

• N/A

• Type:Void
• Description:N/A

MemberwiseClone()

• N/A

• N/A

• Type:Object
• Description:N/A

AddBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Dictionary<String,RouteSegment>

DeleteBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Collection<String>

UpdateBuffer

• N/A

• It is recommended that you use this dictionary for reviewing and not for adding new items. The reason is that the Add, Delete and Edit methods to various validation checks. For example if you call the DeleteRouteSegment twice it will handle the case that you really only want to delete the record once. Another example is if you edit a record twice it will replace the existing edit with the new one.

• Type:Dictionary<String,RouteSegment>