-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model Architecture: Implement SdmxCatalogItem #3524
Comments
Ping Rowan or Nanda if the master sdmx stuff is still unclear |
ABS has released the latest data api based on SDMX JSON v2.1 |
I have types for all SDMX data messages, and some SDMX structure messages - https://github.com/nf-s/sdmx-json-types |
Groups are now working in this order:
|
SDMX item structure:
All of this information is given by = https://stats-nsi-stable.pacificdata.org/rest/dataflow/SPC/DF_CPI?references=all |
Very basic SDMX item is now working Some TODOs:
|
It is now working on CI-deployment http://ci.terria.io/sdmx-next/#clean&https://gist.githubusercontent.com/nf-s/24b9288c6cdb6ba41d12f3d269318a0d/raw/c5ed64071c8a651ae458b4c0d3dc79c8618cb86d/sdmx.json Not all layers will work (especially some ABS ones), but quite a few do. |
Some layers will require setting Setting up regionsInformation about that can be found here - https://github.com/TerriaJS/terriajs/blob/c351cb6c598ce66dc1ed373e7cc811a88766f0c5/lib/Traits/SdmxCommonTraits.ts
For example SPC - Option 1 aboveThe following catalog json specifies that the "conceptOverrides": [
{
"id": "urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=SPC:CS_COMMON(2.0).GEO_PICT",
"type": "region",
"regionType": "CNT2"
},
... Another example, ABS - Option 2 aboveSome dataflows use "conceptOverrides": [
{
"id": "urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=ABS:CS_C16_COMMON(1.0.0).REGION_TYPE",
"type": "region-type",
"selectedId": "SA3"
},
{
"id": "urn:sdmx:org.sdmx.infomodel.conceptscheme.Concept=ABS:CS_C16_COMMON(1.0.0).REGION",
"type": "region"
},
... Options 3 - 5These are a bit more obvious, and are kind of handled in the same way a column title is used to find the corresponding Other
|
Some TODOs:
|
HTTP 400 issue may be related to lack of IPv6 support. |
I might add |
Update!I consider this finished (as a first pass anyway) - I just need to write tests. There are a few things missing from master implementation:
Other possible features
|
rowan: test some of the ways we use in nationalmap for it - and if we get the same results then we are good. nick: main difference w/ v7 implementation, we have sdmx groups, instead of creating a catalog item for every single data flow @nf-s to update post-Wedneday |
Feedback from meeting
|
Other thoughts
|
I'm going to close this as #4659 has been merged. We can create new issue(s) after we have received more feedback - I will make issues on current feedback |
I'm going to re-open this for - NationalMap - Beta release (V8) - Feb 2021 TerriaJS/nationalmap#997 I wanted to create separate tickets, but I didn't have time |
Maybe write a featureInfoTemplate using region feature info from #5211 |
|
|
|
Update!
|
URL to test it out! Known dataset issues
|
ABS Dataflow issuesSupply Use Table
|
Issues
|
Closing again! |
No description provided.
The text was updated successfully, but these errors were encountered: