ASCII File Rules for Well Data Loading

[Joel Scott]

Has anyone found the rules for well data import format rules.

• Delimiters allowed
• Requirement for quotes
• How to handle null text fields
• How to handle null elevation fields

Joel Scott

[Joel Scott]

I have a follow up question. Using the Import Well Locations tool, I imported Well Name, Latitude, Longitude, MDTD, KBelev, and UWI. Apparently, even though I imported the UWI, non-unique well names were not allowed. Is this an application feature? Why, if there is a UWI? 

Joel

[Friso Brouwer]

Joel,

I used the well locations import a few times myself recently. This may not help you with everything, but a few things I know/deduced:

delimiter: only tab and space I believe, if you have a csv format, awk, or python do a good job to quickly replace those.

double quotes are used to read names that have spaces in them as one.

Often OpendTect reads 1e30 as undefined, using this value  may be an option to handle null fields, but I do not know for sure.

OpendTect uses well names, not API/UWI to recognize wells. If you have duplicate names you need to add something to the well name to make it unique (a,b,c .. or drilling date). Alternative is to use the UWI as well name. I think the developers always like to improve these things, and possibly an option to automatically add the UWI at the tail of the well name or some other system employing UWIs would be nice to have. as people often alternate between using names and UWIs.

Cheers,

Friso

--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/626bca3d-de34-4528-8d00-0da7f7ab87c4n%40opendtect.org.

[jesc...@gmail.com]

Friso,

 

Thanks for your response. I have deduced the same as you. I’ll have to try the NULL value next time.

 

A suggestion for the developers, they may be able to concatenate the well name with UWI internally (in the backend) out of view of the users which could silently allow duplicate well names. Hopefully, the developers appreciate how common it is for duplicate well names to occur in legacy operating areas.

 

Joel

To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/CA%2BA_U%3DrQtyjgo13i7WCrAeMzgqS8r%2BUA6MgyEMe65Yb3jA-yXA%40mail.gmail.com.

[Mark Crawford]

Hi Joel,

Thanks for bringing this up...

We've logged this as a suggestion for improvement.

Whilst we can't promise anything, it's been noted that this could well be a useful addition.

Kind regards,

Mark

To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/212801d85fcb%245779f5c0%24066de140%24%40gmail.com.

--

Kind regards,

Mark

Mark Crawford

Support Manager

-----------------------------------------------------------------------------------------------------------------------   dGB Earth Sciences
Phone: +31 53 4315155 E-mail: mark.c...@dgbes.com Internet: dgbes.com

-----------------------------------------------------------------------------------------------------------------------