-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Maps] GeoJSON upload can't index polygons #61794
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
This seems to be an underlying Elasticsearch issue. elastic/elasticsearch#54441 |
@kevinkraft as a workaround I managed to index the wards geojson file after passing it through mapshaper.org: just import and then export it again and it should be OK in Kibana. |
@jsanz It isn't working yet. How long should the "Write to index" take? What options did you use on the mapshaper site? |
For the Leeds file, on my personal laptop, it indexes it immediately. I did a quick (1 minute) video of the processing using mapshaper cli, I hope it helps. Those geojson files follow a old spec that includes a In fact, if you run the mapshaper command with the $ mapshaper -i leeds_wards.geojson -clean -verbose -o leeds_wards.fix.geojson
[i] Importing: leeds_wards.geojson
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Warning: reversing a CCW ring
[i] Removed 117 duplicate points
[i] - 56ms
[clean] Find mosaic rings 5ms
[clean] Detect holes (holes: 0, enclosures: 1) 3ms
[clean] Retained 21 of 21 features
[clean] - 63ms
[o] Wrote leeds_wards.fix.geojson
[o] - 23ms |
@jsanz That's great thanks. It worked for the Wakefiled geojson, but it didn't work for the Leeds geojson. I used an alternate file from another website (https://martinjc.github.io/UK-GeoJSON/), and used the map shaper CLI, and it worked. |
Glad you get it working, thanks for reporting; this will help us to make GeoJSON upload more resilient to somehow invalid files. |
Hi I'm having the same issue, my input data comes from: TopoJSON. I did the following:
After uploading it to Kibana it seems to hang on "Writing to index: ch-municipalities". Any ideas? |
@michaelimfeld your geojson file is not in WGS84 coordinate system, you need to follow the repo instructions on having the coordinates in In any case, we definitely can do better on reporting issues in the upload interface. |
@michaelimfeld I got no problems on importing that file in log
|
Whoops my reverse proxy was limiting the max request size. Maybe some sort of error message on the UI would be nice to indicate that the request wasn't successful. Now I'm facing a different issue, the importer seems to mess up the encoding: |
That's already reported at #56604 You may want to try the OGR path as described on this blogpost, just as of today I answered another post adding some details on how to use it with Docker, since OGR/GDAL is still to officially release a version with support for Elasticsearch 7 |
Awesome works, thank you @jsanz ! |
Hi all... I've got a sample countries json file from here https://datahub.io/core/geo-countries... ran into the hanging on "writing to index" issue while uploading it to Maps. Same issue after cleaning it with mapshare. Any tips would be appreciated.... using Kibana 7.6.2. |
thanks for reporting @shayant85 these are my results after testing this dataset in particular:
|
Thanks for the info @jsanz ... I think some of the issues we are seeing are also related to some stuff being cached in Kibana / Maps if you had an unsuccessful upload attempt (In my case unsuccessful refers to getting stuck on "writing to index" indefinitely). For instance I've noticed that if after an unsuccessful attempt you simply click 'Cancel' and try to add a new layer again with the - presumably - fixed file from mapshare, then it will not work. However, if you either restart Kibana or refresh the browser (sometimes) the same fixed file will work. I had this happen with two files which I had fixed (AKA imported/exported) via mapshare so thought it is worth mentioning. |
Closed by #92620. Just tried loading leeds wards geojson file and it now successfully imports the file without any UI hangs or leaving the add layer button disabled. The import indexes 21 features and fails indexing 3 features. |
Kibana version:
7.6.1, master
Elasticsearch version:
7.6.1, snapshot
Server OS version:
Ubuntu 9.10
Browser version:
Version 1.5.115 Chromium: 80.0.3987.149 (Official Build) (64-bit)
Browser OS version:
Ubuntu 9.10
Original install method (e.g. download page, yum, from source, etc.):
Docker image, from source
Describe the bug:
A polygon dataset is not being successfully indexed by GeoJSON Upload.
Steps to reproduce:
Expected behavior:
The documents are created and layer can be added to the map.
Screenshots (if relevant):
Errors in browser console (if relevant):
I can't see any errors on the browser
Provide logs and/or server output (if relevant):
I can't see any errors on the Kibana or ES logs when running from source, on the docker image I could see these errors
trace
Any additional context:
Reported by @kevinkraft at https://discuss.elastic.co/t/geojson-upload-hangs-on-creating-index/225661
The text was updated successfully, but these errors were encountered: