Multi Column Support

Comma-Separated Coordinate Input for Reverse Geocoding

In order to highlight the advantages and functionalities offered by the reverse geocoding feature, we will use the same coordinates for the San Francisco Union Square in California and we will keep the same geographic coordinates for this location, namely “37.787994” and “-122.407437”. But this time we will use a comma in order to separate those two components forming the geographic coordinate for the San Francisco Union Square in California instead of a single column support.

Enter reverse geocoding pair coordinates

Accordingly, by using the comma for the input data, those two components are now in two separate columns and now for each column the user must select the correct element, namely latitude and longitude. And then the user should click on the “Process data” button. The output result is the same one as in the previous example, but the difference is that the input file is used from two different columns instead of only one column as in the previous example for the same geographic coordinates. This example points out that the CSV2GEO tool is very versatile and flexible regarding the input data in order to run reverse geocoding processes.

Select from columns latitude and longitude Preview first ten geocoded results

This multi-column approach is especially useful when working with datasets where latitude and longitude values are stored in separate columns, which is the most common format for geographic data exports from databases, GPS devices, and spreadsheet applications.

block is still compiled — and in THIS file that makes the partial include ITSELF. It recurses until PHP's memory limit dies and every page that renders it returns 500. That is not hypothetical: this header carried exactly such an example on 2026-08-15 and it was caught only by tests/Unit/BladeRendersWithoutRecursionTest.php on a full-suite run. It was invisible while the partial was wired into nothing, and went live the moment it was included. Describe the call in words; never spell a directive in a comment. Pass the URL in the SAME form the page's own tag uses. A layout that emits a bare /js/min/common.min.js should pass the bare path, so the retry hits the same cache entry the browser already tried rather than downloading a second copy. A layout whose tag is cache-busted should pass AssetVersion::url() for the same reason — note the asset-version Blade directive ECHOES, so it cannot go inside a PHP array; call \App\Support\AssetVersion::url() directly. --}}