New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GEO] Add optional left/right parameter to GeoJSON #8764
Comments
nknize
added
>feature
discuss
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
labels
Dec 3, 2014
This was referenced Dec 8, 2014
nknize
added a commit
that referenced
this issue
Dec 22, 2014
This feature adds an optional orientation parameter to the GeoJSON document and geo_shape mapping enabling users to explicitly define how they want Elasticsearch to interpret vertex ordering. The default uses the right-hand rule (counterclockwise for outer ring, clockwise for inner ring) complying with OGC Simple Feature Access standards. The parameter can be explicitly specified for an entire index using the geo_shape mapping by adding "orientation":{"left"|"right"|"cw"|"ccw"|"clockwise"|"counterclockwise"} and/or overridden on each insert by adding the same parameter to the GeoJSON document. closes #8764
nknize
added a commit
that referenced
this issue
Dec 22, 2014
This feature adds an optional orientation parameter to the GeoJSON document and geo_shape mapping enabling users to explicitly define how they want Elasticsearch to interpret vertex ordering. The default uses the right-hand rule (counterclockwise for outer ring, clockwise for inner ring) complying with OGC Simple Feature Access standards. The parameter can be explicitly specified for an entire index using the geo_shape mapping by adding "orientation":{"left"|"right"|"cw"|"ccw"|"clockwise"|"counterclockwise"} and/or overridden on each insert by adding the same parameter to the GeoJSON document. closes #8764
nknize
removed
discuss
v2.0.0-beta1
v1.5.0
v1.4.3
>feature
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
labels
Jan 7, 2015
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
This feature adds an optional orientation parameter to the GeoJSON document and geo_shape mapping enabling users to explicitly define how they want Elasticsearch to interpret vertex ordering. The default uses the right-hand rule (counterclockwise for outer ring, clockwise for inner ring) complying with OGC Simple Feature Access standards. The parameter can be explicitly specified for an entire index using the geo_shape mapping by adding "orientation":{"left"|"right"|"cw"|"ccw"|"clockwise"|"counterclockwise"} and/or overridden on each insert by adding the same parameter to the GeoJSON document. closes elastic#8764
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suggested by @clintongormley in issue #5968 this feature will add support for an optional orientation parameter enabling users to specify explicit intent on vertex ordering. Note that orientation is with respect to the map/coordinate system - left = cw, right = ccw
The following provides an example where the order parameter specifies explicit dateline crossing and will result in https://gist.github.com/nknize/d122b243dc63dcba8474. Using 'left' will result in https://gist.github.com/anonymous/82b50b74a7b6d170bfc6 Note that in the following example all holes will be converted to clockwise (left) order for OGC compliance (see #8762).
Absent this parameter functionality will work as described (and implemented) in #8762
The text was updated successfully, but these errors were encountered: