"Capacity" string should be split into multiple strings because the same label is used for example on amenity=restaurant - in my language it's not the same word ("obj臋to艣膰" for storage_tank and "liczba miejsc" for restaurant).
@jidanni Do i have to change the label in presets.yaml file or fields.json or in capacity.json file??
@karmanya007 Change the label in capacity.json and then run npm run build and commit the derived data as well.
@quincylvania Thanks 馃槃
@karmanya007 Actually, for this you'll have to create a new field like capacity_volume.json and leave the existing capacity field alone, since it's used for other things too. Check out the presets guide.
@quincylvania Okay. One more thing. Do i have to switch to the dev server on the localhost version?
@karmanya007 You only have to use the dev server if you need to upload fake data, so probably not for this issue. If you're unsure about something, feel free to open a draft pull request and we can discuss things there.
@quincylvania I have add the units to both the water tank and the storage tank (They both use the same key=capacity). Is this fine or only the water tank needs the units (cubic meter)?
@quincylvania PR Opened
@quincylvania Could you review #8112
Done by @karmanya007 in #8112.
Most helpful comment
"Capacity" string should be split into multiple strings because the same label is used for example on amenity=restaurant - in my language it's not the same word ("obj臋to艣膰" for storage_tank and "liczba miejsc" for restaurant).