This content has been marked as final. Show 5 replies
Basic�??With the Basic edition, you get geodatabase management (ArcSDE) and the ability to publish feature services for map visualization and query (no editing). You also get the geometry service and the ability to publish geodata services.
- This means yes! You can publish services using data that is being stored in SDE.
Your second question is a little confusing.
A feature access is capability that exists within map services (could be dynamic or cached).
Feature services allow you to serve features over the Internet and provide the symbology to use when displaying the features. Clients can execute queries to get features and perform edits that can be applied to the server. Feature services provide templates that can be used for an enhanced editing experience on the client. Data from relationship classes and nonspatial tables can also be queried and edited using feature services.
Since editing isn't allowed with the basic license you do not need to use feature access and will not gain or lose any performance.
Thanks NelsonDM1 for your reply. Now the issue that I am not getting here is that if both feature service and dynamic service can render data,
1 - Why is the feature service supported as read-only in the basic license? Is the read-only feature service identical to dynamic service?
2- In other words, what is a read-only feature service used for? and what is the exact difference between feature service and dynamic service?
3- Can i create a read-only feature service under a basic license, where the map contains many layers and complex geometries, and consume it from a Flex app?
I know I am asking a lot of questions, but I am kind of lost here... Thanks in advance for your responses...
1 - Why is the feature service supported as read-only in the basic license?
This is something that is controlled by esri to make different levels of server accessible to users that may not need all the functionality at the higher license levels (standard / advanced)
2- Is the read-only feature service identical to dynamic service?
No. A feature service is used mainly for editing. It also allows users to query and view the data in the feature service. Unlike with map services, which have an ExportMap function to draw the map, visualization of feature services works completely from queries. The server returns the queried features to the client, then the client does the work of drawing the features.
3- In other words, what is a read-only feature service used for?
I think this was answered in the previous question.
4- Can i create a read-only feature service under a basic license, where the map contains many layers and complex geometries, and consume it from a Flex app?
Thanks Nelson. You've been of great help!! I will try to create and publish a feature service with complex geometries and consume it from flex under the basic license.
Before launching into building the web application, allow me to restate one additional time my concern. If I am to build a GIS flex web-based application to a certain new project/client:
1- What ARCGIS for Server license and what related map services would I choose for the project and why? (Dynamic map services, feature map services with standard licensing or read-only feature map services with the basic licensing or any combination of?)
- Case 1: The main functionalities are regualr mapping capabilities (view, search, retrieve map data in addition to identifying map features), without editing map features.
- Case 2: The main functionalities are regualr mapping capabilities (view, search, retrieve map data in addition to identifying map features), with editing map features enabled.
2- Would you advise of any literature/documentation that can help clarify the above?
In other words, would I recommend ARCGIS for Server basic to my client and build a web-based flex application consuming read-only feature map services (Noting that no web editing functionality is required)? Or would it be better to recommend ARCGIS for Server standard and have the web based flex application consume the dynamic map services?
Also, if web editing funcitonality is required (accordingly we would need ARCGIS for server standard), would I drop the use of dynamic map services totally and rely on feature map services for display as well as for editing in the web application? Or should they be mashed up, the dynamic map services for the display and the feature map services for the editing?