Web maps support workflows on connected and disconnected use as well. Web maps also integrate directly to the ArcGIS Security Model and you can use the sharing functionality to define who has access to them. Full platform and API supportĪs part of the key information model, web maps have full support from the ArcGIS Runtime SDK. You could say that the web map is a single point of truth that contains the map definition. When you use one map in many from different clients, you can be sure that the changes are delivered to all of them since all of them are pointing into the same configuration. You don’t need to make a new release just for this. You can, for example, change the symbology, change popup definition or add a new layer and changes are used when the web map is loaded next time. Since the application is loading the map dynamically from the Portal, all the new updates made to the web map is delivered to the client. Dynamic content distribution with single configuration It makes sense to separate map definition from the application code and with web maps, you can achieve this very easily. Separation of concerns is a very used principle in software development. Often creating data architecture and maps is a very important part of the project and requires dedicated people with a different skillset. If you are a developer who is focused on the application development, you could focus on the application features and leave map creation for other team members. Separation of responsibilities and specialisation These applications make it easy to search or create services and create, publish and share web maps. You can use tools that are tailored for creating web maps such as the Map Viewer or ArcGIS Pro. Sure enough, that sounds all fine and dandy but what’s in for me? Here is a couple of good reasons why you should look into using web maps as part of the ArcGIS Runtime application. When these two parts are present, it is easy to share the web map between multiple clients and systems. In my point of view, the definition of the map and the description of the map are logically one unit – a web map. Web maps can also be stored locally as Mobile Map Packages (mmpk-file) or offline maps but more about these later. These items define metadata about the map such title, description and terms of use. The web map definition is typically stored and shared through ArcGIS Portal ( ArcGIS Online or ArcGIS Enterprise) as ArcGIS Portal Items. The web map definition is a json representation of the map and its content and implements Web Map Specification. They have 2 different parts of data, web map definition and item information. ![]() Web maps are in general a framework for sharing geographically referenced data. Often people also use terms map and web map interchangeably. You can find several different definitions or explanations of what web maps are if you look at the documentation around. Using web maps in ArcGIS Runtime: Accessing groups and items.Using web maps in ArcGIS Runtime: Simple architecture on ArcGIS Online.Using web maps in ArcGIS Runtime on high-level.This post is part of “using web maps”-series. The topics are based on the “Working with maps online and offline”-presentation but hopefully I will go to the scenarios in more detail. The idea is to look on how to use the platform to leverage functionality in the ArcGIS Runtime level and how to do that in code. In the next posts, I will be looking into the capabilities that the ArcGIS platform provides around the web maps from ArcGIS Runtime SDKs point of view. In this post, I will be taking a high-level look at what web maps are and why using them is a good idea. Over the years, they have also changed how maps could or should be defined and used in ArcGIS Runtime applications. Maps or web maps have become a central piece of the ArcGIS information model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |