Upgrade titiler and titiler-pgstac

[ividito]

Fixes: #147

Tested with a local DB instance, front-end seemed to work fine with a handful of collections. This upgrade might not require as many front-end changes as we expected.

One thing this does break/change are asset_expressions (ref1, ref2).

Version changes:

• titiler.pgstack 0.1.0.a9 -> 0.2.3 https://github.com/NASA-IMPACT/veda-backend/pull/148/files#diff-192f712a18c62e5709e6c7a9b84abd890e20581a4215ff1aecb2afa4962e9587R9

[ividito]

Ready for review now that #149 has been merged.

[vincentsarago]

by using titiler-pgstac==0.2.0 you can remove the custom factory in https://github.com/NASA-IMPACT/veda-backend/blob/develop/raster_api/runtime/src/factory.py#L61-L258

which is now directly in titiler-pgstac https://github.com/stac-utils/titiler-pgstac/blob/0.2.0/titiler/pgstac/factory.py#L721-L879 (you need to pass add_mosaic_list=True in MosaicTilerFactory(add_mosaic_list=True) instead of https://github.com/NASA-IMPACT/veda-backend/blob/develop/raster_api/runtime/src/app.py#L50

[anayeaye]

I rebuilt and ran with docker locally. Looks like /cog/viewer is replaced by /cog/map which offers more configuration options but may be a tad less intuitive for less technical users. I.e these are the differences I noticed and want to confirm are expected:

• url /cog/viewer --> /cog/map
• users must use url parameter in browser because there isn't an automatic input (I think most everyone does this anyway)
• underlying map context is no longer present
• configuration widget/side bar is gone (although the side bar offered less options than the new /cog/map endpoint provides)

If this is the expected behavior I'll approve the changes, we probably need to do a light refactor on our data provider documentation to make sure users know how to the new endpoint works and to update any references to the old viewer.

[j08lue]

Hmm, from the new viewer template, it seems like the UI elements for setting some of the URL parameters should still be there: https://github.com/NASA-IMPACT/veda-backend/pull/148/files#diff-42a81a69a9d962db79e4c01b3f757dbdb666fa17d46967b4e030ab8e2a3b1070R1. So the absence from your deployment might not be intended, @anayeaye.

@vincentsarago, what do you think about the expected changes with our update here regarding /cog/viewer -> /cog/map?

From a project perspective: we have not been relying a lot on /cog/viewer or promoted the use of it for our data contributors and curators, but it has come in handy sometimes to discover and debug data issues. So if we can keep a functioning viewer that at least has a background map (so users can confirm correct geo-reference fo their data), that would be great. If not, no problem to remove it.

[vincentsarago]

/cog/viewer should still be there

veda-backend/raster_api/runtime/src/app.py

Lines 95 to 107 in 1ea51c6

	@cog.router.get("/viewer", response_class=HTMLResponse)
	def cog_demo(request: Request):
	"""COG Viewer."""
	return templates.TemplateResponse(
	name="viewer.html",
	context={
	"request": request,
	"tilejson_endpoint": cog.url_for(request, "tilejson"),
	"info_endpoint": cog.url_for(request, "info"),
	"statistics_endpoint": cog.url_for(request, "statistics"),
	},
	media_type="text/html",
	)

there is also a new /cog/map that is provided directly by the tiler factory

[anayeaye]

I rebuilt and ran the changes locally and now see the viewer which is working as expected. Not sure what I had running on Friday, sorry about that!