Wrong accessURLs in new DCAT data.json files

164
4
Jump to solution
04-06-2022 10:22 AM
worldwidew
New Contributor

Up until about last week, it was possible to identify the correct URL for all ArcGIS-Hub-hosted files from the /data.json file. This week, I'm finding that at least some of the links in those data.json files are giving 404 errors.

For instance, if you look at https://hudgis-hud.opendata.arcgis.com/data.json and search for Public Housing Developments, the accessURL for the CSV-formatted version of the data is listed as

https://hudgis-hud.opendata.arcgis.com/maps/HUD::public-housing-developments.csv?outSR=%7B%22latestWkid%22%3A3857%2C%22wkid%22%3A102100%7D

Following this link gives a 404 error. This seems to be a template error because if the "/maps/" part of the URL is changed to "/datasets/", the URL works. 

0 Kudos
1 Solution

Accepted Solutions
ThomasHervey1
Esri Contributor

@worldwidew  @kaworth_csurams we've released a fix for this issue. Apologies again for the inconvenience.

View solution in original post

4 Replies
ThomasHervey1
Esri Contributor

Hi @worldwidew ,

Thanks for your question. This appears to be an issue where the URL is pointing to the incorrect link for a download file. I've logged an issue for the team to look at.

Additionally, for your information we made some updates to the Hub feeds (including DCAT) back at the end of 2021. Take a look at this blog post to see details and how to access the feed on the prefered URL https://www.esri.com/arcgis-blog/products/arcgis-hub/announcements/upcoming-changes-to-dcat-configur...

0 Kudos
worldwidew
New Contributor

Thanks! And thanks for the information about the new DCAT endpoint.

0 Kudos
kaworth_csurams
New Contributor

We're experiencing the same issue here at Colorado State University. The URL riddled with broken download links is https://geospatialcentroid-csurams.hub.arcgis.com/api/feed/dcat-us/1.1.json

Thanks for raising this issue. Hopefully it can be resolved swiftly. 

btw: Great workaround @worldwidew 

0 Kudos
ThomasHervey1
Esri Contributor

@worldwidew  @kaworth_csurams we've released a fix for this issue. Apologies again for the inconvenience.