You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The terriajs will support some default resource formats. Loading a ckan item will fail when none of its resource formats fall into the default supported formats and if no additional info is given in supportedResourceFormats trait. The error message will be generic.
If a resource is a csv file, the terriajs expects that the resource format should be explicitly set to csv-geo-au according to this guidance. However, some data providers do not follow this guidance strictly, setting the resource format to csv instead of csv-geo-au, which will cause error when users try to add the item to the map and there is no way to create a shared link to communicate the error to the developers at the moment. There is a work-around by manually adding supportedResourceFormats trait :
The work-around is not feasible for dynamically created items from ckan-group. In that case, we should ask the data providers to fix the problem from the sources. The above info is not well known to catalog creators too, which often causes problem. We should make this prominently in the documentation.
The text was updated successfully, but these errors were encountered:
The terriajs will support some default resource formats. Loading a ckan item will fail when none of its resource formats fall into the default supported formats and if no additional info is given in
supportedResourceFormats
trait. The error message will be generic.csv
file, the terriajs expects that the resource format should be explicitly set tocsv-geo-au
according to this guidance. However, some data providers do not follow this guidance strictly, setting the resource format tocsv
instead ofcsv-geo-au
, which will cause error when users try to add the item to the map and there is no way to create a shared link to communicate the error to the developers at the moment. There is a work-around by manually addingsupportedResourceFormats
trait :ckan-group
. In that case, we should ask the data providers to fix the problem from the sources. The above info is not well known to catalog creators too, which often causes problem. We should make this prominently in the documentation.The text was updated successfully, but these errors were encountered: