Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Validation</strong></p> <p>The example you give (in the first version of your question) does not pass validation at <a href="http://validator.nu/" rel="nofollow">http://validator.nu/</a>. You cannot use directly a property in the same node that declares the entity type. Probably the rich snippet tool is not strict enough. To confirm, this <a href="http://foolip.org/microdatajs/live/" rel="nofollow">alternate tool</a> also refuses to generate a JSON expression from your block because of the lack of a top level element.</p> <p>So an additional node is required for the <code>geo</code> property, here is a proper way to express it (doctype and title are for validation tool only):</p> <pre><code>&lt;!DOCTYPE html&gt; &lt;title&gt;Nottingham City Neighbourhood&lt;/title&gt; &lt;div class="hidden" itemscope itemtype="http://schema.org/GeoShape"&gt; &lt;div itemprop="geo"&gt; &lt;meta itemprop="circle" content="52.953 -1.149 32186.88"/&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p><strong>Recommendation</strong></p> <p>According to this <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=1093493" rel="nofollow">Google FAQ</a> only few entities are really supported and based on <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=146861" rel="nofollow">Organization</a> and <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=164506" rel="nofollow">Event</a> examples in microdata format, the optional <code>geo</code> property only propose <code>longitude</code> and <code>latitude</code> elements from <a href="http://schema.org/GeoCoordinates" rel="nofollow">http://schema.org/GeoCoordinates</a>. So there is less doubt to use that simple <em>point</em> definition compared to <code>circle</code>. By the way this example is valid and properly extracted:</p> <pre><code>&lt;div itemscope itemtype="http://data-vocabulary.org/Organization"&gt; &lt;span itemprop="name"&gt;Nottingham City Neighbourhood&lt;/span&gt; &lt;div itemprop="geo"&gt; &lt;meta itemprop="circle" content="52.953 -1.149 32186.88"/&gt; &lt;/div&gt; &lt;/div&gt; </code></pre> <p>If you use <a href="http://sindice.com/" rel="nofollow">sindice.com</a>, there is no hit for <code>http://schema.org/GeoShape</code> whereas <code>http://schema.org/GeoCoordinates</code> is extensively used. Not so easy to find real world usage of <code>circle</code>.</p> <p><strong>Circle property value</strong></p> <p>For the circle property content itself, many documentation refers to <a href="http://www.w3.org/2003/01/geo/" rel="nofollow">WGS84</a> but it only concerns point. This <a href="http://www.georss.org/simple" rel="nofollow">documentation</a> confirms the content text structure for the <code>circle</code> element.</p> <p>This <a href="http://dev.iptc.org/rNews-10-The-Geo-Coordinates-Class" rel="nofollow">example for rNews</a> obviously lacks a space before the 500 radius and is not properly rendered, the page source contains <code>&lt;td class="rnews_td codestyle"&gt;38.920952 -94.645443500&lt;/td&gt;</code> instead of <code>&lt;td class="rnews_td codestyle"&gt;38.920952 -94.645443 500&lt;/td&gt;</code></p> <p>You should look at <a href="http://schema.rdfs.org/tools.html" rel="nofollow">schema generators or parsers</a>. Maybe one of them has implemented a fine grain editor for GeoShape properties instead of a raw text field, so that you can confirm property content structure. I have looked at <a href="http://developers.any23.org/" rel="nofollow">Any23</a> but still the same issue: GeoCoordinates is implemented but not GeoShape.</p> <p><strong>Box and polygon property value</strong></p> <p>No coma is expected between longitude and latitude values for point, box, polygon or line (only use space) according to both <a href="http://dev.iptc.org/rNews-10-The-Geo-Coordinates-Class" rel="nofollow">rNews</a> and <a href="http://www.georss.org/simple" rel="nofollow">GeoRSS</a>.</p> <p><strong>As a conclusion</strong>, you should avoid <code>GeoShape</code> if your aim is to provide a location to search engines... At the moment, only <code>GeoCoordinates</code> seems to be a reasonable choice.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload