>
> Probably that's it, the explicit SRS. I started with data that have native
> SRS epsg:3067 and OpenJUMP JML format which has no means for holding SRS.
> Conversion into ES gives always an empty layer, just the schema gets
> inserted but no geometries, even is I use -s_srs and -t_srs.
>
>
> I made a test and it appears to work but isn't is confusing because it
> makes a different effect than with most other drivers? Manual page
> http://www.gdal.org/ogr2ogr.html tells "-a_srs srs_def: Assign an
> output SRS " . With Elastic Search if you use -a_srs epsg:3067 the output
> SRS
Even Rouault wrote:
>>
>> Probably that's it, the explicit SRS. I started with data that have native
>> SRS epsg:3067 and OpenJUMP JML format which has no means for holding SRS.
>> Conversion into ES gives always an empty layer, just the schema gets
>> inserted but no geometries, even is I use
Even Rouault spatialys.com> writes:
>
> Hi Jukka,
> > but I can still save for example
> > EPSG:3067 geometries without transforming them into EPSG:4326.
>
> On-the-fly reprojection should occur normally (provided that your source
layer
> has explicit SRS)
Probably that's it, the explicit
Hi Jukka,
> Are the geometries which are stored into Elastic Search supposed to be in
> EPSG:4326?
That's my understanding of ES doc. For geo_point mapping, you can put
arbitrary coordinates if I remember, but I believe the behaviour is undefined.
So basically the driver is reprojecting
Hi,
Are the geometries which are stored into Elastic Search supposed to be in
EPSG:4326? Now I can see that the driver is writing EPSG:4326 definitions
into the metadata of the ES index but I can still save for example EPSG:3067
geometries without transforming them into EPSG:4326.
-Jukka
