<div dir="ltr">Hi Damian<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 16, 2015 at 5:42 AM, Damian Dixon <span dir="ltr"><<a href="mailto:damian.dixon@gmail.com" target="_blank">damian.dixon@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:'comic sans ms',sans-serif">Hi,</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">When ever anyone mentions ISO metadata I think of:</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">ISO 19103</div><div style="font-family:'comic sans ms',sans-serif">ISO 19115</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">Are we talking about these?</div></div></blockquote><div><br></div><div>I am thinking <span style="font-family:'comic sans ms',sans-serif;font-size:12.8px">ISO 19115 and </span><span style="font-family:'comic sans ms',sans-serif;font-size:12.8px">ISO 19115-1 </span><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">If we are then I would just like to mention that both of these standards lose information and context when you attempt to populate the fields from actual data products.</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">There is also the issue of interpretation as to what data fields to copy to which metadata fields.</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">Because of this I would suggest that each data format should store it's metadata in a lossless form.</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">An xlst should be provided to convert each data-format metadata to the appropriate ISO metadata format. </div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">Regards</div><div style="font-family:'comic sans ms',sans-serif">Damian</div><div style="font-family:'comic sans ms',sans-serif"><br></div><div style="font-family:'comic sans ms',sans-serif">PS. Metadata for data does not excite me, but it is a necessary evil that is becoming very important.</div><div style="font-family:'comic sans ms',sans-serif"><br></div></div></blockquote><div><br></div><div>Metadata only excites me when I get someone else's data and I need to know how it was created. At which point it has my full attention :-)</div><div><br></div><div>Doug</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div style="font-family:'comic sans ms',sans-serif"></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 15 October 2015 at 22:07, Kurt Schwehr <span dir="ltr"><<a href="mailto:schwehr@gmail.com" target="_blank">schwehr@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">If anyone wants to follow up on metadata, Sean is right... here is a different subject thread for metadata.<br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 15, 2015 at 11:44 AM, Sean Gillies <span dir="ltr"><<a href="mailto:sean@mapbox.com" target="_blank">sean@mapbox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Kurt,<br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Oct 14, 2015 at 4:20 PM, Kurt Schwehr <span dir="ltr"><<a href="mailto:schwehr@gmail.com" target="_blank">schwehr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Sean got what I was meaning to say. Do we want the output to have some record of which mode was used. I think the answer is likely no. </div></blockquote><div><br></div></span><div>I agree, no. Without a larger provenance framework of some kind there's not much to be done with that information. And such a provenance framework (<a href="http://www.w3.org/TR/prov-o/" target="_blank">http://www.w3.org/TR/prov-o/</a> for example) covers this kind of thing already.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">And it reminds me that I need to think about a driver for writing ISO metadata files. (bleck) The processing steps would go in an xml iso metadata sidecar.</div></blockquote><div><br></div></span><div>Let's discuss ISO metadata in a different thread :)</div><span><font color="#888888"><span><font color="#888888"><div><br></div></font></span></font></span></div><span><font color="#888888"><span><font color="#888888">-- <br><div><div dir="ltr">Sean Gillies</div></div>
</font></span></font></span></div></div><span><font color="#888888">
</font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>--<div><a href="http://schwehr.org" target="_blank">http://schwehr.org</a></div></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div>Doug Newcomb</div><div>USFWS</div><div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div><div>---------------------------------------------------------------------------------------------------------</div><div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. As a federal employee, my email may be subject to FOIA request.</div></div></div></div>
</div></div>