<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Barry:    <br>
    </p>
    <p>    Sorry, I don't have a sample GeoPackage that addresses the
      metadata issue.   I'm retired, no longer have work data on my
      laptop, and my archive DVDs are in the attic.  If you already have
      generated an XML metadata doc that validates according to ISO
      19115 schemas, all you need do is insert it into a GPKG metadata
      table record column, with the mime_type column value "text/xml", a
      md_standard_uri column value pointing to the public 19115 XML
      Schema, and the md_scope column value set to the appropriate
      value, probably "dataset", assuming it applies to the entire
      GPKG.  If that is the case, then you also need a
      metadata_reference table record with a reference_scope column
      value of "geopackage" that refers to the metadata table record id
      column value in the md_file_id column, and with table_name,
      column_name, row_id_value and md_parent_id column values of NULL. 
      <br>
    </p>
    <p>    If you want to add additional metadata records (perhaps from
      another source?) that only apply to particular subsets of
      geopackage data, and that amend or supplement the record above,
      then the metadata_reference table records for those metadata
      documents should refer to the metadata table record id above in
      the md_parent_id column value, and the other column values set to
      specify the data subsets described.</p>
    <p>    I hope that helps.  If you have other particular questions,
      I'll try to answer them.</p>
    <p>Paul<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 6/3/2018 2:09 PM, Barry O'Rourke
      wrote: <br>
    </div>
    <blockquote type="cite"
      cite="mid:9d4f7a57-d4d4-2a14-3c2d-ad2d25162d44@compusult.net">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p>Hello Paul, Jeff,</p>
      <p>We have also been investigating techniques for generating and
        utilizing GeoPackage metadata. Our first workflow provides a
        user with the ability to create an ISO 19115 metadata document
        that describes the GeoPackage overall. The user can then publish
        this ISO 19115 metadata document into a service registry and
        provide other users with the ability to discover GeoPackages of
        interest using a catalog search and determine suitability of
        use.<br>
        <br>
        We are also storing this metadata as an XML document in a
        relational table within the GeoPackage itself.<br>
        <br>
        Paul, we are very interested in investigating how you are using
        ISO 19115 to describe "data" within the GeoPackage. Do you have
        a sample GeoPackage we could work with?<br>
        <br>
        How are we planning to document these approaches and make them
        available for discussion?<br>
        <br>
        Thanks,<br>
        <br>
        Barry<br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 4/20/2018 6:52 PM, Jeff Yutzler
        via Geopackage wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CACuR0Kv7gHbeqFJ9r2FPWNgcvsRGZjWeqNFzviJyiXM0aTzSSw@mail.gmail.com">
        <div dir="ltr">OK, I get it now. I haven't actually seen an
          example of many-to-many metadata in the wild so I didn't know
          that was possible.
          <div>-Jeff</div>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Apr 20, 2018 at 3:51 PM, Paul
            Daisey via Geopackage <span dir="ltr"><<a
                href="mailto:geopackage@lists.opengeospatial.org"
                target="_blank" moz-do-not-send="true">geopackage@lists.opengeospatial.org</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>All:</p>
                <p>    Pepijn has it right; the GeoPackage v1.0 metadata
                  model had two tables following a common relational
                  database design for implementing many to many
                  relationships, which were needed to implement the
                  hierarchical metadata model defined in ISO 19115.  One
                  metadata record can apply to many data items (tables /
                  rows / columns or any subset thereof), and one data
                  item can be described by many metadata records (e.g.
                  from different sources).</p>
                <p>    Cheers,<br>
                </p>
                <p>Paul Daisey<br>
                </p>
                <div>
                  <div class="h5"> <br>
                    <div class="m_-2354720600429198695moz-cite-prefix">On
                      4/20/2018 3:19 PM, Pepijn Van Eeckhoudt via
                      Geopackage wrote:<br>
                    </div>
                    <blockquote type="cite"> Hi Jeff,
                      <div><br>
                      </div>
                      <div>Which tables do you mean exactly?
                        gpkg_metadata and gpkg_metadata_reference?</div>
                      <div><br>
                      </div>
                      <div>One stores the metadata itself; the other is
                        the association relationship between the
                        metadata and the data it describes. Splitting
                        the two allows reuse of metadata for multiple
                        tables.</div>
                      <div><br>
                      </div>
                      <div>If I remember correctly, Paul Daisy did most
                        of the work on metadata so he might be able to
                        give you a better answer.</div>
                      <div><br>
                      </div>
                      <div>Pepijn</div>
                      <div><br>
                      </div>
                      <div>
                        <div>
                          <blockquote type="cite">
                            <div>On 20 Apr 2018, at 21:10, Jeff Yutzler
                              via Geopackage <<a
                                href="mailto:geopackage@lists.opengeospatial.org"
                                target="_blank" moz-do-not-send="true">geopackage@lists.<wbr>opengeospatial.org</a>>
                              wrote:</div>
                            <br
                              class="m_-2354720600429198695Apple-interchange-newline">
                            <div>
                              <div dir="ltr">Hello list.
                                <div>Does anyone out there remember why
                                  we have two separate metadata tables
                                  as part of the Metadata Extension
                                  (this was originally part of core)? I
                                  am trying to produce guidance for this
                                  extension and as far as I can tell,
                                  there is a 1:1 mapping between the two
                                  tables. Am I missing something?</div>
                                <div>-Jeff<br clear="all">
                                  <div><br>
                                  </div>
                                  -- <br>
                                  <div
                                    class="m_-2354720600429198695gmail_signature"
                                    data-smartmail="gmail_signature">
                                    <div dir="ltr">
                                      <div>
                                        <div dir="ltr">
                                          <div>Jeff Yutzler<br>
                                            <a
                                              href="http://www.imagemattersllc.com/"
                                              target="_blank"
                                              moz-do-not-send="true">Image
                                              Matters LLC</a><br>
                                            Mobile: (703) 981-8753<br>
                                          </div>
                                        </div>
                                      </div>
                                    </div>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                        <br>
                      </div>
                    </blockquote>
                    <br>
                  </div>
                </div>
                <span class="HOEnZb"><font color="#888888">
                    <pre class="m_-2354720600429198695moz-signature" cols="72">-- 
Paul Daisey 301-651-7148</pre>
                  </font></span></div>
            </blockquote>
          </div>
          <br>
          <br clear="all">
          <div><br>
          </div>
          -- <br>
          <div class="gmail_signature" data-smartmail="gmail_signature">
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div>Jeff Yutzler<br>
                    <a href="http://www.imagemattersllc.com/"
                      target="_blank" moz-do-not-send="true">Image
                      Matters LLC</a><br>
                    Mobile: (703) 981-8753<br>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Paul Daisey 301-651-7148</pre>
  </body>
</html>