[GF] Strange Survey Origin

Brian Stevens brian.stevens at dataporters.com
Mon Aug 16 13:16:12 CDT 2010


Thanks for the responses I received.  I found this morning that at least one other project (probably a "clone" of the first) is exhibiting the same behavior.  I'll try to find a one of the projects not actively in use and see if I can fix it.  I'll report back with what does (or does not) work.

Brian Stevens

Brian Stevens
Systems Administration Consultant
Data Porters, LLC
brian.stevens at dataporters.com
(713) 419-6250



On Aug 13, 2010, at 2:43 PM, Brian Stevens wrote:

> I have run into something I've not seen before and I'm wondering if anyone else has seen it and whether anyone can comment on how it should [not] be fixed.
> 
> [Environment is GeoFrame 4.4 running on Solaris 10 systems.]
> 
> In a particular [problematic] interpretation project, when I post a particular survey (shared from a seismic master project), it appears "not right".  The survey's inlines and xlines both start at negative values, and the area of the survey appears much larger than it should be.  Examining the survey origin/locations in the data manager, it has these three points:
> 
> First
> CDP:  -9728
> Line:  -3106
> Lat:  25.589639611 N
> Long:  87.603744833 W
> 
> Second
> CDP:  13158
> Line:  -3106
> Lat:  27.391089944 N
> Long:  89.658645722 W
> 
> Third
> CDP:  13158
> Line:  13496
> Lat:  28.736924861 N
> Long:  88.189690472 W
> 
> 
> In both the seismic master project and my own interpretation project, the data manager shows the defining points of the same survey as follows:
> 
> First
> CDP:  8790
> Line:  10016
> Lat:  28.111543222 N
> Long:  88.102818500 W
> 
> Second
> CDP:  13158
> Line:  10016
> Lat:  28.456224667 N
> Long:  88.500651389 W
> 
> Third
> CDP:  13158
> Line:  13496
> Lat:  28.736924861 N
> Long:  88.189690472 W
> 
> 
> In both cases, the third points match up (last inline and xline), but the "origins" seem quite different.  It's almost as if the "origin" of the survey in the problematic project somehow got messed up.
> 
> Does anyone have any ideas on how this could happen?
> 
> Is simply changing the Survey Origin through the data manager a safe way to fix the problem, or will that have effects on any/all of the interpretation?  I've not seen this before, and my experience is limited in dealing with survey data.
> 
> Thanks in advance for any input!
> 
> 
> Brian Stevens
> Systems Administration Consultant
> Data Porters, LLC
> brian.stevens at dataporters.com
> (713) 419-6250
> 
> 
> 
> 
> 
> _______________________________________________
> GF mailing list
> GF at stevens.com
> http://lists.stevens.com/mailman/listinfo/gf



More information about the GF mailing list