Arcade Library - City of Dublin, Ohio

This respository organizes examples of Arcade expressions based on their function and language features. We use this repository internally to gather and organize examples of arcade script within our projects. It is our hope that this tool will create a more streamlined way of learning, utilizing, and stealing repurposing arcade script, especially in the context of local government GIS development.

Organization

Files/script examples should be organized into folders based on their function/language feature. For example, intersect functions examples should be included in the intersects folder which is nested in the GeometryFunctions folder For naming conventions, we recommend a brief explanation of the project purpose/work unit. For example, a file containing intersect functions used to create informative pop-ups in a webmap for the Legislative Affairs work unit is named LegislativeAffairsPopUps in the intersects folder.

How to Contribute

Thank you for contributing to our growing library of arcade expressions for GIS users and developers in local government! Here are some important resources:

• City of Dublin, Ohio tells you more about who we are.
• ArcGIS Arcade Library gives you an overview of arcade.
• ArcGIS Arcade Function Reference provides general examples of Arcade functions.
  • Our organizational sysem closely follows the structure of this resource. When contributing, we ask that you follow this structure.

Submitting changes

Any contributions you make are greatly appreciated. When adding a new file of arcade script, we recommend including a few notes describing what your script accomplishes.

If you wish to add a file/make a change, the best practice is to create changes in a branch and submit a pull request. This lets you discuss and review potential changes with collaborators and add follow-up commits before making changes to the main branch. However, as administrators through DublinOhio, you will have permission to directly commit changes to the main branch without submitting a pull request.

Make Changes by Dublin Staff

1. Navigate to Directory
2. Create File
3. Name File
4. Commit Changes to Main Branch

Make Changes if Outside Dublin

1. Fork the Project (if outside the City of Dublin)
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request
6. (Administrator) Merge pull request (accept changes)

Additional Information

• Please see our CONTRIBUTING.md to learn more information about adding files, folders, and text formatting.
• To learn more about pull requests please click here.
• The purpose of this project is to organize a library of arcade expressions. Read more about coding conventions within arcade here.

License

Distributed under the General Public License version 3. See LICENSE for more information.