File Export Issues

Nate The Surveyor

Well-Known Member
I've always done the same as Darren, above.

It's something of interest.

I've thought of a number of schemes. "Export by base session", where it displays all base sessions, with it's respective sideshots. (like dpos does). And, we havee a check box mechanism, to select the base sessions. I'd like this. With an EXTRA check box "include cogo coords, made during session". And, an extra check box "include all cogo from entire job". This second option, would not be session dependant.

The issues that arise, are the fact that alpha only point names are permitted. If we export numbers 35-70, where does that put the alpha only points?

So, point name can be "pipe". (by accident, or on purpose).

Either way, it involves US the end users, having more power, and ability, than we are used to. So, we must think, consider, and be aware of what we are doing.
 

Jon Gramm

Member
Those are good ideas Nate!

The learning process is, for the most part enjoyable. Terminology, functionality, and the other traits, and capabilities of the equipment are things that take time to learn, mostly through trial and error on my (our) part.

Some of the functionality is very intuitive for me, some isn't. That is where practice, and experimentation are necessary. I like to test things, take notes, see the results, and if possible improve them, or make suggestions to improve them. Some of those suggestions may be purely selfish.

We have all had to use and create workarounds.
If I have to use a workaround enough times, I will write a permanent solution for it either in an application that accepts scripting or external routines, or an application that I write or have written from the ground up. Determining when to develop a permanent solution is the tricky part, and I have my own set of criteria for this.

The system, and thought put into it is amazing, as are its capabilities. I hope to push it to its limits someday.
 

Shawn Billings

Shawn Billings
5PLS
Obviously, having the date export would be optimal. I also really like Nate's suggestion regarding session export. Currently if I think I only want to export today's work, I'll put today's work in a new page and export by page. This has some limitations as we only have 10 pages and this may disrupt using pages for other schemes.
 

Matt Johnson

Well-Known Member
5PLS
We have the ability to filter and export by date already but it requires a number of button presses to configure. If we want to add the ability to only export new points I would suggest adding a field in the database to track if an object has been exported yet or not. Then an option could be added in the "What to Export" screen to "Skip Previously Exported and All Imported Points". This would then filter out points that have previously been exported and also filter out all design points that were imported. Design points that were created with J-Field would pass if they had not been exported previously.
 

Jon Gramm

Member
Shawn,
The pages idea is a good one, and we have contemplated using it. Yes, there would be limitations, especially on long term projects. I have been on several that lasted over a year, with multiple field crews, kind of a nightmare at times. (There are times that I work in the exploration industry. We lay siege to these projects.)

Matt,
The addition of an exported field is a very good suggestion. I would also suggest adding a "Resurveyed" field in case a previously surveyed point needs to moved.
(It happens a lot in the exploration industry.)

I do not wish the process to be over-simplified, and I know this exists in spirit by setting a date range of since and before but, on the 'What to Export" screen, a "Today" button would bring a smile to my face.
 

Jon Gramm

Member
Darren,
I agree wholeheatedly!
The help here has been truly impressive, and encouraging!

We still have a few issues to iron out, and we typically do not ask questions until most of the options have been explored.
You can't learn if you don't try.
 
Top