Maptitude - http://research.umbc.edu/~roswell/maptitude.html
Armando,
I would wait until Mapt. 4.5 comes out in a month or so
and then upgrade. 4.5 is going to solve a lot of problems.
You can have 2nd copy; first is mine.
Later
Carl L. Chance
GIS Manager
City of Lake Charles
At 03:18 PM 1/16/01 +0000, you wrote:
>Maptitude - http://research.umbc.edu/~roswell/maptitude.html
>
>Dear Mike,
>
>I was caught by the description of your work. I did some oblique photos of
>shorelines long time ago in Ireland and I am about to embark in a similar
work
>this year in Argentina.
>
>I would very much appreciate if you could provide more detail on the type of
>hardware you are using (photo camera, GPS, etc) and the software you are using
>for keeping photos and positional information linked during the flight.
>
>Also, while going through the description of your work I have noticed that you
>are using the standard maptitude interface. You could do some of those tasks
>faster with a little programming with GIDSK. The map editing needed to locate
>the photo on the coast is a simple macro and can work well for you
>
>Cheers,
>
>Armando Scalise
>GeoMatic
>Argentina
>
>
>Mike Baum wrote:
>
>> Maptitude - http://research.umbc.edu/~roswell/maptitude.html
>>
>> Thanks Larry, Here's what I wrote to Simon at Caliper earlier today:
>>
>> Here's my project. I take aerial photos of the shoreline in Washington
>> state. My digital camera stores the lat and long with each file. I then
>> extract that information and build a database with a record for each photo
>> and a field for lat and long. One mapping aspect involves the fact that
>> where the plane is located at exposure isn't the location of the subject.
>> These are oblique photos. So I need to move all the photos to the shoreline.
>> I use the map editing function for this. The other major chore is locating
>> photos which didn't include geodata. I use "locate by pointing" for this.
>> Works well. Tedious.
>>
>> File management seems to be my biggest challenge. When I try to use ODBC
>> with Excel I get error messages about invalid field arrays when I try to
>> locate by coordinate. (import,1729,0) I haven't been successful at all using
>> ODBC with Access.
>>
>> (Simon replied that the Excel ODBC solution may have to wait till 4.5 which
>> they hope to release this spring. That release might not be official so
>> don't tell anyone else.)
>>
>> My workaround has been to create a master file in Excel, save it as a .dbf,
>> open it in Maptitude, mapt builds a .dbd file, I edit, then save as a .dbf
>> file then cut and paste back to my master file. It actually works fairly
>> well. I do have memory problems after I work awhile. Windows isn't letting
>> go of memory and I need to reboot. I've got 128mb RAM. But in addition to
>> Mapt I'm also running my photo management software. It's a memory pig also.
>> <end quote>
>>
>> Today's little hitch was after I located two counties worth of photos I
>> discovered that when I made a selection set for the county that it didn't
>> include the photos which were in the water. So I did a "within" selection
>> and got the rest of them along with a couple from the neighboring counties.
>> I'll probably just manually remove them from the set. I'm learning.
>>
>> Thanks again Larry for the support. I appreciate it.
>>
>> Mike
>>
>> ______________________________________________________________________
>> To unsubscribe, write to [EMAIL PROTECTED]
>
>
>______________________________________________________________________
>To unsubscribe, write to [EMAIL PROTECTED]
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
