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

Groundwater Wells (GWELLS) - Custom Search and Interactive Map #1101

Closed
bcdevex opened this issue Jan 17, 2019 · 8 comments
Closed

Groundwater Wells (GWELLS) - Custom Search and Interactive Map #1101

bcdevex opened this issue Jan 17, 2019 · 8 comments
Assignees

Comments

@bcdevex
Copy link

bcdevex commented Jan 17, 2019

This issue has been auto-generated to facilitate questions about a paid opportunity that has just been posted on the BCDevExchange.

To learn more or apply, visit the opportunity page. The opportunity closes on Saturday, January 26, 2019.

@LindsayMacfarlane
Copy link

Hello! @ashleydhillon and myself are the main contacts for this code with us opportunity. Please feel free to reach out to us with any questions you may have about this opportunity and we will do our best to respond as soon as possible.

@mark-a-wilson
Copy link

Hello all interested applicants. Please note that the closing deadline for proposals is January 25, 2019 at 4:00 PM PST (as stated on the opportunity page), NOT Jan 26 as stated at the beginning of this thread. (Bug with the BCDX app) Apologies! 🙏

@imoon
Copy link

imoon commented Jan 22, 2019

@LindsayMacfarlane or @ashleydhillon, for the search API, should the searching be real-time as the query is being typed or are you expecting a request response flow? Also, can the filtering and ordering be done on the client on the search results, or do you want those as distinct functionalities of the API?

@LindsayMacfarlane
Copy link

We would not be expecting real-time searching, but the API should include functions to filter and order the results.

We would hope the successful candidate would work with the team to determine the best approach.

As an FYI - the data set includes about 110,000 wells and that number grows on a daily basis so this could affect the approach taken/proposed.

@bcdevex
Copy link
Author

bcdevex commented Feb 8, 2019

This opportunity has been assigned

@ashleydhillon
Copy link

We want to thank everyone who submitted proposals for this opportunity. For the unsuccessful candidates, if you'd like to have feedback, please don't hesitate to contact @LindsayMacfarlane or @ashleydhillon.

@mark-a-wilson
Copy link

Hey @ashleydhillon - presuming that closing this issue means that work is complete and you'll be paying the full amount? (Thanks for confirming ... just following up on tracking Code With Us opportunities.)

@ashleydhillon
Copy link

Hi @mark-a-wilson - yes that's correct. I'm hoping this is the last step but please let me know if there's anything else I should be doing :) Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants