Global ports (WFP SDI-T - Logistics Database)

  • 90+ Downloads
  • This dataset updates: Never

Gallery

This layer contains ports locations. This dataset brings together various public sources with WFP logistics information. It is updated regularly with inputs from WFP logistics but also from many partners through the Logistics Cluster and the Logistics Capacity Assessment (LCA: dlca.logcluster.org). The information is compiled at a global level by the Emergency and Preparedness Geospatial Information Unit at the World Food Programme (WFP) Headquarters in Rome, Italy.

This dataset is at a global scale and is updated country by country. The last update date can be retrieved from the data of the country of interest.

Feel free to contribute to this dataset by contacting hq.gis@wfp.org.

Metadata

Source WFP, Logistics Cluster
Contributor
Date of Dataset Oct 08, 2015
Expected Update Frequency Never
Location
Visibility
Public
License
Methodology Registry
Caveats / Comments

Date: 2015-10-08

Any attributes which are blank or '0' had no data entered at the time of release. Please contribute by giving your inputs at hq.gis@wfp.org or connect on http://geonode.wfp.org/

Category: Transportation Shape: Point

Schema and Attribute Details:

wld_trs_ports_wfp

objectid integer NOT NULL: ArcGIS ID

portname character varying(100): Port name (Often, name of the town/city)

code character varying(10): Port code

prttype character varying(25): Port type: Unknown, Sea, River, Lake

prtsize character varying(25): Port size: Unknown, Huge, Large, Medium, Small, Very Small

status character varying(25): Port status: Unknown, Open, Closed, Planned, Restricted

maxdepth numeric(3,1): Maximum depth for vessels

maxlength numeric(5,1): Maximum length for vessels

annualcapacitymt numeric(7,1): Annual capacity (in MT)

humuse character varying(10): Used by WFP for humaniatarian assistance: Unknown, Yes, No

locprecision character varying(25): Precision of the location: Accurate => GPS coordinates, digitized from an high resolution satellite imagery or a detailed map (accuracy at the street level), Approximate => Precision which is not below the city/town level. It often corresponds to a point equivalent at the point of the city/town/village, Bad => Feature with a very low precision. A feature exists in 1 area (province, region...) but we don't know where exactly, the reference (settlement) is impossible to find and the point is put randomly, Unknown => No information regarding the precision

latitude numeric(8,5): Latitude of the point in Decimal Degrees (WGS 1984, Calculated automatically from the geometry)

longitude numeric(8,5): Longitude of the point in Decimal Degrees (WGS 1984, Calculated automatically from the geometry)

iso3 character varying(5): ISO3 code of the country where the feature is located. This field is calculated automatically at the database level

iso3_op character varying(25): List of ISO3 code (separated with a character '-' or ','). Use to quickly filter the data for the features of interest for 1 operation. 1 feature could be located in 1 country but be an asset for the operation of another country (for example an office delocalized for security reason in the neighbor country or a warehouse used for storage for several countries). Exceptionnally, it happens that the code do not refer to an iso3 code of a country but to the name of an operation (Ebola, Haiyan...)

country character varying(50): Name of the country where the feature is located. This field is calculated automatically at the database level

lastcheckdate timestamp without time zone: Date of the last check of all (or a part) of the attributes. The date has to be specified manually during the edits

remarks character varying(1000): Notes/Description/Remarks - The user is free to enter any information that is necessary but cannot be stored in the others fields

url_lca character varying(254): Reference to the LCA page of the feature

source character varying(254): Source of the information. It could be the source of the geometry or the source of the main attributes. Several sources can be accepted for the same feature(list of names)

createdate timestamp without time zone: Date when the feature has been created. Calculated automatically at the database level while saving (commit) the edits.

updatedate timestamp without time zone: Date of the last update. Calculated automatically at the database level while saving (commit) the edits. Different of the lastcheckdate because the user can forget to specify the date manually or because sometimes when doing a quick edit (for example change the status or correct misspelling) without checking all attributes.

geonameid integer: geonameid of the closest village/town from the geonames database

shape geometry: Geometry

Tags