mirror
/
vizicities
kopia lustrzana https://github.com/robhawkes/vizicities
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

Updated readme

0.2
Robin Hawkes 2014-11-02 22:39:26 +00:00
rodzic 8c489327fb
commit 26daa5743e
1 zmienionych plików z 1 dodań i 1 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

2
README.md
Wyświetl plik

@ -36,7 +36,7 @@ Numerous lessons were learnt after releasing 0.1.0-pre to the public, so much so
### Blueprint API
Data input and visualisation output is now controlled by the [Blueprint API](http://dev.vizicities.com); think Zapier or IFTTT but for geographic data visualisation. It underpins the entire system for 0.2.0 and it completely changes the way you pull data into ViziCities and how you output it. A lot of hard work went into formulation and construction it — we're incredibly proud of it!
Data input and visualisation output is now controlled by the [Blueprint API](http://dev.vizicities.com). It's based on the concept of triggers and actions; much like Zapier or IFTTT, just instead for geographic data visualisation. It underpins the entire system for 0.2.0 and it completely changes the way you pull data into ViziCities and how you output it. A lot of hard work went into formulation and construction it — we're incredibly proud of it!
In short, the Blueprint API has 3 parts; an input, an output and a mapping configuration. Neither the input nor the output know about each other or care about each others data structure. Everything is neatly brought together by a configuration object that describes which input to use, which output to use, as well as how and, more importantly, when to map the data between them.