-
Notifications
You must be signed in to change notification settings - Fork 0
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
Develop a plan on moving the service to SWRCB #15
Comments
@jrmerz sez... @brmagnuson Perhaps this should be a new ticket, but here is the breakdown for transferring the application. Application assets (HTML, JS, CSS), basically everything in stored in this repository, needs to be hosted on a state server. Finally, we are still working out the solution for submitting data back to postgres instance (this ticket). @qjhart I think we need to have a more formal discussion about this if that functionality is required for the transfer. |
@brmagnuson / @jrmerz . OK, so I want to make sure that we are all on the same page here, so that we understand everything that our backend is doing, and what needs to be done.
OK so...
|
@qjhart great point about the HUC layer. Think that comes from a layer hosted over on Google Maps Engine, which is due to be shutdown soon and we need to find a replacement. |
Updates on this issue
|
Hi all, We're getting going on delivering this service to SWRCB again - @qjhart and @jrmerz I have two quick questions for you:
Thank you! |
OK, looks like it's a self-contained node app that relies on a water board GIS server and Google Docs - question 1 still stands though if you have a moment, and I may have questions about how uploads were handled. |
@nickrsan Let me see if I can help here. So no NodeJS. The app itself is a static web app. Files are either 'uploaded' (not to server, just added to client), then parsed and rendered on client. Or files can also be added to a public readable google drive directory, that how they show in 'Public Directory' (https://docs.google.com/spreadsheets/d/1ACi7P0pOy-JRjtw6HribQphhEOZ-0-CkQ_mqnyCfJcI/edit#gid=0). The Id column is the id of the sheet to be rendered. Both directory sheet and data sheet need to be public readable on google drive. The (http://atlas.cws.ucdavis.edu/arcgis/rest/services/Watersheds/MapServer/0/query) service is then used to lookup region geometry while the (http://gispublic.waterboards.ca.gov/arcgis/rest/services/Water_Rights/Points_of_Diversion/MapServer/0/query) service is used to look up point information. |
Thanks for the clarification Justin - that helps a bunch and will save me a
bit of trouble looking for the geometry (I'd seen the reference to the
Water Board services in the code, but not to Atlas).
So, I'd assumed that it was node originally because I saw the build
instructions, but seems like I just have a misunderstanding about how this
all works - I saw that it ultimately builds a static set of files (which is
really nice construction for this, by the way). I'll take a look and see if
I have any other questions, but I think for now I know enough to proceed
and probably to get them the working setup.
Thanks again for chiming in!
…-Nick <nick@enviroconsumer.org>
On Sat, May 6, 2017 at 9:08 AM, Justin Merz ***@***.***> wrote:
@nickrsan <https://github.com/nickrsan> Let me see if I can help here.
So no NodeJS. The app itself is a static web app. Files are either
'uploaded' (not to server, just added to client), then parsed and rendered
on client. Or files can also be added to a public readable google drive
directory, that how they show in 'Public Directory' (
https://docs.google.com/spreadsheets/d/1ACi7P0pOy-JRjtw6HribQphhEOZ-0-CkQ_
mqnyCfJcI/edit#gid=0). The Id column is the id of the sheet to be
rendered. Both directory sheet and data sheet need to be public readable on
google drive.
The (http://atlas.cws.ucdavis.edu/arcgis/rest/services/
Watersheds/MapServer/0/query) service is then used to lookup region
geometry while the (http://gispublic.waterboards.
ca.gov/arcgis/rest/services/Water_Rights/Points_of_
Diversion/MapServer/0/query) service is used to look up point information.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApzMS1HzbGhwqSuySxVUR_DXCO_pih0ks5r3JrigaJpZM4Fa_6Y>
.
|
Ya, so the code is written using NodeJS/CommonJS Modules, they run through Grunt + Browserify to create a browser friendly package. Proly why you got thrown off. Here a couple commands of interest while developing Commands
install NPM and Bower dependencies
Runs watch process. This watches for changes to the lib/shared js files and builds a new public/js/app.js file automagically after you make a change
Serves /public
Builds /dist
Serves /dist |
@brmagnuson sez...
Just checking in on the status of this. The State Board is starting to murmur about getting started on porting the website over to their side rather than perpetually maintaining it at Davis, which I believe was the intent all along. I said you guys had some improvements you still wanted to make (mainly this issue) and I would check in and see how it was going.
The text was updated successfully, but these errors were encountered: