You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #10510 and #10539 the discussion involves adding an optional mapping parameter to throw an exception if an input GeoJSON contains coordinates with >2 dimensions.
The loosely defined GeoJSON spec (at http://geojson.org/geojson-spec.html#positions) states: "There must be at least two elements, and may be more." With no limit on how many elements can be in a coordinate. Since ES currently supports 2D only, it seems natural for default behavior to throw an exception if a coordinate is received with any more than 2 elements. There are a few "user-friendly" questions surrounding this (which have cropped up more than once on the issue list)
Should another validation parameter be added to optionally fail on coordinates > 2d?
Should it be part of the existing 'validate' parameter?
Should the default throw an exception for >2d coordinates forcing users to set the parameter to handle pre-existing geojson data?
The text was updated successfully, but these errors were encountered:
@rjernst I have outstanding pr #10248 that deprecates the "old" validate and normalize options. I can update the behavior there prior to merge /cc @colings86
Related to #10510 and #10539 the discussion involves adding an optional mapping parameter to throw an exception if an input GeoJSON contains coordinates with >2 dimensions.
The loosely defined GeoJSON spec (at http://geojson.org/geojson-spec.html#positions) states: "There must be at least two elements, and may be more." With no limit on how many elements can be in a coordinate. Since ES currently supports 2D only, it seems natural for default behavior to throw an exception if a coordinate is received with any more than 2 elements. There are a few "user-friendly" questions surrounding this (which have cropped up more than once on the issue list)
The text was updated successfully, but these errors were encountered: