profile
viewpoint

cusu/stv-tools 5

A free reference implementation of Single Transferable Vote

cyclestreets/tflcid-conversion 5

Conversion of TfL CID attributes to OSM

cyclestreets/streetfocus 4

Helping local communities benefit from new development

mvl22/openwebmapping 4

Web mapping with open data - talk given to PHP Cambridge, November 2017

cyclestreets/cyclescape-issuemap 3

Embeddable map module - Cyclescape API integration, by @georgio8

mvl22/trac2github 2

Converts Trac milestones, tickets and comments into Github issues 2.0 using github api v3

cyclestreets/Mapboxgljs.LayerViewer 1

Layer viewer GUI using Mapbox GL JS

campop/travelintimes-deploy 0

Historic journey planner - deployment

cyclestreets/transporthack 0

Lake District Bike Network transport hack for Smarter Travel LIVE! 2016

issue closedcyclestreets/android

Improve GRADLE build Performance

We have submitted a PR called the same title of this issue. We find that there are some tips which can Improve GRADLE build Performance for this project.

1.Parallel test execution maxParallelForks, running multiple test cases in parallel is useful and helpful when there are several CPU cores.

2.According to Process forking options, Gradle will run all tests in a single forked VM by default. This can be problematic if there are a lot of tests or some very memory-hungry ones. one option is to fork a new test VM after a certain number of tests have run. So our recommendation is to configure "forkEvery" and we give a specific value of 100

3.Disable report generation, Gradle will automatically create test reports by default which will slowing down the overall build. So it's better to disable the test reports while we don't need it

closed time in 11 hours

ChenZhangg

push eventcyclestreets/mobileweb

mvl22

commit sha 8b14a879b30bcfd3bc35ae05ea1453abf37c96b0

Disable first-run message, pending getting cookie support in

view details

push time in 14 hours

issue openedcyclestreets/cyclescape

Autosave editor content every few seconds

A user looking at the new designs has requested this. I have run into this problem myself.

Every so often the content in the richtext editor box should be autosaved. (Don't bother with other reply types.)

The session/cookie memory should be indexed by thread ID, so that there is no crosstalk between thread boxes.

Submitting the page should clear the session/cookie memory for that thread.

created time in 18 hours

push eventcamunigeography/muscat-conversion

mvl22

commit sha 7fc97a7fdfdd852ff09200d4efed51e117086485

Add installer script for system software libraries

view details

push time in 2 days

push eventcamunigeography/muscat-conversion

mvl22

commit sha c356ed4a1136867ba09fc385c2e1ec0e1110b3d3

Add installer script for system software libraries

view details

push time in 3 days

issue commentcyclestreets/cyclescape

Deadline not shown when creating issue

Sure, though it's probably just a simple View change surely? This is the deadline in the issue, a thread message. I assume it just needs printing to the thread page in the same way that the description and link are.

soundplusfury

comment created time in 3 days

issue commentcyclestreets/cyclescape

New design migration: AJAX scroll mechanism within thread

Well done, thanks for your work on this.

mvl22

comment created time in 3 days

issue commentcyclestreets/cyclescape

New design migration: AJAX scroll mechanism within thread

Thanks - looks good to go.

mvl22

comment created time in 4 days

issue commentcyclestreets/cyclescape

Issue elimination - database migration

I'd like to add a validation to ensure all future message threads have tags so we don't get new ones.

Yes, definitely. Soon as we have the current data cleaned up, we should apply that to editing also so that the constraint is in before we do the main site migration.

Finally the top tags

I see we have some tags with zero references to them. I suggest we zap those as they aren't useful and will just create autocomplete noise.

mvl22

comment created time in 4 days

push eventcamunigeography/supervision-signup

mvl22

commit sha ad65eb0893c480ac8440cedc7c602ca286c5e2e0

Admins can also edit a supervision

view details

push time in 5 days

push eventcamunigeography/supervision-signup

mvl22

commit sha 3e9181cc8d8aed177451a8dffdb4e7f116d4878d

Add direct link to edit introduction for admins

view details

push time in 5 days

push eventcyclestreets/Mapboxgljs.LayerViewer

mvl22

commit sha c93992773cab05324f47a861e6b73a508d4f6be3

In direct GeoJSON, add support for merging in layer configuration

view details

push time in 5 days

push eventcyclestreets/Mapboxgljs.LayerViewer

mvl22

commit sha ab5cabee469d558e0061022e48c44fa33139c541

Add support in GeoJSON layers for setting data directly rather than API

view details

mvl22

commit sha 90e5edfff58ee6ee3a6b90cb4ad59f8eb4610275

Add support for adding (and erasing) a GeoJSON layer directly

view details

push time in 5 days

push eventSDCA-tool/sdca-package

mvl22

commit sha a41b0c0e2dbbeeea58134ea3c73c0da00c2f31d8

Fix typo

view details

push time in 5 days

push eventSDCA-tool/sdca-website-deploy

mvl22

commit sha bced75680786767a945dc7295424b1f120e62d82

Seems update.packages() isn't enough to update with dependencies; using full install instead

view details

push time in 5 days

push eventcyclestreets/Mapboxgljs.LayerViewer

mvl22

commit sha 653f23fe7938bae7630a55e5e6fb1a750aa98788

Fix long-standing bug whereby popups appear during drawing This was a difficult bug to fix, but the solution seems robust. The fix works by disabling the interactivity of each layer that has popups by using map.off as soon as drawing is started, and reinstating using map.on when drawing stops or is stopped. See: https://docs.mapbox.com/mapbox-gl-js/api/map/#map#off To facilitate this, the popup handlers have to be registered to a global registry, so that map.off and map.on have a handle (see third argument) that can be referenced; see: https://stackoverflow.com/a/45665068/180733 This has to be hooked into the mapbox-gl-draw events as documented at: https://github.com/mapbox/mapbox-gl-draw/blob/main/docs/API.md#events If adding new buttons using the mapbox-gl-draw events, they will also need to set the _drawingHappening state as relevant. A variety of other strategies were tried, including the following, but none worked: - Attempting to avoid the click propagating, but e.stopPropagation does not exist in this context so this generates an error; see mapbox-gl-js issue #9369 - Stopping the popup opening at the point of querying for features (using queryRenderedFeatures) at the clicked location; see: https://stackoverflow.com/questions/47576527/ - Closing the popup immediately on opening (which would probably have given flicker) - Overriding the map click somehow; see: https://stackoverflow.com/questions/45298202/ , which though helpfully pointed to the use of map.off/map.on

view details

push time in 5 days

push eventcyclestreets/Mapboxgljs.LayerViewer

mvl22

commit sha 70e20bf8c00bff17d878008509a231542c10251a

Fix long-standing bug whereby popups appear during drawing This was a difficult bug to fix, but the solution seems robust. The fix works by disabling the interactivity of each layer that has popups by using map.off as soon as drawing is started, and reinstating using map.on when drawing stops. See: https://docs.mapbox.com/mapbox-gl-js/api/map/#map#off To facilitate this, the popup handlers have to be registered to a global registry, so that map.off and map.on have a handle (see third argument) that can be referenced; see: https://stackoverflow.com/a/45665068/180733 This has to be hooked into the mapbox-gl-draw events as documented at: https://github.com/mapbox/mapbox-gl-draw/blob/main/docs/API.md#events If adding new buttons using the mapbox-gl-draw events, they will also need to set the _drawingHappening state as relevant. A variety of other strategies were tried, including the following, but none worked: - Attempting to avoid the click propagating, but e.stopPropagation does not exist in this context so this generates an error; see mapbox-gl-js issue #9369 - Stopping the popup opening at the point of querying for features (using queryRenderedFeatures) at the clicked location; see: https://stackoverflow.com/questions/47576527/ - Closing the popup immediately on opening (which would probably have given flicker) - Overriding the map click somehow; see: https://stackoverflow.com/questions/45298202/ , which though helpfully pointed to the use of map.off/map.on

view details

push time in 5 days

issue commentcyclestreets/cyclescape

Issue elimination - database migration

Just to say we now have a volunteer for the tagging work, so if you can generate the data for this I can get them started.

mvl22

comment created time in 6 days

CommitCommentEvent
CommitCommentEvent
CommitCommentEvent

issue commentPanopto/SchedulingTool

Set up instructions need updated everywhere - ReadMe, Video, Support Article

We've just ran into this also. This really mainly just needs updating in section 2 at https://support.panopto.com/s/article/scheduling-tool

@Panopto Is there any chance this could be expedited? The documentation bug above was reported almost five years ago now, and I doubt it really takes that long just to update a webpage to change a reference. Thanks :)

gjgbarclay

comment created time in 9 days

push eventcamunigeography/abstract-submissions

mvl22

commit sha b548a69195b0c2cbe5d2151baf717ca3414454f7

Add additional presentation type

view details

push time in 11 days

push eventcamunigeography/spri-shop

mvl22

commit sha e65bbaabd835ee1835016743b9e6e3156f5b0464

Add support for disabling themes, to avoid having to delete their allocations

view details

push time in 12 days

push eventcyclestreets/cyclescape

mvl22

commit sha 61ddaa0ecb320b64ba202a423688025abfd01273

Fix missing links on group homepage

view details

push time in 13 days

push eventcyclestreets/cyclescape

mvl22

commit sha 7437b98876626fb47547ed7341208d78dc15d894

Redesign files: Add robots.txt

view details

push time in 13 days

issue commentudsleeds/openinfra

recode_pedestrian()

I've been thinking about encouraged pedestrian network (discussed above) and how I could sensibly categorize OSM highways based on that.

In general, the problem with deciding up-front on what is encouraged is that preference is quite subjective, and it depends really on your use-case. Admittedly, walking at least isn't quite as bad as cycling, where 10 cyclists will have 11 opinions as we say here in Cambridge ;)

For instance, is it preferable to walk on a very wide pavement, or to take the parallel street that has much less traffic but has lower subjective safety due to low levels of natural surveillance?

For instance, paths in a park may be preferred by some, but once it gets dark, that status changes.

Personally I would aim for a dataset that simplifies a key set of attributes to simple booleans, enabling downstream uses to make that subjective judgement by querying those pre-assembled fields. For instance:

  • isWide
  • isLit
  • isSegregatedFromCyclists
  • isSharedSpace

Each of these are quite painful for people to determine, so if this package determines them upfront, you suddenly make it much easier for people to then make whatever subjective judgements they want to optimise on.

GretaTimaite

comment created time in 15 days

issue commentudsleeds/openinfra

recode_pedestrian()

but the lines are currently straight

Yeah, we just haven't put the geography alignment up the priority list yet.

GretaTimaite

comment created time in 15 days

issue commentudsleeds/openinfra

recode_pedestrian()

sidewalk tag would be a good indicator for that

The sidewalk tag is really a negative tag, in the sense that in most part of the world is only used to indicate an exception to the norm. No-one bothers to put sidewalk=yes on every road, because people know that roads by default do have footways alongside. You only need it when there isn't a sidewalk, which is relatively rare. Using it to indicate any kind of quality level would give incorrect results.

For instance, pretty-much every street here has footways on both sides, but only a fraction use the tag, and those that do are a completely random subset: https://overpass-turbo.eu/s/1eRZ

the encouraged one could return only the primary roads where motor traffic's segregated, to some extent, from pedestrians

Even if the path is separately drawn you can't really determine the level of separation from the road.

NB Areas with better OSM coverage tend to see a higher ratio of streets with the footway drawn in separately, but most areas of the world haven't yet bothered.

However, if the speed limit is 20mph (i.e., in residential areas) then sharing the space with motor traffic might be fine.

Not really. In Cambridge for instance, every local street (<tertiary) is now 20mph, like an increasing number of towns that have gone "Twenty's Plenty". They are former 30mph. They really are not shared space. You could walk in the middle of the road in many cases but you have to be alert for vehicles coming behind.

This street is 20mph, though admittedly it is tertiary: https://www.cyclestreets.net/location/152460/

GretaTimaite

comment created time in 15 days

push eventcamunigeography/timetables

mvl22

commit sha 290001e588c9fbbef85ba1ba9150c6482df9680c

Add link to settings from lecture capture page

view details

push time in 16 days

more