Support WKT syntax in geo_point and geo_shape #9120
Labels
Comments
clintongormley
added
the
:Analytics/Geo
|
+1 |
|
yes adding support for WKT would be awesome! |
|
@nknize is WKT on your roadmap? |
|
+1 |
|
+100 |
|
@nknize ping about this and whether it's on the roadmap? |
|
+1 |
|
ping again @dakrone @nknize @clintongormley. The recent geo performance boost will probably require WKT support to ease work with geo-shape with Elastic. |
nknize
added a commit
to nknize/elasticsearch
that referenced
this issue
Dec 5, 2017
This commit adds WKT support to Geo ShapeBuilders. This supports the following format: POINT (30 10) LINESTRING (30 10, 10 30, 40 40) BBOX (-10, 10, 10, -10) POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10)) POLYGON ((35 10, 45 45, 15 40, 10 20, 35 10), (20 30, 35 35, 30 20, 20 30)) MULTIPOINT ((10 40), (40 30), (20 20), (30 10)) MULTIPOINT (10 40, 40 30, 20 20, 30 10) MULTILINESTRING ((10 10, 20 20, 10 40),(40 40, 30 30, 40 20, 30 10)) MULTIPOLYGON (((30 20, 45 40, 10 40, 30 20)), ((15 5, 40 10, 10 20, 5 10, 15 5))) MULTIPOLYGON (((40 40, 20 45, 45 30, 40 40)), ((20 35, 10 30, 10 10, 30 5, 45 20, 20 35), (30 20, 20 15, 20 25, 30 20))) GEOMETRYCOLLECTION (POINT (30 10), MULTIPOINT ((10 40), (40 30), (20 20), (30 10))) closes elastic#9120
nknize
added a commit
that referenced
this issue
Dec 5, 2017
This commit adds WKT support to Geo ShapeBuilders. This supports the following format: POINT (30 10) LINESTRING (30 10, 10 30, 40 40) BBOX (-10, 10, 10, -10) POLYGON ((30 10, 40 40, 20 40, 10 20, 30 10)) POLYGON ((35 10, 45 45, 15 40, 10 20, 35 10), (20 30, 35 35, 30 20, 20 30)) MULTIPOINT ((10 40), (40 30), (20 20), (30 10)) MULTIPOINT (10 40, 40 30, 20 20, 30 10) MULTILINESTRING ((10 10, 20 20, 10 40),(40 40, 30 30, 40 20, 30 10)) MULTIPOLYGON (((30 20, 45 40, 10 40, 30 20)), ((15 5, 40 10, 10 20, 5 10, 15 5))) MULTIPOLYGON (((40 40, 20 45, 45 30, 40 40)), ((20 35, 10 30, 10 10, 30 5, 45 20, 20 35), (30 20, 20 15, 20 25, 30 20))) GEOMETRYCOLLECTION (POINT (30 10), MULTIPOINT ((10 40), (40 30), (20 20), (30 10))) closes #9120
This was referenced Dec 6, 2017
|
thanks. helped a lot, I had a serializer for each type of shape, now I just had to set it as a string and works for all types of shapes, also the overhead to json-serialize this data is now zero. thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So indexing stuff like
POINT (30 10)andPOLYGON ((30 10, 40 40, 20 40, 10 20, 30 10))can be done into geo_point and geo_shape field typesThe text was updated successfully, but these errors were encountered: