Hi all,
I hope you and yours are well in these times.
I'm wondering how close we are to having support for vsis3 URLs in a TMS
ServerUrl and if it would be worth doing the work to add it.
The issue is that HTTPS requests for non-public S3 objects have to be (as I
understand it) signed per
Thank you. At this point I have decided to do nothing and will wait to see if a
future update will resolve the problem. As I mentioned, despite the error, the
calls to ‚ogr2ogr‘ do produce the results I need (GeoJSON outputs from
Postgresql) and otherwise seem to have no side effects (except a
On mercredi 18 mars 2020 10:49:48 CET Francesco Bartoli wrote:
> Does it mean that can be done only programmatically? How would it be
> translated into a -lco of ogr2ogr?
With ogr2ogr, you can do something like
ogr2ogr [...] {src_ds_name} -sql "select geonameid as _id, ... from ..."
Even
--
Does it mean that can be done only programmatically? How would it be translated
into a -lco of ogr2ogr?
Il 18 mar 2020, 10:36 +0100, Even Rouault , ha
scritto:
> On mercredi 18 mars 2020 09:05:39 CET Francesco Bartoli wrote:
> > Thanks Even, I was misleading the behavior. However, is there a way
On mercredi 18 mars 2020 09:05:39 CET Francesco Bartoli wrote:
> Thanks Even, I was misleading the behavior. However, is there a way to
> ingest and set the value of a unique identifier, for instance geonameid, in
> the key _id of each item of the index?
Yes, you need to set the "_id" field of
Thanks Even, I was misleading the behavior. However, is there a way to ingest
and set the value of a unique identifier, for instance geonameid, in the key
_id of each item of the index?
Francesco
Il 17 mar 2020, 22:13 +0100, Even Rouault , ha
scritto:
> Francesco,
>
> The behaviour in ES7 has
