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
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
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)
+++
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 `
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
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
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
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
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
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
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
-
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
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
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
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
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
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
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
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
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]
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
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
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
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
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*
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
43 matches
Mail list logo