hyo2.bag 1.2.12

A package to manage Bathymetric Attributed Grid (BAG) data files.

HydrOffice BAG

• GitHub: https://github.com/hydroffice/hyo2_bag

• Project page: url

• License: LGPLv3 or IA license (See Dual license)

General Info

HydrOffice is a research development environment for ocean mapping. It provides a collection of hydro-packages, each of them dealing with a specific issue of the field. The main goal is to speed up both algorithms testing and research-2-operation.

The BAG package collects tools for working with Bathymetric Attributed Grid (BAG) files. The BAG package is used in BAG Explorer to explore BAG data files.

Note

BAG is a data format developed and maintained by the Open Navigation Surface Working Group. For the official reference implementation, go to https://github.com/OpenNavigationSurface/BAG

Dependencies

For the BAG library, you will need:

• python [>=3.8]

• numpy

• h5py

• lxml

• gdal

• PyInstaller [for freezing the tools]

For running some of the example scripts, you might also need:

• matplotlib

---

History

1.0

2018-12-02

• Move to hyo2 namespace

0.5

2018-06-21

• Bug fix to follow GDAL-convention for geotransform

2018-04-08

• Switch to git

2017-04-21

• Switch to Python 3

0.2

2016-05-27

• Added option to read a slice of rows for elevation and uncertainty layers

2016-03-21

• Added option to reproject layers into user-defined EPSG

2015-10-24

• Split BAG Explorer as stand-alone hydro-package

2015-10-09

• Added BAG Explorer

• Started Schematron schema for BAG Metadata profile

0.1

2015-03-31

• Initial commit.

---

Credits

Authors

HydrOffice BAG is written and maintained by:

• Giuseppe Masetti

Contributors

The following wonderful people contributed directly or indirectly to this project:

• Matt Wilson

• Brian Calder

Please add yourself here alphabetically when you submit your first pull request.

---

How to contribute

Every open source project lives from the generous help by contributors that sacrifice their time and this is no different.

To make participation as pleasant as possible, this project adheres to the Code of Conduct by the Python Software Foundation.

Here are a few hints and rules to get you started:

• Add yourself to the AUTHORS.txt file in an alphabetical fashion. Every contribution is valuable and shall be credited.

• If your change is noteworthy, add an entry to the changelog.

• No contribution is too small; please submit as many fixes for typos and grammar bloopers as you can!

• Don’t ever break backward compatibility.

• Always add tests and docs for your code. This is a hard rule; patches with missing tests or documentation won’t be merged. If a feature is not tested or documented, it does not exist.

• Obey PEP 8 and PEP 257.

• Write good commit messages.

• Ideally, collapse your commits, i.e. make your pull requests just one commit.

Note

If you have something great but aren’t sure whether it adheres – or even can adhere – to the rules above: please submit a pull request anyway! In the best case, we can mold it into something, in the worst case the pull request gets politely closed. There’s absolutely nothing to fear.

Thank you for considering to contribute! If you have any question or concerns, feel free to reach out to us.