Vast amounts of data content is available through ArcWeb Services. For example, when you create a map, you choose what data to show—streets, live weather, topography, census statistics, and so on. ArcWeb Services refers to this content as layers and data sources. A layer is a specific piece of data. On a street map, for example, roads, national parks, political boundaries and rivers are examples of different layers. A data source is a combination of related layers plus information about how to display or use the data. For example, a mapping data source contains information about the map's appearance and an address data source contains information about how to geocode x,y coordinates. See Service Finder for a complete list of available data sources (for SOAP services only).
You can use data content from ArcWeb or you can build your own data sources from custom data files and layers. You can also use ArcWeb layers to build your own data sources. See Builder overview for more information on creating custom data sources.
|
|
Developer APIs expect the same four-part format, separated by periods.
The first part is the owner of the service, for example, ArcWeb.
The second part is the name of the data provider, for example, ESRI.
The third part is a general description of the type of data; for example, "Satellite" is a satellite imagery map.
The fourth part is the geographic coverage of the data source, for example, "World". Map icon sources list "Icons" in the third part instead of a geographic coverage.
Each part is separated by periods, for example, ArcWeb:ESRI.Satellite.World.
Short descriptions are intended to be easier-to-read versions of the API name; for example, the short description of the SOAP name ArcWeb:ESRI.Satellite.World is ESRI World Satellite Map.
All ArcWeb and custom content comes with extensive metadata (information about the content). Use the Content Library or Content Finder Web Service to view metadata. You can also use the Data Source Finder for a quick view of available content and related metadata.
You can use Builder to upload your own data to use with ArcWeb Services. This data can be point, line, or polygon data. When you upload data, the system creates a default layer for it. You can later modify this layer.
Only an administrator can transfer a user’s content and styles to a different user in that group. Content and styles must have unique names so new users may need to rename some content.
Administrators can set user data to inactive and can later reactivate the data (for example, when the administrator gives the user more credits).
If a user unshares a layer, that layer is automatically removed from all services, even if other users created services with that layer. ArcWeb sends warning e-mails to all users using the now unshared layer so they can update their services. If a user unshares a Spatial Query layer, the Spatial Query service is automatically deleted and users using that service are notified.
See Managing users and groups for more information.
Data storage space belongs to the group.
Data storage costs are charged to the users who uploaded the data on a per-MB per-day basis. Storage cost is discounted by the free storage allocated to the group on a proportional basis to each user.
For example:
Bob uploads 80 MB of data; Jill uploads 20 MB.
Your upload – (Free * your upload / group upload).
So Jill owes 20 – (50 * 20/100) = 10 MB worth of cost each day.
See Viewing storage information for details.
Visit the Feedback page to give comments or suggestions about the ArcWeb Developer's Guide.