GediFinder python code

[ryanmcarlson]

No description provided.

[crich011]

Sorry that this took so long; I noted a couple small things. One question I have about the process as a whole is whether we will need to run this multiple times per bounding box or per level. For example, it looks to me like the url that gets created on L59 will have only the 1B data.

If that's the case, I think the code here looks reasonable and we could potentially put it into a function which takes the level and any other relevant information (like the bounding box and version, maybe?) and outputs the granules, for example.

[crich011]

Request: before merging, it probably makes sense to remove most of this auto-generated preamble that Colab throws in when exporting. Lines 2-10, that is; the description on L11 seems helpful to me.

[ryanmcarlson]

Just went through and cleaned up some of the commented stuff.

[crich011]

One other thing I forgot to mention, but if you haven't, it might be worth trying to run black on this file to see if there's any formatting it decides to clean up.

[ryanmcarlson]

If that's the case, I think the code here looks reasonable and we could potentially put it into a function which takes the level and any other relevant information (like the bounding box and version, maybe?) and outputs the granules, for example.

You are correct in saying that the code can only determine the granules for one level at a time. Putting this all into a function would be fairly easy so yeah we can do that. It might be worthwhile sharing this function with the group making the pyGEDI module.