<p>Hi <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1651447" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ppKrauss">@ppKrauss</a>,</p>
<p>"The problem is the shortening-codes technology that is a black-box maintained by Google".</p>
<p>My interpretation of the link <a href="https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes">https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes</a> is different. I interpret it as follows:</p>
<blockquote>Anybody is free to pick a reference point and shorten the code accordingly. There isn't just one "right reference point" for shortening the code. So instead of  6889CW6G+6X I could use "Quatro Bocas sandwich shop, Altamira, Brazil, CW6G+6X ". 
<p>That's how we use the code: We pick a village as reference, and buildings then acquire short codes accordingly. The precise location of the village doesn't matter: as long as you don't stray too far, you can find the village (and the short code is the same, irrespective of reference point).</p>
<p>To use shortcodes with google maps, sure I need to use points that google maps knows about. To use shortcodes with OSM, I can enter the POI that I care about (as long as that POI is genuine and map-worth of course), and then shorten the code accordingly.</p></blockquote><p></p>
<p>This is not advice or a correction to your post: It's a different interpretation of <a href="https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes">https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes</a>. If you post your comment to <a href="https://wiki.openstreetmap.org/wiki/Proposal_Open_Location_Code" rel="nofollow">https://wiki.openstreetmap.org/wiki/Proposal_Open_Location_Code</a>, then I can post my view as well!</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-451544117">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLVOZWyIlm-OjFHJGJmm2YICFczeuks5u_6uigaJpZM4TDycy">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLTeTpT_wwSTJ4QzdbUSe6ZWbxo5Pks5u_6uigaJpZM4TDycy.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":"PERSON","message":"@bjohas in #1807: Hi @ppKrauss,\r\n\r\n\"The problem is the shortening-codes technology that is a black-box maintained by Google\".\r\n\r\nMy interpretation of the link https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes is different. I interpret it as follows: \r\n\r\n\u003cblockquote\u003eAnybody is free to pick a reference point and shorten the code accordingly. There isn't just one \"right reference point\" for shortening the code. So instead of  6889CW6G+6X I could use \"Quatro Bocas sandwich shop, Altamira, Brazil, CW6G+6X \". \r\n\r\nThat's how we use the code: We pick a village as reference, and buildings then acquire short codes accordingly. The precise location of the village doesn't matter: as long as you don't stray too far, you can find the village (and the short code is the same, irrespective of reference point). \r\n\r\nTo use shortcodes with google maps, sure I need to use points that google maps knows about. To use shortcodes with OSM, I can enter the POI that I care about (as long as that POI is genuine and map-worth of course), and then shorten the code accordingly.\u003c/blockquote\u003e\r\n\r\nThis is not advice or a correction to your post: It's a different interpretation of https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes. If you post your comment to https://wiki.openstreetmap.org/wiki/Proposal_Open_Location_Code, then I can post my view as well! "}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-451544117"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-451544117",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-451544117",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>