This repository has been archived by the owner on Feb 7, 2020. It is now read-only.
Use carto dataset instead of Open311 API endpoint #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This still limits queries to the request ID, but uses the open data set instead of the Open311 API that Unisys built that's behind gatekeeper. The reason is so that we can later allow searches by other fields (address and request type, which 311's requested). We may want to have 311 test this with a few requests just to be sure, but so long as the open data sync is working this should be fine.
/cc @tswanson @Alexander-M-Waldman