I've just discovered the photo modules and have looked at them briefly. If
I understand correctly, the set of modules is designed to use information
from the plane and camera to compute the affine transformation.
What I do not see in this module set is a way to use GPS-collected
reference points for the orthorectification. Can this be done? If so, please
point me to the right modules for this.
In our current system, we identify point common to the photograph and the
ground, then collect a position reading there. The software permits us to
mark that point on the scanned aerial photograph image and uses the set of
points to compute the affine transformation.
Many of the photographs which are available to us are either historic or
provided by resource/regulatory agencies. I don't even know if airplane
orientation and camera details could even be made available for these.
Thanks,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
Hello,
I have compiled Grass 5b3 on an alpha with
digital unix. The compilation has been a little difficult
and took me a whole day, editing the scripts and the
code in many points.
If developers are interested I can send the complete
log of changes I made. The most relevant, al least I
think, is that I had to delete in many places the prototype
of the free() call due to the complaints of the gcc
compiler about the redefinition.
Also I have neither ncurses, nor root privileges to install
them so I simply used curses, but this shouldn't be
a big problem, at least not related with what follows.
Ok, finaly I got it. I have then imported a Location of
data I was working with under i586 Linux.
No problem with raster files, But when i go working
with vector files strange things happen:
For example running v.support on a vector file I get
SYSTEM_ERROR: OLD_T_NEW Got a bad type code ffffff9c
OUT OF MEMORY!
SYSTEM_ERROR: OLD_T_NEW Got a bad type code ffffff9c
OUT OF MEMORY!
Read_line: Out of Memory
Could not build support (dig_plus) file.
If i run d.vect on the same file:
Initializing [ds] ... Vector format version (4.706) is not known by this
release. EXITING
Try running v.support to reformat the dig_plus file
It seems like if GRASS does not recognize anymore the
vector files build under linux.
any suggestion ?
LP
--> Luca Palmeri - Dip. Proc. Chimici dell'Ingengeria
Universita' di Padova TEL: +390498275527 -------
------------------------- FAX: +390498275528 -------
--> Think holistic @ the end of the 2nd millenium <--
On Sun, 17 Oct 1999, Luca Palmeri wrote:
Hello,
I have compiled Grass 5b3 on an alpha with
digital unix. The compilation has been a little difficult
and took me a whole day, editing the scripts and the
code in many points.
If developers are interested I can send the complete
log of changes I made. The most relevant, al least I
think, is that I had to delete in many places the prototype
of the free() call due to the complaints of the gcc
compiler about the redefinition.
Yes! I suggest to contact Bill Hughes on that as he
is owning/using an ALPHA machine.
No problem with raster files, But when i go working
with vector files strange things happen:
Initializing [ds] ... Vector format version (4.706) is not known by this
release. EXITING
Try running v.support to reformat the dig_plus file
It seems like if GRASS does not recognize anymore the
vector files build under linux.
any suggestion ?
Sorry for this! It is already *fixed* for the next GRASS 5beta4 to
come very soon. To fix this:
- src/mapdev/diglib/portable.h
3c3
< #define LNG_SIZ 8
---
> #define LNG_SIZ 4
The value of LNG_SIZ in portable.h was OK for 64-bits OS but not for
Linux/Intel. This prevented *many* vector programs to work (e.g.
d.vect).
Many more fixes we could already apply but before publishing this
version a few things shall be finished.
The next GRASS 5 version will be *much* better, I am shure.
Best regards
Markus Neteler
All this problems have stopped my from trying GRASS5.0b3
on DU (or OSF1 ). 
On the 19. November is GIS day, as many of you know.
I will probably run GRASS on a computer as demonstration here at
the University Wisconsin Milwaukee.
1. Has anybody really nice graphical examples or research work
I could actually run to show GRASS' power?
2. Is the source code in CVS for GRASS 5.0b4? Can I get access
(read I mean) to the latest version.
On Sun, Oct 17, 1999 at 07:51:22PM +0100, Markus Neteler wrote:
> I have compiled Grass 5b3 on an alpha with
> digital unix. The compilation has been a little difficult
> and took me a whole day, editing the scripts and the
> code in many points.
> If developers are interested I can send the complete
> log of changes I made.
But it on the web as fast as possible.
Many more fixes we could already apply but before publishing this
version a few things shall be finished.
The next GRASS 5 version will be *much* better, I am shure.
To Bill and Markus:
It almost looks to me as the PVF has to be recoded using the
XDR (External Data Representation) RFC1832
(e.g. at http://www.cis.ohio-state.edu/htbin/rfc/rfc1832.html)
http://www.acc.umu.se/~balp/rpcunix/xdrtechnotes.HTML
Bernhard
--
Research Assistant, Geog Dept UM-Milwaukee, USA. (www.uwm.edu/~bernhard)
Association for a Free Informational Infrastructure (ffii.org)
Intevation GmbH