|
|
Data file uploads are supported through the ArcWeb site (Build tab>Upload Data and Create Layer). See Uploading data for details on uploading data to the ArcWeb site. File uploading is not supported through SOAP.
To geocode features, first use the method addFeatures to add addresses and any other corresponding attribute information to your data file. Once the data file is populated, use the method geocodeFeatures to have ArcWeb geocode the addresses and assign x,y coordinate locations to each record. When you use the method geocodeFeatures, ArcWeb automatically appends two fields—Geocode Service and Geocode Status—to your data file. The values in Geocode Service show which Address Finder data source geocoded the addresses. The values in Geocode Status contain geocode match codes. See Geocoding codes for match code descriptions.
To update features in a data file, use the method updateFeatures. This method expects parallel arrays in order to successfully complete the updates. The array of feature IDs specified in the method’s featureIDs property need to match up with the FeatureUpdateOptions.fieldValues array.
NOTE: You cannot have a fieldname and the same fieldname with an underscore after it, for example, "TEXT" and "TEXT_".
Data Manager charges .1 credit for each feature you upload, edit, or delete and charges one credit for each geocode attempt. If you upload x,y fields, Data Manager uses those values and does not geocode your records (or charge for geocoding).
You are charged credits when your group stores more than 50 MB worth of data. You are charged 0.2 credits per day for each MB over 50 MB that you consume. The credits are charged to all user accounts that have created data files that are using storage space. The number of credits charged to each account is based on the ratio of each user’s storage space to the entire group’s storage.
For example:
Bob: 10MB
Joe: 20MB
Jim: 30MB
TOTAL FOR THE GROUP: 60MB
The group as a whole is charged 2 credits per day for storing 10 MB more than the allotted 50MB of data (10MB * 0.2 credits per MB).
Broken down per user, this would be:
Bob: 0.33 credit (10/60 * 2)
Joe: 0.67 credit (20/60 * 2)
Jim: 1 credit (30/60 * 2)
If your account expires or you run out of credits, ArcWeb stores your data for 30 days. After that time, you will need to upload your data when you reactivate your account.
Data Manager supports any language that uses UTF-8 characters. Geocoding works in the country's native language.
Visit the Feedback page to give comments or suggestions about the ArcWeb Developer's Guide.