geospatial

Looking through the scripts in package.json, a lot of the tasks have inconsistent naming or have misleading names

To point out a few issues:

• some tasks use kebab-case (e.g. prettier-check) while others use camelCase (e.g. buildApps). We should pick a consistent style. (Personally I find kebab-case easier to type on the command line)
• generateDocumentation seems needlessly l

Hi!

My suggestion/request is simple. When filtering the data, sometimes one needs to use the edge values of the data distribution in the filter histogram.

For example, one wants to choose the data of an hourly distribution (from 0:00 to 24:00) for the time between 22:00 and 6:00 in the nighttime and discard the data from 6:00 till 22:00 during the daytime.

So, when filtering the data with

Please respect the following template to report a new issue, otherwise your issue will be automatically closed.

Before submitting, search through existing open or closed issues reports and through blender.stackexchange.com to check whether the issue already exists.

If the issue concerns an operator that grab geodata from an external web service (Basemaps, OSM, SRTM), then it can be a network

Currently the layer cannot be selected for low zoom levels.

As noted in #599, we don't have unit tests for the kinds of polyfill cases (non-contiguous cells) that make outline-tracing necessary. We should add unit tests here.

Hello Maurits,
This is more of a request than it is an actual issue, but I think the value in this request is really high (for newcomers, especially - but not limited to).
Could you please add a COMPLETE application example of using the API (with user authentication, maybe even with the user-creation SQL script, table authorization, etc).
This would be really really helpful as a quickstart /

Is there a way to know when the imagery was collected? I assume sometime in the daylight hours, and probably recently(?) but I have no way of knowing by looking at the output and the associated image.

Can that output be put in the CLI output or some other metadata file that gets associated with the LC####### directory?

'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings

react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• R

Context: this from @agila5: https://twitter.com/a_gilardi5/status/1487813588454678528

I have not had a chance to read the explanation and am not sure what we should say on the topic but guess it's worth a mention here. Any thoughts?

http://www.ontosoft.org/portal/#list

I stumbled upon Ontosoft recently, which is a compilation of geoscience academic software.

Not all is open-source and I've not used any of them yet, so I decided to just post here in case anyone wants to check them out.

Add it here: https://github.com/georust/geo/blob/1d3b32970a49746de6ce2400305725edd21f7c15/geo/src/lib.rs#L124-L130