@rossi45 I have no idea what FME is. But the file should not use Windows linefeed style (return+newline), but Linux style (newline). And should be UTF-8 encoded.
Thanks flamber! You are right, they are just some shapes I wanted to test with that I would like to use further on. Secondly, FME is a Universal translator between File Types. It’s excellent if you are in need of that type of function.
I’ve been testing and I think the translation needed some tweaks, but I do believe the tweaks I made changed the encoding and linefeed style because I finally got one to work. I just started with Metabase last week and I have a lot to learn, however it seems to provide a lot of function that I have been wanting for a while. I appreciate your help and quick response. Also, I used geojson.io but it was still giving me grief. Could be something to do with the files I am using, too.
@rossi45 No, Metabase currently only has a map of World and US - search the internet for “canada geojson” and I’m sure one of the first results will be something you can use.
Well I’ve been trying for days, and today it worked…
I was on 0.37.8 and 0.38 rc4.
Infra Team make it we can only use metabase with company’s VPN.
You think it could be a network error?
Metabase trying to access the map url and couldn’t?
Getting “Invalid custom GeoJSON key” in some urls, but this i think is from the json file itself.
@PauloHFM Sounds like network issues. But without the logs, it’s difficult to say for sure.
We have an issue open about providing better errors: https://github.com/metabase/metabase/issues/14635 - upvote by clicking on the first post
Hello, I received that r.features is undefined before. But then somehow the issue was resolved suddenly and the custom maps worked fine. However, a few days ago the same GeoJson file doesn’t work anymore and I got a new error message.
@wtlin I’m not getting any errors, when I try that map on 0.38.0.
Post “Diagnostic Info” from Admin > Troubleshooting.
And check for more detailed errors in Admin > Troubleshooting > Logs.
Post “Diagnostic Info” from Admin > Troubleshooting.
Are you using any antivirus/firewall on the machine hosting Metabase, or an outgoing proxy? Then try disabling those if they might intercept/change the request, when Metabase is reading the GeoJSON.
Without a way to reproduce, and if you are not using the latest release, then don’t create issues.
I think we need to address this issue first: https://github.com/metabase/metabase/issues/14635 - upvote by clicking on the first post
on the first post
