Type of PR

• [X] Bug Fix
• [ ] Feature

What is the Goal of the PR?

Fix bug in wrapGeom.

What is the Motivation for the PR?

wrapGeom passes input object rather than only geometry when srs matches georaster, causing wrapped function to raise "Invalid point object was used." or similar error.

What Tests are Included?

New test for the bug that is fixed.

Describe the bug I can import geoblaze but stats is not available. It doesn't seem to have an export listed here: https://github.com/GeoTIFF/geoblaze/blob/master/src/index.js

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

Describe the bug The geoblaze build is not compatible with IE11, which is 2-3% of web traffic. Since the project is already using webpack/babel, it may be reasonable to specify older browsers as transpile/polyfill targets, but I'm not sure how to make this happen with the current .babelrc setup.

Its possible to use a preloaded and cached TIF file on a Float32array from geotif.js to use it with geoblaze? In order to avoid load multiple times from url. How can i achieve that?

Thanks

Describe the bug Line 36 of /src/max/max.module.js const noDataValue = georaster.no_date_value;

should be (from taken from min): const { noDataValue } = georaster;

To Reproduce Use the function with a dataset where the nodata would be max.

Expected behavior Output of the real max value not the nodata value

Type of PR

• [ ] Bug Fix
• [ ] Feature
• [x] Maintenance

What is the Goal of the PR?

General dependency updates for maintenance. The main packages that were updated are:

• webpack (move to v4)
• documentation
• turf

What is the Motivation for the PR?

1. We are currently adding all of turf (@turf/turf) as a dependency, which feels a bit unnecessary and unduly heavy
2. Webpack 4 has been out for a while now and is fairly stable, figured it was time to move over to it

What Tests are Included?

No tests included, but ran all tests locally after updating packages

Type of PR

• [x] Bug Fix
• [ ] Feature

What is the Goal of the PR?

Fix issues with not being able to load the latest version in Angular and other projects

What is the Motivation for the PR?

We need this library in our application, version 0.2.2 works but we'd rather keep up to date with later versions. Trying to import the newest version throws errors similar to https://github.com/GeoTIFF/geoblaze/issues/165. As far as my understanding about webpack and bundling goes (please note, I haven't used those tools directly a lot, so my understanding might be limited), the browser key can be directly set to the script to use. Setting an object is usually used when other modules are required which are not available in the browser, which you can then shim or just completely ignore. (https://github.com/defunctzombie/package-browser-field-spec)

What Tests are Included?

None

Trying to utilize geoblaze on the frontend in a react app, I have the latest release of georaster concurrently installed as an independent dependency also.

Anyway, upon loading the geoblaze module into a react component, regardless of whether I use the require/import syntax, everytime I try to perform an operation like rastercalculator or load with geoblaze, I get the following error:

Uncaught ReferenceError: require is not defined at Object. (44e88b0d-451a-4137-87d5-910ea3128104:1) and the reference is to the geoblaze.node.min script rather than the web version. I'm not sure how to get react's webpack dev server to load the minified web script in lieu of the geoblaze.node.min script. Before that there was some errors related to georaster as well, so I also tried to create the georaster directly instead of having geoblaze handle it, and passing the prepared georaster object to the geoblaze function seemed to remove those.

Looks like maybe the package.json could be amended, just perusing npm's module docs I came across this:

"The main field is a module ID that is the primary entry point to your program. That is, if your package is named foo, and a user installs it, and then does require("foo"), then your main module’s exports object will be returned. This should be a module ID relative to the root of your package folder. For most modules, it makes the most sense to have a main script and often not much else.

browser§ If your module is meant to be used client-side the browser field should be used instead of the main field. This is helpful to hint users that it might rely on primitives that aren’t available in Node.js modules. (e.g. window)

Haven't looked into environment detection variable that might clear the issue up

Thanks -- take care

• Made it so production build is geoblaze.min.js and dev build is geoblaze.js
• Added files for testing if builds can be required and also included in a web page.
• Added node-fetch to webpack externals, so that it's not included in the build, but instead when node-fetch is required, it looks for it in the node_modules folder (https://webpack.js.org/configuration/externals/). Problem with webpacking node-fetch is that the author explicitly states node-fetch is only for node and any issue is webpack's fault.

Type of PR

• [X] Bug Fix

What is the Goal of the PR?

Fix issues where can't require in node

What is the Motivation for the PR?

Fix build

What Tests are Included?

Added test-loading-builds.js

What

This PR adds a logger file which exports an object to handle logging in various environments. The logger looks at the process.env.DEBUG_LEVEL environment (defaulting to 0 if none is specified) and determines when to log certain information to the console.

The logger is accessed by importing it (const logger = require('../../logger'); for most packages) and then running its logging functions. There are currently three logging functions corresponding to two levels of logs:

• logger.debug() - debug level 2
• logger.info() - debug level 1 or lower
• logger.error() - errors caught at debug level 1 or lower

Why

By centralizing how logging works across geoblaze, we can simplify the process of moving between debug levels and handling logging. By removing logic handling logging for each location where logging occurs, we can minimize the possibility of syntax errors.

Bumps mathjs from 6.6.5 to 7.5.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

const geoblaze = require('geoblaze')
const fs = require('fs');

//const file = '/MAPS/DEMS/trentino-altoadige.tif'
const file = process.argv[2];

const point = {
	"type": "Point",
	"coordinates": [
	  11.0,
	  46.0
	]
}
fs.readFile(file, async (err,data) => {
	const res = await geoblaze.identify(data, point)
	console.log(res)
});

run in node 16.16 return null and this error "Node worker_threads not available. Trying to fall back to tiny-worker polyfill... │o.png null"

Is your feature request related to a problem? Please describe. There is no documented way to use geoblaze with WMS. This is a very important use case as raster data is generally large in nature and usually served through WMS.

Describe the solution you'd like One should be able to use geoblaze with WMS. Instead of passing the file url, one can pass the WMS url and get results.

Describe alternatives you've considered No alternatives considered yet. Looking for some way to do stuff on client-side, if geoblaze can deal with WMS, that'd be awesome.

Additional context GetFeatureInfo can help to get actual pixel values. This can be integrated into the code.

Describe the bug When trying to calculate means for many (thousand) polygons, I frequently receive the "No Values were found in the given geometry" error. However, the raster definitely covers the given geometry and has values in it (checked using QGIS → Zonal Statistics). Also, the mean calculation works when I just pass the geometries bboxes. Could it be that the type of polygon, e.g. "MultiPolygons" or concave polygons are not supported by geoblaze?

To Reproduce See the following Observable notebook to reproduce: https://observablehq.com/@chrispahm/geoblaze-unsupported-geometry-type

Expected behavior The mean method should return the same mean as QGIS zonal statistics.

First of all: Thanks for this awesome library! 🚀 🔥

Describe the bug Before throwing an error, geoblaze currently also logs the error to the console using console.error (see here for an example https://github.com/GeoTIFF/geoblaze/blob/f99483b7446eadbaf55c5371294353451e020ec3/src/stats/stats.core.js#L67.

Especially when working with large datasets, the excessive logging becomes a serious performance hit (see https://stackoverflow.com/a/26754011/6213343), and there is no option to turn it off.

To Reproduce See the following Observable notebook: https://observablehq.com/@chrispahm/geoblaze-unsupported-geometry-type When opening the console, a log of the error can be found.

Expected behavior IMHO logging should only happen on the user side. Instead of relying on geoblaze to log to the console, I think the library should just throw the error so users can decide how to proceed.

Another approach could be to pass a debug option to the geoblaze function that enables logging.

P.S.: I can create a PR if desired!

Describe the bug I have a Vue/Webpack app that uses geoblaze. When I try to compile (eg. npm run serve) the app I get the following errors:

 ERROR  Failed to compile with 2 errors                                           4:21:10 PM

 error  in ./node_modules/geoblaze/src/load/load.module.js

Module not found: Error: Can't resolve 'url' in 'C:\Projects\forest-opt\client\forest-opt-client\node_modules\geoblaze\src\load'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. 
This is no longer the case. Verify if you need this module and configure a polyfill for it. 

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
        - install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "url": false }

 error  in ./node_modules/geoblaze/src/parse/parse.module.js

Module not found: Error: Can't resolve 'url' in 'C:\Projects\forest-opt\client\forest-opt-client\node_modules\geoblaze\src\parse'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. 
This is no longer the case. Verify if you need this module and configure a polyfill for it. 

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
        - install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "url": false }

ERROR in ./node_modules/geoblaze/src/load/load.module.js 3:0-26
Module not found: Error: Can't resolve 'url' in 'C:\Projects\forest-opt\client\forest-opt-client\node_modules\geoblaze\src\load'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. 
This is no longer the case. Verify if you need this module and configure a polyfill for it. 

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
        - install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "url": false }
 @ ./node_modules/geoblaze/src/load/index.js 20:0-40 20:0-40
 @ ./node_modules/geoblaze/src/wrap-load.js 1:0-26 8:13-17
 @ ./node_modules/geoblaze/src/raster-calculator/raster-calculator.module.js 5:0-32 79:15-19 @ ./node_modules/geoblaze/src/raster-calculator/index.js 14:0-53 14:0-53
 @ ./src/modules/foRasterLayer.js 22:0-71 212:24-40
 @ ./node_modules/babel-loader/lib/index.js??clonedRuleSet-40.use[0]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./src/components/Map.vue?vue&type=script&lang=js 13:0-55 314:22-35
 @ ./src/components/Map.vue?vue&type=script&lang=js 1:0-195 1:0-195 1:196-380 1:196-380     
 @ ./src/components/Map.vue 2:0-54 3:0-49 3:0-49 8:49-55
 @ ./node_modules/babel-loader/lib/index.js??clonedRuleSet-40.use[0]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./src/views/Tool.vue?vue&type=script&lang=js 2:0-42 18:4-9
 @ ./src/views/Tool.vue?vue&type=script&lang=js 1:0-196 1:0-196 1:197-382 1:197-382
 @ ./src/views/Tool.vue 2:0-55 3:0-50 3:0-50 8:49-55
 @ ./src/router/index.js 14:0-37 58:13-17
 @ ./src/main.js 18:0-30 29:8-14 40:3-9

ERROR in ./node_modules/geoblaze/src/parse/parse.module.js 2:0-26
Module not found: Error: Can't resolve 'url' in 'C:\Projects\forest-opt\client\forest-opt-client\node_modules\geoblaze\src\parse'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. 
This is no longer the case. Verify if you need this module and configure a polyfill for it. 

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
        - install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "url": false }
 @ ./node_modules/geoblaze/src/parse/index.js 24:0-41 24:0-41
 @ ./node_modules/geoblaze/src/wrap-parse.js 1:0-28 8:13-18
 @ ./node_modules/geoblaze/src/get/get.module.js 3:0-33 105:15-19
 @ ./node_modules/geoblaze/src/get/index.js 14:0-39 14:0-39
 @ ./node_modules/geoblaze/src/raster-calculator/raster-calculator.module.js 4:0-25 39:22-25 @ ./node_modules/geoblaze/src/raster-calculator/index.js 14:0-53 14:0-53
 @ ./src/modules/foRasterLayer.js 22:0-71 212:24-40
 @ ./node_modules/babel-loader/lib/index.js??clonedRuleSet-40.use[0]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./src/components/Map.vue?vue&type=script&lang=js 13:0-55 314:22-35
 @ ./src/components/Map.vue?vue&type=script&lang=js 1:0-195 1:0-195 1:196-380 1:196-380     
 @ ./src/components/Map.vue 2:0-54 3:0-49 3:0-49 8:49-55
 @ ./node_modules/babel-loader/lib/index.js??clonedRuleSet-40.use[0]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./src/views/Tool.vue?vue&type=script&lang=js 2:0-42 18:4-9
 @ ./src/views/Tool.vue?vue&type=script&lang=js 1:0-196 1:0-196 1:197-382 1:197-382
 @ ./src/views/Tool.vue 2:0-55 3:0-50 3:0-50 8:49-55
 @ ./src/router/index.js 14:0-37 58:13-17
 @ ./src/main.js 18:0-30 29:8-14 40:3-9

webpack compiled with 2 errors

To Reproduce Compile or build an app using geoblaze. [email protected] [email protected]

Expected behavior Expected app to compile without errors

Additional context This worked fine before when I was using [email protected] and webpack was likely < 5

Type of PR

• [+] Bug Fix
• [+] Feature

What is the Goal of the PR?

To enable build on Windows platform.

What is the Motivation for the PR?

I'm using Windows :) I'm new to community based development and js dev and github. I forked the repository and cloned it to my pc and followed instructions to build, but that failed. This should not happen. The project/repository should be platform independent.

What Tests are Included?

It builds