<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1257">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NO-BOK" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Hei Markus,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I see.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">With Maris hint on r.support, I managed to assign custom band names at import / t.register.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I still have to figure out how (or if) the different temporal modules handle band references.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I do get invalid temporal topology errors in g.gui.animation for example, but that may be due to start = end time stamp.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Documentation of features and none-features with band-references deserves some love for GRASS 8 release I guess…<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Cheers<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Stefan<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Markus Metz <markus.metz.giswork@gmail.com>
<br>
<b>Sent:</b> mandag 6. september 2021 09:27<br>
<b>To:</b> Maris Nartiss <maris.gis@gmail.com><br>
<b>Cc:</b> Stefan Blumentrath <Stefan.Blumentrath@nina.no>; Martin Landa <landa.martin@gmail.com>; GRASS developers list <grass-dev@lists.osgeo.org><br>
<b>Subject:</b> Re: [GRASS-dev] lib/gis/band_reference.c ?<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">The easiest way to assign custom band names to raster maps in a strds is to create a corresponding file for t.register.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Note that band names in a strds do not need to match band names assigned with i.bands. The whole concept of band references in GRASS is IMHO still experimental and unfortunately far away from the STAC eo bands extension.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Markus M<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">On Tue, Aug 24, 2021 at 11:09 AM Maris Nartiss <</span><a href="mailto:maris.gis@gmail.com"><span lang="EN-US">maris.gis@gmail.com</span></a><span lang="EN-US">> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">Band reference rules were totally relaxed 7 days a go:<br>
</span><a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fcommit%2Fabe194dce78adf5f63885a6a09c452fc7ae4f735&data=04%7C01%7C%7C84da7a235fa0418cfe3f08d97107ae4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637665100081158341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OXOunlOeOPMIGv8lyo6bpVMnOVkJ7SpTYgHfu5iXsXc%3D&reserved=0" target="_blank"><span lang="EN-US">https://github.com/OSGeo/grass/commit/abe194dce78adf5f63885a6a09c452fc7ae4f735</span></a><span lang="EN-US"><br>
<br>
New relaxed rule changes haven't propagated to the documentation yet<br>
(PR's welcome).<br>
<br>
Band reference editing via r.support was added on 4th of July:<br>
</span><a href="https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass%2Fcommit%2Fca1551206eaa0fc462f4849a06ebb035808470da&data=04%7C01%7C%7C84da7a235fa0418cfe3f08d97107ae4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637665100081168336%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=MqIan9AmoGhM3PIJ1AF3kEyE%2FXmRtiw9PG9%2FqUVDfYw%3D&reserved=0" target="_blank"><span lang="EN-US">https://github.com/OSGeo/grass/commit/ca1551206eaa0fc462f4849a06ebb035808470da</span></a><span lang="EN-US"><br>
<br>
Still – keep in mind – there are no changes in band metadata as<br>
managed by g.bands. Changes only deal with ability to have a band<br>
reference without extended metadata in json files. Thus limitation of<br>
not being able to define your own band reference is still in place,<br>
now only you can assign a band reference without having a definition<br>
(and thus any extended metadata apart from its name).<br>
<br>
Mâris.<br>
<br>
2021-08-24 11:18 GMT+03:00, Stefan Blumentrath <</span><a href="mailto:Stefan.Blumentrath@nina.no" target="_blank"><span lang="EN-US">Stefan.Blumentrath@nina.no</span></a><span lang="EN-US">>:<br>
> Thanks Maris for the reply.<br>
><br>
> I could not find that option in r.support.<br>
><br>
> i.band allows to add e.g. S2_12 as band reference, but nothing custom. And<br>
> the g.bands manual says that user-defined band references are not yet<br>
> supported.<br>
><br>
> Has that been added recently? Or would I have to edit the bands json file of<br>
> the system first?<br>
><br>
> My system is:<br>
> g.version -ger<br>
> version=</span><a href="https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2F8.0.dev%2F&data=04%7C01%7C%7C84da7a235fa0418cfe3f08d97107ae4d%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637665100081178328%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fxKLaiDra3SU%2FFu3d%2F4CUCH9x1wQ0nshhcFgrR0RazQ%3D&reserved=0" target="_blank"><span lang="EN-US">8.0.dev</span></a><span lang="EN-US"><br>
> date=2021<br>
> revision=dd9d36830<br>
> build_date=2021-07-08<br>
> build_platform=x86_64-pc-linux-gnu<br>
> build_off_t_size=8<br>
> libgis_revision=d2a5e8e8f<br>
> libgis_date=2021-06-16T04:05:21+00:00<br>
> proj=7.0.0<br>
> gdal=3.0.4<br>
> geos=3.8.0<br>
> sqlite=3.22.0<br>
><br>
> Cheers<br>
> Stefan<br>
><br>
> -----Original Message-----<br>
> From: Maris Nartiss <</span><a href="mailto:maris.gis@gmail.com" target="_blank"><span lang="EN-US">maris.gis@gmail.com</span></a><span lang="EN-US">><br>
> Sent: tirsdag 24. august 2021 09:03<br>
> To: Stefan Blumentrath <</span><a href="mailto:Stefan.Blumentrath@nina.no" target="_blank"><span lang="EN-US">Stefan.Blumentrath@nina.no</span></a><span lang="EN-US">><br>
> Cc: Martin Landa <</span><a href="mailto:landa.martin@gmail.com" target="_blank"><span lang="EN-US">landa.martin@gmail.com</span></a><span lang="EN-US">>; Markus Metz<br>
> <</span><a href="mailto:markus.metz.giswork@gmail.com" target="_blank"><span lang="EN-US">markus.metz.giswork@gmail.com</span></a><span lang="EN-US">>; GRASS developers list<br>
> <</span><a href="mailto:grass-dev@lists.osgeo.org" target="_blank"><span lang="EN-US">grass-dev@lists.osgeo.org</span></a><span lang="EN-US">><br>
> Subject: Re: [GRASS-dev] lib/gis/band_reference.c ?<br>
><br>
> GRASS supports arbitrary band reference names. Just make them unique enough<br>
> to not mix together apples with oranges by accident (e.g. "min"<br>
> is a bad idea, "min_t_c" is better; "NDVI" would work; "elevation" – bad,<br>
> "elevation_m" – better).<br>
> You can set band references after import with r.support module.<br>
</span>><br>
> Have fun,<br>
> Mâris.<br>
><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>