Good Morning!
I have noticed that the GeoServer API references are not up to date. Some endpoints are invalid or deprecated. I am exploring a method to create a new layer from a geopackage file.
Waiting for your reply,
Oscar
Hello Oscar,
Indeed the GeoServer REST API documentation is not up-to-date. It has been generated once from a static document and requires manual updates from now,. You can participate in the update effort by editing the obsolete documentation and help the community to have better information!
Regarding your question, I am not sure you can do that in one go. Perhaps you can try to use the /resource endpoint to upload your geopackage on the server and then use the /datastores endpoint to create the datastore. The last step would be to create a feature type with the /featuretypes endpoint.
I hope it will help you
Regards
Alexandre
Hi @AlexGacon Alex, sorry to barge in, is there a roadmap on the REST API update documentation link? I am new here and interested to look into that part of the GeoServer project.
Thanks.
Lyes.
Hello !
Thank you for joining the GeoServer community. As far as I know, there is no roadmap regarding specifically the REST API documentation. The one already available is quite good even if not up-to-date.
What kind of information are you looking for?
Regards
Alexandre
I thought to help in the update.
Yes please!
The documentation is hand made and in some parts out of synch, doc improvements are always
well received. If you plan to make small changes, just dive in, if instead you have a larger plan
in mind, please let us know what you want to do in advance.
Hi Lyes
I, too, am interested in improving the OpenAPI (Swagger) specs, which were hand crafted some years ago and not kept up to date.
I envisaged an AI agent comparing these docs to the actual code and making automated changes to REST — GeoServer 2.28.0 User Manual and below.
Once we have the OpenAPI specs polished up, we can test them for generating a client.
After that, we could probably back-annotate the code and then add a workflow to generate the specs from the code, comparing against our improvement, and finally use that in place of the static specs that we currently have.
I think that will be a huge and valuable improvement, is that along the lines that you were thinking of? In which, case, I will gladly join forces with you (possibly only in January, though). We can submit the proposal as a new GSIP.
Welcome to the community!
Peter
PSC
How to contact you guys ? This thread is moving outside of the OP’s topic I guess. Sorry about that.
Hi Lyes
Contact me privately gs@smytheDOTco,za and/or contribute here: GSIP-237 Update OpenAPI (Swagger) specs and/or in the Wiki: GSIP 237 · geoserver/geoserver Wiki · GitHub (ask for Wiki editor access).
Like Andrea says, if you have small improvements that you want to contribute right now (e.g. because a spelling mistake is bugging you), then see Quickfix — GeoServer 3.0 Documentation Guide
Peter