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 <[email protected]>, 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 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 feature before calling > CreateFeature() > > Even > > > > > Francesco > > > > Il 17 mar 2020, 22:13 +0100, Even Rouault <[email protected]>, ha > scritto: > > > 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. > > > By default, the mapping name is "FeatureCollection" and the documents > > > will be written as GeoJSON Feature objects. If another mapping name > > > is chosen, a more "flat" structure will be used. This option is > > > ignored when converting to Elasticsearch >=7 (see `Removal of mapping > > > types > > > <https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-o > > > f-types.html>`__). With ElasticSearch 7 or later, a "flat" structure is > > > always used. > > > > > > Even > > > > > > -- > > > Spatialys - Geospatial professional services > > > http://www.spatialys.com > > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
