open-historical-map-labs / vectortilesdemo Goto Github PK

Switch map to 1950 and the states of KS and MO vanish.

I am guessing this is an issue in the date filtering, as Kansas was formed on 1950/08/30 and I think I have my "01/01" and "12/31" swapped. The match here should be for START <= 1950/12/31 AND END > 1950/12/31 tro encompass a feature having a presence at any point during the year.

Need a place to host the tiles. Initial pilot is running them from my EC2 "playground" which won't be around forever, and which does not support HTTPS.

• Set up AWS org and/or accounts.
• Generate API key
• Set up S3 bucket.
• Upload tiles
• Adjust demo to use new tile source.

When changing from one year to the next (YearPickerControl) is it possible to introduce some sort of easing effect?

Possible methodology:

• have 2 copies of the states/counties vectors, only one visible at a time
• upon a year change, apply the filter to the "new" layer, and ...
• ... begin a timer which sets the opacity of the "old" display from 1 to 0, and the "new" display from 0 to 1; when one reaches 0, set visibility: none

Could be complicated, particularly if we introduce user-defined opacity (opacity sliders) which would need to be kept in sync to two different sets of layers, and as we break apart the layers into more sub-layers (e.g. counties, broken up for color-classification, for county, township, etc.) and keeping potentally dozens of layer in sync...

The usual basemaps we would use on most projects, have state/province boundaries, streets, etc. but of course, for a historical map that's not appropriate and can be distracting. Even terrain maps and hydrology maps (white land, blue water) can be wrong at various points in history, as they do change in subtle ways and in large ways (river meandering, dams flooding valleys).

• Come up with a basemap solution suited to having no time-dependent detail. This may just be a solid fill of coastline!
• Implement this (Mapbox?)
• Implement in demo as the basemap

Additionally:

• Would this be the one and only basemap, or would more be available, e.g. modern-day Satellite photo could provide historical context, and historical basemaps with features at the time may exist, which could provide interesting context.

Tooltip behavipor in place at present, is placeholder to show what's there. Needs design, or rethinking as to desired behaviors. Should this happen only on a click for example, while hover shows a smaller tooltip?

Current setup is not amenable to local development. Running a browser directly on index.html won't load vector data (PBFs) due to cross-origin considerations. Adding a setup for webpack-dev-server or similar would work well.

Also, current implementation is written in "old style" JavaScript and CSS. No SASS/LESS, no ES2017 classes and syntax, etc.

• configure a webpack system including a webserver, SASS support, and Babel/ES2017 support
• document local-development process

At present there is no persistence mechanism to share my view, e.g. URL params to load the map at a given XYZ and then to toggle layers as well.

The layerpicker is defined in #4 and probably needs styling there in #4 This is different.

Counties don't become valid until z6, and states until z3. If one goes directly to Counties from the opening view, it "seems broken" that nothing happens.

• Can layerpicker (via LAYER_GROUPS) define min/max Zs per layer, then monitor the map.zoom events to enable/disable the UI for that layer? Disable the checkbox, decrease opacity, ...
• Can modern counties be enabled at all zooms? It's a much smaller dataset, and I think could be exempt from the COUNTIES_MIN_ZOOM

Continuing with #2 to refactor into a more modular design. The mouse behavior in place is a placeholder for #5 but should be broken into a separate Control-like behavior.

Cartography isn't determined, so this just uses some ugly brown and yellow fills for States and Counties. What would be the desired cartography here: classifications (layers) and colors?

• States
  • by type: Territory, State, etc?
• Counties
  • is type avaiable, e.g. Land Grant, Township, County, ...?

At present there is no layer picker. Need to toggle historical state/county and to toggle modern state/county individually.

Time slider has basic functionality, but not yet UI considerations:

• play/prev/next/stop buttons to automate the show
• readout to show the current year