Publishing data in ArcGIS Enterprise: Difference between revisions
From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs) Created page with "A checklist == Feature Service == == Map Image Service (cached tiles) == Pro's * Symbolization designed in ArcMap is preserved so not much to do in the client. * You will n..." |
Brian Wilson (talk | contribs) m Brian Wilson moved page Publishing in data in ArcGIS Enterprise to Publishing data in ArcGIS Enterprise without leaving a redirect: Wordo |
(No difference)
| |
Revision as of 21:29, 28 August 2019
A checklist
Feature Service
Map Image Service (cached tiles)
Pro's
- Symbolization designed in ArcMap is preserved so not much to do in the client.
- You will need to set up a separate group for each zoom level. This is incompatible with Feature Services so you need two MXD's to publish both Map and Feature Services.
Con's
- Don't use Maplex. Since the tiles are built on the server it will do a terrible job at labels. You might want to use annotation instead of labels. (ick)
- If you get the projection wrong, tiles will be unusable in a web map.
- Bulky, lots of raster data.
- When you zoom in you'll see the rasterization.
The service should be in Web Mercator (EPSG:3857) so that it's most compatible with other public map services (OSM, ESRI, Google, ...).
Sometimes this just happened but I don't know why. These days I put the source data into the ArcMap document, and then
