-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map source JSON format #97
Comments
There are some examples in the README to help get started. The map JSON is fairly complex and we are actually working on creating a 2.0 rev of this that has some dynamic editing via point and click vs building out the JSON objects manually or (how we do it) with scripts. Generally speaking each item in the The The Hopefully that helps. As I said above, we're working on making the UX of designing and updating maps a lot more cleaner in a future rev of this. Ideally people would not need to look at the raw JSON going forward at all. |
That's nice to hear. Could this text be added to the README please? I also found that there can be a |
daldoyle, I love the look of your product. I'm trying to pull data from an Influx DB and I'm not very good with coding. I've got the map set up and I'm getting the endpoints and link set up, but there's no data. Do you have any examples of the JSON file we'd need to use? JSON: |
Hey, I got it. Here's what I did if anyone else needs to use it. And here's the JSON: { |
Hi, I can't seem to find anywhere what the correct format for the map source JSON should be, what each item means, which items are required, ...
The text was updated successfully, but these errors were encountered: