GeoModelGrids v1.0.0rc2

New features

• Allow independent uniform resolution along each of the coordinate directions.
• Allow variable resolution along each coordinate direction.
• Update metadata to better match IRIS EMC metadata.
• Improve geomodelgrids_info output, including bounding box and coordinate system units.
• Convert documentation from Jekyll (GitHub Pages) to Sphinx+MyST (readthedocs).
• Use Azure Pipelines for continuous integration testing.

Bug fixes

• Fix squashing queries. Adjust elevation before checking if query location is in model.
• Add tolerance for checking whether query location is below top surface.

Known issues

• The interpolation algorithm does not respect fault block and zone boundaries and the boundary between water and solid materials. This means fault block and zone ids will be interpolated across block and zone boundaries, and Vp and density will be interpolated Vp and density across the boundary between water and solid materials. Vs will end up with NODATA values, because it is not defined in water; the workaround is to query at just below the top grid cell.
• GeoModelGrids does not support unit conversions. All values returned in queries are in the units of the underlying models. We do check that all models have consistent units for values contained in multiple models. Queries for the elevations of the top surface or topography/bathymetry will be returned in the units of the input Coordinate Reference System.
• The model storage has been optimized for faster successive queries in the vertical direction. That is, querying for points on a vertical slice will generally be faster than querying the same number of points on a horizontal slice.

GeoModelGrids v1.0.0rc1

Known issues

• The interpolation algorithm does not respect fault block and zone boundaries and the boundary between water and solid materials. This means fault block and zone ids will be interpolated across block and zone boundaries, and Vp and density will be interpolated Vp and density across the boundary between water and solid materials. Vs will end up with NODATA values, because it is not defined in water; the workaround is to query at just below the top grid cell.
• GeoModelGrids does not support unit conversions. All values returned in queries are in the units of the underlying models. We do check that all models have consistent units for values contained in multiple models. Queries for the elevations of the top surface or topography/bathymetry will be returned in the units of the input Coordinate Reference System.
• The model storage has been optimized for faster successive queries in the vertical direction. That is, querying for points on a vertical slice will generally be faster than querying the same number of points on a horizontal slice.