-
Notifications
You must be signed in to change notification settings - Fork 46
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
Surfacing more data from catalogue.data.wa.gov.au #848
Comments
@keithmoss the query is fairly configurable. Here's the list of properties that can be configured: And here is how the WA group is configured: |
to investigate: There’s an ‘access_level’ property on our CKAN resources that can be used to filter to only show truly public data, but everything on https://docs.terria.io/guide/connecting-to-data/catalog-type-details/ckan/ indicates that Terria is operating on package/dataset level, not resource level. Is that accurate? |
@keithmoss We're using CKAN's |
@steve9164 Am I right in saying there's nothing in that mix to let us further filter the resources that go into NatMap? That is, once NatMap gets a package in the e.g. https://catalogue.data.wa.gov.au/dataset/bush-forever-areas-2000-dop-071 has 7 resources
So if we could (in theory) further filter the package_search response to the the 2 public resources that are actually relevant to NatMap by looking for |
@keithamoss That is correct. Terria does a bit of resource filtering to try to list all and only the resources it can display but it doesn't have a way to filter by "access_level". |
it might be possible with a |
Hi team,
We're beginning to harvest more third party web GIS services into Western Australia's CKAN and would like to surface them in NationalMap. Historically, you've only been surfacing data from the central SLIP (slip.wa.gov.au) geospatial data services platform.
We've recently harvested a range of spatial services from Main Roads who are hosting data on their own ArcGIS Server instances. There's several other agencies in a similar situation that we're planning to harvest this year, so we'd like to make sure these datasets are going to be able to show up in NationalMap.
To start with, can you remind us how much control we have over the config of the package_search query NatMap sends us[1]?
[1] https://nationalmap.gov.au/proxy/_1d/http://catalogue.beta.data.wa.gov.au/api/3/action/package_search?rows=100000&sort=metadata_created%20asc&start=0&q=data_homepage%3A*_Public_Services*&fq=res_format%3AWMS
Ping @vduong2
The text was updated successfully, but these errors were encountered: