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 current status of CCCS team deliberation was to use abbreviations in order to make file directory organization intuitive and orderly. Essentially we arrived at the following system:
Kartoza clearly has more experience in addressing these issues, so I'd appreciate getting your insights and recommendations. Our primary concern is avoiding duplication of names (like "census_area" and "road_lines").
Let's figure out a good approach to ensure that we can scale naming practices to work for multiple projects in different global regions.
The text was updated successfully, but these errors were encountered:
This issue continues an ongoing discussion from the cccs web 'core' on GitHub, as well as from discussions over email and elsewhere.
The current status of CCCS team deliberation was to use abbreviations in order to make file directory organization intuitive and orderly. Essentially we arrived at the following system:
We're currently using a Google spreadsheet to track files named using this convention.
And I am working on another file to clarify the taxonomy more generally.
Kartoza clearly has more experience in addressing these issues, so I'd appreciate getting your insights and recommendations. Our primary concern is avoiding duplication of names (like "census_area" and "road_lines").
Let's figure out a good approach to ensure that we can scale naming practices to work for multiple projects in different global regions.
The text was updated successfully, but these errors were encountered: