Hi All,
I'm trying to investigate this issue
https://github.com/geopython/pygeoapi/issues/379 in the pygeoapi project. I'm
using an instance of ES7 and if I understand well the command below:
docker run --rm --network=host -u $(id -u ${USER}):$(id -g ${USER}) \
-v $(pwd):/data \
-e OGR_GEOJSON_
Francesco,
The behaviour in ES7 has been changed. Now only flat structure is supported.
This was discussed in https://github.com/OSGeo/gdal/issues/1246 and I've just
made the doc of the driver clearer:
- **MAPPING_NAME=**\ =name. (Elasticsearch < 7) Name of the mapping type
within the index.
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 b
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 the
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 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
--
Sp