You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None of the trees in Vancouver, for instance, seem to have a common name specified, which is required to make any changes or updates to that in the backend. So the FE has to choose some arbitrary way of setting that field to make an edit.
All tree data in the vector tiles should have consistent naming and formats. Trees without required fields should get defaults or not be included in the tiles.
The text was updated successfully, but these errors were encountered:
None of the trees in Escondido have any name or species info, which makes them uneditable. If these trees are going to be included in the vector tiles, the UI needs special handling for them.
None of the trees in Vancouver, for instance, seem to have a
common
name specified, which is required to make any changes or updates to that in the backend. So the FE has to choose some arbitrary way of setting that field to make an edit.All tree data in the vector tiles should have consistent naming and formats. Trees without required fields should get defaults or not be included in the tiles.
The text was updated successfully, but these errors were encountered: