<p>The <a href="https://en.wikipedia.org/wiki/Geo_URI_scheme" rel="nofollow">geo URI</a> standard is free, is neutral  and is a consensus... By other hand  the only consensual feature at issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="310542210" data-permission-text="Issue title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/1807" data-hovercard-type="issue" data-hovercard-url="/openstreetmap/openstreetmap-website/issues/1807/hovercard" href="https://github.com/openstreetmap/openstreetmap-website/issues/1807">#1807</a> is to point a "location context" for the search... All users will be happy with the approximated lat-long coordinates. Summary:</p>
<table>
<thead>
<tr>
<th>Search string box today</th>
<th>With <code>geo:</code></th>
<th>Effect with <code>geo:</code></th>
</tr>
</thead>
<tbody>
<tr>
<td>Pronto Socorro Maria</td>
<td>Pronto Socorro Maria geo:-23.55,-46.63</td>
<td>The result will be near São Paulo center, even when user is not browsing at Brasil</td>
</tr>
<tr>
<td>Pronto Socorro Maria</td>
<td>Pronto geo:-23.55,-46.63 Socorro Maria</td>
<td>(identical)</td>
</tr>
<tr>
<td>Champs-Élysées</td>
<td>Champs-Élysées geo:48,2</td>
<td>Ensures the Paris reference</td>
</tr>
</tbody>
</table>
<p><strong>Illustrative Scenario</strong>: suppose an user of the Openstreetmap's website   entering a string "Pronto Socorro Maria". It is  a <code>http://OSM.ORG/search?query=Pronto+Socorro+Maria</code>  query.  The result is something-aleatory, any hospital can be showed.  Now suppse the same user have some positional reference to say "nearst this point", how to say to the search engine?</p>
<p>The syntax to say is using the tag <code>geo:</code> with coordinates. If the user need to check the neighborhoods of <code>geo:-23.55,-46.63</code>  (that is a standard RFC 5870 string) can concatenate this string into the query,   <code>http://OSM.ORG/search?query=Pronto+Socorro+Maria+geo:-23.55,-46.63</code>. Simple, only it.</p>
<p>The <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions" rel="nofollow">javascript regular expression</a> for <code>geo:</code> tag is</p>
<pre><code>/(^|\s)geo:(\-?\d+(?:\.\d*)?,\-?\d+(?:\.\d*)?)(\s|$)/
</code></pre>
<h2>Step2. option to geocodes as OLC</h2>
<p>After implemented the <code>geo:</code>  tag and OSM community accepted the new feature.... We can suggest a little adaptation, the <code>geo:{geocodeSchema}:</code>. The main motivation is to entering pluscodes, that   is, the <a href="https://github.com/google/open-location-code/wiki/Supporting-OLC-in-your-app">OLC geocode-schema</a>, but not only it: there are an "open door" to implement in the future other geocode-schemas, without any privilege for Google's preferred scheme.</p>
<p>Will be a new consensus process, the "step2 consensus", if sucess the <code>geo:olc:{olcCode}</code>  will be implemented (<a href="https://github.com/openstreetmap/openstreetmap-website/pull/1818" data-hovercard-type="pull_request" data-hovercard-url="/openstreetmap/openstreetmap-website/pull/1818/hovercard">the implemetation is near ready</a>!) .  The javascript regular expression for OLC (named "global codes") is</p>
<pre><code>/(^|\s)geo:olc:([23456789C][23456789CFGHJMPQRV][23456789CFGHJMPQRVWX]{6}\+[23456789CFGHJMPQRVWX]{2,3})(\s|$)/
</code></pre>
<h2>Step3. Option for loose-OLC</h2>
<p>A testing feature can be solicitated,  to interpretate and expand a loose OLC.  For example  “588MC9X8+RC” in the search box text will be expanded to “geo:olc:588MC9X8+RC” in the real search. At implementation in  the search engine, it  can be a <a href="https://en.wikipedia.org/wiki/Preprocessor" rel="nofollow">pre-parsing</a> to simplify the work.</p>
<p>Will be a new consensus process, the "step3 consensus",  and only a "testing mode" feature to be implemented... Suggesting "step4 consensus" to be definitive implementation.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2104">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLS4CdphtCIMYPPUnQNyQ9Qr9GF7sks5vBczYgaJpZM4Z3QWX">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLUWvc_g7ouDoUrz-usVCJQdI3Xylks5vBczYgaJpZM4Z3QWX.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Add geo tag to OSM website search options (#2104)"}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2104"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2104",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2104",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>