The "logarray" web service provides meta data about a log array.

A typical URL is: http://myserver.mycompany.com:8080/INTGeoServer/json/logarraydata?filePath=DLISOut_W25.dlis&logCurve=NMR_Teste%2F342710278300%2F0%260%26NMR_T2_DIST&showValues=false

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.

logCurve: The name of the log array to be retrieved.

compatibleZUnitSymbol: a measurement symbol, such as "m" or "s". If the requested symbol does not match one of the compatibleZUnitSymbol in the welldata web service, the server will return a bad request response (error 400) in the HTTP header. This is an optional parameter. By default, the log array will be returned in its native vertical unit.

decimation: The decimation factor. Ex: If the decimation is 2, measured depths and value arrays with indices 0, 2, 4, 6 .... will be included in the response. This is an optional parameter. By default, the decimation factor is 1 (no decimation is applied)

showValues: If this value is false, the measured depths, log array values, and numberOfValues portions of the response will not be sent. This is an optional parameter. By default, all portions are sent.

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.

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

{

"minimumMD":5600.01416015625,

"maximumMD":5840.04443359375,

"minimumValue":2.202525877237349E-7,

"maximumValue":0.09397319704294205,

"nullValue":-999.25,

"decimation":1,

"description":"T2 Distribution",

"unitSymbol":"m3/m3",

"unitName":"m3/m3",

"shortName":"T2_DIST",

"mds":[

5600.01416015625,

5600.20458984375,

5600.39501953125,

5600.5859375

],

"values":[

[

4.315806165777758E-7,

4.315806165777758E-7,

0.0011847479036077857,

0.0040788655169308186

],

[

4.32006686423847E-7,

4.32006686423847E-7,

4.32006686423847E-7,

4.32006686423847E-7

],

[

3.5236217081546783E-4,

3.348252212163061E-4,

0.0012725632404908538,

0.0022448713425546885

],

[

0.0012725632404908538,

0.0022448713425546885,

0.0021222447976469994,

4.3183212028452544E-7

]

],

"numberOfValues":4

}

The minimumMD entry is the minimum measured depth for this log array, expressed in the Z unit of the associated well data.

The maximumMD entry is the maximum measured depth for this log array, expressed in the Z unit of the associated well data.

The minimumValue entry is the minimum curve value for this log array, expressed in the unit given by the unitName entry.

The maximumValue entry is the maximum curve value for this log array, expressed in the unit given by the unitName entry.

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.

The decimation entry is the decimation factor as entered in the request.

The description entry is the array description of this log array. For example, "Impedance", "Porosity", instead of MNEMONICS.

The unitSymbol entry is the symbol which represents the unit of the values for this log array. Ex: "m", "ft", "s". This can also be "noUnit".

Note: This unit is not necessarily a unit of distance, time can also be used.

The unitName entry is the full name of the vertical measurement unit for the measured depths. Ex: "Meters", "Feet", "Seconds". This can also be "noUnit".

The shortName entry is the name for this log array.

The mds entry are the measured depths where each array of values is located.

The values entry is the list of all array values for a given measured depth index.

The numberOfValues entry is the number of measured depths associated with this log array.

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.