John,
Thanks for your ideas and thoughts on this. 'maintenanceAndUpdateFrequency' doesn't really
describe what we want since it's used to say how often the dataset is updated e.g yearly, monthly
etc. TM_PeriodDuration also isn't appropriate as this is for a specific time interval and doesn't
relate to a monthly average based on several years of data.
I had a look today at some other websites with metadata for climatology datasets e.g US-NCDC website
to see how others had described time periods. There was metadata for climatology datasets but the metadata
(FGDC format) doesn't describe a monthly subset (what we want describe in for our datasets) but rather
the whole "parent" dataset with a start date and an end date. The start/end dates are the dates over which data for the
dataset was gathered.
So it looks like there are no elements in the ISO19139 standard yet to describe a something thats averaged
over a particular month/season/day etc. This means we will need to describe somewhere it else like
in the title or the abstract. Start/end dates will be the date range the dataset is composed from.
There is one element (extension to ISO19139) in the ISO19139 - Australian Marine Community Profile (MCP)
called 'MD_TemporalAggregationUnitCode' which we could use for climatology type data.
It has code list values for day, multi-day, week, month, multi-month(season) etc..
See the URL (document):
http://www.aodc.gov.au/files/MarineCommunityProfilev1.4.pdf
and look at section B.4.2 titled 'Marine Profile Defined CodeLists'
Thinking about this further I realised for these climatology type datasets we should be using parent and child metadata
records to describe things correctly. So for example the parent dataset could be titled "Australian Salinity Atlas"
and it would have children records titled "Australian Salinity Atlas - January", "Australian Salinity Atlas - February", etc.
Each child record would have parentIndentifier with the uuid of the parent and an
aggregateDatasetName->CI_Citation->title with the same title as the parent.The parent dataset would
have a hierarchyLevel='series' and the children have hierarchyLevel='dataset'
A similar thing with parent/children has been done on the BlueNet-Geonetwork catalog e.g look at
this URL (the parent record):
http://bluenet.its.utas.edu.au/geonetwork/srv/en/metadata.show?id=1395&currTab=simple
Title: Parent record: Vertical coherence of currents in Jervis Bay: Winter deployment
of an Acoustic Doppler Current Profiler (ADCP)
and this URL (one of the children):
http://bluenet.its.utas.edu.au/geonetwork/srv/en/metadata.show?id=1414&currTab=simple
Title: Current values collected through the water column using an Acoustic Doppler Current Profiler (ADCP)
in the centre of Jervis Bay: Winter Deployment
This way of composing the metadata should hopefully be convenient for users searching the catalog.
A user might want say a map of salinity for July, so they would type in a free text search "salinity July"
and the catalog would list datasets that had 'salinity' and' July' in the title. The user could then click on a
WMS link in the record to bring up the map they wanted.
Andrew Walsh
RAN-DODC
----- Original Message ----- From: <John.Hockaday@anonymised.com>
To: <GeoNetwork-users@lists.sourceforge.net>
Sent: Wednesday, May 06, 2009 3:57 PM
Subject: Re: [GeoNetwork-users] How do encode metadata forclimatology dataset in a temporal sense [SEC=UNCLASSIFIED]
Hi Sune and Andrew,
Is it possible that you can use the temporal extent to show that the information has a beginning date of 1999-12 and an end date of 2010-02, then use the resourceMaintenance information to show a 'maintenanceAndUpdateFrequency' of "annually" and use the 'userDefinedMaintanceFrequency/TM_PeriodDration' element to record the summer months?
I haven't looked into this but that *may* be a solution. If the TM_PeriodDuration doesn't work then you could use the free text 'maintenanceNote' element to define the summer months etc.
Just a thought.
John
-----Original Message-----
From: Sune Edmund Pedersen
[mailto:sune.edmund.pedersen.grontmij@anonymised.com]
Sent: Monday, 4 May 2009 3:05 PM
To: GeoNetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] How do encode metadata for
climatology dataset in a temporal sense
Dear Andrew
We are currently trying to do the same thing for climate model data,
and fa e exactly the same problem. How to model metadata for 12 band
raster where each band represent the monthly average for the period
2071-2100? The question is not only relevant for the temporal extent,
but also the dimensions in the data set, where the options seems
limited.
I will keep you posted as we progress over the next 1,5 month, and
please post any findings you make.
Best regards,
Sune Edmund Pedersen
Head of GIS & IT, Vietnam
_____
Grontmij | Carl Bro Vietnam
Number 23, Lane 183, Dang Tien Dong Street
Dong Da District, Hanoi
Vietnam
M +84 9 0479 2908
T +84 4 3537 4861
E sune.edmund.pedersen@anonymised.com
On May 4, 2009, at 11:06 AM, awalsh wrote:
> Dear GN list/ANZLIC list,
>
> We have a lot of datasets here that describe average weather or
> climate or ocean conditions in particular month
> (e.g December) or a season e.g summer. However we are not sure how
> you encode
> this in the temporal sense. We can't use a simple begin date/end
> date as only format
> allowed are yyyy, yyyy-mm or yyyy-mm-dd
>
> Anybody else out there written metadata for climatology datasets?
> which XML elements did you use
> (By the way we are using ISO19139 as base standard for our metadata)
>
> Andrew Walsh
> RAN-DODC
>
--------------------------------------------------------------
----------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions
from industry
> leaders in dedicated Performance & Operations tracks. Use code
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
>
--------------------------------------------------------------
----------------
The NEW KODAK i700 Series Scanners deliver under ANY
circumstances! Your
production scanning environment may not be a perfect world -
but thanks to
Kodak, there's a perfect scanner to get the job done! With
the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork