Alan,
I'm also supportive of your change while not having a strong opinion
on the ogr-brush-1 issue. Thanks for showing some love to feature
styles *including* the specification.
Best regards,
Frank
On Wed, Jan 3, 2018 at 12:52 AM, Alan Thomas
wrote:
> Thanks for
Thanks for the feedback, Even. If there is no other feedback in the
next few days I will merge the change, as well as an extra code fix to
implement change 8.
On 2 January 2018 at 21:47, Even Rouault wrote:
>> 5. [...] change the definition of
>> ogr-brush-1 to mean a
Sorry about this! I knew it was only a matter of time before I would
break the build.
In r41170 I have got rid of std::to_string for now. It's easy enough
to replace it with CPLString().Printf(...).
Alan
On 3 January 2018 at 06:34, Kurt Schwehr wrote:
> +gdal-dev (oops!)
>
>
Hi list,
I see that there is a driver for Sentinel-1 manifest.safe and I tested it
against the tough case of the SLC (complex).
These products consists of three HH-HV dual-pol images, they only overlap at
the edges (see screen shot, when I load the *.tiff one by one in OpenEV viewer)
I'm trying to account for building parallax differences between images
collected at different viewing angles. When I use a DSM created from VRICON
data as my DEM source, I notice that building roof pixels are properly
shifted to the correct location; however, they're also left in their
original
+gdal-dev (oops!)
On Tue, Jan 2, 2018 at 11:34 AM, Kurt Schwehr wrote:
> Alan,
>
> https://trac.osgeo.org/gdal/changeset/41166 broke the android build. e.g.
>
> https://travis-ci.org/OSGeo/gdal/jobs/324249526
>
> I tried upgrading the android build to r16b and fixed up the
Alan,
Thanks a lot for this refresh ! I've just a single remark
> 5. [...] change the definition of
> ogr-brush-1 to mean a solid fill in the selected background color;
> change the suggested default for BRUSH bc to transparent (#FF00).
>
> Rationale: The spec is not explicit on how fc and