You now have another reason to zoom in with Elastic Maps. We recently released a global administrative regions layer to support more detailed IP analytics.

administrative-regions-on-dashboard.jpg

administrative-regions-elastic-maps-thumb.jpg

Bring new insights to your IP analytics with a global administrative layer in Elastic Maps

Getting geospatial data into Elasticsearch has never been easier. Ingest your data with GDAL, and start adding layer upon layer within Elastic Maps.

sales-by-district-dashboard.png

sales-by-district-map.png

Ingest geospatial data into Elasticsearch with GDAL

We're adding new country subdivision layers to the Elastic Maps Service so you can take your region map visualizations to a whole new level.

web-visits-by-europe-country-subdivisions-kibana-dashboard.png

web-visits-by-country-subdivisions-kibana-dashboard.png

New Country Subdivision Vectors in the Elastic Maps Service

full-bleed-opt.png

thumbnail.png

Custom basemaps for region and coordinate maps in Kibana

<p>Bonjour les amis. We're constantly adding new vector layers to our <a href="/elastic-maps-service">Elastic Maps Service</a>. Most recently, we've added support for France department boundary vector layers to region maps. You may match results of terms in your Elasticsearch data to department names in either French or English. We have also included INSEE codes for each department as defined by <a href="https://www.insee.fr/">Institut national de la statistique et des études économiques (INSEE)</a> [National Institute of Statistics and Economic Studies]. INSEE collects, analyzes, and distributes information on the French economy and society.
</p><h4>#TalkPay</h4><p>Kaggle has an interesting dataset from INSEE on <a href="https://www.kaggle.com/etiennelq/french-employment-by-town">employment, salaries, and population per town in France</a>. We can import this dataset into Elasticsearch and visualize in Kibana region maps. For this project we will look at salary information.
</p><h4>Prepare the data</h4><p>There are several data files in the Kaggle dataset that require a little massaging before we can import into Elasticsearch. The net_salary_per_town_categories.csv file includes a column called CODGEO which the dataset describes as the INSEE code for the Town. This can be joined to the code_insee column in the name_geographic_information.csv file. The name_geographic_information.csv file includes INSEE codes for the administrative regions, departments, and prefectures for each town. This normalization strategy works well for importing into relational databases, but we will want to join these tables (de-normalize) for importing into Elasticsearch.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt6fef0732095723f2/5c584199516e21cf0b2a1246/blog-france-salary-tables-1.png" data-sys-asset-uid="blt6fef0732095723f2" alt="blog-france-salary-tables-1.png">
</p><p><a href="https://www.sqlite.org/">SQLite</a> is an incredibly useful and versatile database engine that we can use to join these tables. We’ll create a database file and import the CSV files into it.
</p><pre class="prettyprint">sqlite3 france-salary.db
sqlite&gt;.mode csv
sqlite&gt;.import data/net_salary_per_town_categories.csv salary
sqlite&gt;.import data/name_geographic_information.csv names
</pre><p>Let’s preview our data.
</p><pre class="prettyprint">sqlite&gt;.headers on
sqlite&gt;SELECT * FROM salary LIMIT 5;
</pre><table style="font-family:Menlo, Monaco, Consolas, Courier New, monospace;">
<tbody>
<tr>
	<td>CODGEO
	</td>
	<td>LIBGEO
	</td>
	<td>SNHM14
	</td>
	<td>SNHMC14
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01004
	</td>
	<td>Ambérieu-en-Bugey
	</td>
	<td>13.7
	</td>
	<td>24.2
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01007
	</td>
	<td>Ambronay
	</td>
	<td>13.5
	</td>
	<td>22.1
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01014
	</td>
	<td>Arbent
	</td>
	<td>13.5
	</td>
	<td>27.6
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01024
	</td>
	<td>Attignat
	</td>
	<td>12.9
	</td>
	<td>21.8
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01025
	</td>
	<td>Bâgé-la-Ville
	</td>
	<td>13
	</td>
	<td>22.8
	</td>
	<td>...
	</td>
</tr>
</tbody>
</table><pre class="prettyprint">sqlite&gt;SELECT * FROM names LIMIT 5;
</pre><table style="font-family:Menlo, Monaco, Consolas, Courier New, monospace;">
<tbody>
<tr>
	<td>code_insee
	</td>
	<td>nom_commune
	</td>
	<td>code_région
	</td>
	<td>nom_région
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>1004
	</td>
	<td>Ambérieu-en-Bugey
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>1007
	</td>
	<td>Ambronay
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>1014
	</td>
	<td>Arbent
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>1024
	</td>
	<td>Attignat
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>1025
	</td>
	<td>Bâgé-la-Ville
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
</tbody>
</table><p>Notice that the CODGEO column has a leading zero, but the code_insee column does not. This discrepancy appears in the CSV tables. In order to join the two tables, we’ll need to pad the code_insee column with a leading zero. We can do this with a little SQLite magic.
</p><pre class="prettyprint">sqlite&gt;CREATE TABLE names_ready as SELECT substr(‘00000’ || code_insee, -5, 5) as insee_town, * as FROM names;
sqlite&gt;SELECT * FROM names_ready LIMIT 5;
</pre><table style="font-family:Menlo, Monaco, Consolas, Courier New, monospace;">
<tbody>
<tr>
	<td>insee_town
	</td>
	<td>code_insee
	</td>
	<td>nom_commune
	</td>
	<td>code_région
	</td>
	<td>nom_région
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01004
	</td>
	<td>1004
	</td>
	<td>Ambérieu-en-Bugey
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01007
	</td>
	<td>1007
	</td>
	<td>Ambronay
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01014
	</td>
	<td>1014
	</td>
	<td>Arbent
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01024
	</td>
	<td>1024
	</td>
	<td>Attignat
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
<tr>
	<td>01025
	</td>
	<td>1025
	</td>
	<td>Bâgé-la-Ville
	</td>
	<td>82
	</td>
	<td>Rhône-Alpes
	</td>
	<td>...
	</td>
</tr>
</tbody>
</table><p>Now the insee_town column in the new names_ready table can be joined to the CODGEO column in the salary table. But first, let’s create indexes on those columns.
</p><pre class="prettyprint">sqlite&gt;CREATE INDEX idx_insee_town ON names_ready (insee_town);
sqlite&gt;CREATE INDEX idx_codgeo ON salary (CODGEO);
</pre><p>Then we will create a table from a select query to join the salary and names tables and create useful aliases for the field names based on the metadata in the Kaggle dataset.
</p><pre class="prettyprint">sqlite&gt;CREATE TABLE france_salary as 
    SELECT 
    CODGEO as Town_INSEE,
    Nom_commune as Town_Name
    code_région as Region_INSEE,
    nom_région as Region_Name,
    numéro_département as Department_INSEE,
    nom_département as Department_Name,
    Préfecture as Prefecture_Name,
    Numéro_circonscription as Conscription_Number,
    Codes_postaux as Postal_Code,
    Latitude,
    Longitude,
    SNHM14 as mean_net_salary,
    SNHMF14 as mean_net_salary_female,
    SNHMH14 as mean_net_salary_male,
    SNHMC14 as mean_net_salary_hour_executive,
    SNHMFC14 as mean_net_salary_hour_executive_female,
    SNHMHC14 as mean_net_salary_hour_executive_male,
    SNHMP14 as mean_net_salary_hour_middlemanager,
    SNHMFP14 as mean_net_salary_hour_middlemanager_female,
    SNHMHP14 as mean_net_salary_hour_middlemanager_male,
    SNHME14 as mean_net_salary_hour_employee,
    SNHMFE13 as mean_net_salary_hour_employee_female,
    SNHMHE14 as mean_net_salary_hour_employee_male,
    SNHMO14 as mean_net_salary_hour_worker,
    SNHMFO14 as mean_net_salary_hour_worker_female,
    SNHMHO14 as mean_net_salary_hour_worker_male,
    SNHM1814 as mean_net_salary_hour_year18-25,
    SNHMF1814 as mean_net_salary_hour_year18-25_female,
    SNHMH1814 as mean_net_salary_hour_year18-25_male,
    SNHM2614 as mean_net_salary_hour_year26-50,
    SNHMF2614 as mean_net_salary_hour_year26-50_female,
    SNHMH2614 as mean_net_salary_hour_year26-50_male,
    SNHM5014 as mean_net_salary_hour_year50+,
    SNHMF5014 as mean_net_salary_hour_year50+_female,
    SNHMH5014 as mean_net_salary_hour_year50+_male
    FROM salary
    LEFT OUTER JOIN names_ready
    ON salary.CODGEO = names_ready.insee_town;
</pre><h4>Ingest into Elasticsearch</h4><p><a href="/logstash">Logstash</a> is a great way to transform and ingest data for Elasticsearch. A multitude of plugins are available for Logstash. For this project we will use the CSV filter plugin to import data from a CSV file.
</p><p>First, let’s generate a new CSV file called salary_data.csv from the table we created above.
</p><pre class="prettyprint">sqlite&gt;.headers on
sqlite&gt;.mode csv
sqlite&gt;.once salary_data.csv
sqlite&gt;SELECT * from france_salary;
</pre><p>Next we’ll create a config file for Logstash to load this CSV file.
</p><p>Here is our definition for the file input plugin. Change the path to the absolute path of your salary_data.csv file. Specifying /dev/null as the sincedb_path will ensure that Logstash always reads from the top of the file, but beware of this in production as it could create duplicate records.
</p><pre class="prettyprint">input {
   file {
       path =&gt; "/path/to/france-salary/salary_data.csv"
       start_position =&gt; "beginning"
       codec =&gt; plain {
           charset =&gt; "UTF-8"
       }
       sincedb_path =&gt; "/dev/null"
   }
}
</pre><p>Then we must specify how to handle the CSV file using the CSV plugin. Columns in CSV files are always assumed to be text, so we need to use the convert parameter to change numeric fields into float for Elasticsearch.
</p><pre class="prettyprint">filter {
   csv {
       separator =&gt; ","
       skip_header =&gt; "true"
       columns =&gt; [
           "Town_INSEE",
           "Town_Name",
           "Region_INSEE",
           "Region_Name",
           "Department_INSEE",
           "Department_Name",
           "Prefecture_Name",
           "Conscription_Number",
           "Postal_Code",
           "latitude",
           "longitude",
           "mean_net_salary",
           "mean_net_salary_female",
           "mean_net_salary_male",
           "mean_net_salary_hour_executive",
           "mean_net_salary_hour_executive_female",
           "mean_net_salary_hour_executive_male",
           "mean_net_salary_hour_middlemanager",
           "mean_net_salary_hour_middlemanager_female",
           "mean_net_salary_hour_middlemanager_male",
           "mean_net_salary_hour_employee",
           "mean_net_salary_hour_employee_female",
           "mean_net_salary_hour_employee_male",
           "mean_net_salary_hour_worker",
           "mean_net_salary_hour_worker_female",
           "mean_net_salary_hour_worker_male",
           "mean_net_salary_hour_year18_25",
           "mean_net_salary_hour_year18_25_female",
           "mean_net_salary_hour_year18_25_male",
           "mean_net_salary_hour_year26_50",
           "mean_net_salary_hour_year26_50_female",
           "mean_net_salary_hour_year26_50_male",
           "mean_net_salary_hour_year50over",
           "mean_net_salary_hour_year50over_female",
           "mean_net_salary_hour_year50over_male"
       ]
       convert =&gt; {
           "mean_net_salary" =&gt; "float"
           "mean_net_salary_female" =&gt; "float"
           "mean_net_salary_male" =&gt; "float"
           "mean_net_salary_hour_executive" =&gt; "float"
           "mean_net_salary_hour_executive_female" =&gt; "float"
           "mean_net_salary_hour_executive_male" =&gt; "float"
           "mean_net_salary_hour_middlemanager" =&gt; "float"
           "mean_net_salary_hour_middlemanager_female" =&gt; "float"
           "mean_net_salary_hour_middlemanager_male" =&gt; "float"
           "mean_net_salary_hour_employee" =&gt; "float"
           "mean_net_salary_hour_employee_female" =&gt; "float"
           "mean_net_salary_hour_employee_male" =&gt; "float"
           "mean_net_salary_hour_worker" =&gt; "float"
           "mean_net_salary_hour_worker_female" =&gt; "float"
           "mean_net_salary_hour_worker_male" =&gt; "float"
           "mean_net_salary_hour_year18_25" =&gt; "float"
           "mean_net_salary_hour_year18_25_female" =&gt; "float"
           "mean_net_salary_hour_year18_25_male" =&gt; "float"
           "mean_net_salary_hour_year26_50" =&gt; "float"
           "mean_net_salary_hour_year26_50_female" =&gt; "float"
           "mean_net_salary_hour_year26_50_male" =&gt; "float"
           "mean_net_salary_hour_year50over" =&gt; "float"
           "mean_net_salary_hour_year50over_female" =&gt; "float"
           "mean_net_salary_hour_year50over_male" =&gt; "float"
       }
   }
}
</pre><p>The hosts parameter in the output plugin section is the URL to your running Elasticsearch instance. We also specify stdout in json format as an output for debugging. The stdout parameters are not required for ingesting the data.
</p><pre class="prettyprint">output {
   stdout {
codec =&gt; json
   }
   elasticsearch {
       hosts =&gt; ["localhost:9200"]
       index =&gt; "france-example-salary"
   }
}
</pre><p>Let’s call this file france-salary.conf and tell Logstash to use it for ingestion.
</p><pre class="prettyprint">./bin/logstash -f /path/to/france-example-salary.conf
</pre><p>Logstash does not terminate automatically when it reaches the end of the file. Instead it will continue to monitor the CSV file for new data. Since we don’t expect to add more data to the CSV file you can safely stop Logstash using Ctrl-C when the output stops.
</p><h4>Create Maps of Salary by France Department</h4><p>Create a new Index pattern in Kibana to match france-example-*. Then check out the Discover tab to make sure our data is there. It should look something like this.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt48e3902d3813eab5/5c584194a4f817ef0b0e8380/blog-france-salary-kibana-1.png" data-sys-asset-uid="blt48e3902d3813eab5" alt="blog-france-salary-kibana-1.png">
</p><p>Switch to the Visualize tab and create a new region map visualization using the france-example-* index. Set the value to average the mean_net_salary. The shape field should be a terms aggregation on the Department_Name keyword. This will average the mean_net_salary for all towns in each department. You may also want to set the size to large number (e.g. 100) in order to display all department data.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt85d63fa43a3eb131/5c58418e122247d10be8ecf3/blog-france-salary-kibana-2.png" data-sys-asset-uid="blt85d63fa43a3eb131" alt="blog-france-salary-kibana-2.png">
</p><p>Nothing will appear on the map yet because we haven’t defined which map layer to use. Switch to the Options tab and change the vector map to France Departments and the Join Field to Department name (French). Click the “Apply Changes” button and each department on the map will automatically be colored depending on the value. You may have to zoom in to France for a better look.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt9c36d74723265a67/5c5841888c741b010cbf6d26/blog-france-salary-kibana-3.jpg" data-sys-asset-uid="blt9c36d74723265a67" alt="blog-france-salary-kibana-3.jpg">
</p><p>It appears that the departments around Paris have a higher mean net salary. That’s probably not a big surprise though. Let’s try another visualization.
</p><p>Our data has mean net salaries for males and females. So we can check for a gender pay gap for each department. To do this, we’ll need to first create a scripted field. Open the Management tab on the sidebar, select “Index Patterns” and choose the france-example-* pattern if necessary.
</p><p>Open the scripted fields tab and click the “Add a Scripted Field” button. Set the name of the scripted field to Gender Salary Ratio and enter
<code>doc['mean_net_salary_female'].value / doc['mean_net_salary_male'].value
</code> as the script. This will calculate the ratio of female salary to male salary. You may also wish to change the format to percentage. Click the “Create Field” button to add this new field to the index.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltff71054bbfb8f9ed/5c584182a209c1ca0be9df64/blog-france-salary-kibana-4.png" data-sys-asset-uid="bltff71054bbfb8f9ed" alt="blog-france-salary-kibana-4.png">
</p><p>Now create a new region map visualization using the new Gender Salary Ratio field and aggregate by department name. Now we can see which departments appear to have towns with higher and lower disparities between male and female salaries.
</p><p><img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt907d42af64d14c06/5c58417d773ad9030c5c2e6c/blog-france-salary-kibana-5.jpg" data-sys-asset-uid="blt907d42af64d14c06" alt="blog-france-salary-kibana-5.jpg">
</p><p>You can explore further by creating other scripted fields for different position levels and age ranges.
</p><p>Region map visualizations are available on Kibana version 5.5 and up. We are working to release more administrative regions soon. Please create an issue on the <a href="https://github.com/elastic/kibana">Kibana GitHub repository</a> if there’s a region dataset that should be included in Kibana.
</p>

blog-france-salary-kibana-fullbleed.jpg

blog-france-salary-kibana-5.jpeg

Visualizing France Salary Data with Region Maps in Kibana

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

headshot-nick-peihl-300x300.jpg

Senior Software Engineer

Nick Peihl

<p>By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.</p>

Communication Preferences - ONLY for /communication-preferences

<p>제출하면 귀하가 <a href="/kr/legal/elastic-cloud-account-terms" target="_self">Elastic 서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 연락처로 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">선택한 커뮤니케이션</a>을 수신하는 데 동의한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.</p>

<p>By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.</p>

Serverless GDPR Text

<p>제출하면 귀하가 Elastic <a href="/kr/legal/serverless-preview-terms" target="_self">서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 세부 정보를 사용하여 Elastic이 관련 제품 및 서비스에 대해 귀하에게 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">연락할 수 있음</a>을 이해한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.</p>

<p>By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.</p>

Cloud Trial GDPR Text

<p>제출하면 <a href="/kr/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud 서비스 약관</a>에 동의하시게 됩니다. 개인 데이터는 <a href="/kr/legal/privacy-statement">Elastic의 개인정보 취급방침</a>에 따라 처리됩니다.</p>

<p>By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.</p>

Newsletter GDPR Text

<p>제출하면 귀하가 Elastic <a href="/kr/legal/terms-of-use" target="_self">서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 세부 정보를 사용하여 Elastic이 관련 제품 및 서비스에 대해 귀하에게 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">연락할 수 있음</a>을 이해한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.</p>

Explore similar demos

Overview

Speakers

Close

See more insights

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

The content on this page is not available in the selected language.

이 페이지의 콘텐츠는 선택하신 언어로 제공되지 않습니다. Elastic은 다양한 언어로 콘텐츠를 제공하기 위해 최선을 다하고 있습니다.조금만 더 기다려주세요!

Author

Articles by

Learn more

Watch now (no PT)

Watch now

See all top stories

All (no PT translation)

Contact information

Press Release

Share on Reddit

Share this story

Share by Email

Thank you for your interest!

Contact Info

Follow us on Youtube

Load More

Share on LinkedIn

Follow us on LinkedIn

Search Integrations

All Solutions

Video for

Follow us on Twitter

See when this webinar starts in my time zone

내 표준 시간대로 웨비나 시작 시간 확인하기

Register to Watch

Register now

See All Posts

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

참여가 어려우신가요? 등록하시면 녹화 자료를 보내드리겠습니다. 이메일로 관련 콘텐츠도 받아보실 수 있습니다.

Small image for

On-demand webinar

Featured webinar

Register to Attend

Share on Facebook

Reset all

Upcoming webinar

View more posts

Print

Hosted by

Sign In to Attend

View next

Follow us on Facebook

Share

Highlights

Read less

You'll also receive an email with related content

이메일을 통해 관련 내용을 보내드리겠습니다.

Thank you for registering. We will send you a confirmation email soon.

등록해 주셔서 감사합니다. 곧 확인 이메일을 보내드리겠습니다.

Author

Articles by Nick Peihl

Senior Software Engineer, Elastic

Bring new insights to your IP analytics with a global administrative layer in Elastic Maps

Ingest geospatial data into Elasticsearch with GDAL

New Country Subdivision Vectors in the Elastic Maps Service

Custom basemaps for region and coordinate maps in Kibana

Visualizing France Salary Data with Region Maps in Kibana