<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Yes, it had occurred to me that XSLT would be a flexible way of handling a
lot of the metadata mappings.</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=damian.dixon@gmail.com
href="mailto:damian.dixon@gmail.com">Damian Dixon</A> </DIV>
<DIV><B>Sent:</B> Monday, October 26, 2015 8:36 AM</DIV>
<DIV><B>To:</B> <A title=tim.crook@sympatico.ca
href="mailto:tim.crook@sympatico.ca">Tim Crook</A> </DIV>
<DIV><B>Cc:</B> <A title=doug_newcomb@fws.gov
href="mailto:doug_newcomb@fws.gov">doug_newcomb@fws.gov</A> ; <A
title=gdal-dev@lists.osgeo.org href="mailto:gdal-dev@lists.osgeo.org">gdal
dev</A> </DIV>
<DIV><B>Subject:</B> Re: Follow on to the "ISO Metadata" post</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">Hi
Tim,</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif">Personally I would not use ISO
19115-1 as an internal format.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">There are
not a huge number of data formats/products that store metadata as XML out of the
box. When they do store metadata it is usually specific to the data and data
product (regardless of how the metadata is stored).</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">There
have been attempts at adding metadata alongside data products such as UK MOD
profile of IS0 19115 (MOD profile has problems). The French equivalent of the
MOD have for a number of years mandated a metadata format alongside all data
products used by them (wish I could find the actual standard for the
metadata).</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">The
biggest problem is actually mapping from data/'data product' metadata to the
target metadata specification.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">Just to
highlight how much a problem the mapping of fields from one metadata format to
another is; we have been arguing off and on for more than a year internally
about the meaning of dates and which date should be in which field. Two of our
big customers do not agree on the meaning of some of the source data date fields
and the mappings we have done.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">I believe
ESRI have their own internal metadata format that they provide a tool to
translate to other XML metadata specifications.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">Where I
work I have been pushing a per data/'data product' format that is XML based that
uses tag value pairs. The tags would basically be a dump of all available
information and specific to each data/'data product'. A set of XSLT scripts
would then translate the information to what ever metadata standard you wanted
to use and if you needed to modify the mapping you could change the XSLT script
for that data/'data product'.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">We have
found that hard-coding the mapping is too costly to maintain and very difficult
to get right.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default style="FONT-FAMILY: comic sans ms,sans-serif">Probably
not the answer you are looking for.</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif">Regards</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif">Damian</DIV>
<DIV class=gmail_default
style="FONT-FAMILY: comic sans ms,sans-serif"> </DIV></DIV>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV class=gmail_quote>On 22 October 2015 at 13:29, Tim Crook <SPAN
dir=ltr><<A href="mailto:tim.crook@sympatico.ca"
target=_blank>tim.crook@sympatico.ca</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello
Doug and Damian.<BR><BR>I saw your post about ISO 19103, ISO 19115 and
ISO 19115-1. I am starting to look at ticket #3549 (<A
href="https://trac.osgeo.org/gdal/ticket/3549" rel=noreferrer
target=_blank>https://trac.osgeo.org/gdal/ticket/3549</A>). This ticket is a
specific problem for metadata translation for image transformations to the
PCIDSK format. The ticket references JPEG and TIFF.<BR><BR>The first thing I
thought of was when I saw your posts was mapping the XML metadata from
different sources into an internal format to GDAL, then passing through the
information for mapping to the destination format. I suppose there are some
image source formats that don't use XML to store their metadata, so this would
require additional handling.<BR><BR>I suppose the internal format to GDAL
could be XML in the ISO 19115-1 format.<BR><BR>Am I completely off base here?
<BR></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV></BODY></HTML>