Bad<\/th>	Better<\/th><\/tr><\/thead>
Rodrigues<\/td>	Port Mathurin, Rodrigues, Maurice<\/td><\/tr>
Quatre Bornes<\/td>	Quatre Bornes, Plaines Wilhems, Maurice<\/td><\/tr>
Reunion<\/td>	Saint-Denis, La R\u00e9union, France<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n\n\n\n <\/span>Reverse geocoding (address from coordinates)<\/span><\/h2>\n\n\n\n <\/span>Use case<\/span><\/h3>\n\n\n\n You have GPS coordinates (e.g., field surveys, geolocated photos) and want to know the corresponding address.<\/p>\n\n\n\n <\/span>CSV example:<\/span><\/h3>\n\n\n\n id,latitude,longitude\n1,-19.7061,63.4209\n2,-20.2473,57.4906\n3,-21.1151,55.5325\n<\/code><\/pre>\n\n\n\n<\/span>Steps:<\/span><\/h3>\n\n\n\n1- Load the CSV file as a layer using Layer->Add Layer->Add Delimited Text Layer\u2026<\/p>\n\n\n \n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n2- QGIS menu: MMQGIS \u2192 Geocode \u2192 Reverse Geocode CSV with Web Service.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nIn the dialog box:<\/p>\n\n\n\n\nSpecify the CSV file.<\/li>\n\n\n\n Select Nominatim as the service.<\/li>\n\n\n\nChoose an output file.<\/li>\n<\/ol>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe plugin returns a description of the address for each point.<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\n \n\n\n\n<\/span>Best practices<\/span><\/h2>\n\n\n\n\nFor best results, check that the coordinates are in EPSG:4326<\/a> (latitude\/longitude in degrees).<\/li>\n\n\n\n Reverse geocoding provides an approximate address: street, locality, or place name, depending on the available data.<\/li>\n\n\n\n Avoid massive processing with Nominatim (respect public usage limits).<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>What to do next?<\/span><\/h2>\n\n\n\nThe data obtained can then be:<\/p>\n\n\n\n \njoined to vector layers,<\/li>\n\n\n\n used to filter, group, or map your field data,<\/li>\n\n\n\n integrated into a QGIS atlas or report.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>Common problems with MMQGIS Geocode<\/span><\/h2>\n\n\n\nError 429 \u2013 Too Many Requests<\/strong> The geocoding server temporarily refuses requests (see explanation above).<\/p>\n\n\n\n No address found<\/strong> This may be due to the address format or a lack of precision.<\/p>\n\n\n\n Addresses incorrectly located on the map<\/strong> The geocoder may sometimes return the center of a street or a municipality.<\/p>\n\n\n\n \n\n\n\n<\/span>⚠️ Error 429: \u00ab\u00a0Too many requests\u00a0\u00bb<\/strong><\/span><\/h3>\n\n\n\nWhen using the Geocode<\/strong> or Reverse Geocode<\/strong> tools in MMQGIS, the following message may sometimes appear:<\/p>\n\n\n\n \u00ab\u00a0Failure connecting to API : HTTP Error 429: too many requests\u00a0\u00bb<\/em><\/p>\n\n\n\n This error means that the geocoding service temporarily refuses requests because it is receiving too many in a short period of time.<\/p>\n\n\n\n MMQGIS uses the Nominatim service from OpenStreetMap<\/strong>, which is a public service. To protect the servers, this service enforces strict usage limits.<\/p>\n\n\n\n The error may appear if:<\/p>\n\n\n\n \nyou geocode a large number of addresses or points;<\/li>\n\n\n\n requests are sent too quickly;<\/li>\n\n\n\n several users are accessing the service from the same IP address.<\/li>\n<\/ul>\n\n\n\n \n\n\n\n<\/span>How can this problem be avoided?<\/span><\/h3>\n\n\n\nSeveral solutions are possible:<\/p>\n\n\n\n \nprocess the data in small batches<\/strong> (for example 100\u2013200 addresses);<\/li>\n\n\n\n wait a few minutes<\/strong> before running the process again;<\/li>\n\n\n\n use an alternative geocoding service<\/strong>;<\/li>\n\n\n\n for large datasets, install a local Nominatim server<\/strong> or use a professional service.<\/li>\n<\/ul>\n\n\n\nPublic Nominatim servers are intended for occasional requests or testing<\/strong>, not for large-scale geocoding.<\/p>\n\n\n\n \n\n\n\n<\/span>Coming next\u2026<\/strong><\/span><\/h2>\n\n\n\nIn the next article, we will see how to use MMQGIS to perform simple spatial joins<\/strong>, such as automatically linking points to the municipality or administrative area in which they are located.<\/p>\n\n\n\n If you frequently use geocoding in QGIS, you will probably encounter the HTTP 429 (Too Many Requests)<\/strong> error. We explained above why it happens and how to avoid it.<\/p>\n\n\n\n \n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":" In a previous article, we saw how to geocode complete addresses with the MMQGIS plugin. Today, we will go further with two very practical use cases, still without coding: 1. Geocoding places based on their names…<\/p>\n","protected":false},"author":1,"featured_media":14774,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3394,1377],"tags":[3536,3538,3540,3542,1758,1386],"class_list":["post-14931","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pluigin-en","category-qgis-en","tag-address","tag-coordinates","tag-gps-en","tag-mmqgis-en","tag-plugin-en","tag-qgis-en"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.sigterritoires.fr\/wp-content\/uploads\/2025\/07\/MMQGIS_3.jpg?fit=1232%2C756&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-3SP","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=14931"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14931\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media\/14774"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=14931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=14931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=14931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

⚠️ Error 429: \u00ab\u00a0Too many requests\u00a0\u00bb<\/a><\/li>
How can this problem be avoided?<\/a><\/li><\/ul><\/li>

Coming next\u2026<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n\n

<\/span>1. Geocoding places based on their names<\/span><\/h2>\n\n\n\n

You have a list of municipalities, countries, or well-known places, but no specific addresses. You want to locate these entities on a map.<\/p>\n\n\n\n

<\/span>CSV example:<\/span><\/h3>\n\n\n\n

id,lieu\n1,Port Mathurin, Rodrigues, Maurice\n2,Quatre Bornes, Maurice\n3,Paris, France\n4,Antananarivo, Madagascar\n<\/code><\/pre>\n\n\n\n<\/span>Steps :<\/span><\/h3>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n\nQGIS menu: MMQGIS \u2192 Geocode \u2192 Geocode CSV<\/a> with Web Service.<\/li>\n\n\n\n
In the dialog box:\n\nCSV file: your table with place names.<\/li>\n\n\n\n
Address column: select the column containing the places.<\/li>\n\n\n\n
Web service: OpenStreetMap \/ Nominatim.<\/li>\n<\/ul>\n<\/li>\n\n\n\nChoose an output file.<\/li>\n<\/ol>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nStart geocoding. Each place will be converted into geographic coordinates.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\n
\n\n\n\n<\/span>Tip: Geocoding quality<\/span><\/h2>\n\n\n\nNominatim tries to interpret the text provided. The more explicit your string is, the better the result will be. <\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
Bad<\/th> Better<\/th><\/tr><\/thead>
Rodrigues<\/td> Port Mathurin, Rodrigues, Maurice<\/td><\/tr>
Quatre Bornes<\/td> Quatre Bornes, Plaines Wilhems, Maurice<\/td><\/tr>
Reunion<\/td> Saint-Denis, La R\u00e9union, France<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\n<\/span>Reverse geocoding (address from coordinates)<\/span><\/h2>\n\n\n\n<\/span>Use case<\/span><\/h3>\n\n\n\nYou have GPS coordinates (e.g., field surveys, geolocated photos) and want to know the corresponding address.<\/p>\n\n\n\n
<\/span>CSV example:<\/span><\/h3>\n\n\n\nid,latitude,longitude\n1,-19.7061,63.4209\n2,-20.2473,57.4906\n3,-21.1151,55.5325\n<\/code><\/pre>\n\n\n\n<\/span>Steps:<\/span><\/h3>\n\n\n\n1- Load the CSV file as a layer using Layer->Add Layer->Add Delimited Text Layer\u2026<\/p>\n\n\n
\n<\/a><\/figure>\n<\/div>\n\n\n<\/a><\/figure>\n<\/div>\n\n\n2- QGIS menu: MMQGIS \u2192 Geocode \u2192 Reverse Geocode CSV with Web Service.<\/p>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nIn the dialog box:<\/p>\n\n\n\n\nSpecify the CSV file.<\/li>\n\n\n\n
Select Nominatim as the service.<\/li>\n\n\n\nChoose an output file.<\/li>\n<\/ol>\n\n\n\n<\/a><\/figure>\n<\/div>\n\n\nThe plugin returns a description of the address for each point.<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\n
\n\n\n\n<\/span>Best practices<\/span><\/h2>\n\n\n\n\nFor best results, check that the coordinates are in EPSG:4326<\/a> (latitude\/longitude in degrees).<\/li>\n\n\n\n
Reverse geocoding provides an approximate address: street, locality, or place name, depending on the available data.<\/li>\n\n\n\n
Avoid massive processing with Nominatim (respect public usage limits).<\/li>\n<\/ul>\n\n\n\n
\n\n\n\n<\/span>What to do next?<\/span><\/h2>\n\n\n\nThe data obtained can then be:<\/p>\n\n\n\n
\njoined to vector layers,<\/li>\n\n\n\n
used to filter, group, or map your field data,<\/li>\n\n\n\n
integrated into a QGIS atlas or report.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\n<\/span>Common problems with MMQGIS Geocode<\/span><\/h2>\n\n\n\nError 429 \u2013 Too Many Requests<\/strong>
The geocoding server temporarily refuses requests (see explanation above).<\/p>\n\n\n\n
No address found<\/strong>
This may be due to the address format or a lack of precision.<\/p>\n\n\n\n
Addresses incorrectly located on the map<\/strong>
The geocoder may sometimes return the center of a street or a municipality.<\/p>\n\n\n\n
\n\n\n\n<\/span>⚠️ Error 429: \u00ab\u00a0Too many requests\u00a0\u00bb<\/strong><\/span><\/h3>\n\n\n\nWhen using the Geocode<\/strong> or Reverse Geocode<\/strong> tools in MMQGIS, the following message may sometimes appear:<\/p>\n\n\n\n
\u00ab\u00a0Failure connecting to API : HTTP Error 429: too many requests\u00a0\u00bb<\/em><\/p>\n\n\n\n
This error means that the geocoding service temporarily refuses requests because it is receiving too many in a short period of time.<\/p>\n\n\n\n
MMQGIS uses the Nominatim service from OpenStreetMap<\/strong>, which is a public service. To protect the servers, this service enforces strict usage limits.<\/p>\n\n\n\n
The error may appear if:<\/p>\n\n\n\n
\nyou geocode a large number of addresses or points;<\/li>\n\n\n\n
requests are sent too quickly;<\/li>\n\n\n\n
several users are accessing the service from the same IP address.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\n<\/span>How can this problem be avoided?<\/span><\/h3>\n\n\n\nSeveral solutions are possible:<\/p>\n\n\n\n
\nprocess the data in small batches<\/strong> (for example 100\u2013200 addresses);<\/li>\n\n\n\n
wait a few minutes<\/strong> before running the process again;<\/li>\n\n\n\n
use an alternative geocoding service<\/strong>;<\/li>\n\n\n\n
for large datasets, install a local Nominatim server<\/strong> or use a professional service.<\/li>\n<\/ul>\n\n\n\nPublic Nominatim servers are intended for occasional requests or testing<\/strong>, not for large-scale geocoding.<\/p>\n\n\n\n
\n\n\n\n<\/span>Coming next\u2026<\/strong><\/span><\/h2>\n\n\n\nIn the next article, we will see how to use MMQGIS to perform simple spatial joins<\/strong>, such as automatically linking points to the municipality or administrative area in which they are located.<\/p>\n\n\n\n
If you frequently use geocoding in QGIS, you will probably encounter the HTTP 429 (Too Many Requests)<\/strong> error. We explained above why it happens and how to avoid it.<\/p>\n\n\n\n
\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
In a previous article, we saw how to geocode complete addresses with the MMQGIS plugin. Today, we will go further with two very practical use cases, still without coding: 1. Geocoding places based on their names…<\/p>\n","protected":false},"author":1,"featured_media":14774,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3394,1377],"tags":[3536,3538,3540,3542,1758,1386],"class_list":["post-14931","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pluigin-en","category-qgis-en","tag-address","tag-coordinates","tag-gps-en","tag-mmqgis-en","tag-plugin-en","tag-qgis-en"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/www.sigterritoires.fr\/wp-content\/uploads\/2025\/07\/MMQGIS_3.jpg?fit=1232%2C756&ssl=1","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-3SP","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=14931"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/14931\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media\/14774"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=14931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=14931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=14931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}