Local installation instruction and formulations in UI, especially "label". #211
Conversation
|
@Ettrig What do you recommend how this should be communicated to general user ?
From your PR I got an understanding you used term : osm features , map features ! |
yes, branching is ideal |
| @@ -114,9 +114,9 @@ const AOI = (props) => { | |||
| return ( | |||
| <> | |||
| <Grid item md={12} className="card" marginBottom={1}> | |||
| <Tooltip title="For each AOI, we need to make sure labels inside it are alighed and complete to acheive best model accuracy"> | |||
| <Tooltip title="For each AOI, we need to ensure that all buildings are mapped and correctly aligned."> | |||
There was a problem hiding this comment.
Currently its building but label might not represent only buildings later stage , I wonder how we can communicate this
There was a problem hiding this comment.
This is surprisingly difficult. We cannot say "all map features" because we cannot handle all kinds of map features. Saying "all map features that fAIr can handle" is too complex and subtle. Can we stay with "buildings" and hope it is updated when needed? I think that even if roads and water flows are added, "buildings" is more useful than "labels".
| @@ -170,7 +170,7 @@ const AOI = (props) => { | |||
| {/* <IconButton aria-label="comments"> | |||
| <DeleteIcon /> | |||
| </IconButton> */} | |||
| {/* <Tooltip title="Create Labels on RapID Editor"> | |||
| {/* <Tooltip title="Create map feature in RapID Editor"> | |||
There was a problem hiding this comment.
map features sound good
The word "label" is used here in a very technical sense that is peculiar to CNNs, especially early CNN research. We should try to not burden the users with more implementation details than necessary.
It was my intention to make divide these changes into two different pull requests. But I missed making branches and find it very difficult to add them now.