Ok, this is somehow what I did. With QChainage plugin, no need to create
new fields and csv table. It directly creates the point geometry layer
corresponding to xat(0)/yat(0) and xat(-1)/yat(-1) with $id field, when
well setting.
I also assume that what I was trying to do directly within the line
Il 15/01/2015 15:59, Sandro Santilli ha scritto:
Leftover issues (open for funding):
- Plugin layers (#11900) -- needs feedback
- Overview map (#11862) -- minor, IMHO
- Composer support (#11912) -- wish ?
- Atlas doesn't consider map rotation when setting scale (#11954)
IMHO none of
I've spent more time on rotation (only partially funded), fixing:
- Label pre-rotation (#11814)
- North Arrow Decoration (#11818)
- Grid decoration (#11817)
Leftover issues (open for funding):
- Plugin layers (#11900) -- needs feedback
- Overview map (#11862) -- minor, IMHO
- Composer
Enviado desde mi iPhone r
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Enviado desde mi iPhone r
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Sandro, Nyall,
Discussing this with Martin earlier today, he came up with a test patch to
see what would happen if the code was blindly modified to use
QgsMapSettings' setRotation() function. The result is interesting, it
actually _mostly_ works (see attached patch):
- before the patch, rotating
On 16 Jan 2015 2:00 am, Sandro Santilli s...@keybit.net wrote:
- Atlas doesn't consider map rotation when setting scale (#11954)
Don't worry about this one - it's been around as long as atlas has existed
and wasn't introduced by your work. I plan on tackling it as part of the
layout refactor
Sandro,
The last few weeks has been a nice leap forward when it comes to your
rotation feature, congratulation on that.
IMO, based on the improvements, it's worth considering _removing the
activation option altogether_ from the preference window. I can't see
any stability and usability issue
Hi all,
I have two shapefiles : a line one (called section) and a point one
(called station) shapefiles.
The line shapefiles has fields like ID_section, ID_first, ID_last
The point file has an ID_station.
All these define a kind of network where a section begins on a station and
ends up at
Thanks Enrico for your reply and for the plugin.
I was aware of RefFunctions and has already used it for relational
questions. And I agree with Jean that such functions (and others of your
plugins) might be core functions. I've moreover reported a feature request
to improve usability of all this
10 matches
Mail list logo