Succès et échecs

Question

<\/HEAD>Hé, cette conférence continue d'être excellente (à mon avis la seule vraiment digne d'être suivie depuis la première année). Mes félicitations cette année vont au Palm Springs Convention Center pour leurs tasses à café redesignées ! Quelqu'un devait dire "non" aux manchons amovibles. Le prix de la meilleure initiative de l'année revient à la mise en place du bracelet : vous n'avez pas réussi à le configurer à temps.<\/P> <\/P> Mis à part cela, le seul conflit que j'essaie vraiment de digérer est celui entre le Cartographic Information Model et la Web Map Specification. Officiellement, l'équipe Runtime soutient ce dernier, mais ensuite ils vantent une plus grande parité avec Pro, mais vous ne pouvez pas faire cela sans adopter CIM. À mon avis, le développement natif ne devrait pas être freiné par les lacunes de JS.<\/P><\/BODY><\/HTML>

MarkCederholm · Answer

I meant that the wristband stations were not set up by 10 AM, and after waiting most of the break, I finally gave up and went to the next session before time ran out.

AmyNiessen · Answer

Hi Mark! Great to see you at DevSummit again this year. Thanks for the feedback about the coffee cups. As for the wristbands, it seemed to us that people who got them during the day on Thursday had a quick and easy time of it for the most part, but that those who had to wait until the party started Thursday evening spent a lot of time on line. We can look into more check-in stations at the party, but the way to get your wristband more quickly would be to pick it up during the day on Thursday at the registration desks in the main lobby. Am I understanding correctly what you meant by us not getting it set up in time? For at least the foreseeable future, the cartographic capabilities of web maps are going to be much simpler when compared to the much more comprehensive tools available in ArcGIS Desktop (Pro and ArcMap), described by the CIM. The web map specification is designed to transport maps efficiently in the Web GIS implementation model, and needs to look and work the same in a client-agnostic way, across all browsers, as well as native apps created for a wide variety of sizes and resolutions: smartphones, tablets, desktops. When the cartographic capabilities you need for your app-deployed maps exceed what the web map specification provides, in a way that is still optimized for Web GIS, there is the Map Image Layer built from a map service you create in Desktop and serve up through Enterprise/Portal. _>>Officially, the Runtime team support [web maps], but then they trumpet greater parity with Pro, but you can't do that without adopting CIM.<<_ True, but Runtime also supports map image layers. Using this service type is the way to fully support your advanced cartographic needs today. As for "parity", ArcGIS Runtime does support a subset of the CIM today, and progress will continue. Feature service expose CIM via their advanced symbology options; that's how the Runtime SDK can see and use this information. The JavaScript API will also have support for the CIM in a future release. In both cases, CIM is exposed through the feature layers individually. In addition, to some degree Pro does use some Runtime code, and this also helps ensure greater parity in how symbols are rendered.