[BUG]: restrict_to_aoi not implemented
See original GitHub issuerestrict_by_aoi
is defined as a boolean argument in the raster tiler but doesn’t appear to be implemented. I was thinking of implementing this but instead of making it a boolean, the portion of the raster that falls within the aoi would remain and the portion of the tile that falls outside the aoi would be filled with the mean of the training dataset. I think this type of filling would work since labels are not present outside of the aoi_boundary (by definition of how aoi_boundary
should be used). Does this sound good @nrweir ?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Unable to restrict API access to REST route with imported auth
Describe the bug. when i try to create or update a REST API path and i choose to “Restrict API access” to “Authenticated...
Read more >Restrict API requests to only my own mobile app
I believe the best solution is to make requests to your API (from native code of course) with a custom header like "App-Version-Key"...
Read more >Maps API requests fail if API restrictions are applied to API key ...
The ability to restrict API keys to specific APIs has been temporarily removed, as it turned out to be incompatible with the Maps...
Read more >API security best practices | Google Maps Platform
Restrict your API keys · Digital signatures · Use separate API keys for each app · Delete unused API keys · Be careful...
Read more >Restricting API access with API keys - Cloud Endpoints
This page describes how to restrict API access to those clients that have an ... At the top level of the file (not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just wanted to say filling in with custom values (0 in particular) would be great to have as one of the options at least. Computing the mean can be time-consuming over a large area, and being able to mask the label raster with 0 where the imagery tile has no data would be useful (i.e. to not have these contribute to the loss during training).
Ideally, we enable both: allow users to specify a fill value (which they could derive from the full-dataset mean) or solaris could derive the mean within the image itself. Would essentially need to provide an argument specifying either a value to fill with, or allow users to specifiy
'mean'
, in which case solaris will get the image’s mean value and use that. e.g. a new argumentnodata_fill=None
where the user can provide, for example,nodata_fill=50
(or whatever other specific value they want) ornodata_fill='mean'
in which case solaris will get it from the image for them.