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
Describe the feature. What should a user be able to do?
This isn't actually a new feature, but changing the current feature "Project Area" to instead be called "Gross Floor Area."
Why do we need this feature?
Currently, the field is called "Project Area," and when you highlight the field, it says, "Total area of development site only, not including areas on the site/parcel that are not developed." We discussed that, generally, the number that you want here is the gross floor area since that is more representative of the size of the development. People continue to input the lot area and not the gross floor area, so changing the name of this field would be very helpful.
Alternatives
Alternatively, we could change the description of the field to very explicitly say gross floor area, but I think changing the field name itself would be better.
Additional context
The text was updated successfully, but these errors were encountered:
Describe the feature. What should a user be able to do?
This isn't actually a new feature, but changing the current feature "Project Area" to instead be called "Gross Floor Area."
Why do we need this feature?
Currently, the field is called "Project Area," and when you highlight the field, it says, "Total area of development site only, not including areas on the site/parcel that are not developed." We discussed that, generally, the number that you want here is the gross floor area since that is more representative of the size of the development. People continue to input the lot area and not the gross floor area, so changing the name of this field would be very helpful.
Alternatives
Alternatively, we could change the description of the field to very explicitly say gross floor area, but I think changing the field name itself would be better.
Additional context
The text was updated successfully, but these errors were encountered: