Feature request: configure map by URL param about rdomap HOT 3 OPEN

I have some ideas about it, but link will be very long, we need to find the way how to shorten it.
If you have any ideas we are open for your suggestions or pull requests.
For now the best way to share the settings is export settings to .json file

from rdomap.

Coming back to this because I'm interested in something similar. Would you need to export all settings or only a selection of animals/plants(/missions/whatever)? If you could limit it to that, you could simplify by only implementing category/ID pairs (perhaps comma separated) so you'd get something like ?animal=34&plant=12,14&birds=4.

from rdomap.

So one way to get round the url size limit is to offload the storage to an external location. I used this technique for the RDR2Collectors map. For my use case, I wrote a webapp to convert a spreadsheet of collection items into a valid settings file, then added a settingsUrl query param and had the map fetch and import the settings.

For this issue though, users won't want the spreadsheet/webapp bit. Hence the storage in url request. Certainly limiting the export selection to a subset helps with url size. Converting to base62 or base64 would also really help to minimise the size. As would your category/ID pairs encoding suggestion.

from rdomap.