ࡱ>  Ȇbjbj cc} """""4G"G"G"h" #G"`bw$%&&&'(D($```````$cf6`")'"'))6`""&&K`---):"&"&`-)`--Xz[&wM,rZ*_a`0`Zg -gTz[z[g" \))-)))))6`6`-)))`))))g))))))))) : WORLD METEOROLOGICAL ORGANIZATION __________________INTERGOVERNMENTAL OCEANOGRAPHIC COMMISSION (OF UNESCO) _____________ Joint WMO-IOC Technical Commission for Oceanography and Marine Meteorology JOINT IODE/JCOMM EXPERT TEAM ON DATA MANAGEMENT PRACTICES, FIFTH SESSION OOSTENDE, BELGIUM 22-24 JUNE 2016 ETDMP-5 /  FORMTEXT Doc. XXX (2016-xx-xx) _______ ITEM: XX ENGLISH ONLY REPORT ON PROGRESS AGAINST ETDMP IV ACTION ITEMS (Submitted by Tobias Spears and Sergey Belov]) SUMMARY AND PURPOSE OF DOCUMENT The purpose of this document is to summarize progress on actions assigned to the ODP team at ETDMP IV and to report on other activities undertaken since the ETDMP IV.  ACTION PROPOSED The Meeting is invited to note the information contained in this document when considering its recommendations. ____________ Appendix: A. ODINAFRICA Review provided to Sergey Belov, Patrick Gorringe, Mika Odido, and Harrison Onganda References: ETDMP IV Report:  HYPERLINK "http://www.iode.org/components/com_oe/oe.php?task=download&id=31090&version=1.0&lang=1&format=1" http://www.iode.org/components/com_oe/oe.php?task=download&id=31090&version=1.0&lang=1&format=1 Report on ODP Status presented to IODE Officers in January 2016:  HYPERLINK "http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=12650" http://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=12650 (Agenda item 5.1 and Annex 1) DOCUMENT CONTENT ETDMP Report: 4. TASK TEAM FOR ODP 4.1 Governance Action 2 - Liaise and collaborate with other groups in order to establish strong links with existing regional and global initiatives Update The ODP team continues to liaise and collaborate with other groups in in attempts to establish strong links between the ODP and these initiatives, and to continue to promote the IODE. SNDM Argentina: A series of WebEx meetings were held with SNDM (Argentina) regarding issues and enhancements of SNDM ODP regional node. WIS: The ODP project manager participated in the first meeting of the Task Team for Integrated Marine Meteorological and Oceanographic Services within WIS (TT-MOWIS) with the ODP being one of the systems listed as a candidate contributor to WIS. The primary goals are to increase data flow into WIS (and the GTS in particular), and to increase the number of accredited WIS nodes and enable interoperability with other mature data systems. In addition, ad-hoc meetings took place between ODP and WIS during the WMO meeting where the Chair of ETMDP was participating. EuroGOOS: A numbers of e-mail discussions were held with EuroGOOS community regarding the ongoing collaboration with this stakeholder group. EMODNet: The ODP and EMODNet Physics teams have had preliminary discussions in order to foster closer collaboration by leveraging the EMODNet Physics portal technologies and to refocus some ODP efforts towards data access and less towards portal development. This collaboration is still in its infancy, but has been presented to the IODE Officers and supported by that group. ODINAFRICA: Progress has been made in implementing the ODINAFRICA node and data providers, but attempts made to improve higher level collaboration with have not been successful to date. An evaluation of the existing African Maine Atlas, metadata portal, and data portal and meetings was completed in order to seek opportunities to support the network in efforts to make marine data accessible to the global community. Progress has been slow due to inability to connect with key points of contact. The document detailing the review of the existing environment is available, but this requires follow-up. After this review occurred, a separate announcement related to revitalizing the ODINAFRICA web presence was released by the IODE Project Office, so this will impact the results of the assessment made by the ODP team. 4.2 ODP Management Action 4 -Monitor progress on the ODP 2012-2013 workplan and advise the SG-ODP on changes if necessary Update - No changes to ODP 2014-2015 workplan during inter-sessional period. Action 5 - Assess the deployment of the ODP nodes with assistance of the Partnership Centre for IODE ODP Update The following node and data provider changes have occurred during the inter-sessional period: MetOffice (UK) has deployed by May 2015 ODP Data Provider software with support from the Partnership Centre for IODE ODP. ODINAfrica regional node has been deployed by Partnership Centre for IODE ODP and KMFRI (Kenya) at the KMFRI infrastructure in November 2015 9 Light Data Providers were configured and deployed for NODC in ODINAfrica region. Action 6 - Liaise with ODS TT on standards and best practices related topics; identify, prioritize, and assign work activities resulting from discussions. Update - A number of email discussions were held in 2015, but no new priorities were raised. 4.4. Metadata Action 7 - Liaise with Metadata TT on vocabularies and metadata related topics; identify, prioritize, and assign work activities resulting from discussions. Update - A number of email discussions were held with Metadata TT in 2015, but due to lack of human resources in task team no actions were made. Action 8 - Revise and distribute the document on interoperability and migration of the ODP metadata into the ISO 19139 encoding in coordination with ETDMP TT for Metadata. Update - Not completed. Document of mapping ODP metadata field has been prepared by Tobias Spears in August 2014 and distributed to TTs. No replies from Metadata TT has been received. Following this, the ODP Partnership Centre implemented a GeoNetwork catalogue and harvester to enable access to ODP metadata via CSW and OAI-PMH and compliant with ISO 19115 Action 9 - Identify and network with potential new data providers (projects, programmes and other communities). Update The following potential data providers were identified: Sistema Nacional de Datos del Mar (SNDM): SNDM currently hosts a regional node delivering data from seven institutes. SNDM is a unique use case in that this node is an example of ODP technology used to deliver a regionalized, standalone portal and the user community is enabled through technology support and user training provided by the Partnership Centre for the IODE ODP. SNDM has sought support in customizing the ODP portal and back-office infrastructure to suit regional needs. This support model aligns with the spirit of the ODP Portal Toolkit a supported core technology stack which can be extended or customized within reason to support the needs of the user. US NODC: The US NODC has provided data to the ODP in the past, but there has been no recent activity. Because the US NODC acts as a hub or mirror for several global programs, there is the potential to enable access to a significant amount of data as part of a collaboration with this organization. Collaborating Programs: WMO/WIS: The collaboration between the WMO Information System (WIS) and ODP has been ongoing for some time and interoperability between the ODP and the WIS data catalogue has been consistently stable. Having WMO/WIS participate in the SG-ODP would provide an opportunity to expand on the existing interoperability arrangement in order to provide additional value-added access to WMO data holdings. GOOS: GOOS has been a strong supporter of the ODP and over the past three years has actively pursued opportunities for GOOS stakeholders and partners to work with the ODP and the IODE as a whole. GOOS represents a significant store of data and value-added geospatial web services which could be leveraged by the ODP. Working with GOOS to coordinate activities with the GOOS Regional Alliances would expand the ODP scope to near global coverage. GEOSS: As with GOOS, GEOSS has great potential as a provider of data and geospatial services. Furthermore, through the collaboration with ODP within the Ocean Data Interoperability Platform (ODIP) initiative, GEOOS provides a useful brokering use case through which access to metadata and data from other complementary programs can be achieved. EMODNet: Through the participation of GOOS personnel within EMODNet, EMODNet has become a strong supporter of the ODP, has provided access to a number of data sources, and a represents a wealth of data and spatial services. Unlike other partner programs, EMODNet is aligned by data theme as opposed to region. In discussions with EMODNet, there are opportunities to collaborate not only in domain of data interchange, but also in standards development and other fundamental data management activities. SeaDataNet: The exchange of data and metadata with SeaDataNet continues to be a priority for the ODP and SeaDataNet participation in the SG-ODP may help facilitate access and work towards addressing some of the existing barriers. Furthermore, SeaDataNet has been involved/led a number of standards related activities which may support the ODP and potential data providers. These standards based activities facilitate seamless access to data across providers and should continue to be undertaken. World Data System (WDS): Recently the ODP team has begun interacting with WDS through the WDS technical committee. The WDS adheres to a formal certification process for data providers which would assist in the development of accreditation procedures for the ODP. Furthermore, the WDS is undertaking the development of a portal to enable access to data from participating WDS members. Collaborating with WDS and the portal development team (PANGAEA) could greatly increase the resources discoverable through the ODP. Other Potential Stakeholders: British Oceanographic Data Centre (BODC): From a data provider perspective, the BODC is in many ways very similar to the US NODC. In both cases, data for many regional and global programs is available, both organizations use a combination of discovery and delivery tools to able data to be discovered and acquired in the manner required by the user, and in both cases, standards and best practices are documented and publicly available. The BODC also provides a niche support in the domain of vocabulary management and access. The BODC supports web services for enabling access to controlled vocabularies from many sources, has ensured consistent and reliable access to these services for a long time, and is actively participating in new initiatives where vocabulary management and access issues is of concern. Having the BODC participate in the SG-ODP may allow the ODP and data provider/node implementations to leverage hosted vocabulary services through partnership with the BODC. Action 9(i) - Identify and assess the contribution of the data from SeaDataNet Update - Since SeaDataNet has been concluded by 2015 no further discussions with SeaDataNet on data access were made. This action was refocused to IODE and its ODP involvement in the ODIP project, which is called to bridge data platforms from US, Europe and Australia. Action 9(ii) - Identify and assess the contribution of the data from EuroGOOS. Update The original plan for GOOS engagement was to establish ODP nodes and/or data providers to enable access to metadata and data from the GOOS GRAs. EuroGOOS was to act as the first stakeholder group to be engaged. With the emergence of EMODNet, the engagement strategy has changed. EMODNet Physics, the first ODP partner within the EMODNet program, is serving data from EuroGOOS and other partners though OGC compliant web services and providing access to the underlying data. Rather than engaging GRAs individually, the ODP has registered the EMODNet Physics web services and to access the data, users are taken to the EMODNet Physics portal. This approach promotes the data served through EMODNet and does not require duplicative effort from the partners in publishing data to ODP. Action 9(iii) - Identify and assess contributions from NMDIS, NODC of Russia, US NODC, ISDM, IMOS, OBIS and other existing data providers Update - Contributions from ISDM and NODC of Russia were made by new and updated dataset accessible from ODP Global node portal. Action 9(iv) - Prepare a document Technical specification on interaction with SeaDataNet, WIS, EuroGOOS, OBIS and ESIMO. Distribute the document within IODE, JCOMM, SeaDataNet, WIS, EuroGOOS and ESIMO. Update - Not completed. Due to changes in the ODP development strategy this will be shifted to new inter-sessional period. 4.6 ODP Portal Action 10 Identify and interact with the ODP user community (feedback/bug tracking) Update - Ongoing. Partnership Centre for IODE ODP is tasked to populate different tools and means of feedback with end users via ODP web site, ODP portal Helpdesk facility (to be completed in 2Q 2016) and ODP JIRA. Action 11 - Provide specifications for the ODP portal interface (features, functionalities, appearance, and user-friendliness manual on how to use the portal) Update No completed. 4.7 Capacity Building Action 12 Revise and distribute the technical documentation on the ODP V2 toolkit components Update Ongoing. Some minor updates were made in Data Provider manuals, new components (GIS and DataCache) will be documented and components will be included into ODP V2 package. Action 14 Prepare Manuals and Guides on IODE ODP Update - Ongoing. Training and educational materials used to support stakeholders in the implementation of ODP node and data providers has been published to OceanTeacher. These materials require updates as the new components of the ODP (e.g. GIS and DataCache) continue to develop and there will likely be additional requirements to revise documentation for existing components. 6.PARTNERSHIP CENTRE FOR THE IODE ODP 3. Action: As part of the ODP engagement tracking, the GOOS GRAs and contacts will be added to data provider register. Tobias will provide the template to Patrick for completion. 4. Action/Decision: Branding of data contribution to the ODP will be a priority for the GRAs. Such branch is already in place with interoperability arrangements such as the one with SeaDataNet. The ODP Partnership Centre will update the ODP Portal to include quick access to GRA data, along with associated branding. The target delivery will be the end of November along with enabling access to GRA data and metadata. 5. Action: In addition to providing quick access to the GRA data, there is a need to provide credit and background related to the GOOS GRAs. The ODP Partnership Centre will update the ODP portal and web site to include information about the GRAs. The target delivery will be the end of November along with enabling access to GRA data and metadata. 6. Action: There will be a need to properly brand contributions from the GRAs within the metadata catalogue. 7. Action: In order to proceed with implementing access to the GRA data, the list of existing FTP sites, web services, and contacts will be required. 8. Action: The ODP Partnership Centre will begin implementing access to GRA data (using EuroGOOS as a test case) within a 1 2 week sprint which will begin once Supporting information is provided by Patrick. 9. Action: In order to properly brand the GRA contributions to ODP, an appropriate high resolution logo will be required for the ODP web site, portal interface, and other communications material. Update (3 9): The original plan for GOOS engagement was to establish ODP nodes and/or data providers to enable access to metadata and data from the GOOS GRAs. EuroGOOS was to act as the first stakeholder group to be engaged. With the emergence of EMODNet, the engagement strategy has changed. EMODNet Physics, the first ODP partner within the EMODNet program, is serving data from EuroGOOS and other partners though OGC compliant web services and providing access to the underlying data. Rather than engaging GRAs individually, the ODP has registered the EMODNet Physics web services and to access the data, users are taken to the EMODNet Physics portal. This approach promotes the data served through EMODNet and does not require duplicative effort from the partners in publishing data to ODP. Appendices: (if any) Appendix A ODINAFRICA REVIEW (Version 20160217a) ODINAFRICA Review In order to identify potential opportunities for collaboration with ODINAFRICA in areas that had been primarily out of scope for the ODP team in the past, a review was undertaken. Observations and potential opportunities are intended as points for discussion and represent a mix of potential short and longer term activities which could be undertaken. The areas that have been reviewed include: Data content and thematic coverage Data accessibility Metadata content and catalogue Data standards Interoperability Infrastructure Connections with other programs/initiatives Data content and thematic coverage Results of review The thematic coverage of the data presents a good mix of framework, physical/environmental , biological, and socioeconomic domains and data hosted in larger (regional/global scale repositories are leveraged heavily). When combined with the regional atlases (ASCLME, BCLME, GCLME, MedSea LME) included in new African Marine Atlas hosted at  HYPERLINK "http://www.africanmarineatlas.org/" http://www.africanmarineatlas.org/, it is clear that there is a great deal of data spanning themes is in existence. A subset of the metadata records (~170 of ~600 entries) in the African Marine Atlas metadata catalogue were reviewed in more detail and the majority of these records were associated with data originating from global scale repositories such as those collected through remote sensing, administrative boundaries other readily available framework data, and synthesized products. Although there were a number of number of datasets in the catalogue which In some cases, the relative number of datasets originating from the participating nations was low compared to data and value-added product originating from data collated/managed outside the nation. A subsequent review of data from different nations showed a great deal of variation in the number of datasets, thematic coverage, and origin (national archives versus global sources). The completeness of layers within a thematic area varied and not all available data was being utilized (e.g. WOA05 was utilized heavily, WOA09 was utilized to a lesser extent, but WOA 2013 did not appear to be utilized at all). Potential opportunities A key objective is to support data providers in making available data not already published elsewhere. In essence, removing the burden of packaging and publishing framework data (e.g. administrative boundaries, coastlines and other features, and environmental data where the data providers are providing value added quality control or post processing) and providing more hands-on guidance and support in structuring, documenting, and publishing locally managed data to facilitate access and re-use. It is worth revisiting the thematic coverage by country in more detail as this provide insight into the types of data that are not being made accessible at the country level. Stakeholders in ODINAFRICA may be able to open communication with these institutes and researchers in order to advance the open data movement. Within the set of metadata records reviewed in detail, the number of global data repositories currently leveraged in the African Marine Atlas is finite (~20 or less). It would be useful to evaluate whether or not the production of layers can be streamlined (e.g. rather than having each nation undertake extract, transform, document, and publish these data, can a more automated approach be developed to produce these layers for all countries). Data accessibility Results of review The review of data accessibility focused specifically on how data was packaged and described for use by both the African Marine Atlas portal and for end users, along with ability to access the specific data used in production of the layer in the atlas. The African Marine Atlas (new version) provides links to both data and metadata. This functionality is not working fully and at this point the links to full metadata records is broken (incorrect call being made from the Atlas to the metadata catalogue) and many of the data access links are broken. However, a quick review of the original atlas ( HYPERLINK "http://omap.africanmarineatlas.org/" http://omap.africanmarineatlas.org/) was undertaken for comparison purposes and it was found that many datasets were accessible. However, data acquired from external systems routinely provided links to the external web site/portal and not to the data used in the atlas. Potential opportunities User engagement is needed in order for data to be brought forward for publication and to clarify how other existing data repositories have been used to produce layers in the atlas. It would be useful for IODE to develop and communicate data publication processes and best practices in order to support data providers in making data accessible and to promote some consistency in the approaches being employed, focusing on ensuring as direct access to data as possible. Metadata content and catalogue Results of review The African Marine Atlas Catalogue hosted by IODE ( HYPERLINK "http://geonetwork.iode.org/geonetworkAMA/srv/en/main.home" http://geonetwork.iode.org/geonetworkAMA/srv/en/main.home) is based on GeoNetwork, which is in use globally, and the existing content is based on ISO 19115, which is also a standard globally. There is some variability in the keywords used and the values supplied range from having country, discipline, and parameters, to having country alone. The overall level of content provided is low and elements are not always populated correctly. The abstracts supplied vary greatly in terms of completeness, which made it difficult to know where the data originated. In some cases, it appears as though a metadata template was provided and comments in the template were not removed prior to metadata publication. Structural metadata is routinely not supplied and although this can be derived in many cases by reviewing the data itself, it takes some effort to fully understand the content of the dataset. Data are routinely not directly associated with the metadata (no links provided) or the links to access the data are broken. There were few cited supporting resources (technical reports, etc.) associated with the metadata records. This is a working best practice that may serve to promote re-use of the data (e.g. user can review supporting documents to understand how data was collected, quality controlled, etc. without the data provider having to copy this information into the metadata records themselves). Although the new African Marine Atlas attempts to link datasets with the associated records in the metadata catalogue (not working - described in infrastructure section later), there are no direct connections between the metadata catalogue to atlas itself. Potential opportunities Based on the review of the ~170 records, IODE could provide additional support and training/education related to metadata development and best practices. This will assist data providers in producing useful metadata while keeping the mandatory content manageable. It is important to demonstrate the value of producing high quality metadata and provide guidance on how to do this. Each record in the metadata catalogue should include at least one data access link. A review of data accessibility and interoperability (discussed later), provide a basis for supplying some of these links. These connections will increase the usefulness of the metadata itself and will simplify the re-use of data within other regional and global systems. The types of links that would typically be included (where available) would consist of: Link to the originator of the data (e.g. WOA) if the data were extracted from another site Link to the packaged data used to produce the layer in the African Marine Atlas Link to any web services produced using the data (will be discussed further under data accessibility) It would be useful to revisit and seek opportunities to standardize the controlled vocabularies in use (e.g. agree upon standard code lists) In metadata as this will simply discovery of the data by other systems. Data standards Results of review In order to make best use of the supplied data while minimizing additional processing steps, some care must be undertaken to support (where possible) data encoding formats which are not only usable by other programs/systems, but which also stand the test of time (e.g. require limited maintenance by the provider). Based on a cursory review of all metadata in the African Marine Atlas metadata catalogue, the following common data interchange formats are in use: ASCII .SHP HDF .NC GeoTIFF .MDB .KML .E00 ** Other ArcGIS (unspecified) Other data formats are used, but are it is unclear how specialized they may be: Saga GIS Grid GRDC98 Generic binary Potential opportunities The data formats in use have implications when attempting to publish and use from within web based portals (interactive data viewers) and for users of the data. IODE could support data providers by providing some guidance/education on the use of file interchange formats, the long term maintenance implications, recommended supporting documentation to enable reuse of the data, and recommended formats depending on how the data will be published. There may also be opportunities to develop standards for data (e.g. ranges from structural conventions to naming conventions for fields in Shapefiles and databases, units of measure, etc.) and related context, though this would be secondary to having accessible and well documented data in their existing form. Interoperability Results of review Overall, technical interoperability supported by the African Marine Atlas and associate metadata catalogue is low. The African Marine Atlas catalogue supports the OGC Catalogue Service - Web specification (implemented within GeoNetwork), which is a useful starting point for enabling discovery and access to atlas metadata and data from the African Marine Atlas data portal and other external systems. Data interoperability is very low to non-existent as there is no evidence of geospatial web services in use. There is also no evidence of the African Marine Atlas using web services to access data from external systems. Potential opportunities There is a great deal of potential in having IODE educate data providers on key interoperability standards and to work with data providers in developing data publication workflows which leverage these standards where possible. Beyond education the use of these standards, their practical application in the context of ODINAFRICA needs to be undertaken and demonstrated. Otherwise, it will be difficult to gain buy-in to take on the additional infrastructure requirements and data publication efforts to implement the proposed interoperability programs. Infrastructure Results of review The review of existing infrastructure focused primarily on the African Marine Atlas data portal, along with the NODC status update provided in September 2015. Although connection issues were experienced between the African Marine Atlas data portal, metadata catalogue, and external sites, these have not been fully explored and are not included here. Translations and language support were not evaluated in this review, though these may be concerns in the future. Where information was provided, the existing NODC implementations include a mix of desktop and server grade hardware. Due to functional issue with the African Marine Atlas data portal, it is unclear how the connections between the atlas and the originating NODCs are configured. The metadata catalogue itself is hosted by IODE and in general, both performance and stability were fine. A small number of sporadic, non-critical errors were returned, so some attention to monitoring catalogue functionality is required as the project moves forward. The catalogue implementation is essentially the default setup of GeoNetwork and both the interface and menu links (e.g. Help, About) provide the default content. Many problems were experienced with the existing African Marine Atlas, including: Lack of functionality in some browsers Slow loading of data Many data layers not rendering properly Broken functionality when attempting to access full ISO or FAQ metadata records Broken links when attempting to access data Potential opportunities First and foremost, the IODE should seek opportunities to provide support to the developing NODCs as their infrastructure develop. In the absence of new hardware and other facilities, providing advice on basic working level best practices to ensure data and information are secured and recoverable in case of failure, is critical. There are many opportunities for IODE to support the development of the African Marine Atlas implementation, including troubleshooting the broken connection to the metadata catalogue (I have quickly looked at this and it appears to be a syntax issue in the code that tries to retrieve the metadata), provide advice on optimizing the access to published data, assist the NODCs and data providers in evaluating where the data should be published in order to provide best access with the infrastructure available, etc. Connections with other programs/systems Result of review The data presented within the African Marine Atlas includes globally recognized framework data source. Examples include: GEBCO -  HYPERLINK "https://www.bodc.ac.uk/data/online_delivery/gebco/" https://www.bodc.ac.uk/data/online_delivery/gebco/ ETOPO1 -  HYPERLINK "http://www.ngdc.noaa.gov/mgg/global/global.html" http://www.ngdc.noaa.gov/mgg/global/global.html GADM -  HYPERLINK "http://www.gadm.org/country" http://www.gadm.org/country MarineRegions.org -  HYPERLINK "http://www.marineregions.org/downloads.php" http://www.marineregions.org/downloads.php The data presented within the African Marine Atlas includes data from globally recognized environmental biological data sources/systems. Examples include: World Ocean Atlas (WOA) -  HYPERLINK "http://iridl.ldeo.columbia.edu/SOURCES/.NOAA/.NODC/" http://iridl.ldeo.columbia.edu/SOURCES/.NOAA/.NODC/ OBIS NASA's Ocean Color Web -  HYPERLINK "http://oceancolor.gsfc.nasa.gov/cms/" http://oceancolor.gsfc.nasa.gov/cms/ World Port Index -  HYPERLINK "http://msi.nga.mil/NGAPortal/MSI.portal?_nfpb=true&_pageLabel=msi_portal_page_62&pubCode=0015" http://msi.nga.mil/NGAPortal/MSI.portal?_nfpb=true&_pageLabel=msi_portal_page_62&pubCode=0015 (now available in database and GIS formats) World Database on Protected Areas -  HYPERLINK "http://www.protectedplanet.net/" http://www.protectedplanet.net/ (now available in multiple machine accessible formats) Although the original African Marine Atlas ( HYPERLINK "http://omap.africanmarineatlas.org/" http://omap.africanmarineatlas.org/) was not reviewed extensively, the structure and approach taken was very informative and there are some lessons which could be carried forward. The atlas included many linkages to external systems and these connections could be more fully leveraged Potential opportunities A review of the original and current African Marine Atlas implementations should be undertaken to verify completeness of the current implementation and to also identify opportunities to more fully leverage and simplify use of these data sources. Conclusion The review that was undertaken has highlighted areas for further exploration in infrastructure, standards and best practices development, data publication, and education/capacity planning. With a new operating model developing for the IODE Ocean Data Portal, and new partnership planned with EMODNet and other global and regional programs, it is the right time to discuss these opportunities with the ODINAFICA team. ______________      REF Meeting_Code \h  \* MERGEFORMAT DMCG-5/ REF Doc_no \* MERGEFORMAT Doc. x.y, p.  PAGE 2 ETDMP-5/ REF Doc_no \* MERGEFORMAT Doc. x.y, p.  PAGE 7  REF Meeting_Code \h  \* MERGEFORMAT DMCG-5/ REF Doc_no \* MERGEFORMAT Doc. x.y, p.  PAGE 1 56|}   $ % 4 7 > A İtcOcE4 hhOJQJ^JmH sH hOJQJ^J'hpOh;OJPJQJ^JnHtH!h;OJPJQJ^JnHtH$hpOhOJPJQJ^JnHtH*hpOh5;OJPJQJ^JnHtH$h5;OJPJQJ^JnHtH'hpOh6OJPJQJ^JnHtHhpOh5;OJQJ^JhpOhOJQJ^JhpOh5OJQJ^JhpOh5CJ^JmH sH 56V{|}lXXX$ $If]a$gd_N`kd$$IfxF`'H`'    4 xaxyt_N$$If]a$gd_N $$Ifa$gd_N$ x$If]a$gd_N   % 5 6 7 X e m n o y $$Ifa$gd $$Ifa$gd_N$:$Ifa$gd_N  :$Ifgd_N$  :$If]a$gd_N$ $If]a$gd_N $If]gd_N A B L M N S T W X c o v x y z 񺩛}n_M8)hh5;CJOJQJ\^JaJ#hD5;CJOJQJ\^JaJhhCJOJQJaJhhqWCJOJQJaJhpOhOJQJ^J hhOJQJ^JmH sH hOJQJ^JmH sH  hhOJQJ^JmH sH hOJQJ^JhNOJQJ^JmHnHu'jqhNh2OJQJU^JhNOJQJ^JjhNOJQJU^Jy z { \TLL$a$gd$a$gdqW`kd$$IfxF`'H`'    4 xaxyt_N$ ` $If^a$gd_N$ ` $If^a$gd_N$  $If^`a$gd_N   $$Ifa$gd_N $$Ifa$gd9g $$*$Ifa$gd $$Ifa$gd_N ~gd$a$gd'gd '$a$gd    X ʹrUC1"h#sCJOJQJ^JaJmH sH "hDCJOJQJ^JaJmH sH 8jhlhCJOJQJU^JaJmHnHtHu#hlh5CJOJQJ^JaJ#hlh5CJOJQJ^JaJhhCJOJQJaJ&hh6CJOJQJ]^JaJ h6CJOJQJ]^JaJ h;6CJOJQJ]^JaJ hD6CJOJQJ]^JaJ&hhCJOJQJ\]^JaJ Q Z _ ˺waL=.=Lhl5CJOJQJ^JaJh {5CJOJQJ^JaJ(hhCJOJQJ^JaJmH sH +hh5CJOJQJ^JaJmH sH hhOJQJ^J&hh5CJOJQJ\^JaJ hhCJOJQJ^JaJ hhCJOJQJ^JaJ hhCJOJQJ^JaJhhCJOJQJaJ hlhCJOJQJ^JaJ(hlh9gCJOJQJ^JaJmH sH  ? @ A B tggg (^`gd( HH]^`Hgd$a$gdgd$a$gd`kdd$$IfTxB04 xayt_NT B O P Q gd$a$gd "t ($ & Fa$gdkgd { & Fgd " & Fgdk$a$gd$ :*$]:a$gd {$ :p*$]:^`pa$gd (^`gd($^`a$gd K M N ;ufWH4H&jh "5CJOJQJU^JaJh "5CJOJQJ^JaJh&"5CJOJQJ^JaJh~5CJOJQJ^JaJh5CJOJQJ^JaJ'h hD0J5CJOJQJ^JaJ#hDhD5CJOJQJ^JaJ&jhD5CJOJQJU^JaJhD5CJOJQJ^JaJ#hh5CJOJQJ^JaJhCJOJQJ^JaJ#hhCJOJQJ\^JaJ M O P ʶާޘuhYG9*hDCJOJQJ\^JaJhCJOJQJ^JaJ"hh "t5;CJOJQJaJhD5;CJOJQJaJhh "tOJQJ^J hhCJOJQJ^JaJ#hh~5CJOJQJ^JaJh~5CJOJQJ^JaJhF5CJOJQJ^JaJ'hxh "0J5CJOJQJ^JaJ&jh "5CJOJQJU^JaJh "5CJOJQJ^JaJ#h "h "5CJOJQJ^JaJ M^ 7$8$H$^gdf 7$8$H$^gd) p7$8$H$^pgd) 7$8$H$^gd) 7$8$H$^gdD h7$8$H$^hgd) & F7$8$H$gdkgd ]LM^һvaLaLa5,h)5CJOJPJQJ\^JaJmH sH )h#sCJOJPJQJ\^JaJmH sH )hDCJOJPJQJ\^JaJmH sH 2hDhD5CJOJPJQJ\^JaJmH sH ,h)hDCJOJPJQJ^JaJmH sH &hDCJOJPJQJ^JaJmH sH ,hD5CJOJPJQJ\^JaJmH sH hCJOJQJ\^JaJhDCJOJQJ\^JaJh%tQCJOJQJ\^JaJ^a6]qRU ὥnU1hhfB*CJOJQJ^JaJnHphtH%h)5CJOJQJ^JaJmH sH "hfCJOJQJ^JaJmH sH "h)CJOJQJ^JaJmH sH /h)h)0J5CJOJQJ^JaJmH sH (h)h)CJOJQJ^JaJmH sH h)5CJOJQJ^JaJ h)h)CJOJQJ^JaJh)CJOJQJ^JaJ'(78ZʹsaO7/h)hB>CJOJPJQJ\^JaJmH sH "h)CJOJQJ^JaJmH sH "hB>CJOJQJ^JaJmH sH )hf5CJOJPJQJ^JaJmH sH /hfh)5CJOJPJQJ^JaJmH sH &hfCJOJPJQJ^JaJmH sH 1hh)B*CJOJQJ^JaJmH phsH 1hhfB*CJOJQJ^JaJnHphtH1hh)B*CJOJQJ^JaJnHphtH !"}0>J^gϷ{d{P{47 *hh5B*CJOJQJ^JaJnHphtH&hXfCJOJPJQJ^JaJmH sH ,h~5CJOJPJQJ\^JaJmH sH &h~CJOJPJQJ^JaJmH sH &hB>CJOJPJQJ^JaJmH sH &heYCJOJPJQJ^JaJmH sH /hB>h#s5CJOJPJQJ^JaJmH sH /hB>hB>5CJOJPJQJ^JaJmH sH /hB>h~5CJOJPJQJ^JaJmH sH "pqJK^`c & Fgd J 7$8$H$^gd J^gd J & F7$8$H$gd J 7$8$H$gd~ 7$8$H$gd J p7$8$H$^pgdB> p7$8$H$^pgdeY 7$8$H$^gdB> ̳s^J3,h Jh JCJOJPJQJ^JaJmH sH &h JCJOJPJQJ^JaJmH sH )h J5CJOJPJQJ^JaJmH sH )h5CJOJPJQJ^JaJmH sH ,h~5CJOJPJQJ\^JaJmH sH &h~CJOJPJQJ^JaJmH sH 1hh JB*CJOJQJ^JaJnHphtH1hXfh JB*CJOJQJ^JaJnHphtH4hXfh J5B*CJOJQJ^JaJnHphtH DEFO☁jVBV.&hCJOJPJQJ^JaJmH sH &h JCJOJPJQJ^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH ,hDh~CJOJPJQJ^JaJmH sH &h~CJOJPJQJ^JaJmH sH 9hh JB*CJOJQJ^JaJmH nHphsH tH1hh JB*CJOJQJ^JaJnHphtH9hh JB*CJOJQJ^JaJmHnHphsHtHDEF@AO,-^gdA 7$8$H$^gd^gd & F7$8$H$gd%tQgd%tQ^gd J & F7$8$H$gd J 7$8$H$gd~ & Fgd J?@ANOXպq]N7]#&h JCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH h%tQCJOJQJ\^JaJ&h%tQCJOJPJQJ^JaJmH sH ,h JhCJOJPJQJ^JaJmH sH 1hh%tQB*CJOJQJ^JaJnHphtH1hh JB*CJOJQJ^JaJnHphtH5hh JB*CJOJPJQJ^JaJmH phsH )h J5CJOJPJQJ^JaJmH sH )h5CJOJPJQJ^JaJmH sH  龣t]I5,hh%tQCJOJPJQJ^JaJmH sH &hCJOJPJQJ^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH +hB*CJOJQJ^JaJnHphtH1hhB*CJOJQJ^JaJnHphtH4hh5B*CJOJQJ^JaJnHphtH,h JhCJOJPJQJ^JaJmH sH &h JCJOJPJQJ^JaJmH sH ,h Jh%tQCJOJPJQJ^JaJmH sH  +,-56{^H/H/1hhB*CJOJQJ^JaJnHphtH+hAB*CJOJQJ^JaJnHphtH9hhAB*CJOJQJ^JaJmHnHphsHtH)hCJOJPJQJ\^JaJmH sH 2hh5CJOJPJQJ\^JaJmH sH ,h5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,hh%tQCJOJPJQJ^JaJmH sH &hCJOJPJQJ^JaJmH sH  GѺѦx[@#9hhAB*CJOJQJ^JaJmHnHphsHtH5hhAB*CJOJPJQJ^JaJmH phsH 8hhA5B*CJOJPJQJ^JaJmH phsH ,hA5CJOJPJQJ\^JaJmH sH ,hAh%tQCJOJPJQJ^JaJmH sH &hACJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH 4hh5B*CJOJQJ^JaJnHphDTjtH Gr !!!#0#9###$$$%%~&&&''')) d^gdAm$ 7$8$H$^gdAGr!!#9#$$&&''))++-.1111122ħxaxI/hh5CJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH 5hhAB*CJOJPJQJ^JaJmH phsH 9hhAB*CJOJQJ^JaJmHnHphsHtH9hhAB*CJOJQJ^JaJmH nHphsH tH<hhA>*B*CJOJQJ^JaJmH nHphsH tH))))**+++---.//11111122^gd & FgdAgd%tQ 7$8$H$^gdAgdA d`gdAm$ d^gdAm$222222222#3$313q3r3ȫz`I5&h8.0CJOJPJQJ^JaJmH sH ,h8.0h%tQCJOJPJQJ^JaJmH sH 2h8.0h%tQ5CJOJPJQJ\^JaJmH sH &hCJOJPJQJ^JaJmH sH 9hhB*CJOJQJ^JaJmH nHphsH tH9hhB*CJOJQJ^JaJmHnHphsHtH5hhB*CJOJPJQJ^JaJmH phsH 8hh5B*CJOJPJQJ^JaJmH phsH  2#3$3s3t344Y5Z5666667777j8k88 7$8$H$^gd^gd & F7$8$H$gd%tQ 7$8$H$^gd "^gd8.0 & FgdAgd%tQ^gdr3s3t3{3|3}366666667$7ջջo[D)4hh5B*CJOJQJ^JaJnHphtH,hAh%tQCJOJPJQJ^JaJmH sH &hACJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH &hCJOJPJQJ^JaJmH sH #hXpoh "CJOJQJ\^JaJh "CJOJQJ\^JaJ2h8.0h8.05CJOJPJQJ\^JaJmH sH ,h8.05CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH $7I7J7777777708⦇s\H4,hAh%tQCJOJPJQJ^JaJmH sH &hACJOJPJQJ^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH &hCJOJPJQJ^JaJmH sH <hh%tQ5B*CJOJQJ^JaJmHnHphsHtH<hh5B*CJOJQJ^JaJmHnHphsHtH9hhB*CJOJQJ^JaJmH nHphsH tH9hhB*CJOJQJ^JaJmHnHphsHtH 0818i8j8r8t88889C9D9tYB.&hSCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH 5hhB*CJOJPJQJ^JaJmH phsH 1hhB*CJOJQJ^JaJnHphtH8hhB*CJOJPJQJ\^JaJmH phsH ,h5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,hAh%tQCJOJPJQJ^JaJmH sH &hACJOJPJQJ^JaJmH sH  888N9O9(:)::::::X;Y;<<E<F<==gd+  & FgdS & F7$8$H$gd%tQ 7$8$H$^gd+ 7$8$H$gd+ ^gd+ 7$8$H$^gd`T & F7$8$H$gd%tQgd%tQD9M9N9O9W9X9h9i9j9&:վeH+H9hh+ B*CJOJQJ^JaJmH nHphsH tH9hh`TB*CJOJQJ^JaJmHnHphsHtH9hh+ B*CJOJQJ^JaJmHnHphsHtH9hh`TB*CJOJQJ^JaJmH nHphsH tH<hh`T5B*CJOJQJ^JaJmH nHphsH tH,h`T5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ,hSh%tQCJOJPJQJ^JaJmH sH  &:(:):3:s:t:::::::::::;A;B;X;Ͷ͢w_J3_Ͷ͢,h+ h+ CJOJPJQJ^JaJmH sH )h+ 5CJOJPJQJ^JaJmH sH /h+ h+ 5CJOJPJQJ^JaJmH sH &h+ CJOJPJQJ^JaJmH sH ,hSh%tQCJOJPJQJ^JaJmH sH &hSCJOJPJQJ^JaJmH sH ,h%tQ5CJOJPJQJ\^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH <hh`T5B*CJOJQJ^JaJmHnHphsHtHX;Y;b; <<<<<E<F<O<=====׾xa׏xP<&h@CJOJPJQJ^JaJmH sH  h@5CJOJQJ\^JaJ,h%tQ5CJOJPJQJ\^JaJmH sH ,h+ h+ CJOJPJQJ^JaJmH sH &h+ CJOJPJQJ^JaJmH sH 4h+ h+ 5B*CJOJQJ^JaJnHphDTjtH1hh+ B*CJOJQJ^JaJnHphtH)h+ 5CJOJPJQJ^JaJmH sH &h%tQCJOJPJQJ^JaJmH sH ==.>x>>>>1?s? @?@@@@AAA B BXBBBBDCsCtC8D9D:DbE 7$8$H$gd@gd@==>>>@@@C@I@AAAABBBBwC}C8D:DIDZG[G\GrGsGtGuGGijġӑrnZ&hh5;CJOJQJ^JaJh h "thCJOJQJ^JaJhCJOJQJ^JaJh-hCJOJQJ\aJ#hXpoh@CJOJQJ\^JaJ h@5CJOJQJ\^JaJh@CJOJQJ\^JaJ&h@CJOJPJQJ^JaJmH sH /hXpoh@5CJOJPJQJ^JaJmH sH bEcE&F'FFF[G\G]GrGsGtGuGGGGGGGGpHrH [$\$gd?I $$^a$gd $$a$gd$$a$gdBigd $^gdgd%tQ 7$8$H$gd@GGGGGGGGI J"J3JKKKKKK.Lͼޜm]UQUC1#jh?I0JCJOJQJUaJh?I0JCJOJQJaJh?Ijh?IUh?ICJOJQJaJmH sH $h?I5CJOJQJ\aJmH sH h?ICJ(OJQJaJ(mH sH h?ICJOJQJaJh?ICJ(OJQJaJ(&hh5;CJOJQJ^JaJ h} a5;CJOJQJ^JaJ h?I5;CJOJQJ^JaJhCJOJQJ^JaJ&hh5;CJOJQJ^JaJrHI IKInIIIIIIII J"J4J.L0LMMNNwOyO]P_PwP & F9D^gd?I [$\$gd?I.L\LiLMMwO_PvPgUzU|UUUWWXX=X>X+YBY[8[:[K[L[[[[[\\abUblbԹԦԞzjԦԞz[h?I6CJOJQJ]aJh?ICJ(OJQJaJ(mH sH #jh?I0JCJOJQJUaJh?I0JCJOJQJaJh?Ijh?IU$h?I5CJOJQJ\aJmH sH h?ICJ(OJQJaJ(h?I5CJOJQJ\aJh?ICJOJQJaJh?ICJOJQJaJmH sH h?ICJOJQJaJmH sH #wPjRSeUgUzU|UUVVW)Y+YCYY[[8[:[L[ ]"]^^M_O_ & F9D^gd?I [$\$gd?I & F9D^gd?IO___PaRaSbUbmbceeNffggggghhii & F 9D^gd?I & F 9D^gd?I & F 89D^8gd?I & F 9D^gd?I [$\$gd?Ilbccffggggg?jVjOm`mbmsmoo+r:r*CJOJQJ\aJh?ICJOJQJaJ iiiiiiiiiij'j.j=j?jWjlMmOm`mbmtmmm & F 9D^gd?I & F 9D^gd?I [$\$gd?I & F 9D^gd?Imo ooopp)r+r:r*B*phB' B :4%Comment ReferenceCJaJ<"< :4% Comment TextOJQJH2H :4% Balloon TextCJOJQJ^JaJRQ@BR {N Body Text 31$CJOJPJQJhmH sH :R: {N CharCJaJmHsHtH4@b4 4A{Header  !4 r4 4A{Footer  !.)@. 4A{ Page Number   Zm+ Table Grid 8:V0jjj%  H5B*\`Jph5B*\`Jph5B*\`JphD"D Zm+Caption xx5\mH sH tH e WHTML Preformatted7 2( Px 4 #\'*.25@9 OJPJ QJ^JmH nHsH tH88 Wmoz-txt-citetags*W`* W`Strong5\tt OColorful List - Accent 1 ^m$CJOJ PJ QJ aJmH sH ^^@^ W0 Normal (Web)dd[$\$CJPJ aJmH nHsH tHT/T heHeading 3 Char CJOJQJ_HaJmH sH tH jj "he paranumbered"!$ 8x1$`a$CJ\aJ hmH sH X/!X !heparanumbered CharCJPJ\aJ hmH sH tH 2 heagendatablebordertop8# & Fdd$dN[$\$^`CJPJaJmH nHsH tHHC@BH Body Text Indent$x^h/Rh Default%1$7$8$H$1B*CJOJPJQJ^J_HaJmH phsH tH jcj /d Table Grid7:V&0&2B@r2  Body Text'x~T@~  Block Text@( # n> ~N rd]r^d`CJOJ QJ aJ PChar Char Zchn Zchn Char Char1 Zchn Zchn Char Char Carattere Char Char Carattere)CJaJmHsHtH66 '~p Footnote Text*@& @ '~pFootnote ReferenceH*^^ Char1 Char Char Car Car,CJaJmHsHtHj/j ANormal1 -dm$5B*CJOJPJQJ^J_HaJmH nHphsH tHX@X ?I List Paragraph .^m$CJPJaJmH sH PK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭VGRU1a$N% ʣꂣKЛjVkUDRKQj/dR*SxMPsʧJ5$4vq^WCʽ D{>̳`3REB=꽻Ut Qy@֐\.X7<:+& 0h @>nƭBVq1u`X=:tڣf{Xx {dV=|kPo۵(h[x )IеnW[@;0PDbRy( "IROnVxCD' bJZ65I[adH+^D )>s=h ۟~7zWo^=[Qr||[?|̦ o{O=4?}}L$Xx%@|Ư'11%i$P,c[GD7sH5. 4kIƉZKTPBM HN7|nB#L7^`!\29pCH3nMb#$.'19b%+vJ~.!DI;DPz l 2I ͚;|y3+~Dؕjw0e1vdǪzO^I57y+d8bnv 4?6CK\M#= ċ(0'1 zxpWc/_X4/A_[)^&(fp[_NiK7@wd5= I?>_q샏[ꚝΡdrv5CojFh>PG3mOs=͡|7n;:N&?\8Lټ@_<}9H}]Ru Vx~p{3AsP~\v!cZ 6JOw׃SB HfЖ gpj*4nR2BM} rfw[BfV= vͅh7/sɳ ̲B3뤓eH=J_:hn$O\ʧFn;/x.M#+d,W87+IwOťwF) uepwPϬ pV$2v Sv(C8L\~+l`k& Y iTU#p~XHYHeʹ,fͰ-;Y7XmM 9ͬYMm*/稺W(r2bUGڱ]]HYUcF8U~ۍZZnJmi}kn^l u?~H uuuuuu"A ^G2r3$708D9&:X;=G.Llb|YȆDGJKNOQRSTVWYZ[\^`bcdfghjlnquwxyzy B )28=bErHwPO_im4xņȆEFHILMPUX]_aeikmoprstv{AMSMOCCCOP=PSSTCttttu0u9ucuuuuuvv(wHw{www!xxxxyyyy~FXXXXtXXXTXX4XTXXtXTX 3:<Ybhoq} "!!!@ @H 0(  (  t  s *? 3"?B S  ?~%rDoc_no OLE_LINK185 OLE_LINK186 OLE_LINK187 OLE_LINK181 OLE_LINK182 OLE_LINK183 OLE_LINK184AAAA    ~T```~  H P cmC6)F[`!!"":"D""")) ***8*B*******"+i+q+,,f,m,,,,,,,----1.8.$/I/J/////0E0O0V0^0X1h1j1&23344A5J5S7]7:;<<3=:=c=j=====j>q>>>>?LCRCTTaaWfafnn}"}}}}}}}}}}~~CE*"+a1'2 ;&;BBTD[DEEaaaa}}}}}}}}}~~3333335[?}}}}} ~~~$~K~P~Z~]~~~~~~~Ov8@,uk f9.38Gb*#+"ힺ^0,/0&dT2EqhK|YL($thN:h)ZtVrQn_ND :bv@ dJ)C l"8dJur1wh^`OJQJo(hHh^`OJQJ^Jo(hHohp^p`OJ QJ o(hHh@ ^@ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJQJ^Jo(hHohP^P`OJ QJ o(hH ^`CJaJo(.^`CJOJQJo(pp^p`CJo(.@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.h>^>`56o(*hHh  ^ `56OJQJo(*hHh  L^ `LhH.h ^`hH.h ~^~`hH.h NL^N`LhH.h ^`hH.h ^`hH.h L^`LhH.^`CJOJQJo(^`CJOJQJo(pp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo(^`CJOJQJo(^`CJOJQJo(pp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo(^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.h ^`hH.h ^`hH.h pL^p`LhH.h @ ^@ `hH.h ^`hH.h L^`LhH.h ^`hH.h ^`hH.h PL^P`LhH.^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.h^`OJQJo(hHh^`OJQJ^Jo(hHohp^p`OJ QJ o(hHh@ ^@ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJQJ^Jo(hHohP^P`OJ QJ o(hH^`CJOJQJo(^`CJOJQJo(pp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo(^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.h^`OJQJo(hHh^`OJQJ^Jo(hHohp^p`OJ QJ o(hHh@ ^@ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJ QJ o(hHh^`OJQJo(hHh^`OJQJ^Jo(hHohP^P`OJ QJ o(hH^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.^`CJo(.^`CJOJQJo(pp^p`CJo(.@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJo(.^`CJOJQJo(pp^p`CJo(.@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(8GT2EOv@ d)ZhN0 :bqhKqhK^0,rQn_9YL+ luk dJur1w                                             d0S@daARBiD%*Fe+H?IbI J@NJ$KL?|L_N9O!O%tQ@RkScAT`TUVOVeY[[.-^-E^r^ ` `} a-c"Acd fXf?fl[h#iBici{iDIj[j!mnKoRoXpo>p'~pq2#rsSt "tuy8uXu8wWxwy;z {4A{\~{<xLzlG^ W>[,2D>heUk9g;k9d !o]xP/uQ3 F7t n0p1nvrkD,~}bo+ MqWbB;[Jlf@FS<PQMSb^`/dsA47@l/DG@T\{N+]A@fqk9(BEJ*?a)NULN~W "#sstw`6PG.d~N6ApY}}@[?[?[?[?~@UnknownG.Cx Times New Roman5Symbol3. .Cx Arial;(SimSun[SO; BatangC.,{ @Calibri Light7.@Calibri5. .[`)Tahoma?= .Cx Courier NewG  MS Mincho-3 fg7@CambriaC" UniversArial;WingdingsA$BCambria Math"1hIzFgYzFgUǦ j@j@!nx4g}g} 2qXR ?9g2! xxR ,TC:\JCOMM\Meetings\Data Management\DMCG\DMCG-5 Geneva 201401\docs\DMCG-5_Template.dotDMCG-5Etienne Charpentier Tobias SpearsT             Oh+'0  < H T `lt|DMCG-5Etienne CharpentierDMCG-5_Template.dotTobias Spears10Microsoft Office Word@e@P@%@vYj ՜.+,D՜.+,4 hp|  WMO@g} DMCG-5 Title 8@ _PID_HLINKSAT.b*$http://omap.africanmarineatlas.org/o-' http://www.protectedplanet.net/o$^http://msi.nga.mil/NGAPortal/MSI.portal?_nfpb=true&_pageLabel=msi_portal_page_62&pubCode=0015X@!%http://oceancolor.gsfc.nasa.gov/cms/)}4http://iridl.ldeo.columbia.edu/SOURCES/.NOAA/.NODC/`6+http://www.marineregions.org/downloads.php6(http://www.gadm.org/country,;0http://www.ngdc.noaa.gov/mgg/global/global.html73https://www.bodc.ac.uk/data/online_delivery/gebco/CB:http://geonetwork.iode.org/geonetworkAMA/srv/en/main.home.b $http://omap.africanmarineatlas.org/9> #http://www.africanmarineatlas.org/sPhttp://www.iode.org/index.php?option=com_oe&task=viewDocumentRecord&docID=12650Fk`http://www.iode.org/components/com_oe/oe.php?task=download&id=31090&version=1.0&lang=1&format=1  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|~Root Entry F ŴData }1TablehWordDocumentSummaryInformation(DocumentSummaryInformation8CompObjr  F Microsoft Word 97-2003 Document MSWordDocWord.Document.89q