nptscot / nptscot.github.io Goto Github PK

The current website uses the PBCC approach. Of a floating box in the bottom left corner.

This can change contextually based on the rnet

And can be minimised for small screens

This is fine for a single layer. But Users may want to add multiple layers.

Currently, no other layers have a legend which is no good.

There are several options. We could do the PCT approach of multiple floating boxes

But this can get cluttered especially on smaller screens.

Or we could put multiple legends in the box in the bottom left.

But I've had two ideas:

The first is to move from vertical dots/boxes to a horizontal bar

I think this remains clear, but it is more compact. But is probably does limit the number of values we can have. Especially if they need text tables.

The second idea is to place the legends below checkboxes/dropdown menus. These can still be contextual and have the added benefit of being next to the control that enables them. I think this may give users a clear idea about which legends are related to which layers/options.

Current version has only partial build with a ~10MB pmtiles input.

This issue will track progress towards testing the dev version with the pmtiles from a full build

See nptscot/npt#150

Following discussion with @Robinlovelace a few things about low flow routes

1. Repalce flows 1-9 with default value e.g. 5 and present as <10
2. Make thinnest line thicker so more visible and clickable

Currently called ATUM, switch to NPT

We should add something on the intellectual property, probably around here: https://github.com/nptscot/nptscot.github.io/blob/dev/about/index.html

Currently we have a UI illustrate in #23. That's sub-optimal.

One option: Leaflet's icon in bottom left a la Bikedata.

Source: https://bikedata.cyclestreets.net/ltns/#17/51.51137/-0.10498

Anti-aliasing improved the appearance of the website but takes a performance hit on low-end devices. Needs a cookies-based control

See

Vs

Currently we're serving the dev branch.

We should switch to serving the production branch.

Details on how: https://stackoverflow.com/a/74066945/1694378

This is the UI component of nptscot/npt#186, which needs to be fixed before this can be tackled. I'm not 100% sure if this is in scope and only worth exploring after nptscot/npt#186 has been tackled.

As well as inline help have a combined manual document

? Way to draw text from the same source?

See https://mahere.at.govt.nz/FutureConnect/ for ideas

Some people may want to complete a survey to provide feedback without the hassle of creating a GitHub account and opening a public issue. For those people something akin to https://forms.office.com/Pages/ResponsePage.aspx?id=qO3qvR3IzkWGPlIypTW3y9orQ9urif9IgBaXiRS9eEpURURCMEZPVjBRUDg2UTlWSjZYOVlRSU9DTC4u would be helpful.

Latest release has rnet_commte as a list with fastest and balanced networks.

Currently the Manual lacks a ToC that would enable people to copy paste links to specific sections. That should be a fairly quick fix. Thoughts @mem48 ?

It would be good to get feedback on new outputs.

That, plus the fact that current network has major bugs, suggest it's time for an updated build.

Old tiles:

      "id": "rnet",
      "description": "",
      "minzoom": 6,
      "maxzoom": 13,
      "fields": {
        "Gradient": "Number",
        "Quietness": "Number",
        "all_balanced_bicycle": "Number",
        "all_balanced_bicycle_go_dutch": "Number",
        "all_ebike_bicycle": "Number",
        "all_ebike_bicycle_go_dutch": "Number",
        "all_fastest_bicycle": "Number",
        "all_fastest_bicycle_go_dutch": "Number",
        "all_quietest_bicycle": "Number",
        "all_quietest_bicycle_go_dutch": "Number",
        "commute_balanced_bicycle": "Number",
        "commute_balanced_bicycle_go_dutch": "Number",
        "commute_ebike_bicycle": "Number",
        "commute_ebike_bicycle_go_dutch": "Number",
        "commute_fastest_bicycle": "Number",
        "commute_fastest_bicycle_go_dutch": "Number",
        "commute_quietest_bicycle": "Number",
        "commute_quietest_bicycle_go_dutch": "Number",
        "school_balanced_bicycle": "Number",
        "school_balanced_bicycle_go_dutch": "Number",
        "school_ebike_bicycle": "Number",
        "school_ebike_bicycle_go_dutch": "Number",
        "school_fastest_bicycle": "Number",
        "school_fastest_bicycle_go_dutch": "Number",
        "school_quietest_bicycle": "Number",
        "school_quietest_bicycle_go_dutch": "Number"
      }
    }
  ]

New fields:

{
  "Gradient": "Number",
  "Quietness": "Number",
  "all_balanced_bicycle": "Number",
  "all_balanced_bicycle_go_dutch": "Number",
  "all_ebike_bicycle": "Number",
  "all_ebike_bicycle_go_dutch": "Number",
  "all_fastest_bicycle": "Number",
  "all_fastest_bicycle_go_dutch": "Number",
  "all_quietest_bicycle": "Number",
  "all_quietest_bicycle_go_dutch": "Number",
  "commute_balanced_bicycle": "Number",
  "commute_balanced_bicycle_go_dutch": "Number",
  "commute_ebike_bicycle": "Number",
  "commute_ebike_bicycle_go_dutch": "Number",
  "commute_fastest_bicycle": "Number",
  "commute_fastest_bicycle_go_dutch": "Number",
  "commute_quietest_bicycle": "Number",
  "commute_quietest_bicycle_go_dutch": "Number",
  "school_balanced_bicycle": "Number",
  "school_balanced_bicycle_go_dutch": "Number",
  "school_ebike_bicycle": "Number",
  "school_ebike_bicycle_go_dutch": "Number",
  "school_fastest_bicycle": "Number",
  "school_fastest_bicycle_go_dutch": "Number",
  "school_quietest_bicycle": "Number",
  "school_quietest_bicycle_go_dutch": "Number"
}

Not sure why.

When the line colour is gradient or quietness disable the number of cyclists slider

As illustrated in the video above, do you know what's causing this @mem48 ?

https://www.cyclestreets.net/help/journey/howitworks/#quietness

Implementing dasymetric mapping similar to

https://www.ons.gov.uk/census/maps/choropleth/population/household-composition/hh-family-composition-4a/one-person-household

Example:

Map colours the buildings in a zone rather than the zone itself. Which makes it easier to see rnet/zones/basemap at the same time.

Verses current zones

Wards,
Scot Parliment
LA
Westminster

Other layers?

I think standard in this case would be something like

• main where day-to-day development happens, pointing to a dev version hosted at https://nptscot.github.io and now https://nptscot.github.io/web after #36 was fixed
• production which is released periodically after sign-off by more than one person, this would not usually be the default branch

Currently it's like this:

We want something more like CRUSE:

It would be good to have a demo of how to reproduce the website locally, e.g. with reference to something like the image below.

As outlined by @mem48 here #56 (review)

From Angus

Im wondering if rather than having the 10 separate SIMD transport related layers it might make more sense to have one combined SIMD transport related data layer (I think the SIMD inlcudes a single combined transport deprivation metric (presumably which incorporates those ten separate metrics).

workshop feedback

After someone renamed this repo from nptscot/web to nptscot/nptscot.github.io the site is no longer available at https://nptscot.github.io/web

The new site is available:

https://atumscot.github.io

Worth adding redirection?

Currently only R net has a legend. What to do about other layers?

Do we cover the screen in legends? Seems a poor solution

Need long-term solution

Any file server will do, but one that supports FTP access is preferable

• Visualise quietness like in CRUSE
• Visualise hilliness
• Remove the ability to visualise other modes in routes: unrealistic as these are cycle routes not car/bus/other routes and also distracting
• Add placeholder enabling people to switch network type, fastest, balanced, quietest
• Zones
• Popup on click
• Info/Help popups
• Sliders

Request from Angus

Docs: https://maplibre.org/maplibre-gl-js-docs/example/measure/

One drop down for scenarios, one drop down for line colour.

Line width fixed to scenarios

Also use route type not network type

Discovered during demo with @temospena, I think a typo has been introduced somewhere:

Sound reasonable? Each change to production can involve bumping the version and the date is my thinking.

With the launch of PMTiles v3 supporting compression, the main barrier to adoption has been removed.

Tests indicate a v3 .pmtiles file is now 6% smaller than a folder of gzipped .pbf files. Not a great saving, but significantly better than v2 which did not easily support compression and so was much larger. This also impacted performance.

The benefits of a single file vs a folder of millions of tiny files are huge.

1. Easier file upload and version control
2. Possibility to switch to cloud hosting e.g. GCP as API billing based on per file uploaded not per MB uploaded.
3. Easier to incorporate into workflows