# Location
In the MMT RDM we have multiple `Location` types to cover those involved in the movement of goods, some well known locations are definied below as are the attributes for this class.
In MMT the locations inherit from the `LogisticsLocation` class
## Attributes
The location is identifed by either or both of the fields:
* `ID` - The UN/LOCODE i.e. GBLIV
* `Name` - The text name for the location i.e. Liverpool
## Types of Location
The definitions of a location are key for common understanding across borders and for legal basis, the definitions are published under a library called the Core Components Library (CCL) and adhere to the 'controlled vocabulary'
The below is a list of commonly used locations in the transport and logistics domain and throughout the message structures and transport contracts.
### Place of Dispatch
> Place at which the goods are taken over for carriage (operational term), this place can be different from the transport contract place of acceptance.
**MMT Name:** `SupplyChainConsignment.CarrierAcceptance.LogisticsLocation`
### Place of Delivery
> Place to which the goods are to be delivered under transport contract terms. This may be different of the location of the consignee.
**MMT Name:** `SupplyChainConsignment.FinalDestination.LogisticsLocation`
### Port of Loading
The original port of loading onto a vessel for sea or river movements, can be referenced as a contractual place related to Inco Terms or is the first point at which the goods embark on their water based journey.
**MMT Name:** `SupplyChainConsignment.LoadingBaseport.LogisticsLocation`
### Port of Discharge
The Final port of discharge for a vessel in sea or river movements, can be referenced as a contractual place related to Inco Terms or is the last place that the goods would be transported by a vessel.
**MMT Name:**`SupplyChainConsignment.UnloadingBaseport.LogisticsLocation`
## Coding of Locations
Locations often are coded values, this makes it easy to exchange an ambiguous value to identify a Location used within the supply chain.
[UN/CEFACT Recomendation 3 and Recomendation 16](https://unece.org/trade/uncefact/cl-recommendations) cover location and their coding.
You should familiarise yourself with the [UN/LOCODE](https://unece.org/trade/uncefact/unlocode) as this commonly used in transport contracts, financial arrangements and identification of a more granular location (i.e. terminal or container facility) under the [UN/LOCODE Child Code](https://unece.org/trade/uncefact/unlocode-child-code-repository), currently the following are listed as child codes to the UN/LOCODE.
### Child Codes of UN/LOCODE
#### Bureau International des Containers (BIC)
*The BIC Facility Code provides a unique, harmonized code to identify container facilities where container related operations take place for example repair, storage, stuffing/de-stuffing.*
More information:
#### IMO GSIS
*It defines port facilities of all kind, with focus on maritime security compliance with the ISPS regulation.*
More Information:
#### SMDG
*The SMDG Terminal Code List (TCL) contains codes for container handling terminal facilities that are called by seagoing cargo vessels in maritime transport.*
More Information: