[Qgis-user] Bugs, release of 1.7 and release of 1.7 as beta

[Andreas Neumann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi again,

> After putting a certain amount of objects in a project, print composer
> would lockup. I don't recall exactly how many objects were in the

lockup during composing or during printing? or during export?


> project before it ceased to function but I ended up with about 45,000
> objects in the .svg file. Specifically, when it came time to print or to

The export to SVG and PDF is certainly an area that needs improvements.
But these have to be done in the qt libraries.

> export to file, it would lock up, crash really, with error message. The
> other thing was the way it handles polylines. I was trying to make
> highway polylines render correctly but there was a difference between
> what was seen on screen and what was actually printed. The polyline

this is a known issue. The preview in the print composer is not WYSYWIG.
The extent and scale is correct, but the dpi is not. I believe this is
already in the pipeline and we have a sponsor to improve it so we can
have WYSYWIG preview regarding line widths, font-sizes, etc.


> widths on screen were scaled too large compared to what I was actually
> trying to do. When printed I noticed they printed correctly. Getting the
> endpoints and intersections of two polylines to merge correctly didn't
> work either. I was trying to represent complex interchanges at the
> intersection of two highways with on-ramps etc. Couldn't do it. Polyline

This is probably more a symbology issue than a print composer issue? I
am not sure I fully understand your problem.

> patterns are clumsy and difficult to set to useful patterns. Setting a

Do you mean the SVG patterns? The SVG patterns could be exported from
Inkscape. I am pretty sure there are pattern libraries in a PDF/EPS
compatible format which could be converted to SVG. Also ttf-fonts with
patterns could be converted to SVG. One issue with SVG is that you can't
easily override colors without copying the pattern definition. This
problem will be dealt with in the medium future.


> scale is difficult. Maybe a wizard would help setting scale. Labeling is

perhaps this could be solved when the WYSYWIG printing is available?

> an issue. With tens of thousands of objects producing a clearly labeled
> print becomes a problem. It was tough even in Inkscape. Sometimes labels

did you try the new label engine where you can mix automated labeling
with manual labeling? Should make your live easier. It is also a
question whether you define your labels for a certain scale (with
font-sizes as map units) or with fixed font-sizes regardless of the zoom
factor.


> had to broken down into objects and each letter manipulated manually to
> make them appear in a readable fashion. I never really did figure out

letterspacing is perhaps something that is missing currently.


> the labeling to my satisfaction but in the end just went with what I
> had, compromising just to get something out the door. The biggest
> problem though was print composer locking up while printing after I had
> all my coverages turned on. Perhaps a memory issue? I had 4gb of ram,
> not enough? I have bigger projects in mind and I'm not sure even
> Inkscape will be able to handle what I want to do.

Inkscape certainly has its limits - after all it is not a GIS or
cartographic software. GIS on the other hand should be able to deal with
larger data sets. If it can't, it is a bug and should be resolved. Can
you make your data sets/projects available to Marco Hugentobler or
others for testing?

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN7nScAAoJELiCsGDopvBC9AEH/3zPh1FmAvNP6IaxVOWSgZgd
5CyMt5vfSTaVlaZ+AMgJiQPFVAmXjNte5Z+tyuEBm++QHBE7usSDDTtrvhJKhJA7
X6hayg3c6h5XoydtqCy71XMpL/olA2ecvzESDbp1PLw4Onpri20u1jjOaWLtC/PH
wbxl7o04K1KtTP4S1C51r/6KEiyParOwQKZXS9d0YKXWCKsQvCVZQiHkNpCMLsSl
hOLF5JaLLARozD0iYHYiIiEwJDJBQWTZlqA/S4QFJfCIawpCUbVysV+LKn2CZCcw
7TCKYNeVi4rBeQyAQsGOYyQ8ch0Z71Q7sZ9EG86NT4mqzRfYKO2RAZi90ZQJYO0=
=rlTk
-----END PGP SIGNATURE-----