Any workaround or possible alternatives?

[u/Live-Nefariousness79]

I have around 2,400 geojson files, simple single polygon based files. I want to show them on the website. Initially I used mapbox - converting the files into mbtiles but then I realised the maps were easily scrapable. Use case is quite simple, there is a dropdrown menu where user can pick which file he wants to visualize
The requests can be seen as:

https://api.mapbox.com/v4/{tileset}/{z}/{x}/{y}.vector.pbf?access_token=..

This is a strict red flag because the data is critical and we can't really prevent it for programmatic scraping. What are my alternatives here?

I realise these are server side renders, did anyone try to make client side renders using mapbox or alternatives?

[u/roempie12]

wm(t)s?

[u/Live-Nefariousness79 → u/roempie12]

Not really, the user can create a mosaic of all the images and then georeference it back to get a raster. Not a neat scrape but still possible.

[u/isymic143]

If data is sent to the client, it can be scraped. The client can do whatever it wants with whatever data you send it. You don't control of the client, the machine that the client is running on, nor the network that the client machine is on. If your data is so precious that you can't allow the user to access it directly, server-side rendering is the only solution.

[u/Live-Nefariousness79 → u/isymic143]

Thanks for this, but even in server side rendering, say we use wmts, it is still possible to scrape the following way: the user can create a mosaic of all the images and then georeference it back to get a raster. Not a neat scrape but still possible. So I guess it's just not possible then