Hub JSON Download Feed is V1 of the Hub API

KristenWobbe1

Hi ESRI Team:

It has come to our attention today that ESRI's Hub JSON Download feed is pointing to V1 of the Hub API. Could it be changed back to how it was?

Comparison item, example 'BLM OR Treatment Project Areas Polygon Hub':

https://gbp-blm-egis.hub.arcgis.com/maps/BLM-EGIS::blm-or-treatment-project-areas-polygon-hub

January-2024 json output was:

{
          "@type": "dcat:Distribution",
          "title": "Shapefile",
          "format": "ZIP",
          "mediaType": "application/zip",
          "accessURL": "https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-or-treatment-project-areas-polygon-hub.zi...
        }

Today's JSON output:

{
"@type": "dcat:Distribution",
"title": "Shapefile",
"format": "ZIP",
"mediaType": "application/zip",
"accessURL": "https://gbp-blm-egis.hub.arcgis.com/api/download/v1/items/836a0cc0013345b0a3ca2dfc5042a0ef/shapefile..."
}

An archive copy of our BLM JSON from April 12th DOES have the Version1 API link. Hub is currently using V3.

----------------------------------Follow-up Information 6/7-------------------------------------

[ESRI] "We don’t have plans to change this back because we’re working on a new more robust and better documented pattern. For context, you’ve seen that Hub site catalog feeds (DCAT-US, DCAT-AP, RSS) now show download URLs using a new “api/v1” because we’re resetting our download API URL pattern."

Hi Thomas,

We hear you about the new HUB API V1 and the sandbox you referenced. You said, "Before deprecating it, we’re making sure that Hub features including the client and Hub catalog feeds use the new more intuitive API URL pattern, which is why you see the new pattern. In fact, customers can try out and use the API directly (including the download API) through a Swagger sandbox (ex. the download sandbox API is https://gbp-blm-egis.hub.arcgis.com/api/download/definition). We intend to publicly document this so that customers can programmatically request download files."

I want to really clearly state what we are seeing and have questions and concerns about.

What we are seeing is a discrepancy between the DOWNLOAD links from the HUB GUI, and the HUB default JSON feed DCAT-US 1.1 (for Developers) is currently not putting a valid link in the JSON to download SHP files.

For example, the DOWNLOAD links below are for this item:

BLM UT National Monuments and National Conservation Areas (Arc): https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-ut-national-monuments-and-national-conser...

This link Works:

The Hub Web Site GUI uses this URL for Download - Shapefile: https://opendata.arcgis.com/api/v3/datasets/217c8e3ac8b142b88218f3dfef15542f_0/downloads/data?format...

(This URL uses the Open Data.arcgis.com API, AGOL REST API V3, well documented)

This link does NOT work:

The default Hub JSON Feed DCAT-US 1.1 uses this URL for Download – Shapefile: https://gbp-blm-egis.hub.arcgis.com/api/download/v1/items/217c8e3ac8b142b88218f3dfef15542f/shapefile...

(This URL uses the HUB API V1, not documented)

The link being generated from the default HUB JSON doesn't work for 'Referenced' feature services from 'stand-alone' Enterprise Server (ArcServer). (We are still at ArcGIS Server 10.9, and hope to migrate to 11.3 in July).

Our QUESTION is: Why aren't you using the link from the HUB DOWNLOADS in the default JSON (DCAT-US 1.1 feed)?

In summary, the default JSON feed (for Developers) currently is not putting a valid link to DOWNLOAD SHP files in the JSON.

This is casting us in a bad light on Data.gov where all Federal Agencies are mandated to have their items harvested to.
For example, a public user pointed out they could not download a SHP (CSV, or GeoJSON) from this Data.gov item ('Referenced' AGOL item harvested from the BLM Hub😞 https://catalog.data.gov/dataset/blm-natl-mlrs-geothermal-leases-5a9ec

Is ESRI going to fix this, or do we have to develop our own fix for the DEFAULT HUB DCAT-JSON 1.1 to include the links from the HUB GUI Download operations?