From c7347490e794b9fcfc5d3c04929a70417adbed65 Mon Sep 17 00:00:00 2001 From: Jesse Schmidt Date: Tue, 5 Sep 2023 15:06:51 -0600 Subject: [PATCH] fix new geoJSON input format version --- docs/data-formats.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/data-formats.md b/docs/data-formats.md index 9a14ef2..f24b6ca 100644 --- a/docs/data-formats.md +++ b/docs/data-formats.md @@ -13,7 +13,7 @@ will work completely with the Aerospike data model. **Note**: GeoJSON and ByteArrays can not be nested in CDTs. -In 2.0.1, a GeoJSON map with the keys "type" and "coordinates" will automatically be understood as a GeoJSON type. +In 2.0.4, a GeoJSON map with the keys "type" and "coordinates" will automatically be understood as a GeoJSON type. ```javascript { @@ -22,7 +22,7 @@ In 2.0.1, a GeoJSON map with the keys "type" and "coordinates" will automaticall } ``` -In version prior to 2.0.1, a GeoJSON object can be provided by sending a base64 encoded GeoJSON string. +In version prior to 2.0.4, a GeoJSON object can be provided by sending a base64 encoded GeoJSON string. Base64 encoding the following string `{"type": "Point", "coordinates": [1.123, 4.156]}` results in `eyJ0eXBlIjogIlBvaW50IiwgImNvb3JkaW5hdGVzIjogWzEuMTIzLCA0LjE1Nl19Cg==`. To write the GeoJSON object use