Ticket #186 (closed task: fixed)

Opened 14 years ago

Last modified 14 years ago

[DS]qxf read methods on csml

Reported by: lawrence Owned by: domlowe
Priority: blocker Milestone: PreBeta
Component: CSML Version:
Keywords: Cc:


Should these be built into cdunif.

Change History

comment:1 Changed 14 years ago by domlowe

  • Summary changed from qxf read methods on csml to [DS]qxf read methods on csml

comment:2 Changed 14 years ago by domlowe

  • Status changed from new to assigned

comment:3 Changed 14 years ago by domlowe

Just done some basic testing on this with the current cdunif read methods. If you parse the CSML document describing the QXF data and do:

print feature.rangeSet.arrayDescriptor.getData(fileposition=1)

Where the arrayDescriptor looks like:

<NetCDFExtract gml:id="qxf_surfaceelevation">


<fileName>BODCSample/b0244122.nc BODCSample/b0244134.nc BODCSample/b0244146.nc BODCSample/b0244158.nc</fileName>



(note I changed the file extensions from .qxf to .nc for testing)

You get the data back for BODCSample/b0244134.nc which looks like: [5.18166256, 4.87685871, 4.63301563, 4.54157448, ... etc]

And this represents "Surface elevation (unspecified datum) of the water column". So I think this is all working. Siva, does this data look right?

If so, then hopefully no new code is needed to read QXF files except for handling .qxf file extentions (subject to results of further testing).

comment:4 Changed 14 years ago by siva

DOM, the output you got is correct. I checked locally.

comment:5 Changed 14 years ago by domlowe

  • Status changed from assigned to closed
  • Resolution set to fixed

Closing this ticket. New ticket 498 created to remind me to add .qxf as a valid file extension for NetCDF files.

QXF 'extracts' should use <NetCDFExtract> although this is quite likely to change with CSML v2 anyway.

Note: See TracTickets for help on using tickets.