tomkralidis on master
fix ESRI Shapefile STAC publish… (compare)
jokes aside, GitHub Discussions now enabled: https://github.com/geopython/pygeoapi/discussions
I kicked things off in https://github.com/geopython/pygeoapi/discussions/665
@pvgenuchten @francbartoli @kalxas @justb4 @jorgejesus and others, please help kick things off with your intros when you have a chance.
I will tweet and send to the mailing list.
thanks @GeoSander I had a look and #664 looks a bit less invasive to the providers, great :). Some questions:
fras well? Shouldn’t their
hreflangbe enough? I’m good with doing language for string properties but for entire objects?
pygeoapi.api.pre_processdecorator and request header handling has been fixed/cleaned up via the
Overall, I think we are close here, and while putting language so deep into the data codepaths is new for me, this work does move the yardstick on multilingual support. Great work!
I did add a few others to review the PR, and would want at least one of them to do a fulsome review of the PR as well.
At first I want to thank you for a great work.
I am participating on a project where I would like to use Pygeoapi.
I have a few questions about functionality I need on my project that I was not able to find in documentation.
Custom projection (epsg: 5514)
I found pull requests that didn't make it to master. Is it planned to finish them? What is the blocker? Can I help it myself?
APIRequestclass as well.
export SCRIPT_NAME="/pygeoapi"and local config
url: /pygeoapiIMO must be external/full URL.