Hello,
I've been working with gvSIG's georeferencing module lately, and I have to say that it rocks ! It allows you to see where you put your GCP's not only on the image to reference, but also on your base map and you can zoom into the points and move them around as needed in both maps. This allows for very precise georeferencing. You can also place and resize your image as you want in the same canvas as the reference map. Etc...
It would be great to have something like this in GRASS if it is in any way feasible. So, maybe an inspiration for someone who has the time and feels inspired. Or for next years Google Summer of Code ?
Moritz
On 23/05/08 15:47, Markus Neteler wrote:
Hi Moritz,
could you post some (links to) screenshots?
http://geog-pc40.ulb.ac.be/grass/misc/georef_gvSIG.pdf
This is an extract of the gvSIG user manual with the chapter on the georeferencer. It contains screenshots + explanations.
Moritz
Markus
On Fri, May 23, 2008 at 2:06 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
Hello,
I've been working with gvSIG's georeferencing module lately, and I have to
say that it rocks ! It allows you to see where you put your GCP's not only
on the image to reference, but also on your base map and you can zoom into
the points and move them around as needed in both maps. This allows for very
precise georeferencing. You can also place and resize your image as you want
in the same canvas as the reference map. Etc...
It would be great to have something like this in GRASS if it is in any way
feasible. So, maybe an inspiration for someone who has the time and feels
inspired. Or for next years Google Summer of Code ?
Moritz
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Moritz:
>> I've been working with gvSIG's
>> georeferencing module lately, and I have to
>> say that it rocks ! It allows you to see where you
put your GCP's not only
>> on the image to reference, but also on your base
map and you can zoom into
>> the points and move them around as needed in both
maps. This allows for very
>> precise georeferencing. You can also place and
resize your image as you want
>> in the same canvas as the reference map. Etc...
>>
>> It would be great to have something like this in
GRASS if it is in any way
>> feasible. So, maybe an inspiration for someone who
has the time and feels
>> inspired. Or for next years Google Summer of Code
?
> could you post some (links to) screenshots?
http://geog-pc40.ulb.ac.be/grass/misc/georef_gvSIG.pdf
This is an extract of the gvSIG user manual with the
chapter on the
georeferencer. It contains screenshots + explanations.
[sorry about the linewraps, broken yahoo webapp..]
see also i.vpoints for neat features like click-a-point on source and target left/right panel images, and test reverse-projection of vector layers from target location over source image.
I would be nice to have the "auto" and "3d" i.points updated+moved from grass5 incoming / contrib code into grass6 addons, or at least well summarized for grass5 on a wiki page or so. the idea is to have a full plate of good ideas with demonstration code available while building the new wxGUI georeferencing app, thus a stronger roadmap of where we want it to go and what features to include.
Hamish
On Sat, May 24, 2008 at 4:46 AM, Hamish <hamish_b@yahoo.com> wrote:
...
I would be nice to have the "auto" and "3d" i.points updated+moved from grass5 incoming / contrib code into
grass6 addons, or at least well summarized for grass5 on a wiki page or so. the idea is to have a full plate of
good ideas with demonstration code available while building the new wxGUI georeferencing app, thus a
stronger roadmap of where we want it to go and what features to include.
Hamish,
which code do you mean? We have there grassaddons/imagery/i.points.auto.
The draft imagery roadmap is (see TODO file in main - should go into the Wiki):
TODO Image libraries:
A)
- lib/imagery/: standard lib, in use (i.* except for i.points3, i.rectify3)
- imagery/i.ortho.photo/libes/: standard lib, in use
(i.ortho.photo, photo.*)
B)
- lib/image3/: never finished improvement which integrated the
standard lib and
the ortho lib. Seems to provide also ortho rectification for
satellite data (i.points3, i.rectify3)
TODO Image modules:
- merge of i.points, i.vpoints, i.points3
- merge of i.rectify and i.rectify3
- addition of new resampling algorithms such as bilinear, cubic convolution
(take from r.proj?)
- add other warping methods (maybe thin splines from GDAL?)
- implement/finish linewise ortho-rectification of satellite data
- Add support for > 8bit colors (only 0-255 supported currently)
Markus
Markus:
which code do you mean? We have there
grassaddons/imagery/i.points.auto.
oh, right. it's already on the table.
The draft imagery roadmap is (see TODO file in main -
should go into the Wiki):
TODO Image libraries:
A)
- lib/imagery/: standard lib, in use (i.* except for
i.points3, i.rectify3)
- imagery/i.ortho.photo/libes/: standard lib, in use
(i.ortho.photo, photo.*)
B)
- lib/image3/: never finished improvement which
integrated the standard lib and
the ortho lib. Seems to provide also
ortho rectification for satellite data (i.points3, i.rectify3)
TODO Image modules:
- merge of i.points, i.vpoints, i.points3
- merge of i.rectify and i.rectify3
- addition of new resampling algorithms such as
bilinear, cubic convolution
(take from r.proj?)
- add other warping methods (maybe thin splines from
GDAL?)
- implement/finish linewise ortho-rectification of
satellite data
- Add support for > 8bit colors (only 0-255
supported currently)
my main point was to raise the awareness that we have all this neat rectification code sitting in the corners which can be drawn upon when it comes to improving the new wxGUI tool. The more we can learn from gvSIG, QGIS, gdal_translate+gdalwarp, and old i.*points*, i.ortho.photo ideas+code while still in the design phase, the better the end result will be. Even if we don't implement it all at once.
meta,
Hamish