[Qgis-developer] georeferencer projective transformation in 2.14

Fri May 20 23:04:14 PDT 2016

Sorry – it was late night… The Helmert works fine ☺

Lene Fischer
Associate Professor

Department of Geosciences and Natural Resource Management
University of Copenhagen

MOB +45 40115084
lfi at ign.ku.dk<mailto:lfi at ign.ku.dk>

[cid:image001.gif at 01D03029.2F3EC6A0]

Fra: Qgis-developer [mailto:qgis-developer-bounces at lists.osgeo.org] På vegne af Lene Fischer
Sendt: 21. maj 2016 01:00
Til: Andreas Neumann; qgis-developer at lists.osgeo.org
Emne: Re: [Qgis-developer] georeferencer projective transformation in 2.14

Hi Andreas,
I have always used the projective… and didn´t try out the others…
The Linear gives in my project a huge error too, but the Linear works fine
Thanks!!!

Lene Fischer
Associate Professor

Department of Geosciences and Natural Resource Management
University of Copenhagen

MOB +45 40115084
lfi at ign.ku.dk<mailto:lfi at ign.ku.dk>

[cid:image001.gif at 01D03029.2F3EC6A0]

Fra: Qgis-developer [mailto:qgis-developer-bounces at lists.osgeo.org] På vegne af Andreas Neumann
Sendt: 19. maj 2016 07:18
Til: qgis-developer at lists.osgeo.org<mailto:qgis-developer at lists.osgeo.org>
Emne: Re: [Qgis-developer] georeferencer projective transformation in 2.14

Hi Lene,

While I acknowledge that this is a bug and should be fixed - why do you have to use the projective method and not any of the other ones? In fact I never used the projective one, but either linear or helmert for raster content that is not distorted within the image or thin plate spline for raster content that needs a lot of control points and needs a lot of local adjusting.

What is the specific reason to use "projective" as opposed to the other methods?

Why the target was moved to 2.16 I don't know. 2.14 is a LT release and I think/hope that there will be several updates to 2.14 in the future. Or maybe it was meant that it will be fixed in 2.16 and then backported ...

Greetings,
Andreas
On 19.05.2016 03:57, Lene Fischer wrote:
Hi
Since 2.14 it has not been possible to georeferencing an image.
There are a bugreport on the issue http://hub.qgis.org/issues/14551 with a priority: Blocker.
There is a comment •  Target version changed from Version 2.14 to Version 2.16
What does that mean?
Regards

Lene Fischer
Associate Professor

Department of Geosciences and Natural Resource Management
University of Copenhagen

MOB +45 40115084
lfi at ign.ku.dk<mailto:lfi at ign.ku.dk>

[cid:image001.gif at 01D03029.2F3EC6A0]

Fra: Qgis-developer [mailto:qgis-developer-bounces at lists.osgeo.org] På vegne af Tim Sutton
Sendt: 18. maj 2016 20:55
Til: Junior Delaz
Cc: qgis-community; QGIS Developer Mailing List
Emne: Re: [Qgis-developer] [Qgis-community-team] Moving the install instructions to a more sexy, visible, coherent and translatable page in qgis.org

Hi

On 18 May 2016, at 12:49, DelazJ <delazj at gmail.com<mailto:delazj at gmail.com>> wrote:

Hi,

2016-05-18 8:24 GMT+02:00 Tim Sutton <tim at kartoza.com<mailto:tim at kartoza.com>>:
Hi

After rereading the thread I think I am +1 for moving to RST in the QGIS Docs repo with the following thinking:

Is the Doc repo a better candidate for this (if we get the go!) than QGIS website?

Sorry yes, you are correct, the Web site is the better place.

Regards

Tim

* QGIS Website is always translatable, so can easily show the most recent procedure in different languages. It also provides a chapter on development steps, might be worth having this beside.
* Using website, we have a unique hyperlink (to use in our communication if needed) instead of having to update it after each released doc
* testing doc (which in the ideal world, is related to master) is not to be translated
* not all QGIS versions are/will be documented: the last doc provided is 2.8. The next should be 2.14 (btw, still looking for volunteers to write it - around 80 issues remaining and not the least) but when will be the release?

* all the good stuff Junior mentioned like translatability, visibility etc.
* when we hit release freeze we could copy the latest output from sphinx (maybe generated as plain text file?) to INSTALL.txt and remove the sources for the install docs from the QGIS code tree. That way the QGIS sources always contain the current notes for that release and the doc sources contain only the most recent procedure.
* we could add a note in the docs sources saying ‘these instructions are for the current state of the develop branch only, for version specific install procedures, please see the INSTALL.txt in the source tree for that release’

+1 though the copy would be from the website repo (as suggested above)

I think that workflow is not too much different from the current system. Of course someone needs to volunteer to get all the processes above into place :-P

I'd RSTed the install doc and opened a pull request at https://github.com/qgis/QGIS-Website/pull/343/files. Might need correction. It's the content on April 15th. Don't however know the steps to keep this up to date nor automate some changes (like date of doc).
Regards,
Harrissou

2016-05-18 8:49 GMT+02:00 Jürgen E. <jef at norbit.de<mailto:jef at norbit.de>>:
Hi Tim,

On Wed, 18. May 2016 at 08:24:05 +0200, Tim Sutton wrote:
> @Jürgen regarding your comments below, I used to use apt-get build-dep too
> but I actually like the explicit package list your script generates more in
> some ways because it is deterministic compared to build-dep which will only
> reflect the deps from the current latest package in apt sources.

The dependencies of the latest automatic nightly are probably more up-to-date
than the list from the latest manual INSTALL update run.

Jürgen

--
Jürgen E. Fischer           norBIT GmbH             Tel. +49-4931-918175-31<tel:%2B49-4931-918175-31>
Dipl.-Inf. (FH)             Rheinstraße 13          Fax. +49-4931-918175-50<tel:%2B49-4931-918175-50>
Software Engineer           D-26506 Norden             http://www.norbit.de
QGIS release manager (PSC)  Germany                    IRC: jef on FreeNode

_______________________________________________
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
Qgis-community-team at lists.osgeo.org<mailto:Qgis-community-team at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

_______________________________________________
Qgis-developer mailing list
Qgis-developer at lists.osgeo.org<mailto:Qgis-developer at lists.osgeo.org>
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[cid:image002.jpg at 01D1B337.5A86C550]

---

Tim Sutton
QGIS Project Steering Committee Chair
tim at qgis.org<mailto:tim at qgis.org>

_______________________________________________

Qgis-developer mailing list

Qgis-developer at lists.osgeo.org<mailto:Qgis-developer at lists.osgeo.org>

List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160521/8ccbf4a6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 4863 bytes
Desc: image001.gif
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160521/8ccbf4a6/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4642 bytes
Desc: image002.jpg
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160521/8ccbf4a6/attachment-0001.jpg>