@@ -175,7 +175,7 @@ PUT /example
175
175
"location": {
176
176
"type": "geo_shape",
177
177
"tree": "quadtree",
178
- "precision": "1m "
178
+ "precision": "100m "
179
179
}
180
180
}
181
181
}
@@ -186,8 +186,8 @@ PUT /example
186
186
// TESTSETUP
187
187
188
188
This mapping maps the location field to the geo_shape type using the
189
- quad_tree implementation and a precision of 1m . Elasticsearch translates
190
- this into a tree_levels setting of 26 .
189
+ quad_tree implementation and a precision of 100m . Elasticsearch translates
190
+ this into a tree_levels setting of 20 .
191
191
192
192
[float]
193
193
===== Performance considerations
@@ -364,7 +364,6 @@ POST /example/doc
364
364
}
365
365
--------------------------------------------------
366
366
// CONSOLE
367
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
368
367
369
368
The following is an example of a Polygon with a hole in WKT:
370
369
@@ -376,7 +375,6 @@ POST /example/doc
376
375
}
377
376
--------------------------------------------------
378
377
// CONSOLE
379
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
380
378
381
379
*IMPORTANT NOTE:* WKT does not enforce a specific order for vertices thus
382
380
ambiguous polygons around the dateline and poles are possible.
@@ -411,7 +409,7 @@ POST /example/doc
411
409
}
412
410
--------------------------------------------------
413
411
// CONSOLE
414
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836 ]
412
+ // TEST[catch:/mapper_parsing_exception/ ]
415
413
416
414
An `orientation` parameter can be defined when setting the geo_shape mapping (see <<geo-shape-mapping-options>>). This will define vertex
417
415
order for the coordinate list on the mapped geo_shape field. It can also be overridden on each document. The following is an example for
@@ -425,14 +423,12 @@ POST /example/doc
425
423
"type" : "polygon",
426
424
"orientation" : "clockwise",
427
425
"coordinates" : [
428
- [ [-177.0, 10.0], [176.0, 15.0], [172.0, 0.0], [176.0, -15.0], [-177.0, -10.0], [-177.0, 10.0] ],
429
- [ [178.2, 8.2], [-178.8, 8.2], [-180.8, -8.8], [178.2, 8.8] ]
426
+ [ [100.0, 0.0], [100.0, 1.0], [101.0, 1.0], [101.0, 0.0], [100.0, 0.0] ]
430
427
]
431
428
}
432
429
}
433
430
--------------------------------------------------
434
431
// CONSOLE
435
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
436
432
437
433
[float]
438
434
===== http://www.geojson.org/geojson-spec.html#id5[MultiPoint]
@@ -484,7 +480,6 @@ POST /example/doc
484
480
}
485
481
--------------------------------------------------
486
482
// CONSOLE
487
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
488
483
489
484
The following is an example of a list of WKT linestrings:
490
485
@@ -496,7 +491,6 @@ POST /example/doc
496
491
}
497
492
--------------------------------------------------
498
493
// CONSOLE
499
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
500
494
501
495
[float]
502
496
===== http://www.geojson.org/geojson-spec.html#id7[MultiPolygon]
@@ -518,7 +512,6 @@ POST /example/doc
518
512
}
519
513
--------------------------------------------------
520
514
// CONSOLE
521
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
522
515
523
516
The following is an example of a list of WKT polygons (second polygon contains a hole):
524
517
@@ -530,7 +523,6 @@ POST /example/doc
530
523
}
531
524
--------------------------------------------------
532
525
// CONSOLE
533
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
534
526
535
527
[float]
536
528
===== http://geojson.org/geojson-spec.html#geometrycollection[Geometry Collection]
@@ -557,7 +549,6 @@ POST /example/doc
557
549
}
558
550
--------------------------------------------------
559
551
// CONSOLE
560
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
561
552
562
553
The following is an example of a collection of WKT geometry objects:
563
554
@@ -569,7 +560,6 @@ POST /example/doc
569
560
}
570
561
--------------------------------------------------
571
562
// CONSOLE
572
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
573
563
574
564
575
565
[float]
@@ -585,12 +575,11 @@ POST /example/doc
585
575
{
586
576
"location" : {
587
577
"type" : "envelope",
588
- "coordinates" : [ [-45 .0, 45 .0], [45 .0, -45 .0] ]
578
+ "coordinates" : [ [100 .0, 1 .0], [101 .0, 0 .0] ]
589
579
}
590
580
}
591
581
--------------------------------------------------
592
582
// CONSOLE
593
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
594
583
595
584
The following is an example of an envelope using the WKT BBOX format:
596
585
@@ -600,11 +589,10 @@ The following is an example of an envelope using the WKT BBOX format:
600
589
--------------------------------------------------
601
590
POST /example/doc
602
591
{
603
- "location" : "BBOX (-45 .0, 45 .0, 45 .0, -45 .0)"
592
+ "location" : "BBOX (100 .0, 102 .0, 2 .0, 0 .0)"
604
593
}
605
594
--------------------------------------------------
606
595
// CONSOLE
607
- // TEST[skip:https://github.com/elastic/elasticsearch/issues/23836]
608
596
609
597
[float]
610
598
===== Circle
@@ -618,7 +606,7 @@ POST /example/doc
618
606
{
619
607
"location" : {
620
608
"type" : "circle",
621
- "coordinates" : [-45 .0, 45 .0],
609
+ "coordinates" : [101 .0, 1 .0],
622
610
"radius" : "100m"
623
611
}
624
612
}
0 commit comments