Layer name convention

Display names for AusSeabed layers on the AusSeabed Marine Data Portal

{Mandatory} | ({Conditional}) | [{Optional}]

{Location} {Product Type} {Publication Date} {Resolution} ({Organisation if not GA}) [{Identifier}]

 Transit: to include in title, have a separate tab for Transit

Examples:

Beagle Commonwealth Marine Reserve Bathymetry 2018 1m

Boags Marine Reserve Bathymetry 2018 1m (CSIRO) bf2018_v01

Name of the layer: name of the survey/file name rather than grouped layer

File name convention

Individual AusSeabed Data Hubs may have limitations on their capacity to define file names (i.e. because of integration with other systems). However, where they do have capacity to define names, the following convention may be useful:

{Location}_{Product Type}_{Survey Date}_{Resolution}_[{Identifier}]_{Vertical Datum}_{Horizontal Datum}_[{Version Identifier}].{Format Extension}

We would want to replace any special characters with _, and version information could simply be the date in an appropriate text format, Lower case characters used for survey identifiers, with a file name character limit of 255.

GA Example: Prefix with GAID (GA-4867)

GA4867_SouthernGreatBarrierReefShelf_Bathymetry_2020_64m_EGM2008__20200827T053422Z_cog.tif

CSIRO example: Prefix with SurveyNameID (In2019_e01)

In2019_t03_IndianOceanTransit_Bathymetry_2019_12m_EM122_CUBE_EGM2008_EPSG4326_20201214T052921Z_cog.tiff

Annex Background Discussion

Essentially, I think we need to agree and document:

a)       The name that we expect for display purposes on the portal

b)      File naming conventions for output products that can be downloaded

Have a read below. I will set up a meeting to discuss. Let me know who needs to be involved.

-------------------------------

A)      On the portal we currently have:

• Apollo Bay Bathymetry 2020 2m

• CSIRO_L3_bf2018_v01_Boags_1m_AHD

• Visioning the Coral Sea Bathymetry 2020 64m

As well as compilations:

• Antarctic REMA Hillshade Z5 and Bathymetry - (SCAR)

• Australian Bathymetry and Topography 2009 250 m

• General Bathymetric Chart of the Oceans (GEBCO) 2019 15 arc seconds

And in elevations:

• New South Wales - Contours - (GSNSW)

The current elements are:

The elements are separated by spaces or underscores, with bracketing of organisation sometimes present.

I suggest we adopt the following naming for the portal:

{Location} {Product Type} {Publication Date} {Resolution} {Vertical Datum} ({Organisation if not GA – Organisation Id})

E.g.

Apollo Bay Bathymetry 2020 2m AHD

Boags Bathymetry 2018 1m AHD (CSIRO – bf2018_v01)

Where Location is preferred to be from https://placenames.fsdf.org.au/. Product Type, Vertical Datum and Organisation are from a fixed vocabularies. Publication Date is most commonly year.

B)      For filenames we currently have:

https://ausseabed-public-warehouse-bathymetry.s3.ap-southeast-2.amazonaws.com/L3/62031b39-54f7-48ad-90f9-39fbc4c6585a/Apollo_Bay_City_of_Rayville_Bathymetry_2020_0_5m_cog.tif

https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/metadata/121620 -> 12160_GEOTIF.zip

https://data.csiro.au/collections/collection/CIcsiro:46110v1#/collection/CIcsiro:46110 -> CSIRO Data Access Portal is currently unavailable due to a scheduled outage. Reason: To perform routine storage maintenance. The application is expected to be back online by Thursday, 3 September 2020 10:00:00 AEST

I suggest we adopt the following naming for files:

{Location}_{Product Type}­_{Publication Date}_{Resolution}_{Projection?}_{Vertical Datum}_{Version Identifier}

Although this would be another option

{Vessel}_{Start Date of Journey}_{Voyage Number}_{Product Type}­_{Resolution}_{Projection}_{Vertical Datum}_{Version Identifier}

Or we could leave it to the institution.

We would want to replace any special characters with _, and version information could simply be the date in an appropriate text format.

 [AM1]MT/Josh to look into