<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/04/2014 10:15 PM, Matej Krejci
wrote:<br>
</div>
<blockquote
cite="mid:CAFZBJFD5MG+8=SzOLBQ8Dc=_mk=yj2A40sYg3pvJKp67sgm3GQ@mail.gmail.com"
type="cite">
<pre wrap="">Hi Stefan,
2014-07-03 18:22 GMT+02:00 Blumentrath, Stefan <a class="moz-txt-link-rfc2396E" href="mailto:Stefan.Blumentrath@nina.no"><Stefan.Blumentrath@nina.no></a>:
</pre>
<blockquote type="cite">
<pre wrap=""> Hei Madi,
Thanks for your clarification.
Very interesting! I see I have to take a closer look on pycsw and it`s
front-ends (as a possible alternative to GeoNetwork).
The pycsw documentation [1] says that also pycsw Metadata repositories are
set up with a database backend (SQLite, PostgreSQL, and even PostGIS
support). However, integration with data portal solutions like e.g. GeoNode
or Open Data Catalogue is unfortunately “read-only” meaning that meta-data
can be only queried [2].
Would be nice if metadata from GRASS could somehow go directly into a
geodata portal (and that the other way around e.g. people, keywords … could
be fetched from there)… (BTW, in the proprietary world such a
functionality requires yet another extension:
<a class="moz-txt-link-freetext" href="https://www.geocat.net/bridge/">https://www.geocat.net/bridge/</a>)
For organization with a geodata portal solution it is maybe possible to
just sync pycsw`s DB with a DB from e.g. GeoNode or so, if one wants to
have that consistent…
If you allow me two more questions in this regard:
Will pycsw become a dependency for GRASS (with metadata support)?
</pre>
</blockquote>
<pre wrap="">Yes it is. Currently there are no packages for Debian. Pycsw has dependency
on SQLalchemy, shapely and pyproj. I have info that debian package
will probably be created during a few months.</pre>
</blockquote>
There are pycsw deb packages for UbuntuGIS and OSGeoLive, but those
were not accepted for Debian and need some more work.<br>
<br>
On a side note, there is work in progress for read/write integration
of pycsw with CKAN.<br>
We are hopping to have a working demo for FOSS4GE in 2 weeks<br>
<br>
<a class="moz-txt-link-freetext" href="http://publicamundi.eu/">http://publicamundi.eu/</a><br>
<br>
Angelos<br>
<br>
<blockquote
cite="mid:CAFZBJFD5MG+8=SzOLBQ8Dc=_mk=yj2A40sYg3pvJKp67sgm3GQ@mail.gmail.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""> And will it be necessary, that pycsw runs on the same computer as GRASS
(meaning also one pycsw for each GRASS installation) or could that somehow
be centralized (in other words that GRASS connects to a central pycsw)?
</pre>
</blockquote>
<pre wrap="">Yes of course, the pycsw is providing csw catalogue which can run on a
local pc (localhost) or on a server. Our vision is to make an interface
based on OWSLib and pycsw which produces essential functions like browsing
based on filtering, harvesting and publishing metadata to csw catalogue.
The user will be able to choose csw catalogue target like a
localhost(probably SQLite) or catalogue on internet. This task will part of
GSOC term and after...
Thank you,
Matej
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
grass-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-dev">http://lists.osgeo.org/mailman/listinfo/grass-dev</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>