ATFutures / geoplumber

Serve geographic data from R and consume with scalable front end.
https://atfutures.github.io/geoplumber/
59 stars 7 forks source link

Open source the repo #12

Closed Robinlovelace closed 6 years ago

Robinlovelace commented 6 years ago
layik commented 6 years ago

I take it, "use case" is real use case such as "serve the included data as an endpoint and consume it on the front end".

So a little bit more to do before we can go public.

Robinlovelace commented 6 years ago

Yes, something like 'imagine you want to visualise a dataset on transport and enable the results to be served on a public-facing website' is what I was thinking. Also showing the geojson-producing API will be another USP of the package.

Robinlovelace commented 6 years ago

Do you have clear next steps? Let me know if I can help in any way.

layik commented 6 years ago

Are you back in Leeds?

Clear steps indeed, how to share them/manage the project not quite sure. I was hoping I would use the GH project tool, but I cannot see other people using it. Throwing another tool into the toolbox is not always a good idea.

You can always help!

layik commented 6 years ago

https://github.com/ATFutures/geoplumber/projects/1#card-12605841

I could create more cards as said above, not quite sure where is best to manage the project. One of those cards would be the "aims and objectives"/scope.

Robinlovelace commented 6 years ago

Back next week. Down south to teach people R (yesterday) and to attend this Thursday/Friday: http://www.cyclingandsociety.org/2018cfa/

Robinlovelace commented 6 years ago

Awesome use of cards! Keen to learn how to use them productively.

layik commented 6 years ago

So the use case in more detail will be: Serve the meta data included in package and view them on front-end using gp_::function()s.

Robinlovelace commented 6 years ago

Sounds good!

layik commented 6 years ago

Almost there!

layik commented 6 years ago
screen shot 2018-09-06 at 19 50 14

Any backend with an endpoint "/api/endpoint1" serving "geojson" can now be added to backend and views on front end.

I actually think that is a "good" enough use case example,.

layik commented 6 years ago

What am I going to decouple? thinking it through ...

Robinlovelace commented 6 years ago

I think this is a great use case.

layik commented 6 years ago
$ du -sh .git
6.5M    .git
layik commented 6 years ago

README

Robinlovelace commented 6 years ago

this is looking really great @layik . the JS stuff seems like magic to me. probably like how R can seem like (black) magic on first sight. I've not tried the example. look forward to doing so. let's do that during a minihack next week. overall impression of this package: fired-up and ready to go :rocket:

Robinlovelace commented 6 years ago

https://www.youtube.com/watch?v=HdU2dxJgNsM

layik commented 6 years ago

“Fired up” is great!

Robinlovelace commented 6 years ago

Good progress. Suggestion: we aim to open source it by Friday. Possible? Good to have a deadline is thinking.

layik commented 6 years ago

Absolutely. Deadlines are great.

layik commented 6 years ago

Leaves us with getting rid of the history!

Robinlovelace commented 6 years ago

Over to you. Go for it!

layik commented 6 years ago

Managed to keep it to less than 0.6mb.

layik commented 6 years ago

Travis build triggered.

mpadge commented 6 years ago

Nice! Did you just get rid of all the history, or did you BFG it?

layik commented 6 years ago

It was not actually big (2.2mb) but decided to just get rid of all my "pseudo" private commits.

layik commented 6 years ago

It is backed up :)

layik commented 6 years ago

Now trying to make Travis happy.