{"id":2381,"date":"2026-10-20T08:32:20","date_gmt":"2026-10-20T07:32:20","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/import-latitude-longitude\/"},"modified":"2026-10-20T08:40:40","modified_gmt":"2026-10-20T07:40:40","slug":"import-latitude-longitude","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/import-latitude-longitude\/","title":{"rendered":"How to import latitude and longitude for your listings"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">GeoDirectory&#8217;s own CSV import has <code>latitude<\/code> and <code>longitude<\/code> columns. If you already have coordinates for each listing, put them in those columns and GeoDirectory will place each marker exactly where you say.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Update existing listings<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to GeoDirectory &gt; Import\/Export &gt; Listings and export the post type. This gives you a CSV with the right columns, including <code>ID<\/code>, <code>latitude<\/code> and <code>longitude<\/code>.<\/li>\n\n\n\n<li>Fill in the latitude and longitude for each row in a spreadsheet. Use decimal degrees, for example 51.4545 and -2.5879.<\/li>\n\n\n\n<li>Keep the <code>city<\/code>, <code>region<\/code> and <code>country<\/code> columns filled. The import rejects a row that has coordinates but is missing any of them.<\/li>\n\n\n\n<li>Save as CSV (UTF-8), then import it on the same screen with &#8220;If post ID exists&#8221; set to Update listing.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Rows with an ID that matches an existing listing update that listing. Rows without an ID are added as new listings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">If you leave the coordinates empty<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When latitude or longitude is blank, GeoDirectory looks the coordinates up from the address during the import. That needs a working geocoding API key and uses your quota, so for large imports it is faster and more accurate to supply the coordinates yourself.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/csv-imports-useful-tips\/\">CSV Imports: Useful Tips<\/a> and <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/explore-settings\/settings-overview-for-import-export-listings\/\">Settings Overview for Import\/Export &gt; Listings<\/a> cover the other columns. If you import with WP All Import instead, see the <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/wp-all-import\/wp-all-import-setup-guide\/\">WP All Import Setup Guide<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>GeoDirectory&#8217;s own CSV import has latitude and longitude columns. If you already have coordinates for each listing, put them in those columns and GeoDirectory will place each marker exactly where you say. Update existing listings Rows with an ID that matches an existing listing update that listing. Rows without an ID are added as new [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,432],"class_list":["post-2381","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-how-tos"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2381","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2381"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2381\/revisions"}],"predecessor-version":[{"id":2442,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2381\/revisions\/2442"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2381"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2381"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2381"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}