Open chanmathew opened 2 weeks ago
I’m on my phone right now so can’t easily look it up, but IIRC someone else mentioned this before and it turned out to be an internal thing with how maplibre represents data internally. I think the best solution here is to look up those entries in the original source data where it looks like it should.
Here was the previous discussion: https://github.com/dimfeld/svelte-maplibre/discussions/162
Pardon me if I'm being annoying here, but on a streak to document some things
Not annoying at all, these are good questions :)
Ah doh! Seems like both issues are blocked then, thanks for the quick clarifications! 😀
Hi @dimfeld - Pardon me if I'm being annoying here, but on a streak to document some things :)
I've noticed that when you pass nested arrays or objects to a GeoJSON source as a feature:
And then you access the features in a MarkerLayer, either via an event, or the feature attribute:
Then the objects would be double stringified, here's an example:
Is there a way to make sure it's not double stringified? Right now my workaround is to have a helper function that parses it all before I do anything with it.