PortML.Documents
1.1.70
See the version list below for details.
dotnet add package PortML.Documents --version 1.1.70
NuGet\Install-Package PortML.Documents -Version 1.1.70
<PackageReference Include="PortML.Documents" Version="1.1.70" />
paket add PortML.Documents --version 1.1.70
#r "nuget: PortML.Documents, 1.1.70"
// Install PortML.Documents as a Cake Addin #addin nuget:?package=PortML.Documents&version=1.1.70 // Install PortML.Documents as a Cake Tool #tool nuget:?package=PortML.Documents&version=1.1.70
1. About
PortML stands for Port Markup Language. It is a descriptive language or document which describes container port assets, such as yard blocks, quay cranes, wharves, and AGVs, as a markup code for modelling and simulation.
PortML document follows the PortML specification which is defined in the schema file PortML.xsd. The schema defines all of the datatypes and base infrastructure types.
2. How to Use
using (StreamReader file = new StreamReader("<path to PortML document>"))
{
try
{
string portMLDocument = file.ReadToEnd();
var parser = new PortML.Documents.PortMLParser();
var portML = parser.Parse(portMLDocument);
...
}
catch (Exception ex)
{
...
}
}
3. Design
To retrieve the design metadata from the PortML
object, use the following code.
var design = portML.GetDesign();
The code above will return a list of DesignInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
DesignToActualScale | double | The scale from design pixel to meter in actual world. |
4. Terminal
There will be one and only one Terminal module in the same PortML document. It is to specify the boundary of the terminal and to provide static properties which are general to the entire port system.
To retrieve the terminal information from the PortML
object, use the following code.
var terminal = portML.GetTerminal();
If you would like the BoundaryPoints
to be in meter, use the following code.
var terminal = portML.GetTerminal(true);
The code above will return a list of TerminalInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
BoundaryPoints | List<Vector2> | Boundary points of the terminal border which is a polygon. The area inside of the polygon is the terminal area. |
NumberOfAGVs | int | Total number of AGVs running inside the terminal. |
AverageAGVSpeed | double | Average AGV speed in m/s. |
ClearanceDistance | double | Clearance distance between vessels, in pixel. |
Forty2TwentyRatio | double | Forty-foot container to twenty-foot container ratio. |
NumberOfQuayCranes | int | Total number of quay cranes available inside the terminal. |
NumberOfAGVsServingEachQuayCrane | int | Number of AGVs serving per quay crane. |
NumberOfTEUsProcessedByEachQuayCrane | int | Number of TEUs processed per quay crane. |
5. Wharf
Wharf is the side of the port terminal where vessels will be parked at.
Quay cranes will be located at the land side of the wharf while vessels will be parked at the sea side. As shown in the following diagram, the direction of the wharf, defined by StartingAt and EndingAt, is important. The wharf direction will decide which side of it is land side and which side of it is sea side.
To retrieve the wharf information from the PortML
object, use the following code.
var wharfs = portML.GetAllWharfs();
If you would like the StartingAt
, EndingAt
to be in meter, use the following code.
var wharfs = portML.GetAllWharfs(true);
The code above will return a list of WharfInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
ReferenceId | string | Reference ID of the wharf. |
StartingAt | Vector2 | The coordinate of the starting point of the wharf. |
EndingAt | Vector2 | The coordinate of the ending point of the wharf. |
Length | double | Wharf length in meter. |
6. Yard Block
Yard block module is corresponding to the container yard in the sea port terminal.
The starting point and facing direction of a yard block is defined in the way shown in the following diagram.
The Facing
property defines the direction of the yard block in radian rotating around the StartingAt
point.
To retrieve the yard block information from the PortML
object, use the following code.
var yardBlocks = portML.GetAllYardBlocks();
If you would like the StartingAt
, SlotWidth
, SlotLength
to be in meter, use the following code.
var yardBlocks = portML.GetAllYardBlocks(true);
The code above will return a list of YardBlockInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
ReferenceId | string | Reference ID of the yard block. |
StartingAt | Vector2 | The coordinate of the starting point of the yard block. |
Facing | double | The direction of the yard block in radian. |
NumberOfRows | int | Number of rows of the yard block. |
NumberOfBays | int | Number of bays of the yard block. |
NumberOfTiers | int | Number of tiers of the yard block. |
NumberOfOperatingTiers | int | Number of operating stacking height (tier) of the yard block. |
BayTypes | BayType[] | Type (either exchange or transhipment) of each bay. |
SlotWidth | double | Average width of each slot in the yard block. The total width of the yard block is thus SlotWidth * NumberOfRows. |
SlotLength | double | Average length of each slot in the yard block. The total width of the yard block is thus SlotLength * NumberOfBays. |
NumberOfYardCranes | int | Number of yard cranes in the yard block. |
7. Traffic Network
To retrieve the traffic network from the PortML
object, use the following code.
var trafficNetwork = portML.GetTrafficNetwork();
If you would like the PositioningAt
to be in meter, use the following code.
var trafficNetwork = portML.GetTrafficNetwork(true);
7.1 Quay Points
To retrieve the quay point information from the trafficNetwork
object, use the following code.
var quayPoints = trafficNetwork.QuayPoints;
The code above will return a list of ControlPointInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
ReferenceId | string | Unique reference ID of the control point. |
Tag | string | Tag of the control point. |
PositioningAt | Vector2 | The coordinate of the control point. |
WharfId | string | Reference ID of the wharf corresponding to the quay point. |
7.2 Yard Points
To retrieve the yard point information from the trafficNetwork
object, use the following code.
var yardPoints = trafficNetwork.YardPoints;
The code above will return a list of ControlPointInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
ReferenceId | string | Unique reference ID of the control point. |
Tag | string | Tag of the control point. It is made unique in the same traffic network. |
PositioningAt | Vector2 | The coordinate of the control point. |
YardBlockId | string | Reference ID of the yard block corresponding to the yard point. |
YardCraneId | string | Reference ID of the yard crane corresponding to the yard point. |
NumberOfRelatedGroundSlots | int | Number of ground slots which are corresponding to the yard point. |
IsExchange | bool | True if the yard point is an Exchange Yard Point. False if it's a Transhipment Yard Point. |
7.3 Quay-Point-to-Yard-Point Distance
To retrieve the distance from each quay point in the traffic network to another yard point, use the following code.
var distanceMatrix = trafficNetwork.PointDistancesFromQuayPointToYardPoint;
The code above will return a list of PointToPointDistanceInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
SourceControlPointReferenceId | string | The unique reference ID of the quay point. |
TargetControlPointReferenceId | string | The unique reference ID of the yard point. |
Distance | double | Distance between the two control points in meter. |
InBetweenControlPointReferenceIds | string[] | Control point reference IDs on the path between the two control points. |
This distance is calculated using Dijkstra's algorithm in the graph of the traffic network.
7.4 Yard-Point-to-Quay-Point Distance
To retrieve the distance from each yard point in the traffic network to another quay point, use the following code.
var distanceMatrix = trafficNetwork.PointDistancesFromYardPointToQuayPoint;
The code above will return a list of PointToPointDistanceInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
SourceControlPointReferenceId | string | The unique reference ID of the yard point. |
TargetControlPointReferenceId | string | The unique reference ID of the quay point. |
Distance | double | Distance between the two control points in meter. |
InBetweenControlPointReferenceIds | string[] | Control point reference IDs on the path between the two control points. |
This distance is calculated using Dijkstra's algorithm in the graph of the traffic network.
7.5 Yard-Point-to-Yard-Point Distance
To retrieve the distance from each yard point in the traffic network to another yard point, use the following code.
var distanceMatrix = trafficNetwork.PointDistancesFromYardPointToYardPoint;
The code above will return a list of PointToPointDistanceInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
SourceControlPointReferenceId | string | The unique reference ID of the yard point. |
TargetControlPointReferenceId | string | The unique reference ID of the yard point. |
Distance | double | Distance between the two control points in meter. |
InBetweenControlPointReferenceIds | string[] | Control point reference IDs on the path between the two control points. |
This distance is calculated using Dijkstra's algorithm in the graph of the traffic network.
8. Quay Crane Statistics
To retrieve the operating time statistics of a quay crane, use the following code.
var quayCraneStatistic = portML.GetQuayCraneStatistics();
The code above will return a dictionary of QuayCraneInfo
objects. The key is the quay crane name and the value contains the following information.
Property | Data Type | Description |
---|---|---|
LoadingServiceTime | double | Time of a quay crane in servicing the loading operation. Unit of time is second. |
LoadingRestoreTime | double | Time of a quay crane in restoring the loading operation. Unit of time is second. |
UnloadingServiceTime | double | Time of a quay crane in servicing the unloading operation. Unit of time is second. |
UnloadingRestoreTime | double | Time of a quay crane in restoring the unloading operation. Unit of time is second. |
9. Yard Crane Statistics
To retrieve the operating time statistics of a yard crane, use the following code.
var yardCraneStatistic = portML.GetYardCraneStatistic();
The code above will return a dictionary of YardCraneInfo
objects. The key is the yard crane name and the value contains contains the following information.
Property | Data Type | Description |
---|---|---|
UnstackingServiceTime | double | Time of a yard crane in servicing the unstacking operation. Unit of time is second. |
UnstackingRestoreTime | double | Time of a yard crane in restoring the unstacking operation. Unit of time is second. |
StackingServiceTime | double | Time of a yard crane in servicing the stacking operation. Unit of time is second. |
StackingRestoreTime | double | Time of a yard crane in restoring the stacking operation. Unit of time is second. |
10. AGV Parking Lot
AGV Parking Lot is where AGVs will be parked at.
To retrieve the AGV parking lot information from the PortML object, use the following code.
var agvParkingLots = portML.GetAllAGVParkingLots();
If you would like the StartingAt
, SlotWidth
, SlotLength
to be in meter, use the following code.
var agvParkingLots = portML.GetAllAGVParkingLots(true);
The code above will return a list of AGVParkingLotInfo
object which contains the following information.
Property | Data Type | Description |
---|---|---|
ReferenceId | string | Reference ID of the AGV parking lot. |
StartingAt | Vector2 | The coordinate of the starting point of the AGV parking lot. |
Facing | double | The direction of the AGV parking lot in radian. |
NumberOfSlots | int | Number of slots in the AGV parking lot. |
SlotWidth | double | Average width of each slot in the AGV parking lot. The total width of the parking lot is thus SlotWidth * NumberOfSlots.. |
SlotLength | double | Length of each slot in the AGV parking lot. |
11. Release Notes
18th Oct 2022
- Bug fix for traffic info summary
4th Jul 2022
- The control point tag information may not be unique. Reference ID should be applied for locating control point in PointToPointDistanceInfo
- Support multiple quay crans and yard cranes statistics outputs. Each type of cranes should have its own statistical information.
24th Feb 2022
- Updated TerminalInfo, WharfInfo, YardBlockInfo, ControlPointInfo, and AGVParkingLotInfo to able to return coordinates, slot width, and slot length in meter.
22nd Feb 2022
- Updated YardBlockInfo to provide NumberOfYardCranes.
11th Feb 2022
- Updated TerminalPortMLModule and YardSetPortMLModule to support SINGAPort Studio handling new configuration parameters.
10th Feb 2022
- Introduced DesignInfo with
MeterToVector
info. - Updated TerminalInfo to have
ClearanceDistance
,Forty2TwentyRatio
,MaxQcNum
,MaxAgvServeEachQC
,QcAgvProcessTeu
,AgvNum
,AgvSpeed
info. - Updated YardBlockInfo to have
OperationStackingHeight
info.
27th Jan 2022
- Introduced AGVParkingLotInfo.
15th Jan 2022
- Updated the shortest distance retrieval methods to return the tag of control points on the path.
11th Jan 2022
- Updated static properties in Yard Block module.
4th Jan 2022
- Added service time and restore time info of each quay crane and yard crane.
2nd Jan 2022
- Introduced traffic network and distance matrices.
31st Dec 2021
- Introduced TerminalInfo.
30th Dec 2021
- Introduced WharfInfo;
- Introduced YardBlockInfo.
12. Contributors
Domain Experts
- Dr Li Haobin;
- Peng Yuming.
Developers
- Riza Marhaban;
- Goh Chun Lin;
- Tan Sin Cho.
13. Feedback
Bug reports and contributions are welcome at PortML Contact Us Page.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Newtonsoft.Json (>= 13.0.1)
- QuikGraph (>= 2.3.0)
- System.ComponentModel.Annotations (>= 5.0.0)
- System.Numerics.Vectors (>= 4.5.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.1.82 | 193 | 4/17/2024 |
1.1.81 | 142 | 3/22/2024 |
1.1.80 | 119 | 3/19/2024 |
1.1.79 | 118 | 2/28/2024 |
1.1.78 | 123 | 2/21/2024 |
1.1.77 | 143 | 2/14/2024 |
1.1.76 | 177 | 8/22/2023 |
1.1.75 | 140 | 8/22/2023 |
1.1.71 | 408 | 11/8/2022 |
1.1.70 | 398 | 10/19/2022 |
1.1.69 | 433 | 10/18/2022 |
1.1.68 | 427 | 10/13/2022 |
1.1.67 | 443 | 7/25/2022 |
1.1.66 | 439 | 7/4/2022 |
1.1.65 | 427 | 6/15/2022 |
1.1.64 | 427 | 6/14/2022 |
1.1.63 | 479 | 6/8/2022 |
1.1.61 | 439 | 6/3/2022 |
1.1.60 | 456 | 5/8/2022 |
1.1.59 | 450 | 4/30/2022 |
1.1.58 | 439 | 4/29/2022 |
1.1.57 | 468 | 4/28/2022 |
1.1.56 | 444 | 4/28/2022 |
1.1.55 | 485 | 4/23/2022 |
1.1.53 | 448 | 3/15/2022 |
1.1.52 | 458 | 2/24/2022 |
1.1.51 | 457 | 2/22/2022 |
1.1.50 | 456 | 2/11/2022 |
1.1.49 | 465 | 2/10/2022 |
1.1.48 | 464 | 1/27/2022 |
1.1.47 | 485 | 1/27/2022 |
1.1.46 | 482 | 1/27/2022 |
1.1.45 | 502 | 1/19/2022 |
1.1.44 | 477 | 1/15/2022 |
1.1.42 | 468 | 1/15/2022 |
1.1.41 | 465 | 1/11/2022 |
1.1.40 | 296 | 1/11/2022 |
1.1.39 | 470 | 1/11/2022 |
1.1.38 | 313 | 1/5/2022 |
1.1.37 | 311 | 1/5/2022 |
1.1.36 | 312 | 1/3/2022 |
1.1.35 | 293 | 1/3/2022 |
1.1.34 | 329 | 1/2/2022 |
1.1.33 | 323 | 1/2/2022 |
1.1.32 | 312 | 1/2/2022 |
1.1.31 | 320 | 1/2/2022 |
1.1.30 | 308 | 1/2/2022 |
1.1.29 | 295 | 1/2/2022 |
1.1.28 | 298 | 12/31/2021 |
1.1.27 | 299 | 12/31/2021 |
1.1.26 | 295 | 12/30/2021 |
1.1.25 | 304 | 12/30/2021 |
1.1.24 | 292 | 12/30/2021 |
1.1.22 | 296 | 12/30/2021 |
1.0.4 | 307 | 12/29/2021 |
1.0.3 | 309 | 12/29/2021 |
Please refer to README.