SLIP (GME)
Minimum Metadata Standards for
GME Assets
Product ID – A.8 - 2328-014-009
Version 1.0
Prepared by
Sarah Armstrong,
Loreen O’Donnell,
Robert Koch
Date Updated:
August 2014
DOCUMENT CONTROL
Version
Status
Date
Author
Description of Version
Version 0.1
Draft
27/03/2013
Version 0.2
Draft
4/10/2013
Sarah
Armstrong
Loreen
O’Donnell
Version 0.3
Draft
28/01/2014
Sarah
Armstrong
Version 0.4
Draft
16/04/2014
Robert Koch
Version 0.5
Draft
08/04/2014
Robert Koch
Version 0.6
Draft
22/05/2014
Robert Koch
Version 0.7
Draft
05/06/2014
Robert Koch
Version 0.8
Draft
29/07/2014
Robert Koch
Version 1.0
Final
August 2014
Jenny Smith
Review, assess and implement any
gaps; and format the appearance of
the document.
Review, assess and implement any
gaps; and identify and incorporate
new features. Align with related
material
Incorporated feedback/support for
developer requirements.
Reformatted following feedback.
Incorporated feedback from WALIS
Office.
Incorporated feedback from
Landgate staff.
Incorporated further feedback
Amendment to accommodate the
Faux Table Replace solution
SLIP OCG endorsed
RELATED MATERIAL
Document Name
Description
SLIP Data Custodian Handbook
Document
Location Information Strategy (LIS)
Published
WALIS Custodian Policy
Published on WALIS website
Overview of New SLIP
Published
Landgate’s Strategic Development Plan
Published
Creative Commons Guide
Document
GME Info Window Content
Document
Google Maps Engine Help
Online:https://support.google.com/mapsengi
ne/?hl=en&topic=3033714
WALIS Location Information Access Framework
DRAFT Document
Version 1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 2
TABLE OF CONTENTS
1
PURPOSE ............................................................................................................................................. 4
2
SCOPE ................................................................................................................................................... 5
3
BACKGROUND TO GME ARCHITECTURE ..................................................................................... 6
4
METADATA HANDLING IN GME ....................................................................................................... 7
4.1
ADDITIONAL REQUIREMENTS AND SUPPORT FOR METADATA RELATED DOCUMENTS ................................................ 7
5
QUICK REFERENCE GUIDE .............................................................................................................. 9
6
DATA SOURCES .................................................................................................................................11
6.1
6.2
6.3
7
LAYERS ................................................................................................................................................22
7.1
7.2
7.3
8
MAP NAME ........................................................................................................................................... 33
MAP DESCRIPTION............................................................................................................................... 33
MAP TAGS ............................................................................................................................................ 35
ATTRIBUTIONS ...................................................................................................................................37
9.1
9.2
10
LAYER NAME ........................................................................................................................................ 22
LAYER DESCRIPTION ........................................................................................................................... 24
LAYER TAGS ........................................................................................................................................ 28
MAPS ....................................................................................................................................................33
8.1
8.2
8.3
9
DATA SOURCE NAME........................................................................................................................... 11
DATA SOURCE DESCRIPTION .............................................................................................................. 14
DATA SOURCE TAGS ........................................................................................................................... 17
NAME.................................................................................................................................................... 37
DISPLAY TEXT ...................................................................................................................................... 38
APPENDICIES .....................................................................................................................................40
10.1
APPENDIX 1.......................................................................................................................................... 40
Version 1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 3
1 PURPOSE
Google Maps Engine (GME) provides the ability to store user defined metadata to describe the GME
asset (Data sources, Layers and Maps). The metadata provided, along with system managed
statistics, provide the basis for asset discovery, both from ‘human-readable’ and programmatic (API)
standpoints.
In addition to making your data identifiable, correctly populated metadata in GME ensures your data
is understood and used appropriately and accurately. It underpins the continued and increased
access and use of your agency’s location information.
This document outlines the standards to which the assignment of GME metadata (Name,
Descriptions and Tags) should comply to achieve the above mentioned outcomes.
While your agency may have its own convention in relation to the naming of data, it is important that
that all GME assets comply with a minimum standard to ensure consistency in understanding and
access. This statement is particularly true of programmatic access of assets. This standard however
does provide opportunity for your organisation’s own standards to be applied, at least in part. It is
worth remembering that Layer Names in Map Services can be aliased (by way of the Display name),
to be context appropriate – this is another avenue of presenting information to your users in familiar,
context specific, or organisational preferred format.
Example of Layer aliasing, within a Map using the Display Name
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 4
2 SCOPE
This document covers the free text components within SLIP (GME) for:
1.
2.
3.
4.
Data sources;
Layers;
Maps;
Attributions
Adoption of this naming standard targets benefits in the following aspects of SLIP:








improve SLIP (GME) search by Map Editors;
improve SLIP website search by Map Viewers; and
providing additional data (i.e. metadata) to search for;
helping formulate expectations and promote consistency;
avoiding naming collisions that might occur when the information of different agencies is
combined;
providing meaningful information to Editors and Viewers;
assist Viewers to determine if your information is ‘fit for purpose’; and
ensuring assets can be consistently and reliably accessed programmatically.
This document is intended to support all users of SLIP to easily identify Data sources, Layers and
Maps within SLIP systems including GME and website. Making Names/titles, Descriptions and Tags
meaningful and descriptive will assist your customers in finding your data.
NB: Layer Names in map services can be aliased (by way of the Display name), to be context
appropriate – this document describes the underlying asset Name, and does not enforce any
standard for Display Names.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 5
3 BACKGROUND TO GME ARCHITECTURE
GME collectively refers to Data sources, Layers and Map services (aka Maps) along with associated
Attributions and Access Lists as assets. To assist in understanding the different GME assets addressed
in this document, the following diagam provides high level overview of how the different type of
assets interact in GME:
GOOGLE MAPS ENGINE
Agency/Custodians
Images and Data
Attributions
(Raster)
Layer
Databases
Data Sources
Raster or
Vector
Layer
Map
Services
Map
Services
Layer
Map
Services
Datasets
Access
Lists
A Data source can be viewed as the foundation level asset within GME. It represents an uploaded
version of the custodial data holding.
A Data source can then be used to create one or more Layers. Creating a Layer involves styling both
the geometry and attributes via the information window. It also optionally allows the filtering of the
Data source to display a targeted theme or subset of information.
Finally, one or more layers can be consumed into a (or multiple) Map(s). Within a Map, Layers may
be grouped into folders, default layer ordering and visibility set, and aliases defined to provide
contextual relevance.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 6
4 METADATA HANDLING IN GME
To assist in the searching (discovery) and understanding of assets, GME has implemented three user
input fields. These fields are Name, Description and Tags (collectively referred to as metadata fields).
Each field has a defined purpose within GME (and this standard), along with limits as described in the
following table:
Field
Purpose
User Interface
Field Type
Limits
Name
To enable editors, viewers and
programs the ability to easily
identify assets, the asset’s
component parts, and the most
recent version thereof.
Text Input
128 characters
Description
To enable further explanation of
the asset, providing opportunity for
viewers to establish if the data is fit
for purpose and correct usage. Link
to additional information, by use of
basic HTML.
Text Input
1024 characters
Tags
Entered as a comma delimited list,
Tags are an opportunity to capture
any relevant keywords related to
the asset, to enhance organisation
of data with GME adding the
discoverability of GME assets.
Tags are not case sensitive.
Text Input
100 characters/Tag
25 Tags per asset
It should be noted that GME has other limits which may affect how data is uploaded/structured
within GME. This includes, but is not limited to, limitations around single geometry type restrictions
or feature limits. This will usually result in multiple Data Sources or Layers. This standard has
provisions to support such custodial datasets requiring the creation of multiple assets in GME.
All values entered in GME metadata fields contribute to the search results for both the SLIP website
and GME administration environment.
4.1
Additional Requirements and Support for Metadata Related Documents
While not specifically detailed in this document, GME offers the ability for additional documentation
to be uploaded with the data (at the Data source level). Known as ‘sidecar files’, this functionally
supports the Item 7.4 of the Location Information Access Framework Guidelines, which includes
provision of a Data Dictionary as a minimum requirement for Data sources (referred to Location
Information Products within the Framework).
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 7
Sidecar files also offer an avenue for custodians who wish to provide additional information (but not
as a substitute) over and above the requirements of this the document and the Location Information
Access Framework.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 8
5 QUICK REFERENCE GUIDE
NAME
For detailed explanation refer to Page 11
Format:
{Title}_{Custodial Agency}_{Part}*_of*_{Part Count}*_{Date}
Example:
Aerial_Photography_Currency_Index_100k_LGATE_1_of_2_20140410
* where applicable
DESCRIPTION
DATA SOURCES
For detailed explanation refer to Page 14
Must
Contain:
{Abstract}
{Contact Details}
{Copyright/License}
{Update Frequency}
Example:
This dataset has been derived from Landgate's Primary Capture imagery metadata footprints.
Geometry of the features has been generalised to 1:100k map sheet index (and as such also serves
as a 1:100k map sheet index for WA). Attribution includes map sheet name and number, year of last
capture, and a capture history summary (as html table). The data has a target monthly update cycle.
Contact: Joe Blogs, WALIS, [email protected], +61812345678
© Western Australian Land Information Authority (Landgate) 2013. Use of digital land information is
subject to the following <a
href="http://www.landgate.wa.gov.au/corporate.nsf/web/shrinkwrap+Licence">Licence</a>.
TAGS
For detailed explanation refer to Page 17
Format:
{ANZLIC Open Data Category},{SLIP Enabler ID}*,{Synonyms},{View Restriction},{Data
License},{Project/Product}*,{Metadata Footprint Flag}*
Example:
* where applicable
Imagery,Maps,Air,LGATE-123,Date,Catalog,Catalogue,Map,Sheet,Tile,View-Public,License-Custom
NAME
For detailed explanation refer to Page 22
Format:
{Title} {Part}* of* {Part Count}*
* where applicable
Example:
Aerial Photography Currency Index 100k 1 of 2
DESCRIPTION
LAYERS
For detailed explanation refer to Page 24
Must
Contain:
{Abstract}
{Contact Details}
{Copyright/License}
{Update Frequency}
Example:
This layer has been derived from Landgate's Primary Capture imagery metadata footprints.
Geometry of the features has been generalised to 1:100k map sheet index (and as such also serves
as a 1:100k map sheet index for WA). Attribution includes map sheet name and number, year of last
capture, and a capture history summary (as html table). The layer is thematically displayed based on
the year of last capture. The data has a target monthly update cycle.
Contact: Joe Blogs, WALIS, [email protected], +61812345678
© Western Australian Land Information Authority (Landgate) 2013. Use of digital land information is
subject to the following <a
href="http://www.landgate.wa.gov.au/corporate.nsf/web/shrinkwrap+Licence">Licence</a>.
TAGS
For detailed explanation refer to Page 28
Format:
{ANZLIC Open Data Category},{SLIP Enabler ID}*,{Synonyms},{View Restriction},{Data
License},{Project/Prouct}*,{Metadata Footprint Flag}*
Example:
* where applicable
Imagery,Maps,Air,LGATE-123,Date,Catalog,Catalogue,Map,Sheet,Tile,View-Public,License-Custom
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 9
NAME
For detailed explanation refer to Page 33
Format:
{Title}
Example:
SLICP Portal
DESCRIPTION
MAPS
For detailed refer to Page 33
Must
{Abstract}
Contain:
{Usage Restrictions}
Example:
Map service supports/is consumed by the SLICP Portal (aka State Capture and Advice Register)
application. The content is designed to aid users of SLICP/SCAR to understand current, and planned
captures, as well as reference layers designed to assist users to identify their area of interest.
This service and its layers have been made available for public viewing.
<p><a href="https://slip.landgate.wa.gov.au" ><img src="https://ngisslipweb.sharepoint.com/SiteImages/slip_logo_sml.png"></a>
<img src="Agency X Image URL"/align=right height="70" >
</p>
TAGS
For detailed explanation refer to Page 35
Format:
{Synonyms},{SLIP Enabler Service}*
Example:
SLICP,Portal,Capture,Program,WALIS,SCAR
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
* Where applicable
Page 10
6 DATA SOURCES
6.1
Data Source Name
The objective of the Data source Name is to provide a unique and recognisable Name as so the
asset can be identified by both users and code projects. To assist with the construction of a
correctly specified Name, the requirement has been broken down to a number of components,
each represented in this document enclosed by curly brackets.
The Data source Name is a text input field supporting a maximum value of 128 characters.
Format:
{Title}_{Custodial Agency}_{Part}*_of*_{Part Count}*_{Date}
* where applicable
Example: Aerial_Photography_Currency_Index_100k_LGATE_1_of_2_20140410
Aerial_Photography_Currency_Index_Townsites_LGATE_20140431
Data source Names should contain underscores as the delimiter to all components and
words/numbers contained therein.
TIP: Some third party applications which can be used to consume data downloaded from GME
have limitations which prevent the use of files names containing spaces. Naming your source
files using underscores instead of spaces will assist end users of downloaded data to user your
data more readily.
IMPORTANT: To facilitate data update procedures within SLIP GME, initial and subsequent
Data source files require persistent naming. This means file names should not contain variable
components including, versioning notation or date stamping.
TIP: To save time when using the GME User Interface, it is recommended that source
file naming reflects that of the Data source Name outlined in this document, less the
_{Date} component. The _{Date} component will then need to be added to the
Data source Name which is prompted (derived from the file name) by the interface
during the load process.
The correct application of the individual components which make up the Data source Name
are outlined below:
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 11
6.1.1 Title (Required):
A title which concisely identifies the nature of the dataset. At least one Key Word
must be provided.
In addition to the Key Word, a well-defined title will contain (where relevant):
-
Extent Descriptor where dataset does not have a whole of WA focus.
Temporal Reference where dataset is a snap shot or has historical content.
Generalisation Reference where the dataset has been generalised (i.e. ABS
Census Statistic data is aggregated to SA1, SA2, SA3,… areas).
Geometry Type Descriptor where the dataset is also available in another
geometry type, or the greater data collection contains data in more than one
geometry (i.e. Point, Line, Polygon, Aspatial).
The syntax is Word[1]_Word[2]_…Word[n] (i.e. underscore delimited string)
Examples:
Pilbara_Road_Condition_{Custodial_Agency}_{Part}_of_{Part Count}_{Date}
2011_Census_B04A_Age_by_Sex_SA1_{Custodial_Agency}_{Part}_of_{Part Count}_{Dat…
2011_Census_B04A_Age_by_Sex_LGA_{Custodial_Agency}_{Part}_of_{Part Count}_{Dat…
Coastal_Infrastructure_Line_{Custodial_Agency}_{Part}_of_{Part Count}_{Date}
Coastal_Infrastructure_Point_{Custodial_Agency}_{Part}_of_{Part Count}_{Date}
6.1.2 Custodial Agency (Required):
Abbreviated name of the Custodial Agency. This item helps users identify the
Custodial Agency.
More than one agency may be identified under the Custodial Agency Name
component. Situations where this may be desirable may include (but not limited
to):
-
Where one agency has performed analysis or manipulation of another
agency’s data.
Where the data is a combination of custodial datasets (i.e. one agency is
responsible for the geometry and another is responsible for the attributes).
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 12
Acceptable abbreviated Custodial Agency values are provided in Appendix 1. For
new/unlisted agencies, SLIP Operations should be contacted for assignment of
Custodial Agency abbreviation.
Examples:
{Title}_LGATE_{Part}_of_{Part Count}_{Date}
{Title}_DRD_ABS_{Part}_of_{Part Count}_{Date}
6.1.3 Part & Part Count (Required where original dataset exceeds GME limits):
Large datasets which exceed GME limits (for example, file size or feature limits)
will need to be uploaded as multiple Data sources.
The Part and Part Count portions for Data source Names provide:
-
An identifier to the part component (corresponding to its numeric count)
and;
The total number (sum) of part components which make up the data in its
entity.
These items helps users and code projects understand when there are multiple
components, how many components they need to collate, and the corresponding
Data sources which are needed to form the data in its entirety.
The syntax is x_of_n (where x is the part component and is >= 1 and <= n and n
is the total number of part components and is > 1)
For datasets consisting of only one GME Data source the Part and Part count
requirement of this standard may be ignored (i.e. there is no need to add ‘1
_of_1’ to the Data source name.
NB: For datasets consisting of multiple GME Data sources, the Name value, for all
components parts must be identical with the exception of the Part identifier.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 13
Examples:
{Title}_{Custodial_Agency}_1_of_2_{Date}
{Title}_{ Custodial_Agency}_2_of_2_{Date}
6.1.4 Date (Required):
This is the date the data (including any of its component parts) commenced
loading or update to GME. This item helps users and code projects understand
and identify the latest data sources.
The syntax is YYYYMMDD.
Examples:
{Title}_{ Custodial_Agency}_{Part}_of_{Part Count}_20140402
{Title}_{ Custodial_Agency}_{Part}_of_{Part Count}_20141231
6.2
Data Source Description
The objective of the Data source Description is to provide more detailed information about the
data and define the constraints upon its use. Basic HTML code may be used to add formatting
and provide hyperlinks to additional resources such as copyright/license statements or data
dictionaries.
To assist the construction of a correctly specified Description, the requirement has been
broken down to a number of components, each represented in this document enclosed by
curly brackets.
The Data source Description is a text input field supporting a maximum value of 1024
characters (including spaces).
Must Contain: {Abstract} {Contact Details} {Copyright/License} {Update Frequency}
Example: This dataset contain road surface condition information for the Pilbara Region
and is collated from inspection reports carried out by work crews. Geometry has
been derived from the Landgate centreline dataset. It excludes private and local
government maintained roads.
Contact: John Smith [email protected] +61812345678
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 14
Agency X, Survey and Maintenance Division
© Agency X YYYY. <br/>
<!--CC-BY-NC for the Public Channel -->
<a rel="license" href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB"><img alt="Creative Commons Licence" style="borderwidth:0" src="http://i.creativecommons.org/l/by-nc-sa/3.0/au/80x15.png"
/></a> This work is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB">Creative Commons
Attribution-NonCommercial-ShareAlike 3.0 Australia License</a>.
This dataset is continuously maintained, and updates provided monthly.
The correct application of the individual components which make up the Data source
Description are outlined below:
6.2.1 Abstract (Required):
An abstract which describes the dataset. A well-defined Abstract will ideally
contain:
-
Dataset Lineage – Outline the history to the data contained in this Data
source.
Notable Omissions which one could otherwise expect the dataset to contain
(i.e. pre-2000 easements).
Extent Descriptor where dataset does not have a whole of WA focus.
Geometry Type Descriptor – Mention of the geometry type of the data (i.e.
Point, Line, Polygon, Aspatial).
Example:
This dataset contains road surface condition information for the Pilbara Region and is
collated from inspection reports carried out by work crews. Geometry (lines) has been
derived from the Landgate centreline dataset. It excludes private and local government
maintained roads.
{Contact Details}
{Copyright/License}
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 15
{Update Frequency}
6.2.2 Contact Details (Required):
Who should be contacted in relation to this data. As a minimum this should
contain:
-
Email
-
Phone Number of syntax +61XXXXXXXXX (no other formatting/spacing).
- Full Custodial Agency Name
Well defined Contact Details will ideally also contain:
-
Contact Name
Division/Team within Agency
Example:
{Abstract}
Contact: John Smith
[email protected]
+61812345678
Agency X, Survey and Maintenance Division
{Contact Details}
{Copyright/License}
{Update Frequency}
6.2.3 Copyright/License (Required):
The copyright/license statement for the dataset. Please note that this may include
links enclosed in HTML <a> tags.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 16
Examples:
{Abstract}
{Contact Details}
© Agency X YYYY. <br/>
<!--CC-BY-NC for the Public Channel -->
<a rel="license" href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB"><img alt="Creative Commons Licence" style="border-width:0"
src="http://i.creativecommons.org/l/by-nc-sa/3.0/au/80x15.png" /></a> This work is
licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB">Creative Commons Attribution-NonCommercial-ShareAlike 3.0
Australia License</a>.
{Update Frequency}
6.2.4 Update Frequency (Required):
A concise statement as to the update frequency of the dataset. This will assist
users to establish currency of the data.
Examples:
{Abstract}
{Contact Details}
{Copyright/License}
This dataset is continuously maintained, and updates provided monthly.
TIP: basic HTML can be used in Descriptions to provide links to additional information.
6.3
Data Source Tags
The objective of Data source Tags is to provide additional search material to aid the discovery
of the data and better organise data within GME. To assist the construction of correctly
specified Tags, the requirement has been broken down into a number of components, each
represented in this document enclosed by curly brackets.
NB: This document only describes Tags required to be specified by the Data Custodian.
Additional Tags may be added by SLIP Operations, via either manual or automated process, to
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 17
enable effective management of the GME repository and to extend the discoverability of data.
Some of these additional Tags may be dependent on other components of the minimum
standard outlined in this document, so it is imperative that this standard is adhered to by all
Custodians.
Examples of such additional Tags, include (but are not limited to):
- SLIP Enabler Service (based on Custodian specified {SLIP Enabler ID})
- ISO Category used in SLIP Enabler (based on Custodian specified {SLIP Enabler ID})
- Inclusion in other product or service, for example Property Interest Report.
The Data source Tag field is of type text input; supporting up to 25 single comma separated
Tags of a maximum 100 characters each (including spaces). Tags are not case sensitive.
Format: {ANZLIC Open Data Category},{SLIP Enabler ID}*,{Synonyms},
{View Restriction},{Data License},{Project/Product},*{Metadata Footprint Flag}*
* Where applicable
Example: Transport,MRWA-044,Main,Roads,View-Public,License-CC BY,PIR
Data source Tags should contain commas as the delimiter to all Tags.
TIP: For the first instance of the creation of an asset, it is recommended to type your Tags in
the field into GME (rather than cutting and pasting), as so the ‘search-ahead’ functions can
match existing tags, and avoid creation of new Tag variants. For example if ‘Parcel’ exists as a
Tag to another asset, there is no need to create a variant of ‘Parcels’. This helps enforce
consistency across Tags and hence search results.
The correct application of the individual components which make up Data source Tags are
outlined below:
6.3.1 ANZLIC Open Data Category (Required):
The ANZLIC Open Data Category provides a standardised set of themes to help
broadly categorise spatial data.
For the purpose optimising search results, the ANZLIC categories have been
modified slightly to form a more contextual specific set of themes, to enhance the
Tag list for assets.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 18
At least one of these themes must be present as a Tag (more than one theme may
be provided where relevant to the Data source).
Allowable Theme Tags (derived ANZLIC Open Data Categories):
-
Farming
Plants
Animals
Boundaries
Climate
Industry
Mining
Terrain
Environment
Geology
Soils
Health
Imagery
Maps
Defence
Water
Places
-
Address
Marine
Estuaries
Property
Planning
People
Society
Buildings
Structures
Transport
Infrastructure
Utilities
Satellites
Space
Disaster
Education
Events
Example:
Defence,{SLIP Enabler ID},{Synonyms},{View Restriction},{Data License},{Project/Product...
Geology,Soils,Boundaries,{SLIP Enabler ID},{Synonyms},{View Restriction},{Data License…
6.3.2 SLIP Enabler ID (Required, for assets which also existed in SLIP Enabler):
To assist those familiar with SLIP Enabler (SLIP GME’s predecessor) terminology
and identifiers, any Data source which existed in SLIP Enabler shall contain the
SLIP Enabler ID as a Tag.
Example:
{ANZLIC Open Data Category},LGATE-001,{Synonyms},{View Restriction},{Data Licence},{…
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 19
6.3.3 Synonyms (Required):
List alternative key words which describe the Data source. This will assist in
searches where a user uses different terminology. A good tip is to consult a
thesaurus service, like the one provided in Microsoft Word.
The table below provides examples of key words synonyms Tags.
Original Tag
Synonym(s)
Imagery:
Satellite, Image, Mosaic
Proprietor:
Owner, Title-holder, Landlord, Possessor, Vendor
Historical:
Past, Precedent, Historic
TIP: Also include common alternate spellings of words such as ‘Colour|Color’ and
‘Catalogue|Catalog’ to cater for users searching using common alternate
spellings.
Example: (assume Data source Name: ‘Aerial Photography Currency Index 100k…)’
…Category},{SLIP Enabler ID},Air,Imagery,Date,Catalog,Catalogue,Mapsheet,Tile,{Data …
6.3.4 View Restriction (Required):
Provides a high level indication of the existence of restrictions or costs associated
with accessing the Data Source. This was previously referred to as ‘Data Access
[Class]’
Allowable Values Are:
-
View-Public
View-Restricted
View-Subscription
Example:
…y},{SLIP Enabler ID},{Synonyms},View-Subscription,{Data Licence},{Project/Product},{M…
6.3.5 Data License (Required):
Provides a high level indication of the licencing restrictions applicable to the asset.
Allowable values refer to ‘off the shelf’ Creative Commons license categories, or a
custom licence implemented by the Custodial Agency.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 20
-
License-CC BY
License-CC BY-ND
License-CC BY-NC-SA
License-CC BY-SA
License-CC BY-NC
License-CC BY-NC-ND
License-Custom
For more about creative commons licences please visit :
http://creativecommons.org/licenses/
Example:
…y},{SLIP Enabler ID},{Synonyms},{View Restriction},License-Custom,{Project/Product},{…
…y},{SLIP Enabler ID},{Synonyms},{View Restriction},License-CC BY,{Project/Product}{Me...
6.3.6 Project/Product (Required where the asset supports a Project or Product):
Assets which support a specific Project, Program or Product may be tagged to flag
their association. This may help others find assets associated with a given project
or initiative.
For example assets consumed by Landgate’s Property Interest report may be
tagged ‘PIR’.
TIP: This is an unregulated requirement of this standard, so it will be the
responsibility project leads/contributors to devise/consistently implement unique
Tags. In construction of a good ‘Project’ Tag please consider:
-
Uniqueness of the Tag – consider using acronyms – common words may
be valid Tags to other requirements of this document.
Search for your proposed Project Tag. – Is it already in use? What other
results does it yield?
Example:
…egory},{SLIP Enabler ID},{Synonyms},{View Restriction},{Data Licence},PIR,{Metadata Fo…
…egory},{SLIP Enabler ID},{Synonyms},{View Restriction},{Data Licence},SPC,{Metadata Fo
6.3.7 Metadata Footprint Flag (Required where asset is ‘placeholder’ for the actual data):
For various reasons, some datasets may not be loaded or made available via SLIP,
however it is still imperative that this data can be discovered by users searching
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 21
the service. In these cases a polygon extent of the dataset should be uploaded to
GME, to ensure the provision of metadata and subsequent discoverability.
The ‘Metadata-Only’ Tag should be considered a ‘reserved word’. It must be
contained in the Tag list where the GME Data source being described is a footprint
representation of the actual dataset.
The syntax is …,Metadata-Only,…
Example:
…abler ID},{Synonyms},{View Restriction},{Data License},{Project/Product},Metadata-Only
7 LAYERS
7.1
Layer Name
The objective of the Layer Name is to provide a presentation name for the Layer. The Layer
name will be displayed in website search results and is the default name displayed in map
services. To assist the construction of a correctly specified Description, the requirement has
been broken down to a number of components, each represented in this document enclosed
by curly brackets.
The Layer Name is a text input field supporting a maximum value of 128 characters (including
spaces).
Format:
{Title} {Part}* of* {Part Count}*
* where applicable
Example: Aerial Photography Currency Index 100k 1 of 2
Aerial Photography Currency Index Townsites
Unlike Data sources, Layer Names should utilise spaces as the delimiter to all components and
words/numbers contained therein to aid human readability and presentation in map services
and website search results.
The correct application of the individual components which make up the Layer Name are
outlined below:
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 22
7.1.1 Title (Required):
A title which concisely identifies the nature of the Layer. At least one Key Word
must be provided.
In addition to the Key Word, a well-defined title will ideally contain (where
relevant):
-
Extent Descriptor where dataset does not have a whole of WA focus.
Temporal Reference where dataset is a snap shot or has historical content.
Generalisation Reference where the dataset has been generalised (i.e. ABS
Census Statistic data is aggregated SA1, SA2, SA3, etc).
Geometry Type Descriptor where the dataset is also available in another
geometry type, or the greater data collection contains data in more than one
geometry (i.e. Point, Line, Polygon, Aspatial).
Style Theme where a Layer has been styled to promote a certain attribute or
value. Incorporation of the Style Theme will help avoid clashes where one
Data source supports multiple layers of differing styles.
-
-
The syntax is Word[1] Word[2] …Word[n] (i.e. space delimited string)
Example:
Pilbara Road Condition {Part} of {Part Count}
2011 Census B04A Infant Distribution SA1 {Part} of {Part Count}
Coastal Infrastructure Line {Part} of {Part Count}
Coastal Infrastructure Point {Part} of {Part Count}
7.1.2 Part & Part Count (Required where original dataset exceeds GME limits):
Large datasets which exceed GME limits will need to be uploaded as multiple Data
sources. In the case of vector data the relationship between Data sources and
Layers is 1:M, thus multiple Layers will be required to display vector Data sources.
The Part and Part Count portions for Layer Names provide:
-
An identifier to the part component (corresponding to its numeric count)
and;
The total number (sum) of part components which make up the data in its
entirety.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 23
These items helps users and code projects understand how many components
they need to collate, and the corresponding Layers which are needed to represent
the data in its entirety.
The syntax is x of n (where x is the part component and is >= 1 and <= n and n
is the total number of part components and is > 1)
For datasets consisting of only one GME Data source the Part and Part count
requirement of this standard may be ignored (i.e. there is no need to add ‘1 of 1’
to the Layer name.
NB: For Layer sets referring to multiple GME Data sources, the Name value for all
component parts must be identical with the exception of the Part identifier.
TIP: While the Part and Part Count component of a Layer Name will be, in most
cases undesirable from a map service presentation perspective, datasets made up
of multiple layers will commonly be grouped in a map service, by way of a ‘locked
folder’. In these cases the ‘locked’ folder name will be the presentation name
viewable by the user. In other cases the Layer Name may be aliased to form the
desired presentation name for the Layer.
Examples:
{Title} 1 of 2
{Title} 2 of 2
7.2
Layer Description
The objective of the Layer Description is to provide further background information about the
data and define the limits of its use. Basic HTML code may be used to add formatting and
provide hyperlinks to additional resources such as copyright/license statements or data
dictionaries.
The Layer Description is a text input field supporting a maximum value of 1024 characters
(including spaces).
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 24
Must Contain: {Abstract} {Contact Details} {Copyright/License} {Update Frequency}
Example: This Layer represents contains road surface condition information for major
highways the Pilbara Region, classified by last inspection date. The data excludes
private and local government maintained roads, and has been further filtered
for major highways (CLASS=1). Condition information has been collated from
inspection reports carried out by work crews. Geometry has been derived from
the Landgate centreline dataset.
Contact: John Smith
[email protected]
+61812345678
Agency X, Survey and Maintenance Division
© Agency X YYYY. <br/>
<!--CC-BY-NC for the Public Channel --><a rel="license"
href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB"><img alt="Creative Commons Licence" style="borderwidth:0" src="http://i.creativecommons.org/l/bync-sa/3.0/au/80x15.png" /></a> This work is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB">Creative Commons
Attribution-NonCommercial-ShareAlike 3.0 Australia License</a>.
This dataset is continuously maintained, and updates provided monthly.
The correct application of the individual components which make up the Layer Description are
outlined below:
7.2.1 Abstract (Required):
A blurb which describes the Layer. A well-defined Abstract will ideally contain:
-
Dataset Lineage – Outline the history to the data contained in this Layer.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 25
-
Notable Omissions which one could otherwise expect the dataset to contain
(i.e. pre-2000 easements).
Extent Descriptor where dataset does not have a whole of WA focus.
Filters Applied to the Data source to limit the displayed contents of the
underlying Data source. (i.e. REGION = ‘Pilbara’)
Geometry Type Descriptor – Mention of the geometry type of the data (i.e.
Point, Line, Polygon, Aspatial).
Example:
This Layer contains road surface condition information for major highways in the Pilbara
Region, classified by last inspection date. The data excludes private and local
government maintained roads, and has been further filtered for major highways
(CLASS=1). Condition information has been collated from inspection reports carried out
by work crews. Geometry (lines) has been derived from the Landgate centreline dataset.
{Contact Details}
{Copyright/License}
{Update Frequency}
7.2.2 Contact Details (Required):
Who should be contacted in relation to this data? As a minimum this should
contain:
-
Email
-
Phone Number of syntax is +61XXXXXXXXX (no other formatting/spacing).
- Full Custodial Agency Name
Well defined Contact Details will ideally also contain:
-
Contact Name
Division/Team of Custodial Agency
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 26
Example:
{Abstract}
John Smith
[email protected]
+61812345678
Agency X, Survey and Maintenance Division
{Contact Details}
{Copyright/License}
{Update Frequency}
7.2.3 Copyright/License (Required):
The copyright/license statement for the dataset. Please note that this may include
links enclosed in HTML <a> tags.
Examples:
{Abstract}
{Contact Details}
© Agency X YYYY. <br/>
<!--CC-BY-NC for the Public Channel -->
<a rel="license" href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB"><img alt="Creative Commons Licence" style="border-width:0"
src="http://i.creativecommons.org/l/by-nc-sa/3.0/au/80x15.png" /></a> This work is
licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-ncsa/3.0/au/deed.en_GB">Creative Commons Attribution-NonCommercial-ShareAlike 3.0
Australia License</a>.
{Update Frequency}
7.2.4 Update Frequency (Required):
A concise statement about the update frequency of the Layer. This will usually
align with the update frequency of the underlying Data source. This will assist
users to establish currency of the data.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 27
Examples:
{Abstract}
{Contact Details}
{Copyright/License}
This dataset is continuously maintained, and updates provided monthly.
7.3
Layer Tags
The objective of Layer Tags is to provide additional search material to aid the discovery of the
data and better organise data with GME. To assist the construction of correctly specified Tags
the requirement has been broken down into a number of components, each represented in
this document enclosed by curly brackets.
NB: This document only describes Tags required to be specified by the Data Custodian.
Additional Tags may be added by SLIP Operations, via either manual or automated process, to
enable effective management of the GME repository and to extend the discoverability of data.
Some of these additional Tags may be dependent on other components of the minimum
standard outlined in this document, so it is imperative that this standard is adhered to by all
Custodians.
Examples of such additional Tags, include (but are not limited to):
- SLIP Enable Service (based on Custodian specified {SLIP Enabler ID})
- ISO Category used in SLIP Enabler (based on Custodian specified {SLIP Enabler ID})
- Inclusion in other product or service, for example Property Interest Report.
The Layer Tag field is of type text input; supporting up to 25 single comma separated Tags of a
maximum 100 characters each (including spaces). Tags are not case sensitive.
Format: {ANZLIC Open Data Category},{SLIP Enabler ID}*,{Synonyms}, {View
Restriction},{Data License},{Project/Product}*,{Metadata Footprint Flag}*
* Where applicable
Example: Transport,MRWA-044,Main,Roads,View-Public,License-CC BY,PIR
Layer Tags should contain commas as the delimiter to all Tags.
TIP: For the first instance of the creation of an asset, it is recommended to type your Tags in
the field into GME (rather than cutting and pasting), as so the ‘search-ahead’ functions can
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 28
match existing tags, and avoid creation of new Tag variants. For example if ‘Parcel’ exists as a
Tag to another asset, there is no need to create a variant of ‘Parcels’. This helps enforce
consistency across Tags and hence search results.
The correct application of the individual components which make up Layer Tags are outlined
below:
7.3.1 ANZLIC Open Data Category (Required):
The ANZLIC Open Data Category provides a standardised set of themes to help
broadly categorise spatial data.
For the purpose optimising search results, the ANZLIC categories have been
modified slightly to form a more contextual specific set of themes, to enhance the
Tag list for assets.
At least one of these themes must be present as a Tag (more than one theme may
be provided where relevant to the Data source).
Allowable Theme Tags (derived ANZLIC Open Data Categories):
-
Farming
Plants
Animals
Boundaries
Climate
Industry
Mining
Terrain
Environment
Geology
Soils
Health
Imagery
Maps
Defence
Water
Places
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
-
Address
Marine
Estuaries
Property
Planning
People
Society
Buildings
Structures
Transport
Infrastructure
Utilities
Satellites
Space
Disaster
Education
Events
Page 29
Example:
Defence,{SLIP Enabler ID},{Synonyms},{View Restriction},{Data License},{Project/Product…
Geology,Soils,Boundaries,{SLIP Enabler ID},{Synonyms},{View Restriction},{Data License…
7.3.2 SLIP Enabler ID (Required, for assets which also existed in SLIP Enabler):
To assist those familiar with SLIP Enabler (SLIP GME’s predecessor) terminology
and identifiers, any Layer which existed in SLIP Enabler, shall contain the SLIP
Enabler ID, as a Tag.
Example:
{ANZLIC Open Data Category},LGATE-001,{Synonyms},{View Restriction},{Data License},{…
7.3.3 Synonyms (Required):
List alternative key words which describe the Layer. This will assist in searches
where a user uses different terminology. A good tip is to consult a thesaurus
service, like the one provided in Microsoft Word.
The table below provides examples of key words synonyms Tags.
Original Tag
Synonym(s)
Imagery:
Satellite, Image, Mosaic
Proprietor:
Owner, Title-holder, Landlord, Possessor, Vendor
Historical:
Past, Precedent, Historic
TIP: Also include common alternate spellings of words such as ‘Colour|Color’ and
‘Catalogue|Catalog’ to cater for users searching using common alternate
spellings.
Example: (assume Data source Name: ‘Aerial Photography Currency Index 100k…)’
…Category},{SLIP Enabler ID},Air,Imagery,Date,Catalog,Catalogue,Mapsheet,Tile,{Data …
7.3.4 View Restriction (Required):
Provides a high level indication of the existence of restrictions or costs associated
with accessing the Layer. This was previously referred to as the ‘Data Access
[Class]’
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 30
Allowable Values Are:
-
View-Public
View-Restricted
View-Subscription
Example:
…y},{SLIP Enabler ID},{Synonyms},View-Subscription,{Data Licence},{Project/Product},{M…
7.3.5 Data License (Required):
Provides a high level indication of the licencing restrictions applicable to the asset.
Allowable values refer to ‘off the shelf’ Creative Commons license categories, or
custom licences implemented by the custodian.
-
License-CC BY
License-CC BY-ND
License-CC BY-NC-SA
License-CC BY-SA
License-CC BY-NC
License-CC BY-NC-ND
License-Custom
For more about creative commons licences please visit:
http://creativecommons.org/licenses/
Example:
…y},{SLIP Enabler ID},{Synonyms},{View Restriction},License-Custom,{Project/Product},{…
…y},{SLIP Enabler ID},{Synonyms},{View Restriction},License-CC BY,{Project/Product},{M...
7.3.6 Project/Product (Required where the asset supports a Project or Product):
Assets which support a specific Project, Program or Product may be tagged to flag
their association. This may help others find assets associated with a given project
or initiative.
For example assets consumed by Landgate’s Property Interest report may be
tagged ‘PIR’.
TIP: This is an unregulated requirement of this standard, so it will be the
responsibility project leads/contributors to devise/consistently implement unique
Tags. In construction of a good ‘Project’ Tag please consider:
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 31
-
Uniqueness of the Tag – consider using acronyms – common words may
be valid Tags to other requirements of this document.
Search for your proposed Project Tag. – Is it already in use? What other
results does it yield?
Example:
…egory},{SLIP Enabler ID},{Synonyms},{View Restriction},{Data Licence},PIR,{Metadata Fo…
…egory},{SLIP Enabler ID},{Synonyms},{View Restriction},{Data Licence},SPC,{Metadata F…
7.3.7 Metadata Footprint Flag (Required where asset is ‘placeholder’ for the actual data):
For various reasons, some datasets may not be loaded or made available via SLIP,
however it is still imperative that this data can be discovered by users searching
the service. In these cases a polygon extent of the dataset should be uploaded to
GME, to ensure the provision of metadata and subsequent discoverability.
The ‘Metadata-Only’ Tag should be considered a ‘reserved word’. It must be
contained in the Tag list where the GME Layer being described is a footprint
representation of the actual dataset.
The syntax is …,Metadata-Only,…
Example:
…abler ID},{Synonyms},{View Restriction},{Data License}{Project/Product},Metadata-Only
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 32
8 MAPS
8.1
Map Name
The objective of the Map Name is to provide a unique and recognisable name as so asset can
be identified by both users and code projects. To assist the construction of a correctly specified
Description, the requirement has been broken down into a number of components, each
represented in this document enclosed by curly brackets.
The Map Name is a text input field supporting a maximum value of 128 characters (including
spaces).
Must Contain: {Title}
Example:
ABS 2011 Census Basic Community Profile by LGA
Map Names should contain spaces as the delimiter to all components and words/numbers
contained therein.
The correct application of the individual components which make up the Map Name are
outlined below:
8.1.1 Title (Required):
A title which concisely identifies the nature of the dataset. At least one Key Word
must be provided.
In addition to the Key Word, a well-defined title will ideally contain:
-
Extent Descriptor where the map has specific regional focus.
Intended Agency where map has been specifically compiled for needs/use of a
given Agency/team. When using abbreviated agency names, for consistency
please consult recommended values provided in Appendix 1.
The syntax is Word[1] Word[2] …Word[n] (i.e. space delimited string)
Examples:
Locate Pilbara
DRD Service
Southwest NRM Service
8.2
Map Description
The objective of the Map Description is to provide further background about the map and its
intended audience/use. To assist the construction of a correctly specified Description, the
requirement has been broken down to a number of components, each represented in this
document enclosed by curly brackets.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 33
The contents of the Map Description is displayed in website search results, and as a header to
the ‘table of contents’ in the default GME map viewer. Basic HTML code may be used to add
formatting, reference images/logos and provide hyperlinks to additional resources.
The Map Description is a text input field supporting a maximum value of 1024 characters
(including spaces).
Must Contain: {Abstract}
{Usage Restrictions}
Example:
Locate is a revolutionary online tool that opens up a wealth of Western
Australian location information from many different WA sources all
provided in a single link for you. To learn more about Locate click <a
href="http://slipfuture.landgate.wa.gov.au/Pages/LocateGettingStarted.asp
x" target="_blank">here.</a> <br/><br/><a
href="http://slipfuture.landgate.wa.gov.au/Pages/LocateHelpAndFAQs
.aspx" target="_blank">Help &amp; FAQs</a><br>
<br>
<a href="http://slipfuture.landgate.wa.gov.au/Pages/LocateDataProviders
.aspx" target="_blank">Data Providers</a><br>
<br>
<a href="http://slipfuture.landgate.wa.gov.au/Pages/LocateTermsandCon
ditions.aspx" target="_blank">Terms and Conditions</a><br/>
<br/>
<img src="https://ngisslip-web.sharepoint.com/SiteImages/_w/SLIP_Locate
_Logo_jpg.jpg" width="255" height="42"/></img>
The correct application of the individual components which make up the Layer Description are
outlined below:
8.2.1 Abstract (Required):
Concise blurb which describes the Map Service.
Example:
This Map service supports the Department of Housing HAGIS Application.
{Usage Restrictions}
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 34
8.2.2
Usage Restrictions (Required):
Who is the intended audience?
Example:
{Abstract}
For non-commercial use by Department of Housing users only.
8.3
Map Tags
The objective of Map Tags is to provide additional search material to aid the discovery of the
Map Service. To assist the construction of correctly specified Tags the requirement has been
broken down into a number of components, each represented in this document enclosed by
curly brackets.
The Map Tag field is of type text input; supporting up to 25 single comma separated Tags of a
maximum 100 characters each (including spaces). Tags are not case sensitive.
Format: {Synonyms},{SLIP Enabler Service}*,{View Restriction}
* Where applicable
Example: DOH,Housing,Assets,Geospatial,Information,System,Private
Map Tags should contain commas as the delimiter to all Tags.
TIP: For the first instance of the creation of an asset, it is recommended to type your Tags in
the field into GME (rather than cutting and pasting), as so the ‘search-ahead’ functions can
match existing tags, and avoid creation of new Tag variants. For example if ‘Parcel’ exists as a
Tag to another asset, there is no need to create a variant of ‘Parcels’. This helps enforce
consistency across tags and hence search results.
The correct application of the individual components which make up Map Tags are outlined
below:
8.3.1
Synonyms (Required):
List alternative key words which describe the Map Service. This will assist in
searches where a user uses different terminology. A good tip is to consult a
thesaurus service, like the one provided in Microsoft Word.
The table below provides examples of key words synonyms Tags.
Original Tag
Synonym(s)
Imagery:
Satellite, Image, Mosaic
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 35
Proprietor:
Owner, Title-holder, Landlord, Possessor, Vendor
Historical:
Past, Precedent, Historic
TIP: Also include common alternate spellings of words such as ‘Colour|Color’ and
‘Catalogue|Catalog’ to cater for users searching using common alternate
spellings.
Example: (assume Map Name: ‘Department of Housing HAGIS Service’)
DOH,Housing,Assets,Geospatial,Information,System,{SLIP Enabler Service},{Data Access…
8.3.2
SLIP Enabler Service (Required, where Map is a SLIP Enabler Service replacement):
GME Map Services which are an equivalent replacement to a SLIP Enabler service,
should contain the SLIP Enabler map service name as a tag. This will assist users
familiar with SLIP Enabler terminology to discover equivalent services in GME.
8.3.3 View Restriction (Required):
Provides a high level indication of the existence of restrictions or costs associated
with accessing the Layer.
Allowable Values Are:
-
Public
Restricted
Subscription
Example:
{Synonyms},csImagery,{View Restriction}
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 36
9 ATTRIBUTIONS
Attributions only apply to Imagery Data and are used to identify copyright details. Attributions
are shown on GME Map services when viewing raster layers with attribution.
The Copyright should reflect the year is the year the asset was first published.
There are two components to Attributions which are described below.
9.1
Name
The Attribution Name provides a reference to the Attribution to assist with management and
assignment of Attributions with GME. To assist the construction of correctly specified Names
the requirement has been broken down into a number of components, each represented in
this document enclosed by curly brackets.
Name:
{Title} {Year}
Example: Landgate 2014
Landgate 2013
The correct application of the individual components which make up Attribution Name are
outlined below:
9.1.1
Title (Required):
A concise name for the Attribution. This will commonly be the agency name to
which the copyright refers.
Example:
Landgate {Year}
State of WA {Year}
9.1.2
Year (Required):
As copyright is bound to the year first published, there will be a need to have
multiple Attributions for an agency name to whom the copyright refers. The Year
component of the Attribution Name is designed to concisely identify this.
The syntax is YYYY.
Example:
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 37
{Title} 2013
{Title} 2014
9.2
Display Text
The Attribution Display Text Field is the copyright text string to appear on the map
accompanying the raster layer. To assist the construction of correctly specified Display Text the
requirement has been broken down into a number of components, each represented in this
document enclosed by curly brackets.
Name:
{Copyright Symbol} {Title} {Year}
Example: © Western Australian Land Information Authority (Landgate) 2014
The correct application of the individual components which make up Attribution Name are
outlined below:
9.2.1
Copyright Symbol (Required):
Start the copyright statement with the copyright symbol ‘©’
Example:
© {Title} {Year}
9.2.2
Title (Required):
To whom is the copyright referring?
A well-defined title will ideally contain:
-
Agency Name.
Common Trading Name (in brackets) where the agency being referred to
trades under a different name.
Example:
{Copyright Symbol} Western Australian Land Information Authority (Landgate) {Year}
9.2.3
Year (Required):
The year to which the copyright is bound.
The syntax is YYYY.
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 38
Example:
{Copyright Symbol} {Title} 2013
{Copyright Symbol} {Title} 2014
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
Page 39
10 APPENDICIES
10.1 Appendix 1
Approved Agency Abbreviations for use within GME:
Agency Name
Australian Bureau of Statistics
City of Busselton
City of Melville
City of Stirling
City of Swan
Department of Aboriginal Affairs
Department of Agriculture and
Food
Department of Commerce
Department of Education and
Training
Department of Environmental
Regulation
Department of Fire and
Emergency Services
Department of Fisheries
Department of Health
Department of Mines and
Petroleum
Department of Parks and Wildlife
Department of Planning
Department of Transport
Department of Water
Environmental Protection
Authority
Geoscience Australia
Harvey Water
Horizon Power
Landgate
Main Roads WA
National Native Title Tribunal
PSMA Australia
Public Transport Authority
South West Development
Commission
State Heritage Office
University of Western Australia
Water Corporation
Western Australian Electoral
Commission
Western Australian Museum
Western Power
World Wildlife Fund for Nature
AKA/Former Name
Formerly Department of Indigenous Affairs
Formerly Department of Consumer and
Employment Protection
Approved Agency
Abbreviation
ABS
BUSS
MELV
STIRL
SWAN
DAA
DAFWA
DOCEP
DET
Formerly Department of Environment and
Conservation
Formerly Fire and Emergency Services
Authority
Formerly Department of Industry and
Resources
Formerly Department of Environment and
Conservation
Includes Gnangara Sustainability Strategy
Formerly Department of Land Information
Includes Satellite Remote Sensing Services
Formerly Public Sector Mapping Agency
Version 0.1
F:\For the SLIP Portal\Minimum Metadata Standards for GME Assets FINAL v1.docx
DER
DFES
DOF
DOH
DMP
DPAW
DOP
DOT
DOW
EPA
GA
HARWA
HP
LGATE
MRWA
NNTT
PSMA
PTA
SWDC
SHO
UWA
WCORP
WAEC
WAM
WP
WWF
Page 40