Eric Hofesmann
Eric Hofesmann
Similar to `dataset.info` it would be useful to be able to store some form of `dataset.field_name.info` that can contain a dictionary (or other structure) of any arbitrary information that the...
[DOCUMENTATION] Add a guide mapping common pandas dataframe operations to FiftyOne view expressions
Pandas provides a lot of similar capabilities to filtering and slicing dataframes that FiftyOne provides to create views of datasets. For new users that are familiar with pandas, it would...
Similar to https://github.com/voxel51/fiftyone/issues/2163, it would be useful to be able to visualize `dataset.info` directly in the App. I imagine in some kind of JSON viewer, potentially alongside the plot plugins?
Currently, when you call `fo.list_datasets()`, it prints either a list of all dataset names or a list of all dataset info. Given that users can end up with hundreds of...
GeoLocations can sometimes be stored at a detection-level. It would be useful to be able to visualize each detection geolocation point in the map directly. Lassoing points could then either...
A number of users have requested being able to visualize 3D meshes in the App in addition to pointclouds. More research needs to be done to decide on mesh formats...
Invalid lat and long coordinates in a `GeoLocation` field will result in the App throwing an error: ``` Error: Invalid LngLat latitude value: must be between -90 and 90 at...
If an image is rotated by default, it would be useful to have the option to rotate it do different angles in the App. While this could be done outside...
The error that is raised whenever a mapbox token is not provided but attempting to visualize a geolocation map in the App should have a link directly to this page...
When a field has a value that is many characters long, the JSON viewer becomes unusable. It would be useful to have a scroll bar in the JSON viewer. ```python...