This is the main page to observe the data of a dataset. This page has two components: a data table and a map. The map will be displayed only for geographical datasets (it makes sense).
=======
# Data
## Research in the data
## Properties display toggle
## Data table (sort properties & complex properties & history of the click elements)
>>>>>>> 754d8f6... Complete the first draft for the map section.
## Fullscreen and Toggle Map/data
...
...
@@ -47,11 +37,7 @@ In case of datasets with a lot of properties, the user might want to display onl
On the client side, the library [Mapbox GL JS](https://github.com/mapbox/mapbox-gl-js) is used. This is a very interesting tool improving quickly.
Just for information the creator of Leaflet, Vladimir Agafonkin, is now working for Mapbox.
<<<<<<< HEAD
### How is the map data fetched and displayed
=======
## How is the map data fetched and displayed ?
>>>>>>> 754d8f6... Complete the first draft for the map section.
The main difficulty to display correctly the data was the heterogeneity of the datasets, both in size and in types. For example we can have a dataset with millions of polygons to display, or a very small one but with personnalized icons instead of a geometric figure.
To manage this very broad range of display we came with the following strategy.
...
...
@@ -61,11 +47,8 @@ At the begigning, we wanted to display just one MVT layer. It's vector, fast and
So first, **to display and see the data, the WMS service is used**. Using cache make it quite fast and we respect the style of the data producers.
Then the question of the interaction. **To let the user interact with the map, we load the MVT layer**. The trick is to paint it transparent by default, and apply a color on hover or click events. The user has the feeling to interact directly with the features on the map (displayed by WMS), but in reality interacts with the MVT layer above it.
<<<<<<< HEAD
#### Restricted datasets
=======
>>>>>>> 754d8f6... Complete the first draft for the map section.
