<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Datasets with null bbox are shown in JSON as [-180,180,-90,90] in Esri Geoportal Server Questions</title>
    <link>https://community.esri.com/t5/esri-geoportal-server-questions/datasets-with-null-bbox-are-shown-in-json-as-180/m-p/400497#M476</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it is definitely 'by design'. see com.esri.gpt.control.georss getValidMinX-like methods. perhaps something to change. there is not such a thing as a 'null geometry' from what I can see on GeoRSS, so better would be to omit the entire georss:polygon element when there is no geometry in a record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if this happens with ArcGIS items, check the ags-toDC.xslt as there is a default extent assigned there upon publishing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 27 Jul 2014 09:44:20 GMT</pubDate>
    <dc:creator>MartenHogeweg</dc:creator>
    <dc:date>2014-07-27T09:44:20Z</dc:date>
    <item>
      <title>Datasets with null bbox are shown in JSON as [-180,180,-90,90]</title>
      <link>https://community.esri.com/t5/esri-geoportal-server-questions/datasets-with-null-bbox-are-shown-in-json-as-180/m-p/400496#M475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi guys,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In instances where a dataset has no bounding box, the GeoPortal doesn't show the Zoom To option in the Search results:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[ATTACH=CONFIG]25995[/ATTACH]&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, the JSON output for these dataset shows a bounding box covering the whole globe:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE __default_attr="plain" __jive_macro_name="code" class="jive_macro_code jive_text_macro"&gt;"bbox" : [-180.0, -90.0, 180.0, 90.0],&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this a bug? IMO the bbox should be null if it doesn't exist for the data. Any workarounds you can suggest?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Steve&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;--&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://geoportalgenie.com"&gt;GeoPortal Genie&lt;/A&gt;&lt;SPAN&gt; | a modern front-end to Esri GeoPortal Server&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jul 2013 07:09:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/esri-geoportal-server-questions/datasets-with-null-bbox-are-shown-in-json-as-180/m-p/400496#M475</guid>
      <dc:creator>StephenLead</dc:creator>
      <dc:date>2013-07-17T07:09:41Z</dc:date>
    </item>
    <item>
      <title>Re: Datasets with null bbox are shown in JSON as [-180,180,-90,90]</title>
      <link>https://community.esri.com/t5/esri-geoportal-server-questions/datasets-with-null-bbox-are-shown-in-json-as-180/m-p/400497#M476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it is definitely 'by design'. see com.esri.gpt.control.georss getValidMinX-like methods. perhaps something to change. there is not such a thing as a 'null geometry' from what I can see on GeoRSS, so better would be to omit the entire georss:polygon element when there is no geometry in a record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if this happens with ArcGIS items, check the ags-toDC.xslt as there is a default extent assigned there upon publishing.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Jul 2014 09:44:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/esri-geoportal-server-questions/datasets-with-null-bbox-are-shown-in-json-as-180/m-p/400497#M476</guid>
      <dc:creator>MartenHogeweg</dc:creator>
      <dc:date>2014-07-27T09:44:20Z</dc:date>
    </item>
  </channel>
</rss>

