Re: [GRASS-dev] problem installing wx.metadata from g.extension

[Matej Krejci]

Hi Madi,
thanks for update wiki page, I have updated (r67551) dependency file for
checking dependency before installation.
ciao Matej

On Mon, Jan 11, 2016 at 2:43 PM Margherita Di Leo 
wrote:

> Figured out I missed dependency python-reportlab. Not sure it's written
> anywhere in https://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
> , I'm updating now the wiki page.
>
> Thanks
>
>
>
>
> On Mon, Jan 11, 2016 at 11:59 AM, Margherita Di Leo 
> wrote:
>
>> Hi,
>>
>> I have problem installing wx.metadata via g.extension:
>>
>> > g.extension wx.metadata
>> Fetching  from GRASS GIS Addons repository (be patient)...
>> Compiling...
>> Traceback (most recent call last):
>>   File
>> "/tmp/grass7-v-user-21088/tmpape9at/wx.metadata/scripts/g.gui.metadata",
>> line 45, in 
>> from mdpdffactory import PdfCreator
>>   File "../mdlib/mdpdffactory.py", line 13, in 
>> from reportlab.platypus import Paragraph, Image, Table
>> ImportError: No module named reportlab.platypus
>> make[1]: *** [g.gui.metadata.tmp.html] Error 1
>> Installing...
>> /usr/bin/install: cannot stat
>> ‘/tmp/grass7-v-user-21088/tmpape9at/wx.metadata/docs/html/g.gui.metadata.html’:
>> No such file or directory
>> make[1]: *** [install] Error 1
>> make: *** [installsubdirs] Error 2
>> WARNING: Installation failed, sorry. Please check above error messages.
>>
>> GRASS trunk installation updated today. ~/.grass7/addons was clean.
>> wx.metadata specific dependencies installed
>>
>> Any pointers?
>> Thank you in advance
>>
>> --
>> Margherita Di Leo
>>
>
>
>
> --
> Margherita Di Leo
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wx.metadata / g.gui.metadata another problem in pdf export

[Matej Krejci]

Hi Paulo,
problem with use constraints is fixed in r67340.
Thanks for the report.
Matej

On Tue, Dec 22, 2015 at 6:40 PM Paulo van Breugel 
wrote:

> When saving the metadata to pdf the 'use constraints' field is not handled
> correctly. Even when filled in, in the pdf output it shows 'unknown' under
> the use constraints header.
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] pygrass util.py set_path bug

[Matej Krejci]

Hi,

can someone please commit this[1] diff to trunk. The current code doesn't
count with parameters of the function.

thanks
Matej


[1]
Index: lib/python/pygrass/utils.py
===
--- lib/python/pygrass/utils.py (revision 66629)
+++ lib/python/pygrass/utils.py (working copy)
@@ -313,7 +313,7 @@
 pathlib = os.path.join(path, dirname)
 if os.path.exists(pathlib):
 # we are running the script from the script directory
-sys.path.append(os.path.abspath(path))
+sys.path.append(os.path.abspath(pathlib))
 else:
 # running from GRASS GIS session
 path = get_lib_path(modulename, dirname)
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] wx.metadata ready for testing

[Matej Krejci]

Hi Martin and others,

2015-10-04 14:33 GMT+02:00 Martin Landa <landa.mar...@gmail.com>:

> Hi all,
>
> recently I fixed some compilation and installation issues of
> wx.metadata addons [1] (GSoC 2014 & 2015 project of Matej Krejci). Now
> it's possible to install it via `g.extension`.
>
> Martine, thanks for work on it.

Testing welcome. Martin
>
>
 I just checked .grass7/addons/etc/wx.metadata and installation deployed
only /mdlib dir but no /configure and /profiles dirs. It is the same issue
like r.green[1]. Correctly placed directories should looks like:

matt@matt-pc:~/grass_trunk/dist.x86_64-unknown-linux-gnu/etc/wx.metadata$
tree
├── config
│   ├── connections_resources.xml
│   ├── default-sample.cfg
│   ├── init_md.txt
│   ├── keywordConcepts.txt
│   ├── keywordGroups.txt
│   ├── keywordThemes.txt
│   ├── record_metadata_dc.html
│   ├── service_metadata.html
│   ├── xml_highlight.html
│   └── xml_render.html
├── mdlib
│   ├── cswlib.py
│   ├── cswlib.pyc
│   ├── cswutil.py
│   ├── cswutil.pyc
│   ├── mdeditorfactory.py
│   ├── mdeditorfactory.pyc
│   ├── mdgrass.py
│   ├── mdgrass.pyc
│   ├── mdjinjaparser.py
│   ├── mdjinjaparser.pyc
│   ├── mdpdffactory.py
│   ├── mdpdffactory.pyc
│   ├── mdpdftheme.py
│   ├── mdpdftheme.pyc
│   ├── mdutil.py
│   └── mdutil.pyc
└── profiles
├── basicProfile.xml
├── inspireProfile.xml
└── temporalProfile.xml

This example is created by local installation which works well.
matt@matt-pc:~/addons/grass7/gui/wxpython/wx.metadata$ make
MODULE_TOPDIR=$HOME/grass_trunk & make MODULE_TOPDIR=$HOME/grass_trunk
install

I am not sure if this issue is about Makefile or not.

Thanks for any idea.
matej

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-August/076034.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.gui.metadata and wxgui addons in GRASS 7.1

[Matej Krejci]

Hi Stephan,

2015-08-21 22:08 GMT+02:00 Blumentrath, Stefan stefan.blumentr...@nina.no:

 Hi Matej,



 I just checked out your new revision. Now I get on sudo make
 MODULE_TOPDIR=/usr/local/grass-7.1.svn/:



 make[1]: Entering directory
 `/data/src/grass7_addons/gui/wxpython/wx.metadata/g.gui.metadata'

 if [ /usr/local/grass-7.1.svn/scripts/g.gui.metadata !=  ] ; then
 GISRC=/usr/local/grass-7.1.svn/demolocation/.grassrc71
 GISBASE=/usr/local/grass-7.1.svn
 PATH=/usr/local/grass-7.1.svn/bin:/usr/local/grass-7.1.svn/bin:/usr/local/grass-7.1.svn/scripts:$PATH
 PYTHONPATH=/usr/local/grass-7.1.svn/etc/python:/usr/local/grass-7.1.svn/gui/wxpython:$PYTHONPATH
 LD_LIBRARY_PATH=/usr/local/grass-7.1.svn/bin:/usr/local/grass-7.1.svn/scripts:/usr/local/grass-7.1.svn/lib:/usr/local/grass-7.1.svn/lib:
 LC_ALL=C /usr/local/grass-7.1.svn/scripts/g.gui.metadata --html-description
  /dev/null | grep -v '/body\|/html'  g.gui.metadata.tmp.html ; fi

 Traceback (most recent call last):

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata, line 27, in
 module

 sys.path.insert(2, os.path.join(os.getenv('GRASS_ADDON_BASE'), 'etc',
 'wx.metadata', 'mdlib'))

   File /usr/lib/python2.7/posixpath.py, line 77, in join

 elif path == '' or path.endswith('/'):

 AttributeError: 'NoneType' object has no attribute 'endswith'

 make[1]: *** [g.gui.metadata.tmp.html] Error 1

 rm g.gui.metadata.tmp.html

 make[1]: Leaving directory
 `/data/src/grass7_addons/gui/wxpython/wx.metadata/g.gui.metadata'


Problem was that I never try *make* with *sudo*. I am not sure why it has
effect. Problem should be fixed in r66007.

thank you for testing
Best
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.gui.metadata and wxgui addons in GRASS 7.1

[Matej Krejci]

Hi Stephan,

I can browse the maps in my mapset and the pen and the “template” button
 get active. Yet, when I click on “template” I get:



 WARNING: Epsg code cannot be identified

 Traceback (most recent call last):

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata, line 291, in
 onCreateTemplate

 if self.onEdit():

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata, line 303, in
 onEdit

 ok = self.editMapMetadata()

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata, line 648, in
 editMapMetadata

 self.xmlPath = self.mdCreator.saveXML(self.mdDestination,
 self.nameTMPteplate, self)

   File /usr/local/grass-7.1.svn/etc/wx.metadata/mdlib/mdgrass.py, line
 513, in saveXML

 profile = env.get_template(self.profilePath)

   File
 /usr/local/lib/python2.7/dist-packages/Jinja2-2.9.dev-py2.7.egg/jinja2/environment.py,
 line 812, in get_template

 return self._load_template(name, self.make_globals(globals))

   File
 /usr/local/lib/python2.7/dist-packages/Jinja2-2.9.dev-py2.7.egg/jinja2/environment.py,
 line 774, in _load_template

 cache_key = self.loader.get_source(self, name)[1]

   File
 /usr/local/lib/python2.7/dist-packages/Jinja2-2.9.dev-py2.7.egg/jinja2/loaders.py,
 line 187, in get_source

 raise TemplateNotFound(template)

 jinja2.exceptions.TemplateNotFound:
 etc/wx.metadata/profiles/basicProfile.xml



Current revision is 66011. Before was everything defined fixedly to grass
addons environment/base. Now it should work in all way of installation.
please try:

sudo make MODULE_TOPDIR=/usr/local/grass-7.1.svn
sudo make MODULE_TOPDIR=/usr/local/grass-7.1.svn install

folders with metadata libs, profiles and configure files need make install.


The location was defined using an EPSG code (25632). It is a standard
 ETRS/UTM based CRS which is quite common for the western to central parts
 of Europe (and INSPIRE compliant)…

This warning does not affect for something important.  Only auto
identifying EPSG from WKT proj is not successful which means that the
metadata attribute has not value. I changed warning to message because a
lots of attributes cannot be filled from r/v.info.




 Anyway, the first glimpse I got from g.gui.metadata looked promising!
 Thanks for your work on that!




big thanks for your endurance :-)

Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.gui.metadata and wxgui addons in GRASS 7.1

[Matej Krejci]

Dear Stefan,

Thanks for bug report. I have done few changes(r65990) which should help
but the installation from add-ons still doesn't work properly[1].

2015-08-20 14:41 GMT+02:00 Blumentrath, Stefan stefan.blumentr...@nina.no:

 Hi,



 I just tried to install g.gui.metadata addon with limited success.



 No AddOn appears under wxGUI when I run g.extension from the GUI (while
 e.g. raster addons do show up). Is this probably do to the path in the
 AddOn repo (which starts with gui and not wxGUI). All other tree elements
 in g.extension are equal to folder names in the repository…

 So, I finally compiled g.gui.extension from source after installing the
 dependencies.



 Now, g.gui.metadata is available, but does not start:



 Traceback (most recent call last):

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 1246, in module

 main()

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 1240, in main

 MAINFRAME = MdMainFrame()

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 88, in __init__

 self.onInitEditor()

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 724, in onInitEditor

 self.MdDataCatalogPanelLeft =

 MdDataCatalog(self.leftPanel)

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 836, in __init__

 self.InitTreeItems()

   File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 860, in InitTreeItems

 self.initTemporalTree(location=location,

 mapset=self.mapset)

  File /usr/local/grass-7.1.svn/scripts/g.gui.metadata,

 line 923, in initTemporalTree

 if self.itemExists(ml[2], varmapset) == False:

   File

 /usr/local/grass-7.1.svn/gui/wxpython/lmgr/datacatalog.py,

 line 213, in itemExists

 item, cookie = self.GetFirstChild(root)

   File /usr/lib/python2.7/dist-

 packages/wx-2.8-gtk2-unicode/wx/_controls.py, line 5409, in

 GetFirstChild

 return _controls_.TreeCtrl_GetFirstChild(*args,

 **kwargs)

 ValueError: invalid null reference in method

 'TreeCtrl_GetFirstChild', expected argument 2 of type

 'wxTreeItemId const '




Best
Matej

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-August/076034.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] grass-addons and nested module libraries

[Matej Krejci]

Dear Pietro, devs,


2015-08-17 12:57 GMT+02:00 Pietro peter.z...@gmail.com:

 Dear devs,

 I've noticed that r.green module is installing his libraries in the wrong
 place:

 {{{
 $ # rm -r $GRASS_ADDON_BASE
 $ g.extension extension=r.green
 Fetching r.green from GRASS GIS Addons repository (be patient)...
 Compiling...
 Installing...
 Updating addons metadata file...
 ERROR: Unable to read manual page: [Errno 2] No such file or directory:
'/home/pietro/.grass7/addons/docs/html/r.green.html'
 }}}

 that generate a tree directory like:

 {{{
 $ tree $GRASS_ADDON_BASE
 /home/pietro/.grass7/addons
 ├── bin
 ├── docs
 │   ├── html
 │   │   ├── grassdocs.css
 │   │   ├── r.green.biomassfor.co2.html
 │   │   └── ...
 │   ├── man
 │   │   └── man1
 │   │   ├── r.green.biomassfor.co2.1
 │   │   ├── r.green.biomassfor.economic.1
 │   │   └── ...
 │   └── rest
 ├── etc
 ├── libgreen
 │   ├── checkparameter.py
 │   └── ...
 ├── libhydro
 │   ├── basin.py
 │   └── ...
 ├── modules.xml
 └── scripts
 ├── r.green.biomassfor.co2
 ├── r.green.biomassfor.economic
 └── ...
 }}}

 I would like that both the directories: libgreen and libhydro are
 installed inside  $GRASS_ADDON_BASE/etc/r.green:

 {{{
 $ tree $GRASS_ADDON_BASE
 /home/pietro/.grass7/addons
 ├── bin
 ├── docs
 │   ├── html
 │   │   ├── grassdocs.css
 │   │   ├── r.green.biomassfor.co2.html
 │   │   └── ...
 │   ├── man
 │   │   └── man1
 │   │   ├── r.green.biomassfor.co2.1
 │   │   ├── r.green.biomassfor.economic.1
 │   │   └── ...
 │   └── rest
 ├── etc
 │   └── r.green
 │   ├── libgreen
 │   │   ├── checkparameter.py
 │   │   └── ...
 │   └──libhydro
 │   ├── basin.py
 │   └── ...
 ├── modules.xml
 └── scripts
 ├── r.green.biomassfor.co2
 ├── r.green.biomassfor.economic
 └── ...
 }}}

 I think the problem is due that when in the Makefile I create the
 ETCDIR the LIBGREENDIR does not exist yet:

 https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.green/libgreen/Makefile#L18


 Therefore I've tried adding to the Makefile something like:

 {{{
 $ svn diff libgreen/Makefile
 Index: libgreen/Makefile
 ===
 --- libgreen/Makefile   (revision 65945)
 +++ libgreen/Makefile   (working copy)
 @@ -15,6 +15,9 @@

  default: $(PYFILES) $(PYCFILES) $(ETCDIR)/__init__.py
 $(ETCDIR)/__init__.pyc

 +$(LIBGREENDIR):
 +   $(MKDIR) $@
 +
  $(ETCDIR):
 $(MKDIR) $@

 }}}

 But it continue to install libgreen and libhydro in the
 $GRASS_ADDONS_BASE root...


 NOTE: if I compile the module with: make MODULE_TOPDIR=$GISBASE both
 the directories are created in the correct place:

 {{{
 $ ls -l $GISBASE/etc/r.green
 total 8.0K
 drwxr-xr-x 2 pietro pietro 4.0K Aug 17 12:52 libgreen/
 drwxr-xr-x 2 pietro pietro 4.0K Aug 17 12:52 libhydro/
 }}}

 Why?

 Someone has an idea on how I could/should fix this?


 Pietro
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev




I have exactly the same problem(described bellow) with installation
wx.metadata from addons. Have you figured out this issue?

1)Local installation works well:

-
matt@matt-pc:~/addons/grass7/gui/wxpython/wx.metadata$ make
MODULE_TOPDIR=$HOME/grass_trunk  make MODULE_TOPDIR=$HOME/grass_trunk
install
...no errors

-
matt@matt-pc:~/grass_trunk/dist.x86_64-unknown-linux-gnu/etc/wx.metadata$
tree
.
├── config
│   ├── connections_resources.xml
│   ├── default-sample.cfg
│   ├── init_md.txt
│   ├── keywordConcepts.txt
│   ├── keywordGroups.txt
│   ├── keywordThemes.txt
│   ├── record_metadata_dc.html
│   ├── service_metadata.html
│   ├── xml_highlight.html
│   └── xml_render.html
├── mdlib
│   ├── cswlib.py
│   ├── cswlib.pyc
│   ├── cswutil.py
│   ├── cswutil.pyc
│   ├── mdeditorfactory.py
│   ├── mdeditorfactory.pyc
│   ├── mdgrass.py
│   ├── mdgrass.pyc
│   ├── mdjinjaparser.py
│   ├── mdjinjaparser.pyc
│   ├── mdpdffactory.py
│   ├── mdpdffactory.pyc
│   ├── mdpdftheme.py
│   ├── mdpdftheme.pyc
│   ├── mdutil.py
│   └── mdutil.pyc
└── profiles
├── basicProfile.xml
├── inspireProfile.xml
└── temporalProfile.xml

...everything is correctly placed


2) Installation from addons doesn't work correctly

-
GRASS 7.1.svn (cr-wgs84):~  g.extension wx.metadata
...successful

-
matt@matt-pc:~/.grass7/addons$ tree
.
├── bin
├── docs
│   ├── html
│   │   ├── db.csw.admin.html
│   │   ├── db.csw.harvest.html
│   │   ├── db.csw.run.html
│   │   ├── g.gui.cswbrowser.html
│   │   ├── g.gui.metadata.html
│   │   ├── grassdocs.css
│   │   ├── grass_logo.png
│   │   ├── r.info.iso.html
│   │   ├── t.info.iso.html
│   │   └── v.info.iso.html
│   ├── man
│   │   └── man1
│   │   ├── db.csw.admin.1
│   │   ├── db.csw.harvest.1
│   │   ├── db.csw.run.1
│   │   ├── g.gui.cswbrowser.1
│   │   ├── g.gui.metadata.1
│   │   ├── r.info.iso.1
│   

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 11

[Matej Krejci]

Dear all,
below is my 11th report for  Improved metadata for GRASS GIS project.

1) What do I have completed this week?

I have
→implemented function for publishing metadata to csw directly from
g.gui.metadata.
→refractored GUI code of g.gui.metadata.
→written html documentation for each new and for each updated modul and
also we have solved problem with EPSG code.

2) What am I going to achieve for next week?
I would like to
→polish code
→update wiki page for users
→try to add wktproj2epsg function for g.proj modul
→publish my progress to add-ons and to test it.

3) Is there any blocking issue?
My computer started overheating and it make noise like helicopter. Still
works - so, here is not any blocking issue.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 10

[Matej Krejci]

Dear all,
below is my 10th report for  Improved metadata for GRASS GIS project.

1) What do I have completed this week?

   - This week I was working on rearranging structure of libraries and
   modules of wx.metadata package.
   - After that I was working on Makefiles but not successfully.
   - I also killed some bugs and refractored parts of code of
   g.gui.metadata editor.

2) What am I going to achieve for next week?
Because I partly worked on other stuff than I proposed last week I will
continue with:

   - Adding support for exporting metadata to catalog(csw) in
   g.gui.metadata.
   - Finalizing code and iso templates- working on #TODO
   - Writing html manuals and documentation for new modules
   - db.csw.start
  - db.csw.admin
  - g.gui.cswbrowser
   - and new features for g.gui.metadata
  - export to pdf
  - export to csw
  - support of tgrass

3) Is there any blocking issue?

   - Makefiles for add-ons. I will consult it with my mentors next week.

Have a nice rest of the weekend!
Best
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 9

[Matej Krejci]

Dear all,
below is my report for  Improved metadata for GRASS GIS project.

1) What do I have completed this week?

   - Implemented command line based module(db.csw) for handling csw server
   on localhost. current functions :
  - setup db(prepare tables,indexes)
  - load metadata
  - delete records
  - optimize db
  - export records
  - executing csw requests from xml
  - function for automatic setup server and establishing catalog in
  default GRASS database backend

2) What am I going to achieve for next week?

   - Finishing db.csw:
  - Getting more familiar with harvesting possibilities of pycsw. My
  vision is to harvest from another csw with defined bounding box filter.
  - Test and debug db.csw.
  - Connect with module g.gui.metadata
 - adding support for exporting metadata to catalog(csw).
  - Starting with writing manual and documentation about csw.

3) Is there any blocking issue?

   - No

Best
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: GSoC 2015 Improved metada for GRASS GIS week 8

[Matej Krejci]

Hi,
I forgot cc of GSOC report.

-- Forwarded message --
From: Matej Krejci matejkre...@gmail.com
Date: 2015-07-20 19:30 GMT+02:00
Subject: GSoC 2015 Improved metada for GRASS GIS week 8
To: s...@lists.osgeo.org


Dear all,
please apologies for late submit my report for Improved metadata for GRASS
GIS project.

1) What do I have completed this week?

   - Fixed known bugs from last week.
   - Added interface for connecting services directly from catalog browser.

2) What am I going to achieve for next week?

   - Implementation of module for establishing csw on localhost PC (pycsw).
  - adding functions for controlling(harvesting, removing) metadata
  from csw.

3) Is there any blocking issue?

   - I had problem with coding of makefiles. Solved.

Best
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 7

[Matej Krejci]

Hello,
below is my report for Improved metadata for GRASS GIS project.

1) What do I have completed this week?

   - Added panel for browsing through catalog. Templates for view of
   service/dataset metadata is used from Metasearch plugin.
  - Keywords filtering
 - basic multiple keywords filtering ( condition)
 - advanced constraints filtering based on boolean operations
- OR
- AND
- combination
 - bounding box filtering
 - global by default
 - from map extent

2) What am I going to achieve for next week?

   - Fixed known bugs in g.gui.metacsw
   - Adding interface for connecting r.in.wms, v.in.wfs with
   g.gui.metadatacsw
   - Starting with designing module for establishing csw on localhost
   (?g.gui.cswcreator?)

3) Is there any blocking issue?

   - no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 6

[Matej Krejci]

Dear all,
this is my report for Improved metadata for GRASS GIS project.
Please apologies
for my lateness.

1) What do I have completed this week?

   - Started with implementation of g.gui.metacsw module
  - Added panel for managing connection to service.
 - Allows reading default xml file with predefined connection which
 is compatible with Meta_Search from QGIS,
 - showing basic inforamtion about service,
 - managing services:
- adding new,
- removing,
- loading list of connection from xml file.

2) What am I going to achieve for next week?

   - Plan for next week is continuing with developing g.gui.metacsw.
  - I will focus on creating search manager for searching/browsing
  metadata from csw according to selected bounding box and keywords.

3) Is there any blocking issue?

   - no
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 5

[Matej Krejci]

Hi,
this is my report for Improved metadata for GRASS GIS project.

1) What do I have completed this week?

   - During last week I
  - established pycsw server on localhost.
  - became familiar with usage of OWSLib csw library.
  - started on designing client-side module based on OWSLib.

2) What am I going to achieve for next week?

   - Plan for next week is to implement class allowing connection to
   service(service info, “getCapabilities” response, add/delete service, edit
   service) and related GUI.

3) Is there any blocking issue?

   - no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 3

[Matej Krejci]

Hi,
this is my report for Improved metadata for GRASS GIS project.

1) What do I have completed this week?

   - I got familiar with temporal metadata ISO standards
   - I have started with designing temporal metadata profile

2) What am I going to achieve for next week?

   - To continue with adding support metadata for Temporal framework to
   g.gui.metadata.

3) Is there any blocking issue?

   - Due to examination period at my university I will compensate less time
   in work after exams(last and next week).

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSoC 2015 Improved metada for GRASS GIS week 1

[Matej Krejci]

Hello. This is my first report for Improved metada for GRASS GIS project
[1].

1) What do I have completed this week?

   - I have partly finished support of exporting metadata to pdf files[2].
   - I have fixed some defects in metadata editor which arose from changes
   in GRASS core.

2) What am I going to achieve for next week?

   - To connect pdf export library with metadata editor.
   - Adding an option for fetching predefined metadata values from a DB
   (the backend used in GRASS GIS) e.g.: keyword lists, points of contacts.

3) Is there any blocking issue?

   - Luckily nothing happened.


[1] https://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata
[2] https://trac.osgeo.org/grass/log/sandbox/krejcmat/src/GSOC2015?rev=65344
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2015: Improved Metadata for GRASS GIS

[Matej Krejci]

Now it should work. The problem was in modification/remove of GuiModuleMain
from core.utils.

2015-04-28 20:55 GMT+02:00 Paulo van Breugel p.vanbreu...@gmail.com:

 Is the addon working in GRASS 7.1? I can't compile it.


 On Tue, Apr 28, 2015 at 8:16 PM, Matej Krejci matejkre...@gmail.com
 wrote:

 Hi,
 Thanks for the chance to participate on GSOC 2015. The page about project
 is on wiki site[1]. Thank you for ideas and notes in advance.

 Matej

 [1] http://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata

 2015-03-11 1:55 GMT+01:00 Matej Krejci matejkre...@gmail.com:

 Hi all,

 Last GSOC I was working on ISO based metadata management for GRASS. In
 this term I was created 'package' wx.metadata which is currently available
 in GRASS add-ons. This part was essential. During playing with
 possibilities of implementation I did a draft of metadata catalogue which
 is the main task of current GSOC topic[1]. Moreover to implement additional
 functions (see list[1]) for current metadata modules is more than suitable.
 Since last GSOC I am still slightly in coding for GRASS and I like to
 continue in this topic. Please let me know if the topic is still free.

 Thanks in advance,
 Matej


 [1]
 http://trac.osgeo.org/grass/wiki/GSoC/2015#ImprovedMetadataforGRASSGIS



 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev



___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSOC 2015: Improved Metadata for GRASS GIS

[Matej Krejci]

Hi,
Thanks for the chance to participate on GSOC 2015. The page about project
is on wiki site[1]. Thank you for ideas and notes in advance.

Matej

[1] http://trac.osgeo.org/grass/wiki/GSoC/2015/ImprovedMetadata

2015-03-11 1:55 GMT+01:00 Matej Krejci matejkre...@gmail.com:

 Hi all,

 Last GSOC I was working on ISO based metadata management for GRASS. In
 this term I was created 'package' wx.metadata which is currently available
 in GRASS add-ons. This part was essential. During playing with
 possibilities of implementation I did a draft of metadata catalogue which
 is the main task of current GSOC topic[1]. Moreover to implement additional
 functions (see list[1]) for current metadata modules is more than suitable.
 Since last GSOC I am still slightly in coding for GRASS and I like to
 continue in this topic. Please let me know if the topic is still free.

 Thanks in advance,
 Matej


 [1] http://trac.osgeo.org/grass/wiki/GSoC/2015#ImprovedMetadataforGRASSGIS

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GSOC 2015: Improved Metadata for GRASS GIS

[Matej Krejci]

Hi all,

Last GSOC I was working on ISO based metadata management for GRASS. In this
term I was created 'package' wx.metadata which is currently available in
GRASS add-ons. This part was essential. During playing with possibilities
of implementation I did a draft of metadata catalogue which is the main
task of current GSOC topic[1]. Moreover to implement additional functions
(see list[1]) for current metadata modules is more than suitable.
Since last GSOC I am still slightly in coding for GRASS and I like to
continue in this topic. Please let me know if the topic is still free.

Thanks in advance,
Matej


[1] http://trac.osgeo.org/grass/wiki/GSoC/2015#ImprovedMetadataforGRASSGIS
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata finished

[Matej Krejci]

Hi,
today I have finished goals within the GSoC project.

Finally, the modules are available in addons [1] and documentation and
manual is on wiki pages [2].

Thank you for giving me chance to take part in this project.

Best,
Matej


[1]
http://trac.osgeo.org/grass/browser/grass-addons/grass7/gui/wxpython/wx.metadata
[2] http://grasswiki.osgeo.org/wiki/ISO/INSPIRE_Metadata_Support
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 13

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - commented code
   - worked on documentation
   - grass wiki
  - modules html

*work to be done in the next week*

   - to finish documentation
   - testing wx.metadata in addons

*blocks*
no


Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] metadata naming and location

[Matej Krejci]

Hi Luca,

I didn't try metadata tool yet but, the metadat are created
 automatically by GRASS or the user have to create them?
 If the answer is the first one I fully agree with your proposal
 otherwise I'd leave the choice where save the metadata to the user...


Metadata are created only by user. In editor is option to set working
directory. By default is the directory path/to/location/mapset/metadata. After
click on save button user is asked by dialog window to selecting directory
in any case. So it meets with your suggestion :)

Thanks Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] metadata naming and location

[Matej Krejci]

Hi,

I would like to introduce possibility/decision of naming and choice of
location for .xml metadata files.
With Margherita and Martin we agreed:

To create new folder 'metadata' in grass location:
path/to/location/metadata

naming:
for raster map:
cell_ + nameofmap +.xml
e.g cell_basin.xml

for vector map:
vector_ + nameofmap+ .xml
vector_route.xml

also prefix can be r_ and v_. What you think?

We decide to leave postfix in accordance with type of profile (basic,
inspire) and hold just one metadata file.

Does that make sense?

Thank you
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 12

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - testing and fixing bugs
   - dynamic adding of widgets in editor
  - exporting xml
   - created interface for update native grass metadata from editor
   (r.support,v.support)
   - consulted and improved file working in editor
   - created validator of BASIC profile
   - captured few videos
  - editing metadata of map [1]
  - creation of template [2]
  - editing external iso xml [3]
  - tutorial on creation custom iso metadata profile [4]

*work to be done in the next week*

   - cleaning code
   - to write documentation on grass wiki.

*blocks*
no


Best,
Matej

[1] https://www.youtube.com/watch?v=7V5NyVdO05o
[2] https://www.youtube.com/watch?v=Pu2sQoAJXfo
[3] https://www.youtube.com/watch?v=npMAavbwfi0
[4] https://www.youtube.com/watch?v=ahl41mFD5w0
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 11

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - created interface which allows pre-defining metadata into templates
   based on jinja [1]
  - allowed editing metadata of multiple maps
   - added validators of text input
   - tested and fixed bugs

*work to be done in the next week*

   - testing editor
   - cleaning code
   - removing of known bugs in dynamic generator of gui
   - improving functionality of multiple editor

*blocks*
I had some issue with non-unicode encoding in jinja2 lib which is throwing
quite weird tracebacks.


Best,
Matej

[1]
http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS#Week11August1
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 10

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - fixed some bugs:
  - in xml exporting module
  - in wx metadata generator
   - created and tested modified jinja template for inspire and grass
   profile
   - worked on GUI features in g.gui.metadata
   - added and connected data-catalog
   - started with text input validator

*work to be done in the next week*

   - to create validators of text inputs
   - to start on implementation of multiple editing metadata of maps
   - testing editor
   - consulting GUI design

*blocks*
no


Best regards,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 9

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - mainly implemented 'metadata multiplicity button' for dynamically
   adding widgets and also removing it
   - finished support of exporting metadata from dynamically generated GUI
   (multiplicity button) (need more working to allow exporting keywords to xml
   (multiple keywords))
   - partially connected finished modules together (g.gui.metadata) [1]
  - validator
  - tree editor
  - main editor
  - toolbox

*work to be done in the next week*

   - to finish connection between modules
  - to change current map catalog(left side)  for grass
  datacatalog.py[2]
   - to fix exporting of metadata-keywords added by 'multiplicity button to
   static box' to xml.
   - to start on implementation of multiple editing metadata of maps
   - to connect v.info.iso, r.info.iso to g.gui.metadata
   - testing

*blocks*
no


Best,
Matej

[1]
http://trac.osgeo.org/grass/attachment/wiki/GSoC/2014/MetadataForGRASS/g.gui.metadata1.jpg
[2] http://grass.osgeo.org/programming7/datacatalog_8py_source.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 8

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - after consultation with mentors I re-implemented generator of GUI
   editor to more object-oriented design
   - implemented functionality for exporting edited metadata to XML
   - started on implementation of dynamically adding objects of widgets to
   crated layout. (1)
   - change timeline on wiki [1]

*work to be done in the next week*

   - to finish (1)
   - to connect implemented components (g.gui.metadata)
  - to connect to v.info.iso, r.info.iso
  - to create toolbox/menu
  - to add map catalog browser
  - to add inspire validator

*blocks*


Best,
Matej

[1] http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] gsoc2014 grass metadata week 6

[Matej Krejci]

Hi Stefan,


2014-07-03 18:22 GMT+02:00 Blumentrath, Stefan stefan.blumentr...@nina.no:

  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:
 https://www.geocat.net/bridge/)

 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)?

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.

  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)?

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
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 7

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - created gui generator from jinja template with conection to OWSLib.
  - this generator connects objects and loops from jinja with xml
  loaded by OWSLib.


*work to be done in the next week*

   - to add functionality for reading ISO keywords
   - to implement functionality for saving edited metadata

*blocks*
a bit.

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] gsoc2014 grass metadata week 6

[Matej Krejci]

Hi Stefan,

 2014-07-02 9:35 GMT+02:00 Blumentrath, Stefan stefan.blumentr...@nina.no
:

 Hi Matej,
 I was wondering, did you consider storing keyword lists, points of
contacts, and  so on in a central (SQLite) database (comparable to what
the t.*-modules do with  time series)? For organizations it would be
useful to have tools which produce
 consistent meta-data (same set of key-words used by all members of
staff…).

Current possibility how to produce consistent metadata (same set of key) is
by modifcation jinja template [1].  Values in jinja template are
represented by Python objects. You can just replace these objects by desire
values for creating pattern. What do you think?


 Furthermore, efficiency might be improved by having e.g. table with
contact
 pers ons within an organization (where all contact details are saved) one
can
 pick from in a combo-box.

 Such a DB should probably be accessible from all locations and mapsets…

It makes sense to me. This task should not be problem, but is more than
essential. Probably I'll do it after the GSOC term.


 BTW, is the metadata publishing functionality based on owslib + pycsw,
which
 you mention on your wiki-page, somehow related to GeoNetwork?
No, I dont know this project in detail...

Thank you for useful hints!
Cheers
Matej

[1]
https://svn.osgeo.org/grass/sandbox/krejcmat/src/data/grassInspireTemplate.xml
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] gsoc2014 grass metadata week 6

[Matej Krejci]

Hi,
2014-06-30 9:37 GMT+02:00 Luca Delucchi lucadel...@gmail.com:

 On 29 June 2014 21:57, Matej Krejci matejkre...@gmail.com wrote:
  Hi all,

 Hi Matej

 
  to finish version 1.1 (by wikipage) of g.gui.editor
 

 I think that g.gui.editor it is not so clear, could you rename it to
 g.gui.metadata or g.gui.metaeditor?

 Thanks for notice. The right/current name is g.gui.metadata. I just wrote
name wrongly in weekly report. Sorry for confusion. However, the final name
of module is open.
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 6

[Matej Krejci]

Hi all,
Below is my weekly report:

*work done*

   - worked on GUI editor
  - implemented generator of metadata items (control text, label,
  button) in main editor
  - fixed some bugs in editor
   - implemented interface for parse information from jinja template
  - added additional information about metadata to jinja template.

*work to be done in the next week*
Continue with working on GUI editor:

   - to finish version 1.1 (by wikipage) of g.gui.editor
  - to connect GUI editor (middle panel) with OWSLib and Jinja template

*blocks*
no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 5

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - redesigned GUI
   - implemented main part of GUI main frame, layout:
   - based on MultiSplitterWindow
  - implemented grass maps browser
  - implemented  advanced xml browser/editor


*work to be done in the next week*
Continue with working on GUI editor:

   - to add toolbox
   - start working on interface for parsing information about metadata from
   jinja template
   - start working on main metadata editor (middle GUI panel)

*blocks*
no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 4

[Matej Krejci]

Hi all,

Below is my weekly report:

*work done*

   - adapted r.info.iso according to update of r.info
   - polished and commented code of v.info.iso and r.info.iso,
   - published alpha version of modules v.info.iso and r.info.iso to sandbox
   - presented on wiki page the future plan of implementation and GUI
   design of metadata editor.

*work to be done in the next week*
For 18 of Jun I have to study thoroughly for bachelor exam (proposed in
timeline). We came up with a plan for next week:

   - to start the implementation of GUI editor:
  -  implementation of gui editor version 1.0: to implement main window
  and layout
   - to publish modules v.info.iso and r.info.iso to GRASS addons

*blocks*
no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 3

[Matej Krejci]

Hi all,

Below is my weekly report:

*Work done*
Consulted design of metadata editor with mentors.
Consulted current implementation of v.info.iso and r.info.iso
Search for alternatives to Jinja templates (current implementation)
Learned basics of wxPython


*Work to be done in the next week*
For 18 of Jun I have to study thoroughly for bachelor exam (proposed in
timeline). We came up with a plan for next week:

   - after update of r.info module to adapt current code,
   - to polish and to comment code of v.info.so and r.info.iso,
   - to publish modules v.info.iso and r.info.iso to GRASS addons,
   - to present on wiki page the design of GUI editor for open discussion.

*blocks*
no
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 2

[Matej Krejci]

Hi all,

Below is my second weekly report:

*Work done*
Created cmd modules for writing ISO-based metadata - r.info.iso +
v.info.iso - support of basic grass ISO schema and inspire schema (for
subsequent editing in future wxGUI editor)

*Work to be done in the next week*
- getting familiar with wxPython,
- to consult with mentors the implementation of wxGUI metadata editor.

*blocks*
no

Best,
Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gsoc2014 grass metadata week 1

[Matej Krejci]

Hi all,

Below is my first weekly report:

Work done
You can find my weekly report on grass wiki [1]
Location of git repository is in discussion..

Work to be done in the next week
Tune up essential metadata profiles.
Design library for generate XML from predefined scheme.

blocks
I have to wait for important update of OWSLib which will be finished during
next week.

Matej

[1] http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRAS
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] request for access to Add-ons

[Matej Krejci]

Hi,

I'd like to request the access to Add-ons for add  module r.mwprecip (which
is  for  computing rainfall data from cellular microwave links). I am agree
with RFC2 [1].

Thank you in advance
 Matej


[1] http://grass.osgeo.org/programming7/rfc2_psc.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Metadata GRASS (GSOC)

[Matej Krejci]

Hi,


  I was wondering was whether it would be possible to extract from pycsw
 just the part for reading/writing the xml meta-data, without all the
 overhead linked to its status as a server.




 More generally, I just think that we can't be the only ones working on
 metadata in a Python environment and that we maybe not have to reinvent the
 wheel.


I got news that OWSLib can be used for parse XML according ISO without
dependence on pycsw server. In addition I found that  there is a pycsw
package in UbuntuGIS and also there is a plan to develop package for Debian
with the development  should start probably after couple of months. OWSLib
have dependence only on lxml so this is not a barrier. If we use OWSLib for
first task, it could to ensure a smoother continuity to develop second
task- pywps.

Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Metadata GRASS (GSOC)

[Matej Krejci]

2014-05-14 22:54 GMT+02:00 Newcomb, Doug doug_newc...@fws.gov:

 With option 1) , would the tool also operate on externally linked datasets
 ( via v.external and r.external) ?

 Doug



 Hi,
I think that first task is to make creator and editor of XML metadata
standards.
Fill in these XML by values from maps  is next step. I do not know at
current stage of project.

Matej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Metadata GRASS (GSOC)

[Matej Krejci]

Hi,

I would like to discuss the metadata management in GRASS which is my topic
for GSOC.

My idea for GSOC term is to Python library, command line modules and wxGUI
front-end.

The current plan has two parts, however the second one is optional.

1)
Main task is to make Python library that can create, read and edit XML (ISO
standard). I think it is necessary to implement standards externally. In
this case it is useful to use XSD (xml template) to generate the valid XML.
There is an option to use generateDS[1] to generates Python code with
classes representing XSD structure. Also the generateDS can fill XSD  and
then export it to XML.
In this case the module will read raster and vector metadata from current
GRASS flat files. In the future(GRASS 8 development) a new C lib can be
created. It would enable to fill in fundamental XML with values from
GRASS(v, r, r3d) and other values by default values that can be replaced
by this module. This C library will be just for fill in basic XML and any
control (edit,read,etc) will be provide by Python module (GSOC). What you
think about generateDS?

2)
If theres some time left in GSOC term or after I would like to implement a
server-client management of metadata using pycsw [3](server side) and
owslib[3] in client side. Demonstration of functions that provide this
solution is i.e. in QGIS plugin (Meta Search).  I  wanted to use this
suggestion at first, but there are quite heavy dependences on others
packages. In addition there is no any package for debian... So this
solution will be for a user who really want to work with metadata but not
fundamental ones.


[1]http://www.rexx.com/~dkuhlman/generateDS.html
[2]http://pycsw.org/
[3]http://geopython.github.io/OWSLib/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev