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

CartoDB integration #21

Open
mtwestra opened this Issue Mar 13, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@mtwestra
Member

mtwestra commented Mar 13, 2014

Overview

Maps are an important way people interact with data. It helps judge progress of data collection, the spatial spread of data, and sometimes clear spatial patterns emerge. To enable users explore data using maps, they need some flexibility in what is displayed. This feature will make it possible to: 1) use street, satellite and terrain backgrounds, 2) show clustered data on different zoom levels, 3) enable filtering of data by survey, 4) styling markers (color, symbol) based on survey, and 3) display detailed data for individual points.

Because mapping is hard, we have decided to integrate flow with the open source CartoDB tool. We have made a carefull investigation of all the options, which clearly led to CartoDB as the most appropriate solution.

Initial features

In the first phase, we will introduce:

  • Use mapbox as tile provider for street, satellite and terrain tiles
  • display data of individual surveys on map using standard markers
  • enable users to specify popup style and content

Phase 2 will introduce:

  • enable data-driven styling of markers and custom icons
  • awareness of administrative boundaries
  • enable filtering of datasets
  • enable creation and saving of visualisations
  • handle translations of questions

Documents

Functional design document: https://github.com/akvo/akvo-product-design/blob/master/FLOW/Features/21-MapDisplay/FunctionalDesign/MapDisplay.md

Technical design document: https://github.com/akvo/akvo-product-design/blob/master/FLOW/Features/21-MapDisplay/TechnicalDesign/MapDisplay.md

Wiki: https://github.com/akvo/akvo-product-design/wiki/CartoDB-integration

@mtwestra mtwestra added the FLOW label Mar 13, 2014

mtwestra added a commit that referenced this issue Mar 13, 2014

@mtwestra mtwestra changed the title from Map display to CartoDB integration Jan 12, 2015

mtwestra added a commit that referenced this issue Jan 12, 2015

@mtwestra mtwestra added the Active label Feb 24, 2015

@mtwestra mtwestra removed the Active label May 15, 2015

@mtwestra mtwestra added the Design label May 27, 2015

@janagombitova

This comment has been minimized.

Show comment
Hide comment
@janagombitova

janagombitova Jul 31, 2015

Contributor

Based on feedback and ideas from Kiarii, here are minor implementation UI + UX fixes for the map, which we can add in with the integration in the first steps we are taking:

cartodb integration

  • Disable scrolling on the overall map page. Enable scrolling only in the sidebar
  • Set the maximum possible zoom, to only see the entire world map. This is to prevent the option for the user to zoom out to see multiple world maps.
Contributor

janagombitova commented Jul 31, 2015

Based on feedback and ideas from Kiarii, here are minor implementation UI + UX fixes for the map, which we can add in with the integration in the first steps we are taking:

cartodb integration

  • Disable scrolling on the overall map page. Enable scrolling only in the sidebar
  • Set the maximum possible zoom, to only see the entire world map. This is to prevent the option for the user to zoom out to see multiple world maps.

@janagombitova janagombitova added Development and removed Design labels Aug 14, 2015

@janagombitova

This comment has been minimized.

Show comment
Hide comment
@janagombitova

janagombitova Aug 27, 2015

Contributor
Contributor

janagombitova commented Aug 27, 2015

@janagombitova

This comment has been minimized.

Show comment
Hide comment
@janagombitova

janagombitova Feb 20, 2017

Contributor

We have decided to solely focus this issue on enabling Carto/Windshaft maps on Flow instances as part of this issue. The custom maps implementation is handled under a different issue.

Contributor

janagombitova commented Feb 20, 2017

We have decided to solely focus this issue on enabling Carto/Windshaft maps on Flow instances as part of this issue. The custom maps implementation is handled under a different issue.

@janagombitova

This comment has been minimized.

Show comment
Hide comment
@janagombitova

janagombitova Aug 2, 2017

Contributor

The Windshaft implementation (currently in progress) will bring to the users:

  • no data point clusters on the map, each point will show separately
  • user will have to select the folder, survey form first before data points will show on the map
  • user can only select those forms she has access to
  • this map implementation will be done for both the public and private maps for each Flow instance

After a new submission it will take 15 minutes for the unified log to "catch up" to log in the submission, so new data points will not appear on the map in real time, but after a 15 minutes delay.

Further improvements to Flow maps can be found here: #274

Contributor

janagombitova commented Aug 2, 2017

The Windshaft implementation (currently in progress) will bring to the users:

  • no data point clusters on the map, each point will show separately
  • user will have to select the folder, survey form first before data points will show on the map
  • user can only select those forms she has access to
  • this map implementation will be done for both the public and private maps for each Flow instance

After a new submission it will take 15 minutes for the unified log to "catch up" to log in the submission, so new data points will not appear on the map in real time, but after a 15 minutes delay.

Further improvements to Flow maps can be found here: #274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment