Azure Function Deployment

[pablo-padua]

Hello,

First of all, thanks for the azure functions deployment option and README file, that consistently helps new developers to learn how to use lambda/functions/cloud deployments... The current README file is a bit outdated though and I have created a branch with updated commands but have no permission to push, so here's my 2 cents regarding the updated commands:

$ git clone https://github.com/developmentseed/titiler.git
$ cd titiler/deployment/azure

$ az login
$ az group create --name AzureFunctionsTiTiler-rg --location eastus
$ az storage account create --name {your-new-storage-name} --sku Standard_LRS -g AzureFunctionsTiTiler-rg
$ az functionapp create --consumption-plan-location eastus --runtime python --runtime-version 3.9 --functions-version 4 --name {your-new-function-name} --os-type linux -g AzureFunctionsTiTiler-rg -s {your-new-storage-name}
$ func azure functionapp publish titiler --python

I changed python runtime version from 3.8 to 3.9 (azure function no longer supports 3.8) and functions version was updated from 3 to 4 (you wont be able to create a new app function on version 3). Here's some testing I made that backs what I am saying:



I have added variables instead of fixed values, such as for container name and app name, given that it must be a unique name for each new instance.

Now, to my actual question - I am getting 404 on /cog/tiles on my newly deployed Titiler on Azure Functions, but /cog/preview works fine. Has anyone experienced this problem yet ?

Not found on /cog/tiles:

But works on /cog/preview

[hrodmn]

Hi @pablo-padua! Thanks for working on the Azure function docs. If you haven't already, please create a fork of the repo in your Github Account and open a PR from your fork to this repo. We would really appreciate it!

I think you are getting a 404 with your other request because it is getting the wrong set of path parameters in the URL.

To request a specific xyz tile you will need to provide the path parameter for tileMatrixSetId (e.g. WebMercatorQuad) before the /{z}/{x}/{y} path parameters. The whole request will look like /cog/tiles/{tileMatrixSetId}/16/24580/36818?....

I hope that helps!

[pablo-padua]

Hi @hrodmn ,
Thanks for the reply. As for the PR, I have opened it here. It's a pleasure to contribute, even if it's just for a minor fix.
As for the path parameter for tileMatrixSetId, has that recently changed? Because I have a dockerized titiler running on a personal VPS and the same request as above works fine for me

[hrodmn]

Yes this was a breaking change introduced in the most recent version (0.19.0). If you want to maintain access to tiles via /tiles/{z}/{y}/{x} you can pin to version <0.19.