Talk:Limitations/User interface

Relatedness of Clickable POI and raster tiles

@Tigerfell: ad special:Diff/2456436:

move POI out of raster tiles section because it is unrelated to that, one could implement them via Leaflet

I don't think so. Yes you could technically implement them via Leaflet, however where would you retrieve the POI information from? The editing API is only meant to be used for editing (and certainly not designed for such high traffic) and neither is Overpass. Have you noticed how Right click > Query features takes like 1-2 seconds? That's Overpass. And for clickable POI you certainly don't want any delay. When you hover over a POI you want the cursor to change instantly to indicate that it is in fact clickable, and that's only possible when the POI information has already been retrieved with the tile (→ vector tiles are necessary).

With that in mind I think your edit should be reverted. --push-f (talk) 05:00, 1 January 2023 (UTC)

I am not sure if you understand my argument. I am basically saying that you can use raster tiles and then add interactive icons and popups using Leaflet (example of a webpage that does that).

however where would you retrieve the POI information from?

We are talking about the webpage which is one software project including the API. In theory, one could just query the OSM database itself. That is probably bad style. You got a point that the API and Overpass are probably no good sources for retrieving this kind of data. There are still the rendering databases left. You need them to produce whatever tiles you want, so you are likely not breaking any internal structure when using them for this use case. Alternatively, one could use a separate database which includes relevant features only. You would then use a query language to retrieve the data.

You see that there is no relation between the types of tiles and the existence of a POI layer on top of them. --Tigerfell  (Let's talk) 19:20, 1 January 2023 (UTC)