* [file upload] document file upload privileges and provide actionable UI when failures occur * doc link * call hasImportPermission * docs tweeks * tslint * Update docs/maps/import-geospatial-data.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/maps/import-geospatial-data.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/maps/import-geospatial-data.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/maps/import-geospatial-data.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * review feedback * fix bullet list format * clean-up i18n ids * Update docs/maps/import-geospatial-data.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * documenation review feedback * add period to last privilege bullet item Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
70 lines
2.9 KiB
Text
70 lines
2.9 KiB
Text
[role="xpack"]
|
|
[[import-geospatial-data]]
|
|
== Import geospatial data
|
|
|
|
To import geospatical data into the Elastic Stack, the data must be indexed as {ref}/geo-point.html[geo_point] or {ref}/geo-shape.html[geo_shape].
|
|
Geospatial data comes in many formats.
|
|
Choose an import tool based on the format of your geospatial data.
|
|
|
|
[discrete]
|
|
[[import-geospatial-privileges]]
|
|
=== Security privileges
|
|
|
|
The {stack-security-features} provide roles and privileges that control which users can upload files.
|
|
You can manage your roles, privileges, and
|
|
spaces in **{stack-manage-app}** in {kib}. For more information, see
|
|
{ref}/security-privileges.html[Security privileges],
|
|
<<kibana-privileges, {kib} privileges>>, and <<xpack-kibana-role-management, {kib} role management>>.
|
|
|
|
To upload GeoJSON files in {kib} with *Maps*, you must have:
|
|
|
|
* The `all` {kib} privilege for *Maps*.
|
|
* The `all` {kib} privilege for *Index Pattern Management*.
|
|
* The `create` and `create_index` index privileges for destination indices.
|
|
* To use the index in *Maps*, you must also have the `read` and `view_index_metadata` index privileges for destination indices.
|
|
|
|
To upload CSV files in {kib} with the *{file-data-viz}*, you must have privileges to upload GeoJSON files and:
|
|
|
|
* The `manage_pipeline` cluster privilege.
|
|
* The `read` {kib} privilege for *Machine Learning*.
|
|
* The `machine_learning_admin` or `machine_learning_user` role.
|
|
|
|
|
|
[discrete]
|
|
=== Upload CSV with latitude and longitude columns
|
|
|
|
*File Data Visualizer* indexes CSV files with latitude and longitude columns as a geo_point.
|
|
|
|
. Open the main menu, then click *Machine Learning*.
|
|
. Select the *Data Visualizer* tab, then click *Upload file*.
|
|
. Use the file chooser to select a CSV file.
|
|
. Click *Import*.
|
|
. Select the *Advanced* tab.
|
|
. Set *Index name*.
|
|
. Click *Add combined field*, then click *Add geo point field*.
|
|
. Fill out the form and click *Add*.
|
|
. Click *Import*.
|
|
|
|
[discrete]
|
|
=== Upload a GeoJSON file
|
|
|
|
*Upload GeoJSON* indexes GeoJSON features as a geo_point or geo_shape.
|
|
|
|
. <<maps-create, Create a new map>>.
|
|
. Click *Add layer*.
|
|
. Select *Upload GeoJSON*.
|
|
. Use the file chooser to select a GeoJSON file.
|
|
. Click *Import file*.
|
|
|
|
[discrete]
|
|
=== Upload data with IP addresses
|
|
|
|
The GeoIP processor adds information about the geographical location of IP addresses.
|
|
See {ref}/geoip-processor.html[GeoIP processor] for details.
|
|
For private IP addresses, see https://www.elastic.co/blog/enriching-elasticsearch-data-geo-ips-internal-private-ip-addresses[Enriching data with GeoIPs from internal, private IP addresses].
|
|
|
|
[discrete]
|
|
=== Upload data with GDAL
|
|
|
|
https://www.gdal.org/[GDAL] (Geospatial Data Abstraction Library) contains command line tools that can convert geospatial data between 75 different geospatial file formats and index that geospatial data into {es}.
|
|
See https://www.elastic.co/blog/how-to-ingest-geospatial-data-into-elasticsearch-with-gdal[Ingest geospatial data into Elasticsearch with GDAL] for details.
|