[Qgis-developer] Atlas Plugin - Serial Printing - Call for financing
Hi all, I am discussing with Oslandia (the authors of the Atlas plugin for serial printing) an option to include Atlas into QGIS core. Currently it is a python plugin, the idea would be to port it to C++ and include it with QGIS by default. It would also be an opportunity to fix several bugs and maybe feature requests. To see what it does: see http://www.oslandia.com/tech/?p=1079 and http://hub.qgis.org/projects/atlas and http://plugins.qgis.org/plugins/atlas/ Oslandia made me an offer/estimate on how much the C++ port and fixing of some bugs would cost. We can only finance parts of it. If one or two others are joining we could probably do it. If not, we will just go with some bug fixing in the Python plugin. Please contact me offlist if you are interested in this functionality and are able to contribute financially. Andreas -- -- Andreas Neumann Böschacherstrasse 10A 8624 Grüt (Gossau ZH) Switzerland ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Atlas Plugin - Serial Printing - Call for
financing MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Good idea. Would the idea be to port it as a plugin or intergrate it into the composer. The later would be very cool. Kind of like the data driven pages in ArcGIS. - Nathan Sent from some fancy phone looking thingo From: Andreas Neumann Sent: 28/06/2012 5:46 PM To: qgis-user; qgis-developer Subject: [Qgis-developer] Atlas Plugin - Serial Printing - Call for financing Hi all, I am discussing with Oslandia (the authors of the Atlas plugin for=20 serial printing) an option to include Atlas into QGIS core. Currently it is a python plugin, the idea would be to port it to C++=20 and include it with QGIS by default. It would also be an opportunity to=20 fix several bugs and maybe feature requests. To see what it does: see http://www.oslandia.com/tech/?p=3D1079 and http://hub.qgis.org/projects/atlas and http://plugins.qgis.org/plugins/atlas/ Oslandia made me an offer/estimate on how much the C++ port and fixing=20 of some bugs would cost. We can only finance parts of it. If one or two=20 others are joining we could probably do it. If not, we will just go with= =20 some bug fixing in the Python plugin. Please contact me offlist if you are interested in this functionality=20 and are able to contribute financially. Andreas --=20 -- Andreas Neumann B=C3=B6schacherstrasse 10A 8624 Gr=C3=BCt (Gossau ZH) Switzerland ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [Qgis-user] Atlas Plugin - Serial Printing - Call for
Hi Nathan, The idea would be to develop a first integration into the composer. The first version would probably look like the current python plugin, but according to the budget we have we will be able to do a full and seamless integration. Contact Andreas and/or me if interested in funding. Vincent Le jeudi 28 juin 2012 10:09:03, Nathan Woodrow a écrit : > financing > MIME-Version: 1.0 > Content-Type: text/plain; charset="utf-8" > Content-Transfer-Encoding: quoted-printable > > Good idea. Would the idea be to port it as a plugin or intergrate it > into the composer. The later would be very cool. Kind of like the data > driven pages in ArcGIS. > > - Nathan > > Sent from some fancy phone looking thingo > From: Andreas Neumann > Sent: 28/06/2012 5:46 PM > To: qgis-user; qgis-developer > Subject: [Qgis-developer] Atlas Plugin - Serial Printing - Call for > financing > Hi all, > > I am discussing with Oslandia (the authors of the Atlas plugin for=20 > serial printing) an option to include Atlas into QGIS core. > > Currently it is a python plugin, the idea would be to port it to C++=20 > and include it with QGIS by default. It would also be an opportunity to=20 > fix several bugs and maybe feature requests. > > To see what it does: > see > http://www.oslandia.com/tech/?p=3D1079 > and > http://hub.qgis.org/projects/atlas > and > http://plugins.qgis.org/plugins/atlas/ > > Oslandia made me an offer/estimate on how much the C++ port and fixing=20 > of some bugs would cost. We can only finance parts of it. If one or two=20 > others are joining we could probably do it. If not, we will just go with= > =20 > some bug fixing in the Python plugin. > > Please contact me offlist if you are interested in this functionality=20 > and are able to contribute financially. > > Andreas > > > --=20 > -- > Andreas Neumann > B=C3=B6schacherstrasse 10A > 8624 Gr=C3=BCt (Gossau ZH) > Switzerland > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ > Qgis-user mailing list > qgis-u...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] valuetool crashes qgis
Il 28/06/2012 08:38, Vincent Schut ha scritto: > Hi, > > is it just me, or is the valuetool plugin crashing qgis (current git build) > when > loading the plugin? I had the same problem, and it turned out being a packaging problem (different pyqt versions). recompiling solved it. All the best. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] valuetool crashes qgis
OK, so I tried to recompile qgis from an emptied build dir, but ccmake gives me this error while configuring: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: PYTHON_LIBRARY linked by target "qgispython" in directory /usr/local/src/qgis/src/python linked by target "python_module_qgis_analysis" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_core" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_gui" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_networkanalysis" in directory /usr/local/src/qgis/python could that have anything to do with it? Qgis used to build fine, and I definitely have python and pyqt installed. Or is this just because I have both python2.7 and python3.2 installed? btw, the source folder was updated from git just yesterday. best, Vincent. On 06/28/2012 10:51 AM, Paolo Cavallini wrote: Il 28/06/2012 08:38, Vincent Schut ha scritto: Hi, is it just me, or is the valuetool plugin crashing qgis (current git build) when loading the plugin? I had the same problem, and it turned out being a packaging problem (different pyqt versions). recompiling solved it. All the best. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] valuetool crashes qgis
sorry to reply-to-self... update: I set cmake PYTHON_EXECUTABLE to /usr/bin/python2, and PYTHON_LIBRARY to /usr/lib/libpython2.7.so, as said in http://hub.qgis.org/issues/5069 (this is also on arch linux). qgis builds fine. however, when I try to install the valuetool plugin, it still crashes with a segmentation fault. best, Vincent. On 06/28/2012 11:56 AM, Vincent Schut wrote: OK, so I tried to recompile qgis from an emptied build dir, but ccmake gives me this error while configuring: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: PYTHON_LIBRARY linked by target "qgispython" in directory /usr/local/src/qgis/src/python linked by target "python_module_qgis_analysis" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_core" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_gui" in directory /usr/local/src/qgis/python linked by target "python_module_qgis_networkanalysis" in directory /usr/local/src/qgis/python could that have anything to do with it? Qgis used to build fine, and I definitely have python and pyqt installed. Or is this just because I have both python2.7 and python3.2 installed? btw, the source folder was updated from git just yesterday. best, Vincent. On 06/28/2012 10:51 AM, Paolo Cavallini wrote: Il 28/06/2012 08:38, Vincent Schut ha scritto: Hi, is it just me, or is the valuetool plugin crashing qgis (current git build) when loading the plugin? I had the same problem, and it turned out being a packaging problem (different pyqt versions). recompiling solved it. All the best. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] valuetool crashes qgis
Il 28/06/2012 12:15, Vincent Schut ha scritto: > however, when I try to install the valuetool plugin, it still crashes with a > segmentation fault. backtrace? thanks. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] valuetool crashes qgis
the gdb backtrace: Program received signal SIGSEGV, Segmentation fault. 0x725f949e in QPen::operator=(QPen const&) () from /usr/lib/libQtGui.so.4 (gdb) bt #0 0x725f949e in QPen::operator=(QPen const&) () from /usr/lib/libQtGui.so.4 #1 0x7fffbbda16f8 in QwtSymbol::clone() const () from /usr/lib/libqwt.so.1 #2 0x7fffd01438b8 in ?? () from /usr/lib/python2.7/site-packages/PyQt4/Qwt5/Qwt.so #3 0x7fffbbdabdaa in QwtPlotCurve::setSymbol(QwtSymbol const&) () from /usr/lib/libqwt.so.1 #4 0x7fffd017ed1e in ?? () from /usr/lib/python2.7/site-packages/PyQt4/Qwt5/Qwt.so #5 0x7fffdefe402a in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #6 0x7fffdefe4eb5 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #7 0x7fffdef75526 in function_call () from /usr/lib/libpython2.7.so.1.0 #8 0x7fffdef5188e in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #9 0x7fffdef5fe68 in instancemethod_call () from /usr/lib/libpython2.7.so.1.0 #10 0x7fffdef5188e in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #11 0x7fffdefa4582 in slot_tp_init () from /usr/lib/libpython2.7.so.1.0 #12 0x7fffdefa421c in type_call () from /usr/lib/libpython2.7.so.1.0 #13 0x7fffdef5188e in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #14 0x7fffdefe0b39 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #15 0x7fffdefe3a53 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #16 0x7fffdefe3a53 in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #17 0x7fffdefe4eb5 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #18 0x7fffdefe312c in PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0 #19 0x7fffdefe4eb5 in PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0 #20 0x7fffdef75526 in function_call () from /usr/lib/libpython2.7.so.1.0 #21 0x7fffdef5188e in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #22 0x7fffdef5fe68 in instancemethod_call () from /usr/lib/libpython2.7.so.1.0 #23 0x7fffdef5188e in PyObject_Call () from /usr/lib/libpython2.7.so.1.0 #24 0x7fffdefde547 in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.7.so.1.0 #25 0x7fffdeafbcf0 in ?? () from /usr/lib/python2.7/site-packages/sip.so #26 0x7fffde820936 in ?? () from /usr/lib/python2.7/site-packages/PyQt4/QtCore.so #27 0x7fffde820c58 in ?? () from /usr/lib/python2.7/site-packages/PyQt4/QtCore.so #28 0x7fffde820d32 in ?? () from /usr/lib/python2.7/site-packages/PyQt4/QtCore.so #29 0x730e4f93 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #30 0x72ae62c2 in QAbstractButton::clicked(bool) () from /usr/lib/libQtGui.so.4 #31 0x7283a22e in ?? () from /usr/lib/libQtGui.so.4 #32 0x7283aa60 in ?? () from /usr/lib/libQtGui.so.4 #33 0x7283accc in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #34 0x7fffde1c44d3 in ?? () from /usr/lib/python2.7/site-packages/PyQt4/QtGui.so #35 0x724d0690 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #36 0x7fffde1c49fb in ?? () from /usr/lib/python2.7/site-packages/PyQt4/QtGui.so #37 0x72480f7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #38 0x72485c5b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #39 0x747b11ae in QgsApplication::notify (this=0x7fffd6b0, receiver=0x3192450, event=0x7fffc9f0) at /usr/local/src/qgis/src/core/qgsapplication.cpp:222 #40 0x730cf8ee in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #41 0x72481dbb in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/libQtGui.so.4 #42 0x724fc804 in ?? () from /usr/lib/libQtGui.so.4 #43 0x724fb591 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #44 0x72521682 in ?? () from /usr/lib/libQtGui.so.4 #45 0x7fffef0d44a5 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #46 0x7fffef0d47d8 in ?? () from /usr/lib/libglib-2.0.so.0 #47 0x7fffef0d4894 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #48 0x730fdae6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #49 0x725212fe in ?? () from /usr/lib/libQtGui.so.4 #50 0x730ce63f in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #51 0x730ce8c8 in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #52 0x730d3568 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #53 0x0053b2f3 in main (argc=1, argv=0x7fffdf58) at /usr/local/src/qgis/src/app/main.cpp:798 I hope this is helpful. I did compile qgis in debug mode, but I think all my (py)qt stuf
[Qgis-developer] Interoperabtility of the SLD import/export
Hi, I will soon attend a workshop discussing the establishment of symbology interchange between different GIS. Our idea is to suggest SLD with FE and SE. My question is if anyone has experience with the interoperability between the QGIS exported SLD and other software like UMN Mapserver or Geoserver or even some commercial GIS. Does it work interchangeably? Thanks for sharing your experiences, Andreas -- -- Andreas Neumann Böschacherstrasse 10A 8624 Grüt (Gossau ZH) Switzerland ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Interoperabtility of the SLD import/export
> My question is if anyone has experience with the interoperability > between the QGIS exported SLD and other software like UMN Mapserver or > Geoserver or even some commercial GIS. Does it work interchangeably? Hi Andreas, my only experience until now is just about a few shapefiles I have downloaded and that were provided with a SLD symbology file. I don't know how that SLD files were created but they worked just fine under QGIS. Cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] vectorlayer new edit type: multi attribute
Hi all,
As I was very demanding these last 2 days, you probably know I was
trying to add a new edit type for vector layers.
Suppose you have a table of options, and you can now select from 0 to n
of this options in a field.
Maybe with an image, it's clearer:
http://postimage.org/image/43fu7kdbn/
I think my code is ok, it is available here
https://github.com/3nids/Quantum-GIS and I made a pull request
https://github.com/qgis/Quantum-GIS/pull/189.
However, due to my poor knowledge of QGIS and cpp, there's a few things
I'm not sure:
1. I do not check the type of the field. Basically it should be either
integer[] or string. My code is writing the field as a string :
'{optionid_a,optionid_b,etc}'
as explained here
http://www.postgresql.org/docs/9.1/static/arrays.html#ARRAYS-INPUT
I don't know if we're supposed to let the user check this or if I should
code this.
2. There is a few lines I copied from the valuerelation edit type
without understanding what it actually does...
https://github.com/3nids/Quantum-GIS/blob/master/src/core/qgsvectorlayer.cpp#L5736
Jurgen just fixed something in this one. I don't get what it's doing.
3. There is some redundancy in the code which updates the columns.
https://github.com/3nids/Quantum-GIS/blob/master/src/app/qgsattributetypedialog.cpp#L57
and
https://github.com/3nids/Quantum-GIS/blob/master/src/app/qgsattributetypedialog.cpp#L680
But, there might be something to be done with signal mapping but that's
beyond my competences. I tried this once in python with no success.
4. More on the postgres side, there is something annoying: apparently
the foreign key is not working: you can delete an option even if it's
used in some features.
Please let me know what you think. Fill free to give me advice on coding
as I am beginner.
Happy testing,
Denis
PS: a small sample set in postgis
CREATE SCHEMA test;
CREATE TABLE test.attributes (id serial NOT NULL);
ALTER TABLE test.attributes ADD COLUMN value varchar(30);
INSERT INTO test.attributes (value) VALUES ('Option 1');
INSERT INTO test.attributes (value) VALUES ('Option 2');
INSERT INTO test.attributes (value) VALUES ('Option 3');
CREATE TABLE test.elements (id serial NOT NULL);
ALTER TABLE test.elements ADD COLUMN options integer[];
SELECT addGeometryColumn('test', 'elements', 'geometry', 21781,
'LINESTRING', 2);
ALTER TABLE test.elements ADD CONSTRAINT options FOREIGN KEY (options)
REFERENCES test.attributes (id) MATCH SIMPLE ;
CREATE INDEX fki_options ON test.elements(options);
INSERT INTO test.elements (options,geometry) VALUES
('{2}',ST_SetSRID(ST_GeomFromText('LINESTRING(555769.76481482
146263.03710034,555751.6995361 146245.46089015,555750.68004915
146244.50211359,555750.35404773 146244.19191515)'),21781));
INSERT INTO test.elements (options,geometry) VALUES
('{1,2,3}',ST_SetSRID(ST_GeomFromText('LINESTRING(555724.04334769
146230.95112375,555727.6687899 146229.26762754,555729.32827011
146227.68620818,555730.09424706 146226.4618166)'),21781));
INSERT INTO test.elements (options,geometry) VALUES
('{}',ST_SetSRID(ST_GeomFromText('LINESTRING(555713.21267068
146274.95065018,555712.43922982 146274.29916376)'),21781));
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] vectorlayer new edit type: multi attribute
Hi Denis, On Thu, 28. Jun 2012 at 18:31:34 +0200, Denis Rouzaud wrote: > As I was very demanding these last 2 days, you probably know I was trying > to add a new edit type for vector layers. Nice work. Thanks for the contribution. I took the liberty to commit the stuff with some modifications. Instead of adding the MultipleAttribute struct I just added a "multiple selection" flag to the value relations. This removes all of the duplication involved and also enables the "order by value" option for the list. I also updated the SIP bindings and ran the code to scripts/prepare-commit.sh. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de committ(ed|ing) to Quantum GIS IRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] vectorlayer new edit type: multi attribute
Indeed this sounds like a useful datatype. I am sure I will have some use for it. I already found a project I can improve with this new data type. Thanks to both Denis and Jürgen! Andreas Am 28.06.2012 20:54, schrieb Jürgen E. Fischer: > Hi Denis, > > On Thu, 28. Jun 2012 at 18:31:34 +0200, Denis Rouzaud wrote: >> As I was very demanding these last 2 days, you probably know I was trying >> to add a new edit type for vector layers. > > Nice work. Thanks for the contribution. > > I took the liberty to commit the stuff with some modifications. > > Instead of adding the MultipleAttribute struct I just added a "multiple > selection" flag to the value relations. This removes all of the duplication > involved and also enables the "order by value" option for the list. > > I also updated the SIP bindings and ran the code to scripts/prepare-commit.sh. > > > > Jürgen > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] vectorlayer new edit type: multi attribute
Sounds great to me! Thanks a lot, Denis On 06/28/2012 08:54 PM, Jürgen E. Fischer wrote: Hi Denis, On Thu, 28. Jun 2012 at 18:31:34 +0200, Denis Rouzaud wrote: As I was very demanding these last 2 days, you probably know I was trying to add a new edit type for vector layers. Nice work. Thanks for the contribution. I took the liberty to commit the stuff with some modifications. Instead of adding the MultipleAttribute struct I just added a "multiple selection" flag to the value relations. This removes all of the duplication involved and also enables the "order by value" option for the list. I also updated the SIP bindings and ran the code to scripts/prepare-commit.sh. Jürgen ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
