Skip to content

Platform Levels

Satellite/Space

What

plp-i-pr where pl = platform level, p = platform, i = instrument, pr = product

Platform level (pl)

Code Platform Level
s Satellite
x Spacecraft/Space Stations

Platform (p)

Code Description Example
Satellite nan
al ALOS
esp1 Esper 1
esp2 Esper 2
ge1 GeoEye-1
hy Hyperion nan
ik IKONOS nan
l1 Landsat 1 nan
l2 Landsat 2 nan
l3 Landsat 3 nan
l4 Landsat 4 nan
l5 Landsat 5 nan
l6 Landsat 6 nan
l7 Landsat 7 nan
l8 Landsat 8 nan
l9 Landsat 9 nan
lz Landsat combinations nan
no NOAA nan
pt Planet nan
p1a Pleiades 1A twin nan
p1b Pleiades 1B twin nan
p1uk Pleiades 1 but unknown if A or B nan
pn3 Pleiades Neo 3 nan
pn4 Pleiades Neo 4 nan
pn5 Pleiades Neo 5 nan
pn6 Pleiades Neo 6 nan
qb2 Quickbird nan
rp Rapid Eye nan
s2a Sentinel-2 A nan
s2b Sentinel-2 B nan
s2c Sentinel-2 C nan
s2d Sentinel-2 D nan
snt generic for Sentinel-2 or mixtures and products which are independent of which satellite nan
sp1 SPOT 1 nan
sp2 SPOT 2 nan
sp3 SPOT 3 nan
sp4 SPOT 4 nan
sp5 SPOT 5 nan
sp6 SPOT 6 nan
sp7 SPOT 7 nan
sm Mixed/multiple SPOT satellite images nan
t1 Terra 1 nan
ta Terra 1 or Aqua combination nan
wl01 Worldview Legion 1 nan
wl02 Worldview Legion 2 nan
wl03 Worldview Legion 3 nan
wl04 Worldview Legion 4 nan
wl05 Worldview Legion 5 nan
wl06 Worldview Legion 6 nan
wl Multiple Worldview Legion satellites
wv01 WorldView-1 nan
wv02 WorldView-2 nan
wv03 WorldView-3 nan
wv04 WorldView-4 nan
wv Multiple WorldView satellites nan
mx Mixed or multiple satellite products nan
Satellite Radar nan
al ALOS nan
a2 ALOS-2 nan
am A mix of ALOS satellites nan
c## Capella ## c01 = Capella 1
ie## ICEYE ## ie01 = ICEYE 1
nr NISAR nan
ns1 NovaSAR-1 nan
rsc## Radarsat constellation ## rsc01 = Radarsat constellation satellite 1
rs1 Radarsat-1 nan
rs2 Radarsat-2 nan
s1 Sentinel-1 nan
ts InfoTerra TerraSAR-X nan
tx Tandem-X nan
um## Umbra ## um01 = Umbra 1
Satellite Lidar/Altimeter nan
is IceSAT nan
is2 IceSAT-2 nan
gedi GEDI nan
nuv NuVIEW nan
Spacecraft/Space Stations nan
sh space shuttle nan
iss International Space Station nan

Instrument (i)

Code Description
Satellite
a2 AVNIR-2
as ASTER
av AVHRR
ge GeoEye sensor aboard GeoEye-1
gl Geoscience Laser Altimeter System (GLAS)
hg HRG for SPOT 5
hv HRV and HRVIR for Spot 1 to 4
hy Hymap
ik IKONOS
mg MISR Global Mode
mi MISR
mo MODIS
ms Landsat Multi-Spectral Scanner (MSS) or Sentinel-2 MultiSpectral Instrument (MSI)
mt Multi-Spectral Scanner (MSS) and Thematic Mapper (TM) or Enhanced Thematic Mapper Plus (ETM+) combination
mx Mixed / multiple sensor combination (generic)
na not applicable
ni NAOMI for Spot6 and Spot7
ol Landsat-8's Operational Land Imager (OLI) - Also used for the thermal, which is technically the TIRS instrument.
p2 Planet - Dove Classic (referred to as PS2)
p2sd Planet - Planet Dove-R (referred to as PS2.SD)
pbsd Planet - Super Dove (referred to as PSB.SD)
pss Planet - SkySat
pl Pleiades
pr PRISM
ps PALSAR
qb Quickbird
s1 SSTL-300 S1 Imager, as carried by the Triplesat/ DMC-3 constellation
re1 Rapid Eye, sensor on board satellite 1
re2 Rapid Eye, sensor on board satellite 2
re3 Rapid Eye, sensor on board satellite 3
re4 Rapid Eye, sensor on board satellite 4
re5 Rapid Eye, sensor on board satellite 5
s3 LISS-III. The Landsat-like sensor on IRS-P6
s4 LISS-IV. The higher resolution, narrower swath instrument on IRS-P6.
sl SLIM-6 instrument, as carried by the DMC constellation satellites.
tm Thematic Mapper (TM) and Enhanced Thematic Mapper Plus (ETM+)
to TOMS (Total Ozone Mapping Spectrometer)
wv WorldView sensor
uk unknown
Radar Wavelength
ra Space Borne Radar (unknown wavelength)
pb P-band
lb L-Band
sb S-Band
cb C-Band
xb X-band
ku Ku-Band
kb K-Band
ka Ka-Band
Lidar/Altimeter
Spacecraft/Space Stations

Product (pr)

Code Description
re reflective (Used for pretty much all multi-spectral reflective instruments)
rp separate panchromatic and reflective imagery (not combined in a single image - see ps code below)
ps General term for pan-sharpened imagery (i.e. the blending of “re” multi-spectral with a higher resolution panchromatic to create a synthetic high-res multi-spectral. This is sometimes done for various sensors)
pan panchromatic
swir short-wave infrared
vnir very-near infrared
th thermal
hyp Hyperspectral
ba SAR backscatter (any imaging mode)
dem Digital Elevation Model
dsm Digital Surface Model
dtm Digital Terrain Model
hs Hillshade
ndvi Normalised difference vegetation index
oz Ozone in Dobson Units
vpd vapour pressure deficit
rain general term for rainfall related products
mod general term for modelled products (generally associated with the ns satellite code)
mx Mixed or multiple products
Lidar
dr discrete return lidar point cloud data
wf full waveform lidar
Satellite Specific
ae aerosol product (MISR)
gp geometric parameters (MISR)
ls land surface parameters (MISR)
ep ellipsoid projected radiances (MISR)
tp terrain projected radiances (MISR)
cf MODIS composite: full resolution ("i.e 1000 metres; “When” field below will be the earliest date")
ch MODIS composite: half resolution ("i.e 500 metres; “When” field below will be the earliest date")
cq MODIS composite: quarter resolution ("i.e 250 metres; “When” field below will be the earliest date")
df MODIS daily: full resolution (i.e 1000 metres)
dh MODIS daily: half resolution (i.e 500 metres)
dq MODIS daily: quarter resolution (i.e 250 metres)
e1 Mosaics of pan-sharpened TripleSat S1 visible band (red/green/blue) imagery pre-processed and supplied by Earth-i.
sm SpotMaps - applies to SPOT satellites (refers to their radiometrically balanced product)
pf PathFinder product (12 layers) from NASA's Goddard Earth Sciences DAAC (“When” field below will be the start date of the ten-day composite)

Where

Where Example Description
Satellite
Landsat 5 TM and 7 ETM+ and 8 OLI p[0-9][0-9][0-9]r[0-9][0-9][0-9] e.g. p089r079 USGS World Reference System (WRS2) Landsat Path and Row
Sentinel-2 t55kfp The tile names as used by ESA. These are roughly based on the US Military Grid Reference System but they seem to have modified it a little. Prefix is always "t" and the next two characters are UTM zone number of the tile and then next letter is the latitude band and the final two letters are the tile id within the zone and latitude band.
Mosaics cnamoi06,msh5508,nsw,pwettropics Please refer to Mosaic Tables for complete list of names. Mosaics must include multiple images or sources. If single source imagery is used then use the imagery location coding below. Mosaics based on S3 search zones or state/territory or continent or mapsheet (e.g. 250k) or project. Mapsheet or project are prefixed with m or p respectively. Where different versions of boundary layers exist (i.e. IBRA v6.1 and IBRA v7) the 'where' field is appended with the year the layer was defined (i.e cnamoi06 is based on the CMA layer defined in 2006). The state/territory or continent codes are the two or three character abbreviations for the state/territory or continent without a prefix. The list is: nt - qld - nsw - vic - tas - sa - wa - act - aus. The "r" prefix tag is a catchall for any arbitrary region names not covered by the other codes. Project "p" specific "where" components are used for airborne lidar mosaics and listed on Mosaic Tables. Start each mosaic where with x.
Other
Imagery Location ID [a-z] e.g. perth, uluru, norfolk-island, murray-river, bunger-hills Use place names of cities or towns or prominent features of the overall location the image was captured. Ensure no spaces by using a "-" to replace the space.
AAD Specific Folder names should use the S3 search zones for the whole of the AAT while filenames should be more specific to locations or stations with subfields for buildings
S3 Search Zones - AAT 45t73, minr, himi S3 search zones based on degree wedges and island zones
S3 Station Search Zones mqs1,dvs-12 S3 search zones based on station search areas (numbers 12 means that the coverage includes zone 1 and 2)
Stations (and extended limits) mqs, dvs, mws, cys, h73, m72 Add "x" to the end for extended station limits (e.g. mqsx = Macquarie Station Extended limits while mqs = Macquarie Station). h73 = Heard Island and m72 = McDonald Island.

When

All dates should be expressed in Universal Time (GMT).

Code Example Description
yyyymmdd 19990923 date by year, month, day (1999 september (09) 23 (UTC))
yyyy 2005 single year (not for a single day within the year)
yyyymm 200503 single month (not for a single day)
yyyymmddHHMMSS 20060810014213 datetime by year, month, day, hour, minute, second (e.g. 2006 august (08) 10 01:42:13 (UTC))
e[yy][yy] e9195 standard epoch between two years(eg. of vegetation change; 1991 to 1995 where the start year is in the range 1990 to 1992 and the end is 1994 to 1996)
d[yyyymmdd][yyyymmdd] d1991032319951014 range of days (e.g. 1991 march (03) 23 to 1995 october (10) 14. The presence of the 'd' clearly defines how the 16 digits should be interpreted)
m[yyyymm][yyyymm] m199103199510 range of months (e.g. 1991 march (03) to 1995 october (10). The presence of the 'm' clearly defines how the 12 digits should be broken up)
y[yyyy][yyyy] y19911999 range of years (span of eight years 1991 to 1999. The presence of the 'y' clearly distinguishes it from a single 8-digit date)
n[yyyymmdd] n20100927 A nominal date ("This has been previously used for the Landsat-7 SLC-off data. When a nominal image is created by starting with a primary one; and merging in other surrounding dates to fill the gaps; the nominal date of the image is the initial date; given in the filename; while other dates are recorded only in the history.")
s[mm][mm] s0305 generic season name ("Excludes Antarctic seasons. This is distinct from the use of the 'm' tag for specific seasons. This 's' tag is used for generic seasons; i.e. not tied to a particular year. The given example; s0305; refers to a generic autumn dataset; rather than a specific autumn of a particular year. This is most useful for things like an average over all autumns.")

Reserved or exceptions eall a subset of the "e" era category to be used where the era is non-specific and can cover ALL eras.

Processing Stage

Ancillary

Code Description
ax0 Ancillary files related to imagery - to include vector-based extents (i.e. pixel shape, order shape, product shape, strip shape, tile shape)
bx0 Ground control points

Optical

GeoEye-1
Code Subfields to Include Description
aa0 Must include product level:
lv2b = product level 2b
lv3b = product level 3b
Imagery provided from Digitalglobe/Maxar either from a provider or Securewatch/MGP Pro
ab1 Provider has done enhanced natural colour
ab2 Provider has done natural colour
ab3 Provider has done false colour
ab4 Provider has done unenhanced swaths/mosaics
bb0 DCCEEW pansharpnening of reflective bands using panchromatic band
Landsat and Sentinel
Code Must include subfield Description
aa0 *See subfield table Imagery provided from download resource or vendor
ab0 *See subfield table Provider has done pansharpening of reflective bands using the panchromatic band
ac0 *See subfield table Provider has generated a composite of Landsat or Sentinel-2 images (not pansharpened)
ac1 *See subfield table Provider has generated a downsampled composite of Landsat or Sentinel-2 images (note downsampled resolution in the optionals)
EDS Only Naming
ga0 *See subfield table NBART Composite of Landsat or Sentinel-2 image sourced from Geoscience Australia's DEA
ga1 *See subfield table NDVI (Normalized Difference Vegetation Index) using Landsat or Sentinel-2 image sourced from Geoscience Australia's DEA
ga2 *See subfield table Fractional Cover using Landsat or Sentinel-2 image sourced from Geoscience Australia's DEA
ga3 *See subfield table fmask applied to Landsat or Sentinel-2 image sourced from Geoscience Australia's DEA
Landsat and Sentinel Subfields
Code Subfield to be included in Landsat and Sentinel processing code Description
clr Clear land Standard terrestrial mask applied (clear land only: water, cloud, cloud shadow and snow excluded).
wtr Water Water surface mask applied.
cw Clear + Water Standard clear mask applied (clear land and water retained: cloud, cloud shadow and snow excluded).
cld Cloud Cloud mask applied.
shd Cloud shadow Cloud shadow mask applied.
cws Clear + water + cloud shadow Clear land: water and cloud shadow retained (cloud excluded).
snw Snow Snow or ice covered surface mask applied.
cst Custom Custom mask applied (user-defined combination of fmask classes).
nm No mask No fmask was applied no subfield needs to be added.
Planet
Code Subfields to Include Description
aa0 Must include product level:
lv1b = PlanetScope basic scene product
lv3b-ar = PlanetScope Ortho Scene Product calibrated to top of atmosphere radiance
lv3b-sr = PlanetScope Ortho Scene Product corrected for surface reflectance
Imagery provided or downloaded from Planet or provided by vendor.
Pleiades
Code Subfields to Include Description
aa0 Must include product level:
ort = imagery provided orthorectified
sen = imagery provided in sensor geometry
Imagery provided from Airbus, Airbus GeoStore or a vendor
ab0 Must include product level:
ort = imagery provided orthorectified
sen = imagery provided in sensor geometry
Provider has done pansharpening of reflective bands using the panchromatic band
ab1 Provider has done enhanced natural colour
ab2 Provider has done natural colour
ab3 Provider has done false colour
ab4 Provider has done unenhanced swaths/mosaics
bb0 DCCEEW pansharpnening of reflective bands using panchromatic band
Quickbird
Code Subfields to Include Description
aa0 Must include product level:
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3b = imagery provided at level 3b
Imagery provided from Digitalglobe/Maxar either from a provider or Securewatch/MGP Pro
ab0 Must include product level:
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3b = imagery provided at level 3b
Provider has done pansharpening of reflective bands using the panchromatic band.
ab1 Provider has done enhanced natural colour
ab2 Provider has done natural colour
ab3 Provider has done false colour
ab4 Provider has done unenhanced swaths/mosaics
bb0 DCCEEW pansharpnening of reflective bands using panchromatic band
SPOT
Code Subfields to Include Description
aa0 Must include product level:
lv1a = imagery provided at level 1a
lv1b = imagery provided at level 1b
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3 = imagery provided at level 3
Imagery provided from Airbus, Airbus GeoStore, or a provider
lv1a = Raw Geometry - Radiometrically corrected but no geometric correction
lv1b = Radiometrically & systematically geometrically corrected to a map projection
lv2a = Radiometric correction & terrain-corrected using a DEM - not yet orthorectified
lv2b = Fully orthorectified using GCPs & DEM - resampled to a cartographic projection
lv3 = Value-Added Product: mosaicked/color-balanced/pansharpened/classified
ab0 Must include product level:
lv1a = imagery provided at level 1a
lv1b = imagery provided at level 1b
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3 = imagery provided at level 3
Provider has done pansharpening of reflective bands using the panchromatic band
lv1a = Raw Geometry - Radiometrically corrected but no geometric correction
lv1b = Radiometrically & systematically geometrically corrected to a map projection
lv2a = Radiometric correction & terrain-corrected using a DEM - not yet orthorectified
lv2b = Fully orthorectified using GCPs & DEM - resampled to a cartographic projection
lv3 = Value-Added Product: mosaicked/color-balanced/pansharpened/classified
ab1 Include product level if known Provider has done enhanced natural colour
ab2 Include product level if known Provider has done natural colour
ab3 Include product level if known Provider has done false colour
ab4 Include product level if known Provider has done unenhanced swaths/mosaics
ab5 Include product level if known Provider has done orthorectification
bb0 Include product level if known DCCEEW pansharpnening of reflective bands using panchromatic band
bb1 Include product level if known DCCEEW orthorectification of image
WorldView
Code Subfields to Include Description
Imagery
aa0 Must include product level:
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3b = imagery provided at level 3b
lv3d = imagery provided at level 3d
Imagery provided from Digitalglobe/Maxar either from a provider or Securewatch/MGP Pro
ab0 Must include product level:
lv2a = imagery provided at level 2a
lv2b = imagery provided at level 2b
lv3b = imagery provided at level 3b
lv3d = imagery provided at level 3d
Provider has done pansharpening of reflective bands using the panchromatic band.
ab1 Provider has done enhanced natural colour
ab2 Provider has done natural colour
ab3 Provider has done false colour
ab4 Provider has done unenhanced swaths/mosaics
bb0 DCCEEW pansharpnening of reflective bands using panchromatic band

Radar

Code Must include subfield Description
aa0 *See subfield table Raw imagery from provider
aa1 *See subfield table Products from provider
ab1 *See subfield table Single Look Complex
ab2 *See subfield table Sensor Independent Complex Data
ab3 *See subfield table Compensated Phase History Data
ab4 *See subfield table Sensor Independent Derived Data
ab5 *See subfield table Geocoded Ellipsoid Corrected
ab6 *See subfield table Geocoded Terrain Corrected
ab7 *See subfield table Colourized sub-aperture Imagery
ab8 *See subfield table Ground Range Detected
ab9 *See subfield table Enhanced Ellipsoid Corrected
ac1 *See subfield table Slant Range Detected
ac2 *See subfield table SAR Video
ac3 *See subfield table National Imagery Tramission Format
ac4 *See subfield table World Neo DEM Terrain Data
Radar Subfields
Code Subfield to be included in radar processing code
de extended dwell
df dwell fine
dp dwell precice
dw dwell
fb fine beam single
fd fine beam double polarisation
mt maritime
pm polarimetry mode
sc scan, scan burst, scan scar
sf spot fine, high resolution spot
sm strip or stripmap
sp spot, spotlight
ss sliding spotlight
st staring spotlight
su spotlight ultra
sw spot extended, spotlight wide
te high resolution terrain elevation (World Neo DEM)
uk unknown radar mode
ws wide scansar, scan wide

Lidar

Code Description
aa0-l raw lidar scanner data (zipped) - provider
aa1-l lidar products - provider
ab1-l lidar scanner data in real world coordinates - provider
ab2-l thinned lidar scanner data in real world coordinates - provider
ab3-l digital elevation model from lidar - provider
ab4-l digital surface model from lidar - provider
ab5-l canopy height model from lidar - provider
ab6-l canopy cover model from lidar - provider
ab7-l canopy density model from lidar - provider
ba0-l raw lidar scanner data (zipped) - DCCEEW
ba1-l lidar products - DCCEEW
bb1-l lidar scanner data in real world coordinates - DCCEEW
bb2-l thinned lidar scanner data in real world coordinates - DCCEEW
bb3-l digital elevation model from lidar - DCCEEW
bb4-l digital surface model from lidar - DCCEEW
bb5-l canopy height model from lidar - DCCEEW
bb6-l canopy cover model from lidar - DCCEEW
bb7-l canopy density model from lidar - DCCEEW

Metadata

Code Description
am0 Any additional metadata
ar0 Processing report from provider
bn0 Any additional notes/readme text about the imagery (must be OCR PDF format)
br0 Processing report stripped of provider details
xfs CSV file that summarises all/some of the EXIF variables

Optionals

The order of optionals is important. If the optional variable does not apply, continue down the list.

Code Example Description
n off nadir angle - use p if you need a decimal point (e.g. n13p1 is an off nadir angle of 13.1 degrees)
b b4,b8 Number of bands
p[v/h,v/h] phh Polarisation (SAR imagery)
rr# rr5m resolution - radar bands (must include units)
rm# rm2p5m resolution - multispectral bands (must include units)
rp# rp30cm resolution - panchromatic band (must include units)
rps# rps50cm resolution - pansharpened product (must include units)
[a-z]# u43, g0, fx Projection: UTM zone starts with u and the two digit zone (excludes the s for south). Geographic coordinates, in latitudes and longitudes, with gx for WGS84 unknown spheroid, g0 for WGS84/GDA94 spheroid and g1 for GDA2020 spheroid. File based or raw pixel/row or sensor coordinates is listed as fx.
e##### e32752 EPSG code (can be 4 or 5 numbers long)
ice Ice-enhanced
File Format
cog Image has been converted to cloud-optimised GeoTIFF
Unusable Data Flag
bad There is an issue with the data and it is not to be used - further information may be available in metadata or by relevant contacts

Who

Code Organisation/Group
aad Australian Antarctic Division
eia Environment Information Australia
ocrp Office of the Chief Remote Pilot

Suffix

.xxx where xxx is the file suffix - Noting that some suffixes may have more than one decimal point (ie. .copc.laz)

An appropriate suffix must be added to the end of the filename relative to the data.

Examples

Satellite Example Description
WorldView swv03-wv-rp_cysx_20240125014017_aa0-lv2a_n11p8-b8-rm133cm-rp33cm-u49_aad [what:] Satellite image from WorldView 3 - using WorldView instrument - containing both reflective and panchromatic images in the folder. [where:] The image is from Casey Station and beyond extended station limits. [when:] The image was taken on 25 of January 2024. [processing:] It was provided directly from Maxar -and is a Level 2A product. [optional:] The off nadir angle is 11.8 degrees - it has 8 bands -the resolution of the reflective bands is 1.33m - the panchromatic band is 33cm - the zone is UTM 49. [who:] The image was purchased for the AAD.
Pleiades sp1b-pl-ps_melrf_20220113_ab0-ort_rps50cm_eia [what:] Satellite image from Pleiades 1B - using Pleiades instrument - pansharpened. [where:] The image is from the Mellish Reef. [when:] It was captured on 13 of January 2022. [processing:] It was provided by a vendor - who pansharpened the image. [optional:] The resolution of the image is 50cm. [who:] It was acquired by EIA.
Mosaic examples Example Description
QuickBird sqb2-qb-ps_xnfk_m200512200705_ab0_rps60cm_eia [what:] Satellite image from QuickBird2- using the QuickBird instrument - pansharpened. [where:] The x indicates it is a mosaic of Norfolk Island. [when:] The first image was captured in December 2005 and the last image in May 2007. [processing:] It was provided by a vendor who pansharpened the image. [optional:] The resolution of the image is 60cm. [who:] It was acquired by EIA.

References

Below lists some details from original naming conventions that can be of assistance to translate to the new naming convention:

SPOT - The SPOT Scene Standard Digital Product Format


Remotely Piloted Aircraft

What

plp-i-pr where pl = platform level, p = platform, i = instrument, pr = product

Platform level (pl)

Code Platform Level
r Remotely Piloted Aircraft

Platform (p)

Code Platform
anr Acecore Noa Regular
at25p DJI Agras-T25P
at30 DJI Agras T30
ap Anafi Parrot
aa Arace Angel
agp Arace Griffin Pro
ae2 Autel EVO II
aa2 DJI Avata 2
aa360 DJI Avata 360
bff6p BirdsEyeView Firefly 6 Pro
dqe DeltaQuad Evo VTOL
dqpm DeltaQuad Pro '#MAP'
fas Freefly Astro
fax Freefly AltaX
fc30 DJI Flycart 30
fc50 Freespace Callisto50
fgs FoxTech Great Shark
ins DJI Inspire
mn2 DJI Mini 2
mvmn DJI Mavic Mini
mvm3p DJI Mavic Mini 3 Pro
mvm4p DJI Mavic Mini 4 Pro
mvm5p DJI Mavic Mini 5 Pro
mvp DJI Mavic Pro
mvpp DJI Mavic Pro Platinum
mv2 DJI Mavic 2
mv2e DJI Mavic 2 Enterprise
mv2ea DJI Mavic 2 Enterprise Advanced
mv2ed DJI Mavic 2 Enterprise Dual
mv2ez DJI Mavic 2 Enterprise Zoom
mv2p DJI Mavic 2 Pro
mv2z DJI Mavic 2 Zoom
mv3pc DJI Mavic 3 Pro Cine
mva2 DJI Mavic Air 2
mva2s DJI Mavic Air 2S
mv3 DJI Mavic 3
mv3m DJI Mavic 3 Mutlispectral
mv3e DJI Mavic 3 Enterprise
mv3t DJI Mavic 3 Thermal
mx Mixed or multiple remotely piloted aircraft products
m4e DJI Matrice 4 Enterprise
m4t DJI Matrice 4 Thermal
m4td DJI Matrice 4 Thermal Drone (dock)
m30t DJI M30T
m200v1 DJI Matrice 200 V1
m200v2 DJI Matrice 200 V1
m210 DJI Matrice 210
m300 DJI M300
m350 DJI M350
m400 DJI M400
m600 DJI M600
m600p DJI M600 Pro
ph4 DJI Phantom 4
ph4a DJI Phantom 4 Advanced
ph4p2 DJI Phantom 4 Pro V2
ph4p2o DJI Phantom 4 Pro 2.0 Obsidian
sdb80 SAI Dynamics Bremer BMR4 80
sfm SwellPro FishermanMAX
skyx10 Skydio X10
sky2 Skydio S2+
ssc Sypaq Systems Corvo PPDS
uk Unknown remotely piloted aircraft
y520 Yuneec 520

Instrument (i)

Code Instrument
agrwq Agrowing Quad multispectral
agrws Agrowing Sextuple multispectral
dpr Duo Pro R
hnhp Headwall Nano HP
hxvs Hyspex Mjolnir VS-620
mv3t Mavic 3 Thermal
mv3e Mavic 3 Enterprise RGB Camera
mv3m Mavic 3 Multispectral (RGB + NIR)
m4e Matrice 4 Enterprise RGB Camera
m4t Matrice 4 Thermal (NIR + Infrared Thermal)
mapt Micasense Altum PT
mmxd Micasense RedEdge MX Dual
mre Micasense RedEdge
mrepd Micasense Red Edge P-Dual
os2 Ouster OS2
p1p3 Phase One P3 (80mm lens)
qrm8 Quanergy M8
rmvx3 Riegl MiniVUX-3UAV
r840gl Riegl VQ-840-GL
st35 Sonnar T*35mm
sz4 Sextuplet Z4
vt300z VT300-Z Skydio Sensor
vt300l VT300-L Skydio Sensor
vt100l VT100-L Skydio Sensor
zh30 Zenmuse H30
zh30t Zenmuse H30 Thermal
zp1 Zenmuse P1
zx5s Zenmuse X5S
zl1 Zenmuse L1
zl2 Zenmuse L2
zl3 Zenmuse L3

Product (pr)

Code Product
chm Canopy Height Model
dem Digital Elevation Model
dsm Digital Surface Model
hyp Hyperspectral
ndvi Normalised difference vegetation index
pan panchromatic
pc Point Cloud Data - Derived from imagery
ps General term for pan-sharpened imagery (i.e. the blending of “re” multi-spectral with a higher resolution panchromatic to create a synthetic high-res multi-spectral. This is sometimes done for various sensors)
rp separate panchromatic and reflective imagery (not combined in a single image - see ps code below)
re reflective - Used for pretty much all multi-spectral reflective instruments.
swir short-wave infrared
th thermal
vthm video - thermal = GoPro Only
vrgb video - red, green, blue = GoPro Only
Lidar
at aircraft trajectory data (airborne lidar)
dr discrete return lidar point cloud data
wf full waveform lidar data

Where

Where Example Description
Satellite
Landsat 5 TM and 7 ETM+ and 8 OLI p[0-9][0-9][0-9]r[0-9][0-9][0-9] e.g. p089r079 USGS World Reference System (WRS2) Landsat Path and Row
Sentinel-2 t55kfp The tile names as used by ESA. These are roughly based on the US Military Grid Reference System but they seem to have modified it a little. Prefix is always "t" and the next two characters are UTM zone number of the tile and then next letter is the latitude band and the final two letters are the tile id within the zone and latitude band.
Mosaics cnamoi06,msh5508,nsw,pwettropics Please refer to Mosaic Tables for complete list of names. Mosaics must include multiple images or sources. If single source imagery is used then use the imagery location coding below. Mosaics based on S3 search zones or state/territory or continent or mapsheet (e.g. 250k) or project. Mapsheet or project are prefixed with m or p respectively. Where different versions of boundary layers exist (i.e. IBRA v6.1 and IBRA v7) the 'where' field is appended with the year the layer was defined (i.e cnamoi06 is based on the CMA layer defined in 2006). The state/territory or continent codes are the two or three character abbreviations for the state/territory or continent without a prefix. The list is: nt - qld - nsw - vic - tas - sa - wa - act - aus. The "r" prefix tag is a catchall for any arbitrary region names not covered by the other codes. Project "p" specific "where" components are used for airborne lidar mosaics and listed on Mosaic Tables. Start each mosaic where with x.
Other
Imagery Location ID [a-z] e.g. perth, uluru, norfolk-island, murray-river, bunger-hills Use place names of cities or towns or prominent features of the overall location the image was captured. Ensure no spaces by using a "-" to replace the space.
AAD Specific Folder names should use the S3 search zones for the whole of the AAT while filenames should be more specific to locations or stations with subfields for buildings
S3 Search Zones - AAT 45t73, minr, himi S3 search zones based on degree wedges and island zones
S3 Station Search Zones mqs1,dvs-12 S3 search zones based on station search areas (numbers 12 means that the coverage includes zone 1 and 2)
Stations (and extended limits) mqs, dvs, mws, cys, h73, m72 Add "x" to the end for extended station limits (e.g. mqsx = Macquarie Station Extended limits while mqs = Macquarie Station). h73 = Heard Island and m72 = McDonald Island.

When

All dates should be expressed in Universal Time (GMT).

Code Example Description
yyyymmdd 19990923 date by year, month, day (1999 september (09) 23 (UTC))
yyyy 2005 single year (not for a single day within the year)
yyyymm 200503 single month (not for a single day)
yyyymmddHHMMSS 20060810014213 datetime by year, month, day, hour, minute, second (e.g. 2006 august (08) 10 01:42:13 (UTC))
e[yy][yy] e9195 standard epoch between two years(eg. of vegetation change; 1991 to 1995 where the start year is in the range 1990 to 1992 and the end is 1994 to 1996)
d[yyyymmdd][yyyymmdd] d1991032319951014 range of days (e.g. 1991 march (03) 23 to 1995 october (10) 14. The presence of the 'd' clearly defines how the 16 digits should be interpreted)
m[yyyymm][yyyymm] m199103199510 range of months (e.g. 1991 march (03) to 1995 october (10). The presence of the 'm' clearly defines how the 12 digits should be broken up)
y[yyyy][yyyy] y19911999 range of years (span of eight years 1991 to 1999. The presence of the 'y' clearly distinguishes it from a single 8-digit date)
n[yyyymmdd] n20100927 A nominal date ("This has been previously used for the Landsat-7 SLC-off data. When a nominal image is created by starting with a primary one; and merging in other surrounding dates to fill the gaps; the nominal date of the image is the initial date; given in the filename; while other dates are recorded only in the history.")
s[mm][mm] s0305 generic season name ("Excludes Antarctic seasons. This is distinct from the use of the 'm' tag for specific seasons. This 's' tag is used for generic seasons; i.e. not tied to a particular year. The given example; s0305; refers to a generic autumn dataset; rather than a specific autumn of a particular year. This is most useful for things like an average over all autumns.")

Reserved or exceptions

eall a subset of the "e" era category to be used where the era is non-specific and can cover ALL eras.

Processing Stage

Ancillary

Code Description
ax0 Ancillary files related to imagery - to include vector-based extents (i.e. pixel shape, order shape, product shape, strip shape, tile shape)
bx0 Ground control points

Imagery

Code Description
aa0 raw images - provider (Can be zipped but must contain ancillary data for reprocessing ie. RINEX or Base Station information)
aa1 processed products - provider
ab0 orthomosaic derived from imagery - provider
ab1 point cloud derived from imagery - provider
ab2 digital elevation model derived from imagery - provider
ab3 digital surface model derived from imagery - provider
ab4 canopy height model derived from imagery - provider
ac0 raw video - provider
ba0 raw images - DCCEEW pilot (Can be zipped but must contain ancillary data for reprocessing ie. RINEX or Base Station information)
ba1 processed products - DCCEEW pilot
bb0 orthomosaic derived from imagery - DCCEEW pilot
bb1 point cloud derived from imagery - DCCEEW pilot
bb2 digital elevation model derived from imagery - DCCEEW pilot
bb3 digital surface model derived from imagery - DCCEEW pilot
bb4 canopy height model derived from imagery - DCCEEW pilot
bc0 raw video - DCCEEW

Lidar

Code Description
aa0-l raw lidar scanner data (zipped) - provider
aa1-l lidar products - provider
ab1-l lidar scanner data in real world coordinates - provider
ab2-l thinned lidar scanner data in real world coordinates - provider
ab3-l digital elevation model from lidar - provider
ab4-l digital surface model from lidar - provider
ab5-l canopy height model from lidar - provider
ab6-l canopy cover model from lidar - provider
ab7-l canopy density model from lidar - provider
ba0-l raw lidar scanner data (zipped) - DCCEEW
ba1-l lidar products - DCCEEW
bb1-l lidar scanner data in real world coordinates - DCCEEW
bb2-l thinned lidar scanner data in real world coordinates - DCCEEW
bb3-l digital elevation model from lidar - DCCEEW
bb4-l digital surface model from lidar - DCCEEW
bb5-l canopy height model from lidar - DCCEEW
bb6-l canopy cover model from lidar - DCCEEW
bb7-l canopy density model from lidar - DCCEEW

Metadata

Code Description
am0 Any additional metadata
ar0 Processing report from provider
bn0 Any additional notes/readme text about the imagery (must be OCR PDF format)
br0 Processing report stripped of provider details
xfs CSV file that summarises all/some of the EXIF variables

Optionals

The order of optionals is important. If the optional variable does not apply, continue down the list.

Code Options Description
h#m numeric value corresponds to height in metres, i.e. h10m = 10m, h30m = 30m height
s#ms numeric value corresponds to speed in metres per second, i.e. s10ms = 10m/s, s30ms = 30m/s speed
o numeric value corresponds to overlap i.e. o8080 = 80/80 image overlap overlap
i image number
n off nadir angle - use p if you need a decimal point (e.g. n13p1 is an off nadir angle of 13.1 degrees)
b number of bands
gsd#cm Ground sample distance in cm
[a-z]# u43, g0, fx Projection: UTM zone starts with u and the two digit zone (excludes the s for south). Geographic coordinates, in latitudes and longitudes, with g0 for WGS84/GDA94 spheroid and g1 for GDA2020 spheroid. File based or raw pixel/row or sensor coordinates is listed as fx.
Digital Elevation/Surface Model/Orthomosaic nan
r r#m = metres, r#cm = centimetres, r#mm = millimetres resolution
Lidar
p p1200, p2200 pulse repetition rate (khz)
e WGS (either e60, e66, e72, e84) ellipsoid
oh MACQ1982 = mq1982 orthometric height
u u44 to u58 (s not needed as its always south) utm zone
d ITRF2000@2000 = d2000 datum
File Format
cog Image has been converted to cloud-optimised GeoTIFF
tmb Thumbnail
Unusable Data Flag
bad There is an issue with the data and it is not to be used - further information may be available in metadata or by relevant contacts

Who

Code Organisation/Group
aad Australian Antarctic Division
eia Environment Information Australia
ocrp Office of the Chief Remote Pilot

Suffix

.xxx where xxx is the file suffix - Noting that some suffixes may have more than one decimal point (ie. .copc.laz)

An appropriate suffix must be added to the end of the filename relative to the data.

Examples

Aircraft Example Description
DJI M300 rm300-zp1-re_uktswcamp1_20231011_ba1_h60m-s4p5ms-o8080-n0-gsd0p9cm-u52_ocrp [what:] Folder of RPA products collected with a DJI M300 platform - using a DJI Zenmuse P1 instrument - containing reflective products (RGB). [where:] The products are of Camp 1 of the UKTSW (Uluru walking trail) [when:] The data was collected on 11th October 2023. [processing:] The folder contains processed products (e.g. orthomosaic/digital surface model/point cloud/processing report) collected by a DCCEEW Pilot. [optional:] The height is 60 m above ground level - the drone was traveling at 4.5 m/s - the overlap was 80% horizonal and 80% vertical - the ground sample distance is 0.9 cm - the zone is UTM 52. [who:] The data was collected by the OCRP.

Piloted Aircraft

What

plp-i-pr where pl = platform level, p = platform, i = instrument, pr = product

Platform level (pl)

Code Platform Level
a Piloted Aircraft

Platform (p)

Code Platform
heli Helicopter
ap Airplane
uk Unknown
mx Mixed or multiple platforms

Instrument (i)

Code Instrument
ag4 Aeroglobe Pod V4
ag5 Aeroglobe Pod V5
ap Aispeco Helix Pod
gp GoPro
has Hasselblad 500 EL
hxvs Hyspex Mjolnir VS-620
k17 Fairchild K17
lin Linhof
p1rsf Phase One iXM-RS150F (70 mm lens)
r840gl Riegl VQ-840-GL
ap50 Applanix AP+50 (INS)
rc5 Wild RC5
rc8 Wild RC8
rc9 Wild RC9
rc10 Wild RC10
uk Unknown
wev Williamson EagleV
wf24 Williamson F24
zs Zeiss

Product (pr)

Code Product
re reflective - Used for pretty much all multi-spectral reflective instruments.
rp separate panchromatic and reflective imagery (not combined in a single image - see ps code below)
ps General term for pan-sharpened imagery (i.e. the blending of “re” multi-spectral with a higher resolution panchromatic to create a synthetic high-res multi-spectral. This is sometimes done for various sensors)
pan panchromatic
swir short-wave infrared
th thermal
hyp Hyperspectral
dem Digital Elevation Model
dsm Digital Surface Model
hs Hillshade
oz Ozone (in Dobson Units)
ndvi Normalised difference vegetation index
vpd vapour pressure deficit (vpd)
rain general term for rainfall related products
mod general term for modelled products - generally associated with the ns satellite code
mx Mixed or multiple products
Aerial Photography
fco film-based colour photographs
fbw film-based black and white photographs
fir film-based infrared photographs
dco digital-based colour photographs
dbw digital-based black and white photographs
dir digital-based infrared photographs
Lidar
dr discrete return lidar point cloud data
wf full waveform lidar
cw continuous wave (phase-shift) lidar
at aircraft trajectory data (airborne lidar)

Where

Where Example Description
Satellite
Landsat 5 TM and 7 ETM+ and 8 OLI p[0-9][0-9][0-9]r[0-9][0-9][0-9] e.g. p089r079 USGS World Reference System (WRS2) Landsat Path and Row
Sentinel-2 t55kfp The tile names as used by ESA. These are roughly based on the US Military Grid Reference System but they seem to have modified it a little. Prefix is always "t" and the next two characters are UTM zone number of the tile and then next letter is the latitude band and the final two letters are the tile id within the zone and latitude band.
Mosaics cnamoi06,msh5508,nsw,pwettropics Please refer to Mosaic Tables for complete list of names. Mosaics must include multiple images or sources. If single source imagery is used then use the imagery location coding below. Mosaics based on S3 search zones or state/territory or continent or mapsheet (e.g. 250k) or project. Mapsheet or project are prefixed with m or p respectively. Where different versions of boundary layers exist (i.e. IBRA v6.1 and IBRA v7) the 'where' field is appended with the year the layer was defined (i.e cnamoi06 is based on the CMA layer defined in 2006). The state/territory or continent codes are the two or three character abbreviations for the state/territory or continent without a prefix. The list is: nt - qld - nsw - vic - tas - sa - wa - act - aus. The "r" prefix tag is a catchall for any arbitrary region names not covered by the other codes. Project "p" specific "where" components are used for airborne lidar mosaics and listed on Mosaic Tables. Start each mosaic where with x.
Other
Imagery Location ID [a-z] e.g. perth, uluru, norfolk-island, murray-river, bunger-hills Use place names of cities or towns or prominent features of the overall location the image was captured. Ensure no spaces by using a "-" to replace the space.
AAD Specific Folder names should use the S3 search zones for the whole of the AAT while filenames should be more specific to locations or stations with subfields for buildings
S3 Search Zones - AAT 45t73, minr, himi S3 search zones based on degree wedges and island zones
S3 Station Search Zones mqs1,dvs-12 S3 search zones based on station search areas (numbers 12 means that the coverage includes zone 1 and 2)
Stations (and extended limits) mqs, dvs, mws, cys, h73, m72 Add "x" to the end for extended station limits (e.g. mqsx = Macquarie Station Extended limits while mqs = Macquarie Station). h73 = Heard Island and m72 = McDonald Island.

When

All dates should be expressed in Universal Time (GMT).

Code Example Description
yyyymmdd 19990923 date by year, month, day (1999 september (09) 23 (UTC))
yyyy 2005 single year (not for a single day within the year)
yyyymm 200503 single month (not for a single day)
yyyymmddHHMMSS 20060810014213 datetime by year, month, day, hour, minute, second (e.g. 2006 august (08) 10 01:42:13 (UTC))
e[yy][yy] e9195 standard epoch between two years(eg. of vegetation change; 1991 to 1995 where the start year is in the range 1990 to 1992 and the end is 1994 to 1996)
d[yyyymmdd][yyyymmdd] d1991032319951014 range of days (e.g. 1991 march (03) 23 to 1995 october (10) 14. The presence of the 'd' clearly defines how the 16 digits should be interpreted)
m[yyyymm][yyyymm] m199103199510 range of months (e.g. 1991 march (03) to 1995 october (10). The presence of the 'm' clearly defines how the 12 digits should be broken up)
y[yyyy][yyyy] y19911999 range of years (span of eight years 1991 to 1999. The presence of the 'y' clearly distinguishes it from a single 8-digit date)
n[yyyymmdd] n20100927 A nominal date ("This has been previously used for the Landsat-7 SLC-off data. When a nominal image is created by starting with a primary one; and merging in other surrounding dates to fill the gaps; the nominal date of the image is the initial date; given in the filename; while other dates are recorded only in the history.")
s[mm][mm] s0305 generic season name ("Excludes Antarctic seasons. This is distinct from the use of the 'm' tag for specific seasons. This 's' tag is used for generic seasons; i.e. not tied to a particular year. The given example; s0305; refers to a generic autumn dataset; rather than a specific autumn of a particular year. This is most useful for things like an average over all autumns.")

Reserved or exceptions

eall a subset of the "e" era category to be used where the era is non-specific and can cover ALL eras.

Processing Stage

Ancillary

Code Description
ax0 Ancillary files related to imagery - to include vector-based extents (i.e. pixel shape, order shape, product shape, strip shape, tile shape)
bx0 Ground control points

Imagery

Code Description
aa0 raw images - provider
ab0 orthomosaic derived from imagery - provider
ab1 point cloud derived from imagery - provider
ab2 digital elevation model derived from imagery - provider
ab3 digital surface model derived from imagery - provider
ba0 raw images - DCCEEW pilot
bb0 orthomosaic derived from imagery - DCCEEW pilot
bb1 point cloud derived from imagery - DCCEEW pilot
bb2 digital elevation model derived from imagery - DCCEEW pilot
bb3 digital surface model derived from imagery - DCCEEW pilot
ca0 raw images from provider - georeferenced by DCCEEW staff

Lidar

Code Description
aa0-l raw lidar scanner data (zipped) - provider
aa1-l lidar products - provider
ab1-l lidar scanner data in real world coordinates - provider
ab2-l thinned lidar scanner data in real world coordinates - provider
ab3-l digital elevation model from lidar - provider
ab4-l digital surface model from lidar - provider
ab5-l canopy height model from lidar - provider
ab6-l canopy cover model from lidar - provider
ab7-l canopy density model from lidar - provider
ba0-l raw lidar scanner data (zipped) - DCCEEW
ba1-l lidar products - DCCEEW
bb1-l lidar scanner data in real world coordinates - DCCEEW
bb2-l thinned lidar scanner data in real world coordinates - DCCEEW
bb3-l digital elevation model from lidar - DCCEEW
bb4-l digital surface model from lidar - DCCEEW
bb5-l canopy height model from lidar - DCCEEW
bb6-l canopy cover model from lidar - DCCEEW
bb7-l canopy density model from lidar - DCCEEW

Metadata

Code Description
am0 Any additional metadata
ar0 Processing report from provider
bn0 Any additional notes/readme text about the imagery (must be OCR PDF format)
br0 Processing report stripped of provider details
xfs CSV file that summarises all/some of the EXIF variables

Optionals

The order of optionals is important. If the optional variable does not apply, continue down the list.

Code Options Description
Aerial Photos
n film name
r run
f frame
l v = vertical, l = left, r = right, o = oblique look direction
a 0 = false, 1 = true annotated
Digital Elevation Models/Surface Model/Orthomosaic
r r#m = metres, r#cm = centimetres, r#mm = millimetres resolution
Other
h numeric value corresponds to height, i.e. h10 = 10m, h30 = 30m, h500ft height (with units)
s numeric value corresponds to speed, i.e. s10 = 10m/s, s30 = 30m/s, s50kn speed (with units)
o numeric value corresponds to overlap i.e. o8080 = 80/80 image overlap, o60p (60%) overlap
File Format
cog Image has been converted to cloud-optimised GeoTIFF
Unusable Data Flag
bad There is an issue with the data and it is not to be used - further information may be available in metadata or by relevant contacts

Who

Code Organisation/Group
aad Australian Antarctic Division
eia Environment Information Australia
ocrp Office of the Chief Remote Pilot

Suffix

.xxx where xxx is the file suffix - Noting that some suffixes may have more than one decimal point (ie. .copc.laz)

An appropriate suffix must be added to the end of the filename relative to the data.


Terrestrial/Surface/Underwater

plp-i-pr where pl = platform level, p = platform, i = instrument, pr = product

What

Platform level (pl)

Code Platform Level
t Terrestrial/Surface
u Underwater

Platform (p)

Code Platform
tp terrestrial platform
sp surface platform
up underwater platform
gp GoPro (can be used on above and below the surface so ensure the platform level is correct to the data)
mx Mixed or multiple platforms

Instrument (i)

Code Instrument
gp7 GoPro Hero 7
ers2 Emlid RS2 (usually base)
ers2p Emlid RS2+
ers3 Emlid RS3 (usually rover)
ers4 Emlid RS4
drtk2 DJI D-RTK-2
drtk3 DJI D-RTK-3
lgs16 Leica GS16 base
lgs18 Leica GS18 rover
lts16 Leica TS16 total station
ls15 Leica LS15 precise level
r4hi Riegl VZ400i
r6hi Riegl VZ600i
r2ti Riegl VZ2000i

Product (pr)

Code Product
re reflective - Used for pretty much all multi-spectral reflective instruments
rp separate panchromatic and reflective imagery (not combined in a single image - see ps code below)
ps General term for pan-sharpened imagery (i.e. the blending of “re” multi-spectral with a higher resolution panchromatic to create a synthetic high-res multi-spectral. This is sometimes done for various sensors)
pan panchromatic
swir short-wave infrared
th thermal
hyp Hyperspectral
dem Digital Elevation Model
dsm Digital Surface Model
mod general term for modelled products - generally associated with the ns satellite code
vrgb video - red, green, blue = GoPro Only
vthm video - thermal = GoPro Only
rgb red, green, blue = GoPro Only
mx Mixed or multiple products
Survey
fn Field Notes
bo Base Observation points
bn Base Navigation data
ro Rover Observation points
rn Rover Navigation data
lo Level Observation points
to Totalstation Observation points
Lidar
dr discrete return lidar point cloud data
wf full waveform lidar
cw continuous wave (phase-shift) lidar

Where

Where Example Description
Satellite
Landsat 5 TM and 7 ETM+ and 8 OLI p[0-9][0-9][0-9]r[0-9][0-9][0-9] e.g. p089r079 USGS World Reference System (WRS2) Landsat Path and Row
Sentinel-2 t55kfp The tile names as used by ESA. These are roughly based on the US Military Grid Reference System but they seem to have modified it a little. Prefix is always "t" and the next two characters are UTM zone number of the tile and then next letter is the latitude band and the final two letters are the tile id within the zone and latitude band.
Mosaics cnamoi06,msh5508,nsw,pwettropics Please refer to Mosaic Tables for complete list of names. Mosaics must include multiple images or sources. If single source imagery is used then use the imagery location coding below. Mosaics based on S3 search zones or state/territory or continent or mapsheet (e.g. 250k) or project. Mapsheet or project are prefixed with m or p respectively. Where different versions of boundary layers exist (i.e. IBRA v6.1 and IBRA v7) the 'where' field is appended with the year the layer was defined (i.e cnamoi06 is based on the CMA layer defined in 2006). The state/territory or continent codes are the two or three character abbreviations for the state/territory or continent without a prefix. The list is: nt - qld - nsw - vic - tas - sa - wa - act - aus. The "r" prefix tag is a catchall for any arbitrary region names not covered by the other codes. Project "p" specific "where" components are used for airborne lidar mosaics and listed on Mosaic Tables. Start each mosaic where with x.
Other
Imagery Location ID [a-z] e.g. perth, uluru, norfolk-island, murray-river, bunger-hills Use place names of cities or towns or prominent features of the overall location the image was captured. Ensure no spaces by using a "-" to replace the space.
AAD Specific Folder names should use the S3 search zones for the whole of the AAT while filenames should be more specific to locations or stations with subfields for buildings
S3 Search Zones - AAT 45t73, minr, himi S3 search zones based on degree wedges and island zones
S3 Station Search Zones mqs1,dvs-12 S3 search zones based on station search areas (numbers 12 means that the coverage includes zone 1 and 2)
Stations (and extended limits) mqs, dvs, mws, cys, h73, m72 Add "x" to the end for extended station limits (e.g. mqsx = Macquarie Station Extended limits while mqs = Macquarie Station). h73 = Heard Island and m72 = McDonald Island.

When

All dates should be expressed in Universal Time (GMT).

Code Example Description
yyyymmdd 19990923 date by year, month, day (1999 september (09) 23 (UTC))
yyyy 2005 single year (not for a single day within the year)
yyyymm 200503 single month (not for a single day)
yyyymmddHHMMSS 20060810014213 datetime by year, month, day, hour, minute, second (e.g. 2006 august (08) 10 01:42:13 (UTC))
e[yy][yy] e9195 standard epoch between two years(eg. of vegetation change; 1991 to 1995 where the start year is in the range 1990 to 1992 and the end is 1994 to 1996)
d[yyyymmdd][yyyymmdd] d1991032319951014 range of days (e.g. 1991 march (03) 23 to 1995 october (10) 14. The presence of the 'd' clearly defines how the 16 digits should be interpreted)
m[yyyymm][yyyymm] m199103199510 range of months (e.g. 1991 march (03) to 1995 october (10). The presence of the 'm' clearly defines how the 12 digits should be broken up)
y[yyyy][yyyy] y19911999 range of years (span of eight years 1991 to 1999. The presence of the 'y' clearly distinguishes it from a single 8-digit date)
n[yyyymmdd] n20100927 A nominal date ("This has been previously used for the Landsat-7 SLC-off data. When a nominal image is created by starting with a primary one; and merging in other surrounding dates to fill the gaps; the nominal date of the image is the initial date; given in the filename; while other dates are recorded only in the history.")
s[mm][mm] s0305 generic season name ("Excludes Antarctic seasons. This is distinct from the use of the 'm' tag for specific seasons. This 's' tag is used for generic seasons; i.e. not tied to a particular year. The given example; s0305; refers to a generic autumn dataset; rather than a specific autumn of a particular year. This is most useful for things like an average over all autumns.")

Reserved or exceptions

eall a subset of the "e" era category to be used where the era is non-specific and can cover ALL eras.

Processing Stage

Ancillary

Code Description
ax0 Ancillary files related to imagery - to include vector-based extents (i.e. pixel shape, order shape, product shape, strip shape, tile shape)
bx0 Ground control points

Data

Code Description
Survey nan
ab0 Base observations - originial - provider
ab1 Rover Observation points - original - provider
ab2 Level Observation points - original - provider
ab3 Totalstation Observation points - provider
bb0 Base observations - originial - DCCEEW
bb1 Rover Observation points - original - DCCEEW
bb2 Level Observation points - original - DCCEEW
bb3 Totalstation Observation points - DCCEEW

Lidar

Code Description
aa0-l raw lidar scanner data (zipped) - provider
aa1-l lidar products - provider
ab1-l lidar scanner data in real world coordinates - provider
ab2-l thinned lidar scanner data in real world coordinates - provider
ab3-l digital elevation model from lidar - provider
ab4-l digital surface model from lidar - provider
ab5-l canopy height model from lidar - provider
ab6-l canopy cover model from lidar - provider
ab7-l canopy density model from lidar - provider
ba0-l raw lidar scanner data (zipped) - DCCEEW
ba1-l lidar products - DCCEEW
bb1-l lidar scanner data in real world coordinates - DCCEEW
bb2-l thinned lidar scanner data in real world coordinates - DCCEEW
bb3-l digital elevation model from lidar - DCCEEW
bb4-l digital surface model from lidar - DCCEEW
bb5-l canopy height model from lidar - DCCEEW
bb6-l canopy cover model from lidar - DCCEEW
bb7-l canopy density model from lidar - DCCEEW

Metadata

Code Description
am0 Any additional metadata
ar0 Processing report from provider
bn0 Any additional notes/readme text about the imagery (must be OCR PDF format)
br0 Processing report stripped of provider details
xfs CSV file that summarises all/some of the EXIF variables

Optionals

The order of optionals is important. If the optional variable does not apply, continue down the list.

Code Options Description
Lidar
r r6mm, r3p5mm, r3mm (use p instead of a decimal point if needed) scan resolution (mm)
p p1200, p2200 pulse repetition rate (khz)
e WGS (either e60, e66, e72, e84) ellipsoid
oh MACQ1982 = mq1982 orthometric height
u u44 to u58 (s not needed as its always south) utm zone
d ITRF2000@2000 = d2000 datum
Survey nan
ce ce0 = manual, ce1 = average fix, ce2 = average float, ce3 = average single coordinates entry method
hd ITRF2000@2000 = hd2000 horizontal datum
u u44 to u58 (s not needed as its always south) utm zone
oh MACQ1982 = mq1982 orthometric height
vd vdmsl = mean sea level, vdep = ellipsoid vertical datum
pl# pl1 = plane, pl0 = grid plane or grid
GoPro
c Alpha character (eg. clA, clZ) camera location
l a = above, s = surface, u = underwater location
Digital Elevation Models
r r#m = metres, r#cm = centimetres, r#mm = millimetres resolution
Unusable Data Flag
bad There is an issue with the data and it is not to be used - further information may be available in metadata or by relevant contacts

Who

Code Organisation/Group
aad Australian Antarctic Division
eia Environment Information Australia
ocrp Office of the Chief Remote Pilot

Suffix

.xxx where xxx is the file suffix - Noting that some suffixes may have more than one decimal point (ie. .copc.laz)

An appropriate suffix must be added to the end of the filename relative to the data.