Use case: description, code

jsfiddle example

Expected behavior

Dont parse '%22', when inside a attribute

Actual behavior (stack traces, console logs etc)

Parses '%22' as a '"', which causes a parsing error.

Library version

Newest

Browsers

• Chrome 49+
• Firefox 45+

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.

Make sure the issue concerns the BlenderGIS addon and not Blender itself.

In preference do not ask for help here, only report

The current portable build script is getting messy and unnecessarily complex. We should separate the Linux build of portable out of the python script and into our Scons build scripts. The portable python build script then would be dedicated to windows.

To Reproduce

See the portable build script.

Expected behavior

Portable for Windows is built with the dedicate python script a

See below; version 2.4.2 from the ubuntugis ppa.

Expected output is just the version information, no crash.

$ gdal2tiles.py --version
GDAL 2.4.2, released 2019/06/28
Traceback (most recent call last):
  File "/usr/bin/gdal2tiles.py", line 2927, in <module>
    main()
  File "/usr/bin/gdal2tiles.py", line 2917, in main
    input_file, output_folder, options = process_args(argv[1:])

Would be good to update example in docs based on: https://rasterio.groups.io/g/main/topic/28593754

Also, in the concurrent processing docs it states:

Python threads can read and write concurrently.

However, it does not actually do the read/write concurrently in the example and in the linked discussion it says read/write is not thread safe. Do you have recommendations for thread safe

The stars package implements methods—slice.stars(), pull.stars(), etc.—for the generic dplyr verbs slice(), pull(): , etc. Since the dispatch starts with the generic function (which is exported by dplyr) before going to the class-specific method, you can't slice or pull a stars object if dplyr isn't loaded.

That may be obvious to experienced R users, but I don't think it w

ubuntu@ip-172-31-31-248:~$ python gdal2tiles-leaflet/gdal2tiles.py -z 0-11 -l -p raster -w none /mnt/1000/combined2.png /mnt/1000/out/
Generating Base Tiles:
0...10...20...30...40...50...60...70..ERROR 1: libpng: Read Error
ERROR 1: /mnt/1000/combined2.png, band 1: IReadBlock failed at X offset 0, Y offset 49257
Traceback (most recent call last):
  File "gdal2tiles-leaflet/gdal2tiles.py"

Description

Currently, there is a legacy method of defining the database connection that uses the following environment variables:

• DB_HOSTNAME=postgres
• DB_USERNAME=opendatacube
• DB_PASSWORD=opendatacubepassword
• DB_DATABASE=opendatacube
• DB_PORT=5432

This came from the first Dockerfile, which used an entrypoint to set the values in a configuration file.

This h

Essentially this vignette is a single overview of stack and crop_image.
It's missing a clean description of stack and how stack works with the parameter options.
It's also missing crop_all.

We should decide whether to have 2 vignettes - or just organize this one to show all three functions:

• crop_image
• crop_all
• stack

https://earthpy.readthedocs.io/en/latest/gallery_vign

Describe the bug
There are unused variables in three temporal (t.) modules and some tests. It is not immediately clear if these can be just removed or they are actually supposed to be used and the code need to be fixed. Note that one is module option.

To Reproduce

Go to the temporal directory in GRASS GIS source code:

cd temporal

(Install Flake8 and) Run:

To do: Add a section to the Wiki on writing image processing algorithms to process collections of imagery using the Group Items By capability in the RFT properties.

In some ways fasterize does diverge from rasterize (e.g., #13). These should be tersely described in the README/vignette and function documentation.

Problem description

There are a few common problems that can occur where a row for the scopes integration is unsuccessful:

• we've mistyped the URL, in which case, the API responds with a 404, but we get Left("Body deserialization failed")
• we don't check scopes in a route, in which case the API (probably) responds with a 400 if the route does any writing (we're not sending a body a

When using an ASCII grid with different cell lengths in the x and y directions, I get this error:

Uncaught Error: Invalid LatLng object: (NaN, NaN)
    at new M (leaflet.js:5)
    at Object.C [as latLng] (leaflet.js:5)
    at e.value (Field.js:73)
    at e.value (VectorField.js:176)
    at new e (VectorField.js:83)
    at Function.value (VectorField.js:21)
    at leaflet_panes.js:11

Follow-up to boostorg/gil#474 (review), we should run another review and remove remains of Boost.MPL e.g. #include <boost/mp11/mpl.hpp>

The documentation suggests that when when uploading imagery to cloud storage as .mrf files, instead of specifying a folder for the raster proxies to be created, a .csv file can be specified (page 12 of OptimizeRasters_UserDoc.pdf). However, when trying to do this, the Raster Proxy Output Folder input box throws an error (see screenshot below).

![image](https://user-images.githubusercontent.c

$ radon cc --min B rioxarray --total-average
rioxarray/rioxarray.py
    M 1080:4 RasterArray.to_raster - B
    M 697:4 RasterArray.reproject - B
    M 861:4 RasterArray.clip_box - B
    M 290:4 XRasterBase.write_crs - B
    M 529:4 RasterArray.nodata - B
    M 562:4 RasterArray.resolution - B
    M 603:4 RasterArray._check_dimensions - B
    M 1172:4 RasterDataset.crs - B
    M 223:

Expected behavior and actual behavior

Cropping any raster with any GeoVector should work. Instead, if the GeoVector is bigger than the world, an error is raised.

simple_world.geojson.zip

Steps to reproduce the probl