Closed 4nonym0us closed 5 years ago
Moving the issue to appropriate repository.
right, i was thinking you probably mean to ask this in https://github.com/elastic/elasticsearch
@sckott yeah, that's what I did. Sorry for opening issue here (had too much tabs opened in my browser and created issue here accidentally).
Having WKT support only for
geo_shape
and not forgeo_point
is a bit confusing because WKT specification has GeoPoint representation.Would't it be good to have an option to use WKT's point syntax
POINT (X, Y)
forgeo_point
for consistency as support even for more complex WKT primitives and multipart geometries is already present forgeo_shape
?