AnsweredAssumed Answered

Incorrect DCAT output on the data.json endpoint

Question asked by amercader on Oct 13, 2015
Latest reply on Oct 29, 2015 by CClaessens-esristaff

Hi,

 

I'm a member of the CKAN maintainers team and I'm using the DCAT extension to import datasets from an ArcGIS Open Data instance from a client (following roughly these steps). This essentially uses the data.json endpoint:

 

http://opendata.arcgis.com/data.json

 

 

I've noticed that some the URLs for the different distributions or resources for the datasets were not imported correctly, and found that the key for `accessURL` in some of the distributions is wrong:

 

distribution": [

...
{

    "@type": "dcat:Distribution",
    "title": "CSV",
    "format": "CSV",
    "mediaType": "text/csv",
    "downloadUrl": "http://opendata.arcgis.com/datasets/9b70131cd4984300bd8af47c4176ca77_0.csv"

},
{

    "@type": "dcat:Distribution",
    "title": "KML",
    "format": "KML",
    "mediaType": "application/vnd.google-earth.kml+xml",
    "downloadUrl": "http://opendata.arcgis.com/datasets/9b70131cd4984300bd8af47c4176ca77_0.kml"

},

    {   
        "@type": "dcat:Distribution",
        "title": "Shapefile",
        "format": "ZIP",
        "mediaType": "application/zip",
        "downloadURL": "http://opendata.arcgis.com/datasets/9b70131cd4984300bd8af47c4176ca77_0.zip"
    }   

],

 

Note `accessUrl` on eg KML vs `accessURL` on the shapefile. The DCAT standard is clear on what the correct case is so I think that's a bug on the ArcGIS side.

 

Is this something that can be fixed on future versions? If so what sort of timeline can be expected?

 

Many thanks

Outcomes