Add crs option to /info endpoints

[JinIgarashi]

The latest titiler now no longer returns lng lat bounds from /info endpoint. Instead, I have to use /bounds endpoint with crs=EPSG:4326 option to fetch lng/lat coordinates.

I am not against new endpoints return original coordinates systems's bounds, but it would be better if /info can have crs option, so we can get all necessary information from them other than requesting to another bounds endpoint.

[vincentsarago]

@JinIgarashi Adding crs option to /info might be a bit complex. the info response comes from rio-tiler .info() method which doesn't take any option (except indexes= for stac reader).

So either we make change to rio-tiler and add a new crs option or add the option only in titiler to transform the bounds received from rio-tiler method. In both case I'll be a bit sceptical TBH.

Can I ask why you need this? The bounds in the geographic crs can be found in the tilejson or tilesets responses

[JinIgarashi]

@vincentsarago I am using bounds in lng/lat format in maplibre, previously info endpoint was enough to fetch all information for maplibre, but now I need to use both info and bounds endpoints. If titiler still can return lnglat bounds from info endpoint like what v0.18 did, it can be easier to integrate with map library.

by the way, this /info endpoint breading change is missing in your change log.

[vincentsarago]

by the way, this /info endpoint breading change is missing in your change log.

Yeah, it's pretty hard to map all the breaking change happening in rio-tiler to titiler 😬

In the new /info response you'll also be missing the min/max zoom information, which will only be available through the tilejson endpoint.

If you really want the bounds in geographic CRS (epsg:4326) you can you the /info.geojson endpoint

titiler/src/titiler/core/titiler/core/factory.py

Lines 388 to 405 in 6fcd564

	def info_geojson(
	src_path=Depends(self.path_dependency),
	reader_params=Depends(self.reader_dependency),
	crs=Depends(CRSParams),
	env=Depends(self.environment_dependency),
	):
	"""Return dataset's basic info as a GeoJSON feature."""
	with rasterio.Env(**env):
	with self.reader(src_path, **reader_params.as_dict()) as src_dst:
	bounds = src_dst.get_geographic_bounds(crs or WGS84_CRS)
	geometry = bounds_to_geometry(bounds)
	return Feature(
	type="Feature",
	bbox=bounds,
	geometry=geometry,
	properties=src_dst.info(),
	)

which is how we do in the cog viewer extension https://github.com/developmentseed/titiler/blob/main/src/titiler/extensions/titiler/extensions/viewer.py#L36

Summary

• /info endpoint now return the dataset CRS and dataset bounds (in the dataset's CRS)
• /info.geojson does have the bounds in geographic CRS (but not min/max zoom)
• /info endpoint doesn't have min/max zoom metadata, so it's better to use /{tileMatrixSetId}/tilejson.json or /{tileMatrixSetId}/tiles endpoints