-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Shapefile Dataset (with its ISO 19115/19139 metadata) not found after uploading it using API #10762
Comments
If we tried to upload a zip without xml then upload xml it returns :
Edit: Even with one download from another geonode then upload to new one : same error. |
So I made some tests on stable Geonode :
Please note as well that some Geonode api have PUT and others POST methods to upload dataset |
thanks @kikislater it clarifies some part, but what is not clear is why Geonode provides a method to upload dataset (eg. shapefile) - with method endpoint I see there is another method that allows to upload an ISO 19115 separately (method endpoint |
Agree and you could test it through api interface: https://master.demo.geonode.org/api/v2/uploads/upload
... different form but should not affect api if using proper base_file, dbf_file among others |
Actually the api answered with a success when I add the metadata, but then
the dataset is not visible and discovered by geonode
Le mer. 22 mars 2023 à 08:29, Sylvain POULAIN ***@***.***> a
écrit :
… Agree and you could test it through api interface:
https://master.demo.geonode.org/api/v2/uploads/upload
- First load of page logged in =>
[image: image]
<https://user-images.githubusercontent.com/13238064/226830397-685e9df3-3c32-491c-969a-d9d8cae32057.png>
- Second attempt after trying to POST a shapefile =>
[image: image]
<https://user-images.githubusercontent.com/13238064/226830769-275c3593-fbc1-48d7-bc2c-b330e27d5736.png>
... different form but should not affect api if using proper base_file,
dbf_file among others
—
Reply to this email directly, view it on GitHub
<#10762 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKDK3HRIA3CRN3ISD6VVW3W5KS5FANCNFSM6AAAAAAVWKP5CY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If you have access to django administration interface it should be in dataset with untick "approved" and "is published" : May be through this point on api : /api/v2/datasets But this issue let me remind me that it's not possible : #8850 |
Here you can post metadata :
https://docs.geonode.org/en/master/devel/api/V2/index.html#put--api-v2-datasets-id-metadata- |
Affects only stable version, master and dev publish metadata |
@eblondel I wasn't able to reproduce the issue. I've tested with Postman and the upload with the XML file worked fine. I could see the resource and the attributes from the file were assigned correctly.
Same test with cURL
|
@giohappy Thanks for your tests, what is your localhost geonode? All my tests were done on https://stable.demo.geonode.org @kikislater 's test sound to indicate the same, it doesn't work on the stable geonode. |
I've tested it over https://development.demo.geonode.org it works, but not on the stable release, so I understand that something was fixed over development. do you confirm? |
This is here |
we can close this, as it works as expected. Thanks for your support |
Expected Behavior
A shapefile + its ISO 19115/19139 XML metadata uploaded through the web API, and made visible over GeoNode.
Actual Behavior
The API returns a success (status code 200) with status "finished" and an URL pointing to the catalogue dataset; BUT
Live examples:
It seems to be an issue finding the dataset through the search
( Are there prequisites of metadata content for the XML file to be uploaded together with the shapefile, and that could be the cause of dataset "invisibility"? )
Steps to Reproduce the Problem
The integration test here (R language) reproduces the full test: https://github.com/eblondel/geonode4R/blob/main/tests/testthat/test_uploads.R
Specifications
https://stable.demo.geonode.org/
The text was updated successfully, but these errors were encountered: