> In this case, I will follow GitHub recommendation [1] to update a PR
> with separate/new commits, but not push-forcing.
> For example, I'm about to update .travis.yml with libjxr-dev installation in
> some of gdal/ci/travis/.../before_install.sh scripts, which I'm going to
> push as a new commit.
On 15 March 2017 at 21:21, Mateusz Loskot wrote:
> On 15 March 2017 at 06:00, Kurt Schwehr wrote:
>> Mateusz,
>>
>> I tried to take a quick stab at some initial review comments. It got
>> confusing with too many comments in a small section of code. Sorry. I'm
>> not used to reviewing in github
On 15 March 2017 at 06:00, Kurt Schwehr wrote:
> Mateusz,
>
> I tried to take a quick stab at some initial review comments. It got
> confusing with too many comments in a small section of code. Sorry. I'm
> not used to reviewing in github. Hopefully you can follow what I'm getting
> at with th
Nikos Alexandris
Why does (attempting to) import a 38m pixel resolution GHSL [0] GeoTIFF
layer, ie GHS_BUILT_LDS1990_GLOBE_R2016A_3857_38_v1_0_p1.tif, in GRASS'
db progress slow?
Markus M:
because it is a very large raster map: Size is 507904, 647168
Markus Neteler:
Can you elaborate a
