Mercurial > hg > LGMap
annotate geotemco/README.md @ 23:d864c58ae667
For avoiding ssl warning, changing the link, mapquest.com, from http to https
| author | Calvin Yeh <cyeh@mpipw-berlin.mpg.com> |
|---|---|
| date | Wed, 29 Mar 2017 07:04:44 +0200 |
| parents | 8f05c2a84bba |
| children |
| rev | line source |
|---|---|
| 0 | 1 # PLATIN |
| 2 Place and Time Navigator | |
| 3 | |
| 4 a fork and extension of [GeoTemCo](https://github.com/stjaenicke/GeoTemCo) | |
| 5 | |
| 6 developed at the [Max-Planck-Institute for the History of Science](http://www.mpiwg-berlin.mpg.de) with funding from [TOPOI](http://topoi.org) within the Project [Atlas der Innovationen](http://www.topoi.org/group/d-6/). | |
| 7 | |
| 8 ## Introduction | |
| 9 | |
| 10 PLATIN is a HTML5-based tool for presentation and analysis of spatial and temporal data, with a focus on historical data. | |
| 11 | |
| 12 The projects starting goal was to bring the functionality of the [DARIAH](http://www.dariah.eu) [GeoBrowser](http://dev2.dariah.eu/e4d/) to [GeoTemCo](http://www.informatik.uni-leipzig.de/geotemco/). | |
| 13 | |
| 14 Which added the following functionality: | |
|
8
8f05c2a84bba
Apply new platin and Add tree layers
nylin@mpiwg-berlin.mpg.de
parents:
0
diff
changeset
|
15 * CSV/XLS/XLSX loading |
| 0 | 16 * loading of URL-specified datasets |
| 17 * deletion of datasets and refining of datasets | |
| 18 * exporting of datasets (to KML or CSV files) | |
| 19 * an UI that leaned on the GeoBrowser layout | |
| 20 * full-text search of table data | |
| 21 * WMS and KML overlays | |
| 22 * time-intervals | |
| 23 * upload of data to a data-store | |
| 24 | |
| 25 ## Important additional features | |
| 26 | |
| 27 The widget-architecture of GeoTemCo led to the creation of following additional features: | |
| 28 | |
| 29 ### Dataset loading via URL | |
| 30 | |
|
8
8f05c2a84bba
Apply new platin and Add tree layers
nylin@mpiwg-berlin.mpg.de
parents:
0
diff
changeset
|
31 Datasets in KML/CSV/XLS/XLSX/JSON format can be loaded via URL. Those attributes of those datasets can be changed, if they don't follow the PLATIN syntax style. Also datasets can be filtered via URL. |
| 0 | 32 |
| 33 ### Pie Charts | |
| 34 | |
| 35 Piechart can be created for each "column" of a dataset. The data can either be the distinct values, | |
| 36 categorized, or even generated by an own function (that takes the objects value as an argument). | |
| 37 | |
| 38 They are interactive with the other widgets, so a selection/highlight of a pie chart slice will | |
| 39 select/highlight those objects in the other widgets. And a selection/highlight in another widget | |
| 40 will reduce the piechart to those selected/highlighted values. | |
| 41 | |
| 42 ### Fuzzy Timeline | |
| 43 | |
| 44 If the dataset has uncertain time-data (as with historical/archaeological data) this uncertainity | |
| 45 should be shown and represented in the time-plot. The fuzzy timeline will add an object in such a | |
| 46 way, that its weight is equaly spread across the timespan that is attached to it. | |
| 47 | |
| 48 Also it is possible to switch to a bar-chart representation of the data. With bar-intervals of e.g. | |
| 49 1,10,100,... years. | |
| 50 | |
| 51 ### Directed Line-Overlay | |
| 52 | |
| 53 With this widget it is possibile to add "lines" (optionally arrows) between objects on the map. | |
| 54 | |
| 55 If objects are clustered the links will be inherited and line thickness will be increased if | |
| 56 lines are doubled by this clustering. | |
| 57 | |
| 58 ### Dataset coloring on element (DataObject) basis | |
| 59 | |
| 60 Each DataObject can have an own color, if objects are clustered together, the cluster color | |
| 61 is calculated as the average of the RGB values. | |
| 62 | |
| 63 ### Dataset color and shape changing (by user) | |
| 64 | |
| 65 (This feature is in beta-state.) | |
| 66 | |
| 67 Color and shape (on map) of the datasets can be changed on-the-fly from a dropdown menu in the table header. | |
| 68 | |
| 69 ### Story-Telling | |
| 70 | |
| 71 (This feature is unstable and under heavy development.) | |
| 72 | |
| 73 As this tool also has an focus on data-analysis, it can be interesting to | |
| 74 * record the steps of selection/piechart creation/dataset refining | |
| 75 * go back a step or more in this history of data transformation | |
| 76 * branch this history | |
| 77 * save this history | |
| 78 * send this history to other persons | |
| 79 * create a presentation, or animation, of that history |