[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-users] Automatically updating a field in a set of selected records
|
> While I'm at it, I have to say that while there are many admirable aspects to uDig, I find the reshape wizard is not one of them. I tried to add a column to a file. The idea that you create a scratch file, and then save the resource while unchecking the scratch file you just created, is about the most confusing sequence of operations I've ever experienced in a software package. Anyway, just my $0.02.
No worries; for "Reshape" it was mostly a programmer teaching device that was too useful to leave out of the application. I would love to put a nicer user interface on top of it.
As for "scratch" files; that is a bit more of a general purpose idea. Giving people a chance to try out what they have done without being forced to save it all the time. The scratch file should be removed after it has been saved (right now when you save any maps that referred to the scratch layer are updated to point to the final location).
Can you think of an more appropriate sequence of events?
> Thanks for your interest and patience. I am extremely pleased that the uDig community exists, and I wish you every success with it.
No worries; my volunteer time has been pushed into making the latest release so I have not have had any time for more features myself. I hope to return to udig development towards the middle of the month.
>>> The list tells me the name of a stream, and the name of the stream it flows into, and the basin in which both are located. The shp file is huge, with more than 80,000 features. One stream in the printed list typically translates to 20-30 features, and sometimes more, in the shp file.
>>
>> This sounds like fun data cleaning work. IF YOU'RE A MASOCHIST.
Okay it sounds like nice honest work; data cleaning in general is rewarding in that you take information that has been collected (often at great expense) and actual produce something useful out of it - SO YOU CAN GET ANSWERS :-)
So rewarding; as oppose to debugging programming; where you do a bunch of work; so you can find out exactly how you confused things (so you can feel stupid in a new way) :-)
>>> If there were an good, internal update tool internal to uDig, I'm sure that would be preferable to phpMyAdmin....
>>
>> Not quite sure what you mean by "internal update tool"? MY WORRY IS THAT IF I CHANGED DATA USING SQL QUERIES IN MYSQL (I.E. EXTERNAL TO UDIG) I WOULDN'T THEN BE ABLE TO SEE THE CHANGES BACK IN UDIG. YOUR BULK UPDATE TOOL WOULD BE "INTERNAL" TO UDIG IN THE SENSE THAT I MEANT.
Oh; uDig does not have an internal (except for the one case of "scratch" layers). When you change things using the user interface they are held on a MSQL transaction. When you commit it goes back to your database. If you use SQL to hack at your database the results should change in the map display right away (well if you hit refresh); and you may need refresh the table view as well.
But yeah; udig tries to operate directly with your source data all the time; not loading it into memory.
Jody
