But that could be a simple fix to detect shape=(1,1) and report missing data instead in this case, I do not expect a valid case for 1x1 pixel data, so using that as a marker for "information not available" is acceptable in my view. Only concern is that native_geobox called on such a Dataset will report valid geobox even though it shouldn't. Indirection involves tricking people by making them pay attention to the wrong things. Spies are often forced to use indirection to keep their identities hidden. Such grid would have CRS: "EPSG:4326", shape: and transform: computed in such a way that 0,0 -> 1,1 square maps to a bounding box of the dataset in lon,lat. Indirection means sneakiness or lying, especially when it's deliberately meant to distract someone or divert his attention. When native projection and resolution data is not available but bounding box or a geometry are defined we can produce a "fake" default grid. One can still search for and load data without knowing up front in what projection pixels are stored, so long as bounding box is accurate enough (fully encloses valid data of the Dataset while being tight). The "essential" information needed by dc.load is "footprint", while "native resolution" and "native projection" information are "nice to haves". The transform also encodes native resolution of the image. The four image corners 0,0 W,0 W,H 0,H are mapped via linear transform to give footprint information. This also means that a common case of "all bands in the dataset share the same footprint and resolution" has minimal textual representation in EO3 format.Įach "grid" is basically shape and transform tuple, that in combination with shared CRS fully define a shared footprint of the bands belonging to that grid. Bands that belong to "default" grid can omit grid specification as "default" grid is implied. One of the grids must be called "default". Bollinger bands actually comprise three separate indicators and each tells you something about the price activity at a current point in the chart. Unlike STAC, EO3 expects an extra indirection layer: each band is assigned to some named grid (shared across several bands), this way if 10 bands share common grid (footprint), then grid information is recorded once. EO3 metadata format expects one to define native projection information for each band.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |