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
The format of the minimum and maximum scale fields is hard-coded as a slash in v_dataset, e.g. “1/1000”. Could we make this a configurable option? In German for example, scales are written with a colon (1:1000).
The selected locale is available in the query v_dataset, so we could add some code there, or we misuse the glossary table for a “scale number separator” item.
Edit: adding a thousands separator would be nice, too. I guess that this can be provided by the system locale / number formatting.
The text was updated successfully, but these errors were encountered:
Do you have suggestions for this? For our internal application, I had added a glossary term scale_fraction which contains the fixed part (“1 :“ or “1 /”) and used in the v_dataset view.
It might be that additional settings (lc_numeric maybe?) are necessary for thousands separator and decimal point/comma in PostgreSQL. I’m not that versed in the topic, though :-(
The format of the minimum and maximum scale fields is hard-coded as a slash in
v_dataset
, e.g. “1/1000”. Could we make this a configurable option? In German for example, scales are written with a colon (1:1000).The selected locale is available in the query
v_dataset
, so we could add some code there, or we misuse theglossary
table for a “scale number separator” item.Edit: adding a thousands separator would be nice, too. I guess that this can be provided by the system locale / number formatting.
The text was updated successfully, but these errors were encountered: