The "welldata" web service provides meta data about a well dataset.

A typical URL is: http://myserver.mycompany.com:8080/INTGeoServer/json/welldata?json={"filePath":"34/10-A-6A.las"}

The following parameters are available:

filePath: the relative path of the specified dataset. This is a required parameter. If a path encoded is used, this path is encoded.

Here is an example response. This response has been formatted to improve readability

{

"name":"MUSQUOE23",

"nullValue":-9999.999,

"zUnitSymbol":"ms",

"zUnitName":"Milliseconds",

"compatibleZUnitSymbols":[

"ms",

"s"

],

"curveMds":[

920,

924,

928,

932,

936,

940,

944,

948,

952

],

"deviationMds":[

372,

376,

380,

384,

388,

392,

396,

400,

404,

408,

412

],

"logCurveNames":[

"AI",

"CAL12W"

],

"deviationCurveNames":[

"MD",

"TVD",

"XCOORD",

"YCOORD",

"AZIM",

"INCL"

],

"markerNames":[

"DAWSON_CANYON",

"MISSISAUGA"

],

"logArrayNames":[

],

"hasTrajectory":true

}

The name entry represents the name of the well dataset. This name is typically the file name without the extension.

The nullValue entry is the double value which will be used to represent any null values. A value typically found in LAS files is -999.25. In the LAS format, this is found in the ~Well section as the NULL attribute.

The zUnitSymbol entry is the symbol which represents the unit of depth measurements. Ex: "m", "ft", "s". This is the unit of the MD values. The unit may vary based upon the content of each LAS file, but also the mapping instructions that INTGeoServer uses.

Note: The z unit does not necessarily have to be a unit of distance, it can also be time if a depth to time conversion was performed on that well data.

The zUnitName entry is the full name of the vertical measurement unit for the log curve or deviation curve measured depths. Ex: "Meters", "Feet", "Seconds"

The compatibleZUnitSymbols entry is the list of zUnitSymbols which can be used when retrieving curve data. If the vertical unit is in time, compatible units will be in time as well (ex: seconds or milliseconds). If the vertical unit is in depth, compatible units will be in depth (ex: feet, meters or inches).

A log curve is a measurement that is taken along the curve measured depths. The nullValue is typically used here if the measurement was not taken at that particular measured depth.

In contrast, deviation curves are positional information related to the deviation measured depths. There are several ways that deviation curves can be retrieved from disk. A LAS 2.0 file has no deviation information, but a .dev file with the same name might contain this information. When INTGeoServer reads a .LAS file, it also reads the associated .dev file to find deviation curves. Depending on the INTGeoServer LAS mapping configuration, the deviation will be calculated based upon the following curves found in the .dev file:

• X, Y, MD and TVD

• INCL, AZIM, MD and TVD

• DX, DY, MD and TVD

Each one of those curves will be a "deviation curve" as it was involved in the calculation of the deviation. If the "INCL, AZIM, MD" or "DX, DY, MD, TVD" methods were used, the XCOORD and YCOORD deviation curves will be included as well. If "INCL, AZIM, MD" was selected, a "Minimum Curvature" method was used to compute these deviation curves.

The curveMds entry is the list of measured depths for the log curves for this well. This is the index common to all log curves.

The deviationMds entry is the list of measured depths for the deviation curves for this well. This is the index common to all deviation curves.

The logCurveNames entry contains the names of all log curves.

The deviationCurveNames entry contains the names of all deviation curves.

The markerNames entry contains the names of all of the markers. Introduced in LAS 3.0, markers are particular points of interest at a certain depth in the well.

The logArrayNames entry contains the names of all of the log arrays. Log arrays are a special structure found in DLIS files. Unlike log curves which have one dimension (only one value per MD), log arrays have two dimensions (one array of values per MD).

The hasTrajectory entry shows if the well has a well trajectory. The trajectory represents the deviation of this well data. A LAS 2.0 might not have a trajectory if no .dev file was found on disk.

If the specified filePath doesn't match a valid well, no JSON response will be provided. The HTTP response will only show a "File or Directory Not Found" (error 404) in its headers.

The HTTP header also contains a "dataHash" header. The hash code can be used to track whether the data file underlying the specified dataset has been changed since the last time it was loaded from disk.