AW: [Qgis-user] Undo and redo editing
Hi Horst I also like to have the node tools in a pull-down menu. Still I think the separation basic editing toolbar / advanced editing toolbar makes sense because some advanced tools are probably used less frequently, so user should have the possibility to show/hide this toolbar depending on his current task. My suggestion is to hide the advanced editing toolbar by default (for the first start of qgis) such that user interface seems less overcrowded for new users. Also, I'd like to move the split feature tool to the advanced editing toolbar as it probably is used less frequently than 'add feature' and the node tools. What do you think? Regards, Marco -Ursprüngliche Nachricht- Von: qgis-user-boun...@lists.osgeo.org im Auftrag von Düster Horst Gesendet: Mo 15.06.2009 09:09 An: qgis-user@lists.osgeo.org Betreff: [Qgis-user] Undo and redo editing Martin and Richard Great news after long weekend. Thank you very much for the great ability to undo and redo the last editings. The editing environment is very matured now. We should think about to rearrange the two editing toolbars. What about to combine p.e. all nodetools inclusive move, add and delete a single node into one pulldown button and so on with the other editing tools? Regrads Horst Dr. Horst Düster GIS-Koordinator, Stv. Amtschef Kanton Solothurn Bau- und Justizdepartement Amt für Geoinformation SO!GIS Koordination Rötistrasse 4 CH-4501 Solothurn Telefon ++41(0)32 627 25 32 Telefax ++41(0)32 627 22 14 mailto:horst.dues...@bd.so.ch http://www.agi.so.ch ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] QGIS citation in the FAQ
Hi, On Mon, 15 Jun 2009 22:37:35 +0200 Agustin Lobo alobolis...@gmail.com wrote: I'm a bit confused by the FAQ entry regarding citation: Quantum GIS Development Team (YEAR). GNU General Public License. http://qgis.osgeo.org; Should we just write the current year? I guess it depends on what you want to cite. It would probably make sense to distinguish. For example the GRASS project offers some ideas, if you just cite the webpage, or a certain software version or manual. http://grass.osgeo.org/wiki/GRASS_Citation_Repository I can something similar for QGIS if you like. What do others think? The citation above is just general. Regards, Otto Thanks Agus ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Public Repository for plugins...
it is very good opportunity to create two repos for the same plugin. One for stable and one for experimental purposes. For those, who didn't enable experimental plugins, how can we enable the experimental plugins in the qgis in order to fetch the plugin from repo if the repo is tagged as experimental? -- View this message in context: http://n2.nabble.com/Public-Repository-for-plugins...-tp3045029p3084708.html Sent from the qgis-user mailing list archive at Nabble.com. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] QGIS citation in the FAQ
On Tue, 16 Jun 2009 08:31:13 +0200 Otto Dassau otto.das...@gmx.de wrote: Hi, On Mon, 15 Jun 2009 22:37:35 +0200 Agustin Lobo alobolis...@gmail.com wrote: I'm a bit confused by the FAQ entry regarding citation: Quantum GIS Development Team (YEAR). GNU General Public License. http://qgis.osgeo.org; Should we just write the current year? I guess it depends on what you want to cite. It would probably make sense to distinguish. For example the GRASS project offers some ideas, if you just cite the webpage, or a certain software version or manual. http://grass.osgeo.org/wiki/GRASS_Citation_Repository I can something similar for QGIS if you like. What do others think? The citation above is just general. I added a wiki page on basis of the GRASS_Citation_Repository and adapted the FAQ. Please tell us, if you think something is wrong or missing. http://www.qgis.org/wiki/QGIS_Citation_Repository Regards, Otto ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: AW: [Qgis-user] Undo and redo editing
Hugentobler Marco wrote: Hi Horst I also like to have the node tools in a pull-down menu. Still I think the separation basic editing toolbar / advanced editing toolbar makes sense because some advanced tools are probably used less frequently, so user should have the possibility to show/hide this toolbar depending on his current task. My suggestion is to hide the advanced editing toolbar by default (for the first start of qgis) such that user interface seems less overcrowded for new users. +1 Also, I'd like to move the split feature tool to the advanced editing toolbar as it probably is used less frequently than 'add feature' and the node tools. What do you think? +1 -- Micha Regards, Marco ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] QGIS citation in the FAQ
Hi Agustin,
in your case, maybe the Geoinformatics article written by the current PSC
members for the QGIS 1.0 release in February this year can be used.
I added the link to the article on the wiki Journals page. It would be
great if more people can provide links to other articles about QGIS there. It
wasn't used for quite some time, so maybe we can start/awake the list again.
http://www.qgis.org/wiki/Journals
In my opinion it always depends. If you want to add a reference to the
QGIS project in general I would use:
Quantum GIS Development Team, (2009). Quantum GIS Geographic Information
System. Open Source Geospatial Foundation Project. http://grass.osgeo.org
but if you prefere to cite from an article, maybe you find something in the
Journals page.
Regards,
Otto
On Tue, 16 Jun 2009 10:26:23 +0200
Agustin Lobo alobolis...@gmail.com wrote:
I will use waht is provided in the web, but
I think that the best would be having the Quantum GIS Development Team
writing an article with a general description of QGIS basic
characteristics, history and
roadmap. Something equivalent to:
Anselin, Luc, Ibnu Syabri and Youngihn Kho (2006). GeoDa: An
Introduction to Spatial Data Analysis. Geographical Analysis 38 (1), 5-22.
but including the url if possible. This would be the best reference to
be used in an article, as
what the interested reader would search in the reference is a general,
readable description of QGIS.
Also, another example would be R, which has a command citation():
citation()
To cite R in publications use:
R Development Core Team (2009). R: A language and environment for
statistical computing. R Foundation for Statistical Computing,
Vienna, Austria. ISBN 3-900051-07-0, URL http://www.R-project.org.
A BibTeX entry for LaTeX users is
@Manual{,
title = {R: A Language and Environment for Statistical Computing},
author = {{R Development Core Team}},
organization = {R Foundation for Statistical Computing},
address = {Vienna, Austria},
year = {2009},
note = {{ISBN} 3-900051-07-0},
url = {http://www.R-project.org},
}
We have invested a lot of time and effort in creating R, please cite it
when using it for data analysis. See also ___citation(pkgname)___ for
citing R packages.
This is more on the line of what we have in the faq for qgis. (BTW, I
would move
or copy the citation from the faq to the home page of the web site).
So, animo!
Agus
Otto Dassau wrote:
On Tue, 16 Jun 2009 08:31:13 +0200
Otto Dassau otto.das...@gmx.de wrote:
Hi,
On Mon, 15 Jun 2009 22:37:35 +0200
Agustin Lobo alobolis...@gmail.com wrote:
I'm a bit confused by the FAQ entry regarding
citation:
Quantum GIS Development Team (YEAR). GNU General Public License.
http://qgis.osgeo.org;
Should we just write the current year?
I guess it depends on what you want to cite. It would probably make sense
to
distinguish. For example the GRASS project offers some ideas, if you just
cite
the webpage, or a certain software version or manual.
http://grass.osgeo.org/wiki/GRASS_Citation_Repository
I can something similar for QGIS if you like. What do others think? The
citation above is just general.
I added a wiki page on basis of the GRASS_Citation_Repository and adapted
the
FAQ. Please tell us, if you think something is wrong or missing.
http://www.qgis.org/wiki/QGIS_Citation_Repository
Regards,
Otto
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Public Repository for plugins...
Tuesday 16 of June 2009 08:47:06 Volkan Kepoglu napisał(a): it is very good opportunity to create two repos for the same plugin. One for stable and one for experimental purposes. You can either create the two repos and recommend the unstable one only for 'experimenting' users, or put two plugin instances to one repo and mark one as experimental. For those, who didn't enable experimental plugins, how can we enable the experimental plugins in the qgis in order to fetch the plugin from repo if the repo is tagged as experimental? Wait, whole repo can't be tagged as experimental. Is there such need? In fact, I would prefer to avoid such complications... Is there Luiz P. Motta reading me? :) Pleeease, correct the version number of your plugin :) ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [Qgis-user] Public Repository for plugins...
Well, I assume that the two plugins I posted will remain in the wild as they are designed from a tester's point of view and from an educational point of view. I would say that plugins that are general enough to benifit ,majority of QGIS users make it to the core. For the other SPECIALIZED plugins a group to review them might be a good idea. I imagine that most of this would depend on the community, for prolific authors might hold more weight than the one times and the learners. A process that merely checks off criteria versus worthiness might make a lot of sense. Making the process objective instead of subjective. Just some thoughts. Cheers -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Alex Mandel Sent: Monday, June 15, 2009 22:07 To: Borys Jurgiel Cc: qgis-user@lists.osgeo.org Subject: Re: [Qgis-user] Public Repository for plugins... Borys Jurgiel wrote: Monday 08 of June 2009 22:42:34 Dane Springmeyer napisał(a): Funny - how is it that there are only two 'official plugins'? Yes - nobody is keen to form a High Committee and evaluate plugins... :( I don't think too many people have asked, besides that it seems that plugins that are really good end up in the core code most of the time and don't exist as separate plugins for long. Alex ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [Qgis-user] Public Repository for plugins...
Just as I am going through a pseudo code exercise of release.py I see three cases. 1. Current and previous stable versions VERSION 2. A Beta version is is being tested an on its way to stable. BETA 3. An unstable snapshot of the development trunkALPHA If we assume that most new feature development is done in the branches and merged to trunk, then trunk should not be all the harry and trashy. The branches would be way to unstable. This way then regular users can try unstable and beta version of the plugins wihtout needing to get into SVN carnage. For now I will call trunk snapshots BETA Just some thoughts. -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Borys Jurgiel Sent: Monday, June 15, 2009 19:15 To: qgis-user@lists.osgeo.org Subject: Re: [Qgis-user] Public Repository for plugins... Monday 08 of June 2009 22:03:47 Sampson, David napisał(a): Maybe those that are interested can have a little thread and come up with a temp solutions while the ducks line up... I would propose sourceforge as that is what I know and I already help admin a project on sourceforge. I would say if we can get three plugin groups working together that is a good start. Any takers? This is good idea. The present state of multi-instance plugins I've tried to explain in my previous post. In general, you can add to your repository two instances of the same plugin: pyqgis_plugin version=0.1 name=Foo Plugin descriptionSome description/description homepagehttp://foo/homepage qgis_minimum_version1.0/qgis_minimum_version file_namefoo.zip/file_name author_nameSomeone/author_name download_urlhttp://some_url/some_dir/foo.zip/download_url /pyqgis_plugin pyqgis_plugin version=0.2-beta name=Foo Plugin descriptionSome description/description homepagehttp://foo/homepage qgis_minimum_version1.0/qgis_minimum_version file_namefoo.zip/file_name author_nameSomeone/author_name download_urlhttp://some_url/another_dir/foo.zip/download_url experimentaltrue/experimental /pyqgis_plugin Note that there are two plugins foo.zip. The latter one has higher version number, but is marked with the optional tag experimental. It means, that will be chosen as the 'best available' for all users allowing experimental plugins. For those, who didn't enable experimental plugins, the former plugin will be chosen. Similarly, you can publish one instance for QGIS=1.0 and another one for QGIS =1.1 Just remember to give a higher version for the latter one and installer choose the highest one if the =1.1 requirement is fulfilled. Note that both files are named foo.zip, so you can't put them together to the main contributed repository, as they all are stored in one directory there. But you can use the suffix I mentioned in my previous mail: foo.zip containing the directory foo foo.beta.zip containing the same directory foo Oh, the main repository doesn't handle the 'experimental' tag yet, AFAIK? But I hope it will be implemented soon. Note that there are only two levels of stability: experimental or not. It has been discussed whether we need more and realized that just don't. Please remember that there are so many authors with different opinions and different willingness to keep metadata accurate ;) that I found keeping it as simple as possible reallyu essential :) ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [Qgis-user] Public Repository for plugins...
For a community plugin repo I assume that multiple authors might be involved in the development of a plugin For the element... author_nameSomeone/author_name Can this be a comman separated value. I am thinking of automaticaly generating this from an AUTHORS.txt file Also, is there an e-mail optio we can add or what about a URL to an AUTHORS file? Cheers -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Borys Jurgiel Sent: Monday, June 15, 2009 19:15 To: qgis-user@lists.osgeo.org Subject: Re: [Qgis-user] Public Repository for plugins... Monday 08 of June 2009 22:03:47 Sampson, David napisał(a): Maybe those that are interested can have a little thread and come up with a temp solutions while the ducks line up... I would propose sourceforge as that is what I know and I already help admin a project on sourceforge. I would say if we can get three plugin groups working together that is a good start. Any takers? This is good idea. The present state of multi-instance plugins I've tried to explain in my previous post. In general, you can add to your repository two instances of the same plugin: pyqgis_plugin version=0.1 name=Foo Plugin descriptionSome description/description homepagehttp://foo/homepage qgis_minimum_version1.0/qgis_minimum_version file_namefoo.zip/file_name author_nameSomeone/author_name download_urlhttp://some_url/some_dir/foo.zip/download_url /pyqgis_plugin pyqgis_plugin version=0.2-beta name=Foo Plugin descriptionSome description/description homepagehttp://foo/homepage qgis_minimum_version1.0/qgis_minimum_version file_namefoo.zip/file_name author_nameSomeone/author_name download_urlhttp://some_url/another_dir/foo.zip/download_url experimentaltrue/experimental /pyqgis_plugin Note that there are two plugins foo.zip. The latter one has higher version number, but is marked with the optional tag experimental. It means, that will be chosen as the 'best available' for all users allowing experimental plugins. For those, who didn't enable experimental plugins, the former plugin will be chosen. Similarly, you can publish one instance for QGIS=1.0 and another one for QGIS =1.1 Just remember to give a higher version for the latter one and installer choose the highest one if the =1.1 requirement is fulfilled. Note that both files are named foo.zip, so you can't put them together to the main contributed repository, as they all are stored in one directory there. But you can use the suffix I mentioned in my previous mail: foo.zip containing the directory foo foo.beta.zip containing the same directory foo Oh, the main repository doesn't handle the 'experimental' tag yet, AFAIK? But I hope it will be implemented soon. Note that there are only two levels of stability: experimental or not. It has been discussed whether we need more and realized that just don't. Please remember that there are so many authors with different opinions and different willingness to keep metadata accurate ;) that I found keeping it as simple as possible reallyu essential :) ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [SPAM] RE: [Qgis-user] Public Repository for plugins...
Tuesday 16 of June 2009 15:18:37 Sampson, David napisał(a): For a community plugin repo I assume that multiple authors might be involved in the development of a plugin For the element... author_nameSomeone/author_name Can this be a comman separated value. sure I am thinking of automaticaly generating this from an AUTHORS.txt file Also, is there an e-mail optio we can add or Not yet, but is definitely essential! Sometimes it's really hard to contact the author, as email is not included even to source files. We can add a tag email or include emails to the author_name tag. The latter option is better for multiple authors as I think. So let's allow both solutions. Installer will both handle the email tag and parse everything looking like an email from the author_name. Of course this could be also an easy pray for spamers, so we need to find the best way to format email address. what about a URL to an AUTHORS file? The main blocker is free space in Installer window ;) If authors are ready to provide more info (screenshots, longer descriptions, changelogs), we can make Installer more verbose and implement a big browser for pretty formatted metadata. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [SPAM] RE: [Qgis-user] Public Repository for plugins...
Tuesday 16 of June 2009 15:03:11 Sampson, David napisał(a): Just as I am going through a pseudo code exercise of release.py I see three cases. 1. Current and previous stable versions VERSION 2. A Beta version is is being tested an on its way to stable. BETA 3. An unstable snapshot of the development trunk ALPHA If we assume that most new feature development is done in the branches and merged to trunk, then trunk should not be all the harry and trashy. The branches would be way to unstable. This way then regular users can try unstable and beta version of the plugins wihtout needing to get into SVN carnage. For now I will call trunk snapshots BETA Just some thoughts. So do we want to have three levels? The present experimental tagging style is related to the fact that many authors just release either plugins considerable as stable, or just some concepts. But if we are going to develop more complicated plugins (and it seems we are), there is a reason to do more precise tagging, of course ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [SPAM] RE: [Qgis-user] Public Repository for plugins...
I don't want to speak on behalf of the community, I just came across what I figured would work for the central repo and kinda matches typical; open source projects that facilitate the three options. Cheers -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Borys Jurgiel Sent: Tuesday, June 16, 2009 09:44 To: qgis-user@lists.osgeo.org Subject: Re: [SPAM] RE: [Qgis-user] Public Repository for plugins... Tuesday 16 of June 2009 15:03:11 Sampson, David napisał(a): Just as I am going through a pseudo code exercise of release.py I see three cases. 1. Current and previous stable versions VERSION 2. A Beta version is is being tested an on its way to stable. BETA 3. An unstable snapshot of the development trunk ALPHA If we assume that most new feature development is done in the branches and merged to trunk, then trunk should not be all the harry and trashy. The branches would be way to unstable. This way then regular users can try unstable and beta version of the plugins wihtout needing to get into SVN carnage. For now I will call trunk snapshots BETA Just some thoughts. So do we want to have three levels? The present experimental tagging style is related to the fact that many authors just release either plugins considerable as stable, or just some concepts. But if we are going to develop more complicated plugins (and it seems we are), there is a reason to do more precise tagging, of course ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] Plugin.xml troubles
So I have posted a plugins.xml file that I thought might work base don previous examples. I double checked the version numbers and did have to make some changes http://voxel.dl.sourceforge.net/sourceforge/qgiscommunitypl/plugins.xml I tried using absolute links to the files residing in sorceforge so that we don't have to wait for redirects. Could someone try it out and let me know where I am messing up. Once this is hammered out then auto generation could become simpler. Cheers ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [Qgis-user] Plugin.xml troubles
For the record, this is the error that is returned from qgis Error reading repository: Qgis Community plugin Repository Couldn't parse output from the repository Cheers -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Sampson, David Sent: Tuesday, June 16, 2009 11:58 To: qgis-user@lists.osgeo.org Subject: [Qgis-user] Plugin.xml troubles So I have posted a plugins.xml file that I thought might work base don previous examples. I double checked the version numbers and did have to make some changes http://voxel.dl.sourceforge.net/sourceforge/qgiscommunitypl/pl ugins.xml I tried using absolute links to the files residing in sorceforge so that we don't have to wait for redirects. Could someone try it out and let me know where I am messing up. Once this is hammered out then auto generation could become simpler. Cheers ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Plugin.xml troubles
Tuesday 16 of June 2009 17:59:08 Sampson, David napisał(a): For the record, this is the error that is returned from qgis Error reading repository: Qgis Community plugin Repository Couldn't parse output from the repository Hi, this error is a bit mysterious. If I open the file with Kate and save it as a new file, it starts to work. However I can't see any problems with encoding nor EOL chars... I'll look at this issue tonight. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
RE: [Qgis-user] Plugin.xml troubles
I plopped mine in the htdocs dir of OSGEO4W and it worked After you log out of SourceForge or leave the project page for a length of time the direct download links are forwarded to their HTML interface instead of a direct download. I am not sure if there is a way around this or not. I think it is to drive advertsiing. Might be able to drop them in a common HTDOCS directory on SF to try that. Cheers -Original Message- From: qgis-user-boun...@lists.osgeo.org [mailto:qgis-user-boun...@lists.osgeo.org] On Behalf Of Borys Jurgiel Sent: Tuesday, June 16, 2009 12:48 To: qgis-user@lists.osgeo.org Subject: Re: [Qgis-user] Plugin.xml troubles Tuesday 16 of June 2009 17:59:08 Sampson, David napisał(a): For the record, this is the error that is returned from qgis Error reading repository: Qgis Community plugin Repository Couldn't parse output from the repository Hi, this error is a bit mysterious. If I open the file with Kate and save it as a new file, it starts to work. However I can't see any problems with encoding nor EOL chars... I'll look at this issue tonight. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] Desktop metadata editing...
Yes, I'm in the same case than Maning. Agus maning sambale wrote: Documentation perhaps? I tried using http://apps.sourceforge.net/trac/qgismetaedit/ But never, got past loading the example xmls, I am having difficulty editing. I'm a newbie in metadata editing, normally I just create a simple textfile for our GIS output. On Tue, Jun 9, 2009 at 4:18 AM, Alex Mandeltech_...@wildintellect.com wrote: Sampson, David wrote: Ahh.. Metadata As I am going through creating some plugins and learning about OWS services and trying my hand at a catalogue plugin I got to thinking, what does the open source world do for managin their metadata on their desktop? I know and quite like projects like geo-network and our own flavour at http://geodiscover.cgdi.ca/ but I am curious as to what people use for their desktop. Back when FGDC was the spec of choice I used MP (metadata Parser) quite extensively http://geology.usgs.gov/tools/metadata/tools/doc/mp.html but with the new world of IS and the upcoming NAP (North American Profile) I wonder what people are doing now. Would a lean desktop editor help people in the workflow. Essentialy maintaining their metadata on the desktop then exporting (through valid XML) to publishing facilities such as geonetwork.. The idea is to couple data and metadata while people are working with the data. Are people working on this? Do open source solutions already exist? Would a plugin for QGIS be useful? Or a desktop app that can hit many softwares like GRASS, QGIS and others? Thoughts? Cheers I'm kinda chuckling because you just brought together the same two things I'm working on. Here's the sourceforge site for the plugin I started http://apps.sourceforge.net/trac/qgismetaedit/ Contributions are welcome, the big thing on the table is we need to swap out the XML parser to allow for better character handling and saving. I've already picked out Elementree as the tool and started a branch but won't have time to work on it for another week or two. Alex ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user begin:vcard fn:Agustin Lobo n:Lobo;Agustin org:Institut de Ciencies de la Terra Jaume Almera CSIC adr:;;Lluis Sole Sabris s/n;Barcelona;;08028;Spain email;internet:agustin.l...@ija.csic.es url:http://www.ija.csic.es/gt/obster version:2.1 end:vcard ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
