sign in sign up
<<
Home , ISO 3166

No. 28993 Gaceta Oficial Digital, miércoles 01 de abril de 2020 1 No. 28993 Gaceta Oficial Digital, miércoles 01 de abril de 2020 2

Powered by TCPDF (www.tcpdf.org) Recommendation 16

UN/LOCODE – CODE FOR PORTS AND OTHER LOCATIONS

At its third session held in October 1972, the Working Considering that the code system should be based on the Party on Facilitation of International Trade Procedures two-letter alphabetic codes for the representation of names agreed to include in its programme of work a task to of , adopted in International Standard ISO 3166 prepare codes for ports, carrier and ships' name and for and recommended by the Working Party in October 1974; type of movement. Recommends that the five-letter alphabetic code system At its eleventh session in September 1975, the Group of described hereafter should be used for purposes of inter- Experts considered the need for a comprehensive code national trade to designate locations whenever there is a covering all locations where goods are subject to Customs need for a coded alphabetical designation for represent- control, and the following task was included in the ing the names of ports, airports, inland freight terminals programme of work: and other locations where Customs clearance of goods can take place, or otherwise proposed by Governments; "To establish the need to designate various locations involved in external trade (cities, ports, airports, border Invites Governments to transmit lists of entities with code crossings, terminals, etc.) with a view to the subsequent designations according to the established criteria and to creation of codes." ensure that each national list is continuously up-dated and communicated to the secretariat, After further consultation with the Economic Commis- responsible for the maintenance of the code system. sion for Latin America (ECLA), with the Economic and Social Commission for Asia and the Pacific (ESCAP), At the forty-second session of the Working Party repre- and with the International Air Transport Association sentatives attended from: (IATA), the secretariat put forward proposals for a pro- ; ; ; Canada; ; gramme of action for the development of a code which ; ; ; ; ; ; was agreed by the Working Party at its fifth session in ; Ireland; ; Luxemburg; ; the Nether- September 1977. lands; ; ; Russian Federation; Slovak A draft recommendation was submitted to the Working Republic; ; ; ; Party on Facilitation of International Trade Procedures, a of Great Britain and and the United subsidiary organ of the United Nations Economic Com- States of America. Representatives from , Bra- mission for Europe, and adopted at its twelfth session on zil, , , Korea, and partici- 22 September 1980. pated under Article 11 of the Commission' s terms of reference. At its fifty-first session in March 1995 the Meeting of Experts on Procedures and Documentation considered The session was attended by representatives of the secre- the secretariat proposals for the amendment of the Recom- tariats of the United Nations Conference on Trade and mendation including the Manual on maintenance princi- Development (UNCTAD), the United Nations Commis- ples for the LOCODE. sion on International Trade Law (UNCITRAL), as well as by representatives of the following intergovernmental The Working Party approved the second edition of Rec- and non-governmental organizations: Central Office for ommendation No.16 at at its forty-second session in International Railway Transport (OCTI), the World Cus- September 1995. toms Organization (WCO), International Air Transport Association (IATA), International Article Numbering RECOMMENDATION Association (EAN), European Electronic Messaging The Working Party on Facilitation of International Trade Association (EEMA), International Federation of Freight Procedures, Forwarders Associations (FIATA), International Cham- Being aware of the need for an internally-agreed code ber of Commerce (ICC), International Express Carrier's system to represent names of certain locations of interest Conference (IECC), International Organization for Stand- in international trade and transport; ardization (ISO), Society for World Wide Interbank Financial Transfers (S.W.I.F.T), International Union of Recommendation No. 16 adopted by the Working Party on Facilitation of International Trade Procedures, , January 1996 Railways (UIC), International Federation of Inspection ECE/ TRADE/205 [Edition 96.1] Agencies (IFIA).

Recommendation 16 103 LOCODE – Code for Ports and other Locations

I. BACKGROUND Latin America (ECLA), and the Economic and Social Commission for Asia and the Pacific (ESCAP). In addi- 1. The identification of a particular location is fre- tion, the secretariat had full access to the list of airports quently required in information interchange in interna- and other locations maintained by the International Air tional trade and transport, to direct the movement of Transport Association (IATA). Contributions were also goods - e.g. in , in shipping marks, and in data received from a number of Governments. elements identifying ports of call, ports or places of loading or unloading, ports or places of transhipment and 7. As to the code structure, particular attention was destination, places of clearance by Customs, etc. given to the three-letter alphabetical code already used within the air transport industry to designate airports and 2. The names of such locations are often spelt in differ- certain other locations. These codes have been widely ent ways and sometimes the same location is given used over a long period, have in most cases a mnemonic different names in different languages (e.g. LIVORNO - link to the place name, and have been introduced in other LIBOURNE - LEGHORN; LONDON - LONDRES - applications, notably in the ports code developed by LONDRA; WARSAW - VARSOVIE - WARSZAWA - ECLA. It was, however, appreciated that the number of WARSCHAU), which creates confusion and difficulties locations that could be foreseen, and the desirability of in data interchange. The identification in a unique and maintaining a reasonable mnemonic link, whilst at the unambiguous way of any place involved in international same time avoiding duplication of code designations for trade is therefore an essential element for the facilitation places with similar names, would require a code consist- of trade procedures and documentation. This can be ing of more than three alphabetic characters. The solu- achieved by using agreed, unique coded designations for tion preferred was to add two characters designating the such locations; this would have the added advantage of in accordance with International Standard ISO permitting an exchange of data in a safer and more 3166/1974 and recommended by the Working Party in economical way. October 1974, thus including a further element of identifi- cation and limiting the need for uniqueness of the location 3. For these reasons, the Working Party on Facilitation code for each place name to the country concerned. of International Trade Procedures agreed to include in its programme of work the tasks of preparing a code for port 8. The question of a numerical code alternative was names and of establishing the need to designate various considered, particularly for countries where the Roman locations involved in external trade, with a view to the alphabet is not widely used. However, there has been no subsequent creation of codes. subsequent demand for a numerical code. The need to add classifying elements to the basic code element was 4. There are several examples of location code systems demonstrated. Such classifying elements which are in use, covering places in individual countries, or belong- generally required and accepted have been included in the ing to a certain category, e.g. airports. Many countries code list in the course of its continuous up-dating and have developed code systems for distribution of mail maintenance. which, however, often include features reflecting meth- ods of postal distribution rendering them less suitable for general trade purposes. II. SCOPE 9. This Recommendation aims at providing a list of 5. The first part of the task therefore was to prepare lists such locations which are of interest in international trade of the ports and other locations to be covered. It became and transport and whose names need to be quoted in an necessary to establish criteria for the inclusion of names unambiguous way in data interchange, at establishing of localities and it was agreed to include - in addition to coded representations of the names of these locations and airports, inland freight terminals and maritime ports as at giving guidance for their use. defined for this purpose - other locations where goods can have their status changed from moving in international to national traffic, i.e. normally places with Customs clear- III. FIELD OF APPLICATION ance facilities (including locations referred to as “frontier 10. This Recommendation applies in all cases where a crossing points”). Moreover, it was felt that any other coded representation is required for names of ports, locations could be included at the request of the Govern- airports, inland clearance depots and freight terminals ment concerned. (In the present version, the criteria for and other locations which are frequently used for goods inclusion have been extended to cover all locations which movements associated with international trade, for use in are frequently used for goods movements associated with information exchange between participants in such trade. international trade.)

6. Major contributions towards the establishment of the IV. DEFINITIONS entity list were made by the International Chamber of Shipping (ICS), the International Association of Ports 11. The following definitions have been adopted for the and Harbours (IAPH), the Economic Commission for purposes of this Recommendation:

104 Recommendation 16 LOCODE – Code for Ports and other Locations

Port: Any location with permanent facilities at which VI. DESIGNATION AND COVERAGE vessels can load or discharge cargo moving in maritime traffic. 14. The code system laid down in this Recommendation may be referred to as the “United Nations LOCODE” Airport: Any location with permanent facilities at which (UN/LOCODE). aircraft can load or discharge cargo moving in air traffic. 15. UN/LOCODE is intended to cover ports, airports, Inland Clearance Depot (ICD): A common user facility, inland clearance depots and freight terminals and other other than a port or an airport, approved by a competent locations, as defined above, for purposes of international body, equipped with fixed installations and offering trade data interchange. services for handling and temporary storage of any kind of goods (including containers) carried under Customs 16. It is recognized that the coverage may not be complete transit by any applicable mode of transport, placed under for all applications, and that code elements for locations Customs control and with Customs and other agencies which may not be of interest in international trade might competent to clear goods for home use, warehousing, be needed for domestic purposes in conjunction with the temporary admission, re-export, temporary storage for international code. Although such additional entities onward transit and outright export. (Definition applies might not be shown in the published code element list, also to synonyms like Dry Port, Inland Clearance Termi- they may be included in the records and code elements nal, etc.) reserved by the secretariat, as appropriate, in consultation with Governments and international bodies concerned, as Inland freight terminal: Any facility, other than a port or part of the up-dating and maintenance procedures. It is an airport, operated on a common-user basis, at which also recognized that users might wish to make a selection cargo in international trade is received or dispatched. of relevant entities from the published list, and that abridged versions might be established for particular Location: Any named geographical place, recognized by applications. a competent national body, either with permanent facili- ties used for goods movements associated with internatio- 17. Place names, code elements and designations used in nal trade, and used frequently for these purposes, or UN/LOCODE do not reflect any opinion concerning proposed by the Government concerned or by a competent international, national, local or other boundaries, owner- national or international organisation for inclusion in the ship or administrative jurisdiction, but merely aim at UN/LOCODE. providing unambiguous and unique code elements to represent the names of the locations included. 12. The following general definitions apply for the pur- poses of this Recommendation: VII. STRUCTURE AND PRESENTATION Code: Data transformation or data representation in OF THE UN/LOCODE different forms according to pre-established rules. (Defi- nition adapted from ISO 5127-1:1983) 18. Besides the present, formal Recommendation, UN/ LOCODE includes “UN/LOCODE Manual” (see An- Code element: Result of applying a code to an element in nex), with a Part I giving technical details and further a set of elements to be coded (In UN/LOCODE a code information regarding its features, a Part 2 containing a element represents then name of a port, an airport, inland list of place names, each with a code element and sup- clearance depot, inland freight terminal, or a location . ported by certain classifiers and reference data, and a Part (Definition adapted from ISO 2382-4:1987) 3 containing support codes.

V. REFERENCES List of place names 19. The list of place names is based on submissions 13. ASCII International character set (ISO 8859-1) received from Governments, national facilitation bodies, ISO 3166/1993 “Codes for the representation of Names of international organisations or on requests received from Countries” users. In countries with more than one national language, more than one name version may be included. IATA Airline Coding Directory (published quarterly) Code element allocation ECLA Ports Code, Edition March 1978 20. A five letter code element is provided for each loca- ESCAP Port Code of the World, 1979 tion included in UN/LOCODE and consists of: UN/ECE/FAL Recommendation No.3 on ISO Country two letters identifying the country, according to the ISO Code - Codes for the Representation of Names of Coun- 3166 two-letter Code for the representation of names of tries countries, and UN/ECE/FAL Recommendation No.3;

Recommendation 16 105 LOCODE – Code for Ports and other Locations

three letters identifying the location within the country. secretariat should be contacted in order to obtain informa- These letters are either: tion on technical and other conditions under which the code list can be procured. - obtained from the IATA list of Location Identifiers; - obtained from the Government concerned; or Maintenance and up-dating - selected by the secretariat after consultation with 25. UN/LOCODE will be continuously maintained national or international bodies concerned, as appro- through the secretariat of the United Nations Economic priate. If consultation has not been possible, the Commission for Europe. Up-dated versions of UN/ secretariat selects code elements by using the three LOCODE will be issued annually, besides, up-dating first letters of the place name, or the initial letter and supplements may be issued occasionally when justified two letters of significance within the name, or initial i.a. by the number or nature of amendments between letters of composite names, always avoiding duplica- annual issues. tion of code elements within the country. 26. Amendments to UN/LOCODE (additions, changes 21. When code elements have been be selected by the and deletions) may be proposed ex officio by the UN/ECE secretariat, they will be presented ad interim pending secretariat, or may be transmitted by the national author- confirmation. ity or international organization concerned, or by users of UN/LOCODE. When practicable, any suggested amend- Classification ment will be submitted to the national authority con- 22. Some classifier functions which might be useful for cerned for approval or comment. Pending such approval, particular applications in various user environments are the amendment may be reflected in a provisional way in incorporated in the data record maintained by the secre- UN/LOCODE. Amended entries will be marked in the tariat. Those indicating administrative subdivision, func- code list; code elements for deleted locations will be tion, geographical area, status and approval date are reserved for five years, as will any code element which has shown after the location code element itself, as explained been changed. in the UN/LOCODE Manual, Annex to this Recommen- 27. If a proposed amendment is not accepted by the dation. national authority concerned, the reasons for rejection Presentation of code list should be communicated to the ECE secretariat which will inform the requesting party thereof. 23. The UN/LOCODE code list takes the form of a computer file, with countries listed in two-letter alpha- 28. In the case of proposals for amendment of a more betic order and with locations listed in comprehensive nature, or on matters of principle, the UN/ alphabetic place name order within each country. The ECE secretariat may invite a limited number of experts to inclusion of classifiers enables the separate listing of advise it on the most appropriate action to be taken, locations of one category, e.g. ports, or the grouping of subject to reporting to and final approval by the Working locations in one country according to their functions. Party on Facilitation of International Trade Procedures. There is also a possibility of grouping locations by Requests for inclusion of additional locations geographic region or sub-region by aggregation of coun- tries, or of maritime ports in geographical areas. 29. Requests for inclusion of additional locations and other changes in UN/LOCODE should be addressed to Availability the Trade Facilitation Section, United Nations Economic 24. UN/LOCODE is incorporated in the ECE data base Commission for Europe, Palais des Nations, CH-1211 and will also be available on computer diskettes; extracts GENEVE 10, Switzerland, in the form explained in the may exceptionally be available as print-out on paper. The UN/LOCODE Manual, Annex to this Recommendation.

106 Recommendation 16 LOCODE – Code for Ports and other Locations

Annex UN/LOCODE MANUAL Part I

1. DISCLAIMERS 2.2 The country code elements used in UN/LOCODE are the alpha-2 codes of ISO 3166. 1.1 General Disclaimer

1.1.1 The designations employed and the presentation of 3. CONTENTS AND LAYOUT OF the material in the United Nations Code for ports and UN/LOCODE; CODES AND other locations (UN/LOCODE) do not imply the expres- ABBREVIATIONS USED sion of any opinion whatsoever on the part of the Secre- tariat of the United Nations concerning the legal status of 3.0 The UN/LOCODE is presented in 7 columns, each any country, territory, city or area, or of its authorities, or with the following content (column designations in brack- concerning the delimitation of its frontiers or boundaries. ets):

1.1.2 Reference to any private entity (company) does not 3.1 Column 1: (LOCODE) imply recognition or endorsement by the United Nations. 3.1.1 Column 1 in UN/LOCODE shows the ISO 3166 1.1.3 UN/LOCODE is provided as a service to users, in alpha-2 Country Code which is followed by a space and a the framework of the trade facilitation effort undertaken 3-alpha code for the place name: XX XXX. The code list within the United Nations Secretariat. The Secretariat is organised in alphabetic code order (not countryname has no means to verify the accuracy of the contents of UN/ order). A code element added to a new version of the code LOCODE but endeavours to obtain approval thereof by list may be preceded by a plus sign (+); a minus sign (-) national authorities and international bodies concerned. means that the code element will be removed from the next The indication of status is intended to enable users to version of UN/LOCODE and a vertical bar (|) indicates a assess the credibility of the code entries; particular care change in the location entry. should be exercised in using codes with status RQ (Re- quest under consideration). The United Nations Secre- 3.1.2 For ease of reading, in the code list the country and tariat assumes no responsibility for any economic or other location parts of the code elements are separated by a damage consequential to the use of UN/LOCODE. space. In actual use, this space could be suppressed.

1.2 Special Disclaimer 3.1.3 As the IATA location code uses only three-letter code elements, it is understood that whenever a separate 1.2.1 Political developments have led to the dissolution three-letter code element appears as a data element to of some countries (former Czechoslovakia, , USSR indicate a location, it will designate the name of airport or and Yugoslavia). In these cases, it has not yet been location as adopted by IATA; whereas the same three possible to determine to which new national territories letters preceded by the two-letter country code might some locations belong. Until official confirmation can be depict a different UN/LOCODE location, e.g. PAR = obtained, the current code list should be regarded as IATA code for Paris, France (UN/LOCODE = FR PAR); provisional for the countries concerned. In the case of GB PAR = UN/LOCODE for Par, United Kingdom. Czechoslovakia, a list of locations not yet determined as belonging to either the Czech Republic or is 3.2 Column 2: (NAME) given under the code CS for former Czechoslovakia, in the 3.2.1 Column 2 shows the names of such locations case of the former USSR the full list hitherto included which have been accepted for inclusion in UN/LOCODE under the code SU is included, with an indication of the in accordance with the provisions of the Recommenda- new state to which each location now belongs, a "?" tion. indicates that this is not yet known. 3.2.2 It is presented by country in alphabetical country 2. REFERENCES code element order according to ISO 3166 and with place names listed in alphabetical order within each country. 2.1 The list of countries for which location codes are provided in UN/LOCODE is based on International Stand- 3.2.3 Place names are given - whenever possible - in ard ISO 3166-1993 “Codes for the representation of their national language versions as expressed in the names of countries” , using the short names in English for Roman alphabet using the 26 characters of the character the countries concerned. (The country names in ISO 3166 set adopted for international trade data interchange, with correspond to those given in the “Terminology Bulletin” diacritic signs, when practicable. Diacritic signs may be and “Standard Country or Area Code for Statistical Use”, ignored, and should not be converted into additional both published by theUnited Nations.) characters (e.g., Göteborg may be read as Goteborg, rather Recommendation 16 107 LOCODE – Code for Ports and other Locations

than Goeteborg, Gothenburg, Gotembourg, etc.), in order I. for Island(s) to facilitate reproduction in the national language. Pto for Puerto Pt for Port 3.2.4 In countries with more than one national lan- St for Saint guage, place names may be different in the respective languages. In such cases, more than one name version 3.3 Column 3: (SUB) may be included, followed by other versions placed within brackets, e.g.: 3.3.1 This column is intended to contain the ISO 1-3 character alphabetic and/or numeric code for the admin- Åbo (Turku) istrative division of the country concerned (state, prov- Turku (Åbo) ince, department, etc.), as communicated to ISO for 3.2.5 The Governments concerned have been or will be inclusion in International Standard ISO 3166/2 and when consulted regarding the most appropriate manner in deemed desirable to enhance the use of the code, or when which different name versions should be presented in UN/ requested by the country concerned. LOCODE. 3.3.2 In UN/LOCODE the country code element is left 3.2.6 As a service to users, names that have been changed out, as it is implicit, and only the subentity code is shown. may be included for reference. Such alternative name Where such codes are used, the corresponding code lists versions are included as a transitional measure after a are reproduced in Part 3 of UN/LOCODE. name change; they are followed by an equal sign (=), e.g.: 3.4 Column 4: (FUNCT) Peking = Leningrad = St Petersburg 3.4.1 This column contains a 1-digit function classifier code for the location, where: The code element will be shown only under the new name. 1 = port, as defined in Rec 16; 3.2.7 In some cases national location names are represen- 2 = rail transport function; ted differently in different languages. This may lead to 3 = road terminal function; misunderstandings which can cause disputes in interpreta- 4 = airport tion of transport and other contracts, in documentary 5 = postal function credits, etc. For any such differing but widely used name [6 = reserved for multimodal functions, ICDs etc] forms, known to or reported to the Secretariat, reference [7 = reserved for fixed transport functions (e.g. oil to the preferred name version may be made in UN/ platform)] LOCODE, followed by an equal (=) sign, e.g.: 8 = frontier passage point Flushing = Vlissingen 0 = function not known, to be specified Munich = München 3.4.2 A group of digits “1234-” in this column means 3.2.8 A place name may be followed, after a comma sign, therefore that all four specified functions apply to the by an indication of geographical or administrative signifi- location. The presence of the digit "4" will normally mean cance, such as the name of an island on which the place is that the code element shown is an approved IATA code. located, e.g. Bandung, Java, Taramajima, Okinawa. The digit “O” means that the criteria for inclusion apply, but that no information is available regarding the specific 3.2.9 There may be subordinate entities under a place transport mode functions of the location. name, e.g. different airports serving the same main loca- tion, outlying ports, freight terminals, etc. If a separate 3.5 Column 5: (GEO) code element has been assigned to such a location, the 3.5.1 This column is intended to show a geographic name of the sublocation is added after the main name, location identifier, to help find places and to aid transport separated by a hyphen (-), e.g. operations and statistics. Pending the creation of such a GB LHR London-Heathrow Apt code, expected to be of 3-digit numeric format, a 1- GB TIL London-Tilbury character code presently used by the Economic Commis- sion for Latin America and the Caribbean (ECLAC) in 3.2.10 The sublocation name is also listed in its proper their version of the UN/LOCODE is shown for some alphabetic name order place, followed by an oblique locations in that region. stroke (slash) (/) and the name of the main place to which it belongs, e.g.: The ECLAC code is the following: GB LHR Heathrow Apt/London 1 = Atlantic Ocean and dependencies, except those GB TIL Tilbury/London covered by 4, 5, 6, 7, 8 and 9 2 = Pacific Ocean and dependencies 3.2.11 Abbreviations used in Column 2 include: 3 = Indian Ocean and dependencies Apt for Airport 4 = North Sea

108 Recommendation 16 LOCODE – Code for Ports and other Locations

5 = Baltic Sea 3, which contains a de-coding list in code order and a code 6 = Mediterranean Sea list in alphabetical country name order. 7 = Black Sea 8 = Gulf of 5.2 The codes included in Column 3, subdivision, are 9 = Caribbean Sea thosecommunicated by the countries concerned to ISO for A = Arctic Ocean inclusion in Part 2of ISO 3166. Codes are presently F = River port available for only a few countries; for those, de-coding G = North American Great Lakes lists are given in Part 3. L = Lake port, except those under G 6. REQUESTS FOR ADDITIONAL 3.6 Column 6: (ST) LOCATIONS IN UN/LOCODE 3.6.1 This column is intended to indicate the status of the entry by a 2-character code, eg. whether approved by 6.1 Criteria for inclusion Government, by Customs, or based on a user requirement 6.1.1 It is recalled that ports, airports, inland clearance not necessarily recognized by an authority, etc. It is also depots, inland freight terminals and such other locations intended to show the status of checking, eg that function which are frequently used for goods movements associ- indicators are not verified. ated with international trade qualify for inclusion in UN/ LOCODE, and that “location” is defined as any “named 3.6.2 The following codes are used at present: geographical place, recognized by a competent national AA = Approved by competent national government body, either with permanent facilities used for goods agency movements associated with international trade, and used AC= Approved by Customs authority frequently for these purposes, or proposed by the Govern- AF = Approved by national facilitation body ment concerned or by a competent national or interna- AI = Code adopted by international organisation tional organisation for inclusion in the UN/LOCODE”. (IATA or ECLA) AS = Approved by national standardisation body 6.1.2 As a condition for including locations (other than AQ = Entry approved, functions not verified ports, airports, inland clearance depots and inland freight RQ = Request under consideration terminals), they should be “frequently used”. This is RR = Request rejected understood to mean on an average at least once weekly. QQ = Original entry not verified since date indicated 6.2 Request procedure UR = Entry included on user's request; not officially approved 6.2.1 Requests for inclusion of additional locations and XX = Entry that will be removed from the next issue other changes in UN/LOCODE should be addressed to the of UN/LOCODE Trade Facilitation Section , United Nations Economic Commission for Europe, Palais des Nations, CH-1211 3.7 Column 7: (DATE) GENEVE 10, Switzerland (Fax: 41 22 917 00 37). Such 3.7.1 Reference date, showing the year and month of requests should preferably be transmitted on diskette or request, of entry into the code list, of latest approval, etc., other electronic medium. For occasional requests or a as relevant. limited number not exceeding 10 entries, hard copy and telefax transmissions are acceptable.

4. SUBSIDIARY LOCATIONS 6.2.2 Generally, requests should emanate from national or international bodies. Requests from transnational 4.1 The code elements can be extended by the addition commercial enterprises will be submitted for scrutiny to of further characters to indicate subsidiary locations, such the national authorities concerned. Pending the outcome as areas of a port, different railway stations at the same of such scrutiny, and provided that other criteria are location, or terminals at the same airport, etc. Such code fulfilled, the request may be honoured and an appropriate element extensions are optional at the discretion of Gov- entry included under the status classification “RQ” (Re- ernments or local authorities concerned. However, if quest under consideration). If it proves impossible to notified to the secretariat, they will be incorporated in the obtain an authoritative response within a reasonable time, data record for the locations in question; they could be and if the Secretariat is convinced of the need for the entry made available to interested parties on request. to be included, it will be given the status classification “UR” (User requirement). 5. SUPPORT CODES 6.3 Request particulars 5.1 UN/LOCODE is supported i.a. by the alpha-2 6.3.1 Any request for additions to UN/LOCODE should country code of ISO 3166-1993. The code elements for the identify the requester and should contain the following countries represented in UN/LOCODE are listed in Part mandatory particulars: Recommendation 16 109 LOCODE – Code for Ports and other Locations

- the name of the place and the country where it is - Place name code (optional, a3, 3-letter code for place located. The name should be given in the national name) language version, as expressed in the Roman alpha- bet. If the national language contains diacritic char- 2. Place name (NAME, mandatory, a..29, plain lan- acters, the name should be given including such guage name) characters, to the extent they can be reproduced using 3. Subdivision (SUBDIV, optional, an..3) the ASCII International character set (ISO 8859-1). 4. Function code (FUNCTION, mandatory, an5), as Other widely used versions of the name may be given for follows (with table presentation within brackets): reference purposes. - the name or designation of any relevant administra- 0 not yet specified (0----) tive division (state, county, , etc.) where the 1 maritime (1----) place is located, including any established code to 2 rail (-2---) represent it. 3 road (--3--) 4 air (---4-) - the functions available at the place, under the criteria 5 mail (----5) established (port, railway terminal, road terminal, 8 border crossing point (----8) airport, parcel mail function, inland clearance depot, border crossing). If a location has more than one function, include all relevant codes in the function code. Example: for a 6.3.2 Optionally, the requester may suggest a 3-letter location with maritime, rail and air functions, assign the code to represent the place name, on the understanding code 12-4- that the Secretariat may have to assign another code if the code proposed is already used or for any other reason that 5. Remarks (REMARKS, optional, an..45) may be explained to the requester. 6.4.3 Allowed file formats 6.3.3 Any other information that the requester considers could be of interest may be included (e.g. proximity to The following formats are acceptable for the request another location, geographical coordinates, type of instal- submissions diskette files: lations and services, etc.). 6.4.3.1 Lotus 123/Symphony worksheet 6.3.4 Requests received will be reflected, as appropriate, The 1-2-3 or Symphony spreadsheet must contain data in in the next version or update of UN/LOCODE. Requesters a table format, in which each row represents a record and will be informed regarding the action taken on their each column represents a field. The table must start in the requests. first cell of the spreadsheet. If the data in the spreadsheet 6.4 Diskette submission characteristics is not in this form, load the file into 1-2-3 or Symphony and delete unnecessary rows and columns before you 6.4.1 Format create the diskette version.

The request submissions should preferably be recorded on Please create the following file name extensions for the 3 1/2 inch diskettes. The diskette should contain at least spreadsheet files: 2 files: Lotus 1-2-3 Versions 1 and 1A: .WKS - a README.TXT in ASCII format containing the Lotus 1-2-3 Version 2: .WK1 following information: Symphony Version 1.01: .WRK 1. format and equipment utilized in the other file Symphony Version 1.1: .WR1 2. organization which submitted the information 3. submission date 6.4.3.2 SYLK/Multiplan file 4. any other relevant information To save Multiplan spreadsheet in SYLK format, you need - a data file containing location inclusion records to issue the Transfer, Options, Symbolic commands in 6.4.2 Information to be submitted Multiplan. Then, issue the Transfer, Save commands. The details for importing SYLK files are similar to those In accordance with the specification in 1.7.1, the follow- used to import Lotus 123/Symphony worksheet. Please ing information should be supplied in the LOCODE make sure the diskette file has .SLK name extension request submission file: 6.4.3.3 dBASE II DBF file 1. Locode (LOCODE) which consists of: - Country code (mandatory, a2, ISO 3166 standard Please make sure the diskette file has .DBF name exten- code, see Part 3) sion

110 Recommendation 16 LOCODE – Code for Ports and other Locations

6.4.3.4 Visicalc/DIF file 2. the actual table ASCII file

The details for importing DIF files are similar to those Example of file description to be included on the used to import Lotus 123/Symphony worksheet. Please README.TXT file: make sure the diskette file has .DIF name extension Location request data structure Field Type From To 6.4.3.5 Character separated ASCII file COUNTRY C 1 2 The character separated ASCII file must have a comma LOCATION C 4 6 between fields and each character field must begin and NAME C 8 36 end with a quotation mark ("). The LOCODE submission SUBDIV C not applicable file must have a header record showing the titles of the FUNCTION C 38 43 fields that are included in every following record. If in an STATUS C not applicable individual record, optional data is missing, it should be DATE_REF C 45 48 shown as two quotation marks with nothing in between, REMARKS C 50 80 i.e. "". with the field names. The following is a sample header record followed by two fictitious data records: e.g., the figure below shows an ASCII file in table format: AE AUH Abu Dhabi 0---- 8103 "COUNTRY","LOCATION","NAME","SUBDIV","FUNCTION", "DATE_REF","REMARKS" ZW WKW Wankie National Park 0---- 8103 "AE","AUH","ABU DHABI","","0----","8103","", Please make sure the table ASCII file has .TBL name extension "ZW","WKW","WANKIE NATIONAL PARK","","0----","8103","" 6.4.3.7 Wordperfect mail merge document Please make sure the diskette file has .ASC name exten- The file should be a WordPerfect 5.1 secondary merge sion file. Please make sure the diskette file has .MRG name extension 6.4.3.6 Table ASCII file 6.4.3.8 dBASE III/dBASE IV This ASCII file is set up as table, with fields appearing in Please make sure the diskette file has .DBF name specified columns. These files do not use any delimiter to extension mark fields. The diskette has to include at least two files: 6.4.3.9 PFS:File 1. a README.TXT file in ASCII format containing the data structure for the table ASCII file; There is no restriction on file name extension.

Note: Part 2 is a UN/LOCODE codelist and Part 3 supports codes, they are available on diskettes only.

Recommendation 16 111