fh-potsdam/digenti-apps

Open-source web-based tool for area accessibility assessment in the context of disaster management – based on satellite data and geovisualization.

digenti-apps's Issues

Add population to places_aoi.json

Estimated population data is in the DANE inform.

Add app config vars in a config.js file

For example:

var config = {};

config.theme = 'dark';
config.layoutdebug = true;

config.apiBase = "localhost:6002/api";

UI Buttons should switch modes, not activate/deactivate layers

Like before ;)

Then we stay consistent with the Small Multiples view.

Check github submodules for commons instead of CodeKit

https://github.com/blog/2104-working-with-submodules

https://gist.github.com/gitaarik/8735255

missing-infrastructure snippet throws error when updating d3 elements on move

Add snippet for upstream areas' FOS query

Accessibility map vs. Risk map

Statistical map that visualizes how accessible is each settlement

Isolines slider should update isolines "on change"

Road network schematization (new app in main repository folder)

• Cartographic schematization
• Tree view
• Morph by: distance / time / threat

"Connect" route nodes

Isotimes for each settlement

This should give an overview about the accessibility by road (by car / truck / feed) for each settlement in the area.

Visualize special areas

Approach to differenciate:

• Vegetation index
• Gradient

"Beautify" isolines

Info Box microvisualizations

• Elevation profile
• Time
• Distance
• Risk index

Missing infrastructure: use HERE API

Now this is calculating the nearest street using the OSM dataset.

Maybe a solution would be to calculate routes also for:

• Bike
• Walk

Since the OSM roads are paths, tracks, etc. not accessible by car.

Combine routes layer and missing-infrastructure layer in map view

Should look like this:

Upstream areas: Darken whole map but upstream area when selecting a settlement

FOS "aspatial" visualization in detail view

Other microvis:

• Place FOS
• Route FOS

digenti-api based routing example

Small multiples view: CSS map disable, not JS

Change settlement coordinates to nearby street

The coordinates of some settlements are located just a few (<50) meters away from a street. We should move these settlements to the next available street location given by our routing api. This would prevent a visual representation as seen in the screenshot.

Overlap upstream areas (blending mode)

Select upstream areas only when selecting a settlement

http://anand.codes/2015/09/21/interative-data-driven-styles-with-mapbox-gl-js/

Load isoline values dynamically with range slider

Now hardcoded values:

var range = '15,30,45';

Isonline and Route View

By clicking on a settlement, the isoline and route of the settlement should be shown on the map. The route should not be shown in the microviz-sidebar.

Remove JS styling. Only style with CSS

Remove colors, etc.

Remove transitions in d3 visualizations when zooming/panning

Keep them only when transitioning between map and small multiple modes.

Repair small multiples

Small Multiples Modes: routes+missing or only missing part

It should be possible to see the distance to the next road (only missing) or a combination of route and missing route part for every settlement.

Isodistances example

Add map labels and make them interactive

For example:

• Settlement layers
• Altitude layers
• Places of interest

Add filters in small multiples view

Should .layoutdebug svg elements always be added?

Now they are always added. Than depending on the value of "layoutdebug" the elements are filled with fill: rgba(255, 0, 255, 0.3); or "fill: none;"

Thickness of paths should correspondent to their importance

getting data from api

Interpolate isodistance polygons with roads

https://github.com/Turfjs/turf-intersect

Find the intersection of spatial features

turf.intersect(poly1, poly2)

Takes two polygons and finds their intersection.

Deactivate "bearing" events (rotation in map)

Avoid strange behaviours in the multitouch display

Update population information with UNGRD data

Remove loading animation only after loading and processing of data

Now it starts without the streets.

Offset bug in small multiples view

The bug with the offsetTop.

Add info box

Info box should show:

• Elevation profile (like Surface API)
• Time
• Distance
• Risk index
• Climate data: http://de.climate-data.org/location/45830/

Add new "risk mode"

Given a route, it should give an overview of risk indexes across the route.

We need to implement an API call (digenti-api) for this.

Detail view: add potential landing sites

• Add sliders into info box

Interactive isolines slider

Settlements as network diagram (morphing by distance, time, etc.)

Switch threat and isolines in detail view

Now both are visualized at once and is too much information. One solution could be to put a switch in the legend to show/hide both layers.

Settlement's points should be bigger or have a bigger hit area

Difficult to "touch" in the multitouch table

Make places (circles) interactive

Needed for: #21

Since we have more than one village circle showing at the same time (for each mode), when hovering or clicking on a village element we don't get to the event handler.

An approach could be:

• Remove all javascript fadein/fadeouts (setting opacity to 0 and 1) and using a class ".active" or ".disabled"
• The class sets opacity and pointer-events

Example:

.map-features {
    & > g {
        opacity: 1;
        pointer-events: all;

        transition: opacity 0.6s;

        &.disabled {
            opacity: 0;
            pointer-events: none;
        }
    }
}

Routing is ignoring some OSM streets

For example, the street between San José del Oriente and Tierra Nueva

Load road elevation profile from API

Morph other route features together with line

For example:

• Route dots
• Vectors (FOS)