search

gisaia / ARLAS-proc

Workaround about data ingestion with computing frameworks
Apache License 2.0
4 stars 0 forks source link

Better handle geometries with a single point #170

Open WilliGautier opened 4 years ago

WilliGautier commented 4 years ago

When only one point is available (fragment with a single geopoint), its trail is a POINT wkt object. Ok.

During the course extraction, some geometries are constructed, in particular the track.motion.visible.trail, and are MULTILINESTRING wkt geometries. In the case of a single geopoint, its location is repeated (single linestring with twice the same location).

However, this geometry with duplicated location crash the ES indexing. (loader course)

This case should be handled differently. Maybe POINT wkt object, in these "single point" case, for fields as track.motion.visible.trail?

sfalquier commented 4 years ago

@WilliGautier is this bug still not fixed?

sfalquier commented 4 years ago

@WilliGautier is this issue still relevant?

WilliGautier commented 4 years ago

Actually we decided to lighten the index and the track.motion.visible.trail is no longer indexed then it doesn't appear anymore. However I'm not sure if the bug has been fixed.

sfalquier commented 4 years ago

In that case, if it is not fixed, do we have to fix it since it's not visible. Is it required for ce processing? If not, maybe we should close the issue without fixing it.