-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the same case on all value lists #385
Comments
Since all theses values have unique codes, we could easily provide a uniformed case french translation. |
It's not only for french, but yes. Now you need to decide wich way go: uppercase or lowercase ;) |
It's mainly a community decision and some user comfort, as these rely on value codes. Here is a sample of reaches in TEKSI wastewater : Here is the equivalent for pipes in QWAT : But what I find hard to decide is when translating, do we care more about the data and its conversion into other systems like geoportals -> approach of having lowercase with underscore is the best (with language like german that will still have some mandatory uppercases.) Or do we care more about the user (geomatician, GIS operator) feeling and how he likes his fields to be displayed. For materials in QWAT in pully we had to create a custom displayname to fit these user needs. This can have a large impact for any user who uses the solution because they will have to adapt this everywhere theses attributes are used. (geoportals, FME, DWG, ...) |
I would fix it like this for now (as it will surely change when SSIGE releases its datamodel) :
|
There is a lack of case consistency for values lists.
Some examples:
qwat_vl.status
:qwat_vl.source_type
:qwat_vl.precision
:The text was updated successfully, but these errors were encountered: