Data Collection for .NET shows how a robust application can be built with the ArcGIS Platform using the ArcGIS Runtime SDK for .NET, WPF, and UWP. It demonstrates best practices around some simple but key functionality of the ArcGIS Runtime. Using your organization's web maps, you can use Data Collection as-is, or extend it to meet your specific needs.
The project also demonstrates some patterns for building real-world apps around the ArcGIS Runtime SDK.
Read the docs for a detailed explanation of the application, including its architecture and how it leverages the ArcGIS platform, as well as how you can begin using the app right away.
You will need Visual Studio 2017 or later (2019 or later is recommended).
Fork the Data Collection repo.
Once you have forked the repo, you can make a clone and open
DataCollection.sln in Visual Studio.
cdinto into the cloned repository's directory
If you make changes in the fork and would like to sync those changes with the upstream repository, you must first configure the remote. This will be required when you have created local branches and would like to make a pull request to your upstream branch.
git remote -vto list the current configured remote repo for your fork.
git remote add upstream https://github.com/Esri/data-collection-dotnet.gitto specify new remote upstream repository that will be synced with the fork. You can type
git remote -vto verify the new upstream.
If there are changes made in the original repository, you can sync the fork to keep it updated with upstream repository.
git fetch upstreamto fetch the commits from the upstream repository
git checkout masterto checkout your fork's local master branch.
git merge upstream/masterto sync your local
upstream/master. Note: Your local changes will be retained and your fork's master branch will be in sync with the upstream repository.
The app can be run as-is, but it's recommended you do some configuration to set up OAuth to be relevant to your users. At minimum, the app should not be deployed without these changes:
For OAuth configuration, create a new Application in your ArcGIS Portal to obtain a
Client ID and configure a
Redirect URL. The Client ID configures the ArcGIS Runtime to show your users, during the login process, that the application was built by you and can be trusted. The Redirect URL configures the OAuth process to then return to your app once authentication is complete.
data-collection://auth. We will use this URL in the Configuring the project section below.
Configuration.xmllocated in the
Propertiesdirectory of the
WebmapURLto match your organization's webmap.
RedirectURLproperty to match the Redirect URL you have set up when you registered your application (see section above).
ClientIDproperty with the Client ID generated when you registered your application (see section above).
Learn more about Esri Open Source Apps here.
Anyone and everyone is welcome to contribute. We do accept pull requests.
Generating table of contents for documents in this repository was performed using the MDTOC package for Atom.
Copyright 2020 Esri
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
A copy of the license is available in the repository's LICENSE file.
For information about licensing your deployed app, see License your app.
This project uses the following 3rd-party components: