-
Notifications
You must be signed in to change notification settings - Fork 3
Add method to post annotations for project #42
Conversation
Previously I was in the habit of adding a method for each RV script, but it's too much work to keep these up to date, and they aren't very useful. The only method we need is one that corresponds to making predictions.
If we can create project config files which represent a set of projects and their associated files, then I can train and eval models using RV without needing anything further from this Python client, which simplifies things.
3170c3e
to
9597250
Compare
Note: I need to make a release containing this PR. |
rasterfoundry/spec.yml
Outdated
x-top-matter: | ||
- title: Introduction | ||
level: 1 | ||
content: | | ||
The Raster Foundry API allows developers to find, view, and analyze geospatial data in Raster Foundry. As the name implies, it's especially useful for working with large raster datasets like satellite imagery. | ||
content: > |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pretty sure this will break things in the spec - the swagger.io editor defaults to swagger 3.0, and we're using 2.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed it. I'll use the 2.0 Editor for now on.
This also has the Polygon definition added which should be added to the spec.yml in the RF repo. I have a note in an issue to do this.
9597250
to
b9c4d84
Compare
Can we try to get this reviewed soon? It's blocking me on https://github.com/azavea/raster-foundry-deployment/pull/115 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
My main concern is hardcoding in rastervision settings
@@ -1,4 +1,4 @@ | |||
RV_CPU_QUEUE = 'raster-vision-cpu' | |||
RV_CPU_JOB_DEF = 'raster-vision-cpu' | |||
RV_PROJ_CONFIG_DIR_URI = 's3://raster-vision-od/configs/projects' | |||
RV_PROJ_CONFIG_DIR_URI = 's3://raster-vision-lf-dev/detection/configs/projects/rf-generated' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't these kinds of settings be stored in a gitignored file with an example placeholder file committed? We do something similar in RF
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I have too much other stuff do right now, so I made an issue to do that: #43
This PR adds a method to posts annotations for a project that are stored in a JSON file on S3. This will be called by the Lambda function in https://github.com/azavea/raster-foundry-deployment/pull/115. This also makes some other changes to stay in sync with the latest RV and removes some methods which are not useful and annoying to maintain.
To test making a prediction, run the following commands:
To test posting predictions, run the following after clearing the annotations in the UI at https://app.rasterfoundry.com/projects/edit/de3780a1-9f3e-4fa3-a811-ad3060b64866/annotate
Connect #41