Include lat/lng with BiG CZ search results

[kdeloach]

CINERGI

Each resource has a Polygon instead of a position lat/lng.

http://cinergi.sdsc.edu/geoportal/rest/find/document?searchText=diamond&f=pjson&start=1

{
  "title" : "PetDB",
  "id" : "{B3A4D7E6-BD5D-4F72-B019-0CAABC1F5E26}",
  "updated" : "2017-00-19T22:59:36Z",
  "summary" : "PetDB, the Petrological Database, is a web-based data management system that provides on-line access to geochemical and petrological data. PetDB is a global synthesis of chemical, isotopic, and mineralogical data for rocks, minerals, and melt inclusions. ...",
  "bbox" : [-180.0, -90.0, 180.0, 90.0],
  "geometry" : {
    "type" : "Polygon",
    "coordinates" : [
      [
        [-180.0,-90.0], [-180.0,90.0], [180.0,90.0], [180.0,-90.0], [-180.0,-90.0]
      ]
    ]
  },
  "links" : [
    {
      "href" : "http:\/\/www.earthchem.org\/petdb",
      "type" : "open"
    },
    {
      "href" : "http:\/\/cinergi.sdsc.edu:8080\/geoportal\/catalog\/search\/resource\/livedata-preview.page?uuid=%7BB3A4D7E6-BD5D-4F72-B019-0CAABC1F5E26%7D&url=http%3A%2F%2Fwww.earthchem.org%2Fpetdb&info=http%3A%2F%2Fcinergi.sdsc.edu%3A8080%2Fgeoportal%2Frest%2Fdocument%3Ff%3Dhtml%26showRelativeUrl%3Dtrue%26id%3D%257BB3A4D7E6-BD5D-4F72-B019-0CAABC1F5E26%257D",
      "type" : "preview"
    },
    {
      "href" : "http:\/\/cinergi.sdsc.edu:8080\/geoportal\/catalog\/search\/resource\/details.page?uuid=%7BB3A4D7E6-BD5D-4F72-B019-0CAABC1F5E26%7D",
      "type" : "details"
    },
    {
      "href" : "http:\/\/cinergi.sdsc.edu:8080\/geoportal\/rest\/document?id=%7BB3A4D7E6-BD5D-4F72-B019-0CAABC1F5E26%7D",
      "type" : "metadata"
    }
  ]
},

HydroShare

Resources do not have a lat/lng or do not expose this field from the API.

https://www.hydroshare.org/hsapi/resource/?full_text_search=water&f=pjson

{
    "resource_type": "GenericResource",
    "resource_title": "GIS in Water Resources Term Project 2015",
    "resource_id": "0359cab7d93f403ba6ee8726cff74f8a",
    "creator": "Tomsen Reed",
    "date_created": "09-24-2015",
    "date_last_updated": "12-05-2015",
    "public": true,
    "discoverable": true,
    "shareable": true,
    "immutable": false,
    "published": false,
    "bag_url": "http://www.hydroshare.org/django_irods/download/bags/0359cab7d93f403ba6ee8726cff74f8a.zip",
    "science_metadata_url": "http://www.hydroshare.org/hsapi/resource/0359cab7d93f403ba6ee8726cff74f8a/scimeta/",
    "resource_map_url": "http://www.hydroshare.org/hsapi/resource/0359cab7d93f403ba6ee8726cff74f8a/map/",
    "resource_url": "http://www.hydroshare.org/resource/0359cab7d93f403ba6ee8726cff74f8a/"
},

CUAHSI

Each resource has a lat/lng field. :+1:

<Site>
<SiteName>
X756-Y276 of Global Land Data Assimilation System (GLDAS) NASA
</SiteName>
<SiteCode>GLDAS_NOAH:X756-Y276</SiteCode>
<Latitude>9.125</Latitude>
<Longitude>9.125</Longitude>
<HUCnumeric>0</HUCnumeric>
<servCode>GLDAS_NOAH</servCode>
<servURL>
https://hydro1.gesdisc.eosdis.nasa.gov/daac-bin/his/1.0/GLDAS_NOAH_001.cgi?WSDL
</servURL>
</Site>

[mmcfarland]

Each resource has a Polygon instead of a position lat/lng.

I think we can potentially work with polygons (presumably coverage areas) + points, so this seems good.

[kdeloach]

It looks like the Polygon field is used to represent both points and bounding boxes. We could make this the standard format for each data source.

[kdeloach]

We should follow up with HydroShare to request that the API is updated to include spatial information for each resource.

[ajrobbins]

We should follow up with HydroShare to request that the API is updated to include spatial information for each resource.

I'll do that.