dsamourkasidis

<p>Map Visualizer allows users to import csv files, and to create a map out of them using the plugin’s interface.<br />
After you have successfully imported (or created) a data source, you can visualise it on a map and add it to your posts/pages with a shortcode.<br />
All shortcodes can be constructed easily through the plugin’s interface.</p>
<h4>CSV File Format</h4>
<p>In order for the CSV file to be imported successfully, its format must comply with the following rules:</p>
<ul>
<li>
<p>The first row must contain all the Header names:</p>
<ul>
<li>If you use geographical coordinates, the headers of <em>the first two column</em> must be named “Latitude” and “Longitude” respectively. </li>
<li>If you use addresses, the <em>first column</em> must be named “Address” and the plugin will geocode the data accordingly.</li>
<li>If you wish to use polygons, the <em>first column</em> must be named “Polygon”. Format of polygon data should be of Well-Known Text.</li>
</ul>
</li>
<li>
<p>The second row must contain the data type of each column:</p>
<ul>
<li>Available data types include “INT”, “FLOAT” and “TEXT”.</li>
<li>For “Latitude” and “Longitude” headers, the data type to be used is “FLOAT”.</li>
<li>For “Polygon” or “Address” headers, the data type to be used is “TEXT”.</li>
</ul>
</li>
</ul>
<h4>shortcode format</h4>
<p>The general format of this plugin’s shortcodes is [visualise]. Available attributes include:</p>
<ul>
<li>“file_name” : The name of the file imported you wish to visualise.</li>
<li>“map” : The map type to be used for the visualization. You can choose between “Satellite” or “Streets” maps and the default one is “Streets”.</li>
<li>“type” : Type of visualization. Either visualise your data as “polygon” or as “marker”. Default type is “marker”.</li>
<li>“marker_type” : Choose between “simple marker” or “circle_marker” to be pinned on the chosen map. The default markers are “simple marker”.</li>
<li>“category” : Header Name of your file, which will be used to differentiate the data based on the marker_type chosen.</li>
<li>“colorant” : Color of circle_markers and polygons, used to differentiate the data.</li>
<li>“circle_radius” : Radius of circle_markers. The default value is 5, and it is advised to stay between a 1-10 scale.</li>
<li>“fill_opacity” : Level of opacity for circle_markers and polygons. The default value is 0.3, and it is advised to stay between a 0.1-1 scale.</li>
<li>“center_point” : An Address for setting the initial center point of the map.</li>
<li>“zoom” : Initial zoom of the map. Value 1 shows the entire world map and the default zoom used is 3.</li>
</ul>


Map Visualizer

Import your data from csv files and visualise them on Google streets/satellite maps

Eyal Fitoussi

<p>WP Job Manager Client-Side Geocoder plugin bypass the geocoder function ( server side ) provided by WP Job Manager plugin and instead uses client-side geocoding system.<br />
By doing so the plugin should overcome the OVER_QUERY_LIMIT issue which you might have been experiencing.</p>
<h4>Features</h4>
<ul>
<li>Client-side geocoding system will try to overcome the OVER_QUERY_LIMIT issue which prevents address from being geocoded. </li>
<li>New “Geocode” button added under the location field in the “New Job” ( and “New Resume” for those who use the Resume Manager add-on ) page in the back-end. A click on the button will geocode the address entered.</li>
<li>When creating/updating job ( or resume ) from the front-end the location will be automatically geocoded once the form is submitted. No “geocode” button added to the front-end forms.</li>
</ul>


WP Job Manager Client-Side Geocoder

Use client-side geocoding to overcome the OVER_QUERY_LIMIT ( failed to geocode a location ) issue when updating job's location

Map Visualizer vs WP Job Manager Client-Side Geocoder