Hi Gareth,

Prior to our troubleshooting session tonight I have refreshed myself on the issues with the petroleum application. The existing one's are as follows:

• The GPS point drop logic still not perfect. Subsequent pressings of the ok button drop multiple points at where the intial point was dropped to open the forms tab
• When a basin is not Cooper then endless errors that make the app unusable
• When a score is captured using the OK button, could the comment and photo clear but the scores remain the same?
• When a line is selected from a survey, the form displays the information correctly associated with the survey but does not display the line name. Need to have this displayed and the combo box to display all lines uploaded for the survey.
• Pressing the clear button does not clear the photo thumbnail from the box
• I know there was some work done to create a tracklog capture tool. That needs to get into the petroleum application if possible.
• What is the expression needed to ensure labels do not come up until zoomed up quite close to the feature?

Enhancement:

• If the incorrect seismic line is selected and changed from the combo box, can the geometry be reset to the midpoint of the line?
• When the 'zoom to GPS' button is activated, could it please centre on the GPS at a fixed scale of 50k? Most of the time we will need it will be in a hurry so very beneficial to have at the scale.

Jack.

Issues from testing:

• OK button appears to be not working. A dialog box briefly appears on the mapapp.apm screen but the form on the GAS scoring side doesn't disappear and reappear like it does when the 'OK, X' ArcPad buttons are used.
• When dropping a point nowhere near a selectable seismic line, get the 'There are no surveys in the result' dialog box appears when a pin is dropped and twice you hit OK. Would like a notification on the pin drop and that's it.
• Rob has requested the size of the icons be increased. I have changed the display (at the windows system level to 150%) so could the forms please be optimised to fit and view in that?
• Still having the problems with 'Lines_WGS' not updating to reflect the 'SIS_MERRegApp_SeismicLines_P' downloads from the main server and thus allow us to create a list of lines to be scored.
• Help screens still aren't loading up (only available for Cooper at this stage)

Issues resolved:

• Cancel button works fine.
• Auto pan has been turned off and center on GPS button works fine.
• Use GPS to drop point button works fine.

Hi Gareth,

Had a walk through Hindmarsh square this morning and found the following issues:

• The GPS point drop logic is still not quite right. It will still grab the first GPS point/pin drop and subsequent captures simply drop another point at the original location. We do want this functionality for when we don't have GPS access but if we do we'd love it to drop at the new location.
• Pictures associated with records still aren't uploading to the AWS and I get the attached error. I've checked with Andrew Noyce and it seems like the photo you uploaded holding the sign saying 'Hi Dan' has worked but none of the others appear to have made it into the bucket.
  
• If any other basin is selected that isn't cooper (i.e. arckaringa, officer etc) I get the error '800A03F7, unterminated string constant line 2 column 27 source text unavailable, thisevent.result = false'
• This also leads to the error in the map display whereby an error box comes up every 4 seconds on top of the previous one.
• When opening the forms on any one which is not Cooper, get error 'Microsoft JScript runtime errorObject expected [Line: x, Column: y] (different x and y for each basin) Source Text unavailable appears, but forms open after that.

Comments

• The Cooper form is working just fine and we have no problems with that.

Jack.

Hey Gareth,

Had a walk through Hindmarsh square this arvo and tested the data sync back. Found the following:

• Seems to be no problems with the database side of things. Data coming back no problem.
• Had trouble running the .py custom script myself with the standard double click. Am I missing the correct way of running it?

Still from last time though are the bugs

• The GPS point drop logic still not perfect
• When a basin is not Cooper then endless errors

Suggested Improvement on workflow:

• When a score is captured using the OK button, could the comment and photo clear but the scores remain the same?

Jack.

When dropping a point nowhere near a selectable seismic line, get the 'There are no surveys in the result' dialog box appears when a pin is dropped and twice you hit OK. Would like a notification on the pin drop and that's it.