-
Notifications
You must be signed in to change notification settings - Fork 13
Post Get Query Syntax
MisterMartin edited this page May 12, 2015
·
1 revision
A page to discuss the syntax and behaviors of Post/Get queries.
Questions:
- Is there an accepted practice?
- Are they symmetrical; i.e. can a the same specification style work for both? In a post, data would be included; for a get, data would be returned.
- What are the specifiers?
- site identifier
- instrument identifier
- parameter name
- units
- time or time range
- What granularity is appropriate? Should a single post should be able to supply multiple parameters or multiple times, or both?
At least for the AHM, we may be able to get by with the default rails syntax, which looks like:
Or Mike may have already modified that, during the ingest development.
Project Management
- Stakeholders
- Communication
- Use Cases
- Requirements
- Deliverables
- Milestones Associated with a Release
- "Sandbox" Milestones
- Github Workflow
AWS
- AWS Portal Migrations
- Amazon Appliance Workflow
- Overview
- Bringing up a new CHORDS Portal
- Cloud Formation
- EC2 Costing and Memory Constraints
Docker
- Running CHORDS
- Docker on AWS
- Duplicating Docker/Influxdb portals
- Docker on Raspberry Pi
- Docker Details and Tips
- Running CHORDS on Windows 10
Influxdb
Data Formats
Google Maps
Ingest Utilities
Miscellaneous
- Recovery from a full disk
- Github/Dockerhub release scheme
- CHORDS gh-pages and jeykll
- Bootstrap
- CHORDS Portal Web Site
- Dashboard Helper Refactor
- Development Notes
- Heroku
- Meteobridge
- Migrating from mysql to mysql/influxdb portals
- NCAR Wx Stations into CHORDS
- PAWS to CHORDS
- Post Get Query Syntax
- Postgres Testing
- Rails Tips
- Ruby and Rails Resources
- CUAHSI Archive
Historical Archive