Support Fonts List

[artyomb]

When using with Maputnik the Glyph url from Martin (https://martin./font/{fontstack}/{range}), Maputnik tries to get the list of available font names by the url:
https://martin./font/%7Bfontstack%7D/%7Brange%7D.

That would be great to have Matrtin provide that list.

[CommanderStorm]

Which map Software are you using that requests this template instead of subsituting the values?
Maplibre for example should replace the {fontstack}/.. variables: https://maplibre.org/maplibre-style-spec/glyphs/

[artyomb]

I use Maputnik (https://github.com/maplibre/maputnik).
In the UI interface, when you select the font for the Symbol text it tries to get list of available fonts from the two version of urls:

• First it requests GET https://martin.domain/font/{fontstack}/{range}

• Second case it calls GET https://martin.domain/font.json

I didn’t quite understand when each of them is used. But for the given case it calls GET https://martin.domain/font/{fontstack}/{range}

For now, I implemented this endpoint in the middleware where I call the GET /catalog and use "fonts" section.

[artyomb]

1. Fonts are working
2. Fonts list doesn't work

Maputnik requests GET https://martin.domain/font/{fontstack}/{range} to show available font in the font selection box

[CommanderStorm]

Ah, I see.

I don't see a request to

• font.json or
• fontstack.json as refered here.

This may be related to maplibre/maputnik#945, I have not looked into this further.

Suplying /font/{fontstack}/{range} as a [fontstack] does seem to work:

Will provide a PR as such

[nyurik]

Don't we already have this as part of the /catalog ? We might not have released it yet though

[CommanderStorm]

Yes, the information is avaliable.
Thing is that we can't realistically ask maputnik to support the /catalog format (can we?)

[nyurik]

sure can :)

[nyurik]

So yes, if we already publish the needed information, lets get maputnik to support that. If on the other hand this is part of a osgeo or similar standard api, than we may consider adding that. I don't think we should be adding multiple non-standard apis for the same functionality

[CommanderStorm]

The code maputnik currently uses to load the metadata looks like this (=> no standard is mentioned 🤔):

https://github.com/maplibre/maputnik/blob/c6174a57d9f934a1569f45edafca48859f799c0f/src/libs/metadata.ts#L20-L35

[nyurik]

The only relevant standards i'm aware of are various OGC API standards like the one for the tiles. BTW, at some point we should support it -- i created #1613. See also https://ogcapi.ogc.org/