Maritime Ports Data Model 2023 Release

[#1]

                                                    

MP 2023 Edition

This is the official release of the 2023 Edition of the Maritime Ports Data Model (MP2023).

It is designed to support data management for the Maritime Ports industry. 

The downloadable file includes:

- ArcGIS Pro 2.9 project

- ArcGIS Pro 3.X project

- Maritime Ports Data Model 2023.pdf - Data Dictionary

The ArcGIS Pro projects include the data model and the sample data. The data dictionary provides full documentation of the data model.

If you have questions, please post them to this Esri Community, so everyone can see and share the information.

Thank you,

Kyle Crawford

Esri Solution Engineer, Ports and Rail

*** April 2025: Included a download for an Updated Change GBD Spatial Reference toolbox that can run in ArcGIS Pro 3.1 and later.

 

[RamB]

Thank you. Is this worldwide data and how to access the complete dataset ?

[Kyle-Crawford]

Hi, @RamB this data model provides Maritime Port organizations with an implementation-ready configuration for ArcGIS. The data provided only covers a specific geographical area for users to visualize and test functionality included in the data model.

[RamB]

Hi @Kyle-Crawford 

yes I understand this is a sample. I was referring to the full data set . Is it worldwide data set or just for US?

thank you 

[Kyle-Crawford]

Hi Everyone! I just wanted to thank everyone who has checked out the data model so far and provided some great feedback!

I also wanted to let everyone know that we have found a bug (bug-000156711) related to the Change GDB Spatial Reference geoprocessing tool included in the ArcGIS Pro project. If you happen to see the message "Tool has failed to open" please just close and then reopen the project. This should remedy the issue and if not please reach out to me here.

Thank you - Kyle

[Kyle-Crawford]

Hi @shipfinex thank you for the comment! Please feel free to reach out if you have any additional feedback. 

[RobertGraham_HDR]

@Kyle-Crawford I am integrating the Maritime model into a Port Houston project.  Where is best place to give feedback? here?

I am focused on dredge operations.  The Dredge Material Placement Areas (DMPA) could use the Wetlands, Facility Boundary or Landuse polygon featureclass templates as a start.  DMPAs are probably at or around most ports.  Could we have a template for Dredge Material Placement Areas (DMPA)?  Our focus is on the capacity available of these areas.  

The Port Houston DMPAs are intersected by many other features like export pipelines, Electric transmission and other utilities.  These may be considered Hazardous Materials but are typically linear.

Dredge Material Placement Areas (DMPA) are surrounded by levees.  I am capturing levees as linear polylineZ features.  The height and condition of the dike or levee are most important.  

For the onshore DMPAs the dredge pipeline route easements are one of the more ambiguous features.  The dredge pipelines are temporal features used temporarily while DMPAs are being filled.  I have captured the dredge pipeline routes as linear features with very little attributes.  Only the size, ownership and inspection dates are being captured.  

[Victor_Centella]

@Kyle-Crawford 

We are implementing this data model for a port client in Spain. We have realized that the addition of a new point layer in the category of “Maritime” could be very useful. This layer would be similar to that of Mooring and Fender, but it would store information about the location of port ladders.

Thank you,

Víctor

[RossLuttrell]

Hi @Victor_Centella 

For our implementation we used 'personal access' to represent ladders around the port. We added 'safety ladders' and 'berthing ladders' to the default domain.

Based on my experience, I'd recommend 'life buoy cabinets' as an addition to the schema.

[Victor_Centella]

Thank you @RossLuttrell, very useful.

[GISDataTasPorts]

There is an issue with the naming of a two feature classes which clash with the name of feature datasets in this model.  In particular, "Rail" and "Pavement" are both feature datasets, and they each contain a feature class with the same name as the feature dataset.  Ie, "Rail\Rail" and "Pavement\Pavement".

This is fine most of the time, but there are instances where ArcGIS tools and arcpy scripts fail on these items.  I think that this is due to them specifying an item by name, and then getting the wrong type of item to work with.

The work around has been to remove the feature class from its feature dataset, run the processing, then move the feature class back into its feature dataset.

(On another slightly related issue, using feature datasets simply for organising feature classes seems to contradict with general advice from ESRI.)

[Mariette_Boudreau]

I am having an issue with running the Change Spatial Reference tool. 

I am getting an exception, the last line is saying
"AttributeError: Object: GetParameterInfo tool <UtilityNetwork_un> not found"
I am running ArcGIS Pro 3.4.3 with a standard license.

Has anyone else had issues running this tool?

[Mariette_Boudreau]

The Change Spatial Reference tool only works with ArcGIS Pro 3.1.

I successfully used it by reverting back to 3.1 with help from tech support.

[Kyle-Crawford]

@Mariette_Boudreau thank you for notifying us of this issue. I have included a new download for an updated Change Spatial Reference tool.

[Mariette_Boudreau]

@Kyle-Crawford Tried the updated tool and received:

"ERROR 000576: Script associated with this tool does not exist."

Thank You 

[Kyle-Crawford]

@Mariette_Boudreau sorry about that and thanks for letting me know. I thought I embedded the script into the tool however I have now replaced the file. Please let me know if that corrects the error you received. 

[Mariette_Boudreau]

@Kyle-Crawford everything is working now. 

Thank You!