Skip to content
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

Follow-up issues for LBLD docs #64

Closed
11 tasks done
jywarren opened this issue Apr 5, 2019 · 4 comments · Fixed by #65
Closed
11 tasks done

Follow-up issues for LBLD docs #64

jywarren opened this issue Apr 5, 2019 · 4 comments · Fixed by #65

Comments

@jywarren
Copy link
Member

jywarren commented Apr 5, 2019

Just collecting some here!!! 👍

Progress to date is really tremendous, @sagarpreet-chadha! You've done an incredible job. I'm now giving it a fresh look, and thinking about what could come next. Would love your thoughts on these!!!

  • Color code the markers on the map according to the precision. -- actually this was just to demonstrate the principle in the demo; we could keep it as a feature but I had imagined not being a default behavior. What do you think, @sagarpreet-chadha ?
  • Can we add a couple screenshots from the blog post into the README to illustrate?
  • Under https://github.com/publiclab/leaflet-blurred-location-display/blob/main/README.md#basic, we should maybe say First, you need to make some blurred locations. Let's create 3 of them and add them to the map. and then show how to create three and add them in as short a code segment as possible. One thing I'm wondering is how the options_display is passed into the constructor and we could show that more clearly in the "Basic" section!
  • could we have a constructor option to switch between heatmap and marker mode? Like:
blurredLocations = new BlurredLocations({
  style: 'heatmap' // or 'markers' or 'both' ?
});

Possible changes

  • does options.locations auto-generate the BlurredLocations? Why do we make only one blurredLocation? It kind of seems like we should make one for each coordinate pair, using this syntax?
  • Actually, perhaps we need to change the syntax of the BlurredLocation constructor so it can be added to a map the same way a standard Leaflet object is added, with `addTo(map) as in these instructions -- sorry, that would be a breaking change, I suppose... but in the spirit of making it a 'normal' Leaflet object?
  • locations_markers_array - maybe we should rename this getVisibleLocations()?
  • SourceUrl_markers_array is this the same as above but for remote locations? What if we instead just added a property to each location like source: 'remote' and then only used the above getVisibleLocations(); method instead of having 2?
  • could getMarkersOfPrecision likewise return just 1 array?
  • could we illustrate precision by referencing the chart in https://github.com/publiclab/leaflet-blurred-location#human-readable-blurring ?
  • let's open an issue to add the ability to pass an array of precisions or a range (not sure how, maybe { min: 0, max: 11 } into getMarkersOfPrecision() -- we don't have to implement it, but it'd be a nice next step later.

OK, this is a lot! But it's so exciting to have come this far!!!

@jywarren
Copy link
Member Author

jywarren commented Apr 5, 2019

Follow-up from #17 !!!

@sagarpreet-chadha
Copy link
Collaborator

sagarpreet-chadha commented Apr 12, 2019

Adding these here :

@sagarpreet-chadha
Copy link
Collaborator

Okay so all the above issues are solved in these PR's 😄 :

⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️ ⭐️

@jywarren
Copy link
Member Author

Awesome, let's close this then!

@jywarren jywarren unpinned this issue Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants