On vendredi 5 mai 2017 20:09:17 CEST Hugues François wrote:
> Sorry, it took me sometimes to answer. I don't know what happenned with the
> copy/paste from terminal but the url was truncated.
>
> However, it ran the gdalinfo with the right layer name and it is after this
> text.
So it looks like
Hi,
If you don't mind some advertising of own work, have a look at:
https://grass.osgeo.org/grass72/manuals/addons/i.landsat8.qc.html
If you want to do this using gdal, the python code might be a source of
inspiration...
Cheers,
Stefan
Von: gdal-dev
All,
Just wanted to contribute some experiences we have gained at Mapbox while
doing our C++ work on attempting to work towards a common format on some
libraries. We have found that clang format is very helpful, but it is still
also very good if you have written documentation on how to follow the
Sorry, it took me sometimes to answer. I don't know what happenned with the
copy/paste from terminal but the url was truncated.
However, it ran the gdalinfo with the right layer name and it is after this
text.
Regards,
Hug
gdalinfo
"WMTS:http://wxs.ign.fr/an7nvfzojv5wa96dsga5nk8w/geopor
astyle would certainly work too.
I find clang-format more robust than almost all other formatting tools as
Mateusz described. As for workflow, there are multiple possible routes as
to how to go about this. I personally write pretty messy code when I'm
working and then just do a format pass befor
On vendredi 5 mai 2017 18:18:54 CEST Hugues François wrote:
> WMTS:http://wxs.ign.fr/{KEY}/geoportail/wmts?SERVICE=WMTS&REQUEST=GetCapabil
> ities,layer=GEOGRAPHICALGRIDSYST
OK, so now try
gdalinfo
"WMTS:http://wxs.ign.fr/{KEY}/geoportail/wmts?SERVICE=WMTS&REQUEST=GetCapabilities,layer=GEOGRAPHI
Hi,
Thanks for your quick reply. No, I did'nt try this simple command.
Here is the output (I removed some of them, keeping just the one I want to use
but the whole output is attached to the message)
Regards,
Hug
gdalinfo
"WMTS:http://wxs.ign.fr/{KEY}/geoportail/wmts?SERVICE=WMTS&REQUEST=GetCapa
> -Original Message-
> From: gdal-dev [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of
> hugfr
> Sent: Friday, May 5, 2017 12:10
> To: gdal-dev@lists.osgeo.org
> Subject: [gdal-dev] WMTS "No zoom level found"
>
> Hello,
>
> I try to create an xml file suitable for gdal wmts but I go
Hi Jonathan,
Jonathan Greenberg-4 wrote
> USGS, in their infinite wisdom, decided to embed what is effectively a
> 1-bit, 16-band byte-interleaved-by-pixel image into a 16-bit, single-band
> geotiff for the Landsat quality mask. I could write some crazy
> translation
> program that "reverse engin
On vendredi 5 mai 2017 08:09:30 CEST hugfr wrote:
> Hello,
>
> I try to create an xml file suitable for gdal wmts but I got this error "no
> zoom level found" (when I try a gdalinfo) and I don't understand where does
> the problem come from. I found this post about zoom level management :
> http:/
Hello,
I try to create an xml file suitable for gdal wmts but I got this error "no
zoom level found" (when I try a gdalinfo) and I don't understand where does
the problem come from. I found this post about zoom level management :
http://osgeo-org.1560.x6.nabble.com/WMTS-Need-TileLevel-option-Serve
On 5 May 2017 at 13:35, Even Rouault wrote:
>
> In case we want to have a policy regarding braces around single statements,
> one finding coming from the openjpeg discussion I mentionned :
>
> """
> Moreover, concerning braces around single statements, it seems astyle does
> this with the add-brac
great, thanks for updating the wiki! This is great for your karma, and
really helps the next person hitting your issue.
Please always reply to the mailing list. Have a nice weekend,
-jeff
On 2017-05-05 6:06 AM, Candy, Liam wrote:
Hi Jeff,
I was going to update the wiki, but have issue
On 5 May 2017 at 13:11, Even Rouault wrote:
>> I made (or copied and agreed with) the statement that the best way to
>> reliably maintain consistent code formatting is to learn how to write
>> properly formatted code and ensure (eg. via code review) all developers
>> learn it too.
>
>> Certainly,
On vendredi 5 mai 2017 10:45:33 CEST Mateusz Loskot wrote:
> On 5 May 2017 at 09:22, Even Rouault wrote:
> >> Please, let's forget about astyle.
> >
> > Because you consider it more limited feature-wise than clang-format ?
>
> Because, clang-format is based on the same tooling as LLVM/clang,
> a
On 05/05/2017 01:11 PM, Even Rouault wrote:
> By the way, git cl format doesn't seem available out-of-the-box on my Ubuntu
> 16.04. Perhaps
> there's an additional package to install ?
There is git2cl, but that only supports the GNU ChangeLog format.
IIRC git-cl is part of clang-format, but I d
> I made (or copied and agreed with) the statement that the best way to
> reliably maintain consistent code formatting is to learn how to write
> properly formatted code and ensure (eg. via code review) all developers
> learn it too.
> Certainly, tools like `git cl format` would be very handy to le
On 5 May 2017 at 09:22, Even Rouault wrote:
>> Please, let's forget about astyle.
>
> Because you consider it more limited feature-wise than clang-format ?
Because, clang-format is based on the same tooling as LLVM/clang,
at least the same tokenizer/lexer, so it can process complex and
convoluted
Jonathan Greenberg-4 wrote
> Folks:
>
> USGS, in their infinite wisdom, decided to embed what is effectively a
> 1-bit, 16-band byte-interleaved-by-pixel image into a 16-bit, single-band
> geotiff for the Landsat quality mask. I could write some crazy
> translation
> program that "reverse enginee
Hi Mateusz,
> Please, let's forget about astyle.
Because you consider it more limited feature-wise than clang-format ?
(https://trac.osgeo.org/geos/wiki/RFC4 : "wrapping long lines whether of code,
strings,
arrays - something which AStyle has no way of doing")
I'm wondering what you mean by "N
20 matches
Mail list logo
