<div dir="ltr"><div dir="ltr">Hi, <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 24 sept. 2019 à 19:07, Falk Huettmann <<a href="mailto:fhuettmann@alaska.edu">fhuettmann@alaska.edu</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear all,<div><br><div>as Paolo suggested,</div><div>I should ask the list, so here I do:</div><div><br></div><div>"QGIS does have support to metadata. In fact, INSPIRE EU officials have<br>run extensive tests, and it is more compliant than any other GIS".</div></div></div></blockquote><div><br></div><div>I think those tests concern web services and web services metadata. QGIS is probably a very compliant client and server since some work has been done in that area. However, I am not aware of an embedded tool to create INSPIRE - ISO compliant metadata from QGIS. We currently can create Dublin Core metadata in the layer properties, and this comes from the great work funded by the world bank to link QGIS and Geonode. <br></div><div><br></div><div>This work has been discussed into the QEP 91: <a href="https://github.com/qgis/QGIS-Enhancement-Proposals/issues/91">https://github.com/qgis/QGIS-Enhancement-Proposals/issues/91</a></div><div><br></div><div>I think this area needs funding to add ISO compliant metadata templates to store and edit (which is not trivial given the hierarchical structure of ISO 19139 ). Maybe Tim has some fresh info on this topic.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>Could somebody please point me to details and to follow up on ?</div><div><br></div><div>There are four questions in this:</div><div>-what about the U.S. and China government and their buy-in with this, aka none?</div></div></div></blockquote><div>I think US goes to FDGC format. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>-if there is ISO compliance, how can there be different fractions and some being ignored </div><div>(e.g. FGDC and USGS)?</div></div></div></blockquote><div><br></div><div>you should try to discuss in the Geonetwork lists. Templates compatibility is often discussed there. I was handling a catalog before and we could reduce easily ISO to Dublin Core. I think we can do the same with most metadata formats <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>-I have 'good' ISO compliant xml metadata files for try out, but they are not loading into QGIS qmd; we need a cross-platform approach to cater biology, geology, geography and social data. How done ?.</div></div></div></blockquote><div><br></div><div>this is because QMD is currently for Dublin Core format. not ISO<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div></div><div>-real-world example: Antarctica is to have mandatory data, and with metadata; for global mankind. Norway runs and offers a QGIS-based Antarctic concept, but widely without relevant metadata. </div><div><a href="https://www.qgis.org/en/site/about/case_studies/antarctica.html" target="_blank">https://www.qgis.org/en/site/about/case_studies/antarctica.html</a></div></div></div></blockquote><div><br></div><div>Up to now, I lived with the INSPIRE regulations this way:</div><div><br></div><div>Use a standard metadata catalog, geonetwork for instance. <br></div><div>Handle all your data in some reference qgs files (or a directory tree of qlr could do)</div><div>Use some ETL to parse these files and generate automatically metadata entries in the catalog using CSW transactions</div><div>Use QGIS server to render nice overviews for those metadata templates. </div><div>Moderate those metadata and publish those that need to be according to your INSPIRE obligations. In most case, one entity produce very few datasets that need to be sent. We often try to publish dataset that are belonging to other autorities. <br></div><div>Use QGIS server to publish datasets <br></div><div>Wait again some years for the real GML application schema to publish full compliant services (or wait for them to be simplified to REST services). If really nessary, hire someone here (but we are way beyond the metadata topic)<br></div><div> Done.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div> <br></div><div>They would be a typical example for us; looks like a violation of the Antarctic Treaty even; not ?</div></div></div></blockquote><div><br></div><div>Mm, I don't follow you on this. <br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>Thanks again, more later</div><div> Falk Huettmann PhD, Professor</div></div><div> Uni of Alaska Fairbanks</div><div><br></div></div></blockquote><div>Regards</div><div>Régis<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div><br></div></div>
_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-user" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></blockquote></div></div>