Publishing data in ArcGIS Enterprise: Difference between revisions
From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs) mNo edit summary |
Brian Wilson (talk | contribs) mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== I have a copy of this at CC == | |||
A checklist | A checklist | ||
| Line 5: | Line 7: | ||
** Set the data frame projection to Web Mercator. | ** Set the data frame projection to Web Mercator. | ||
** For Feature Services, create a label layer and a shape layer. | ** For Feature Services, create a label layer and a shape layer. | ||
** Symbolize your feature layers. | |||
** Label, but NOT WITH MAPLEX. MAPLEX will sort of work and then fail you when you least expect it, and then you'll have to start with a clean MXD. You can't switch. | |||
*** Turn off fields that should not be exposed. | *** Turn off fields that should not be exposed. | ||
** For Map Services, create a group for each zoom level supported, normally 10-19. (Use an existing map as a template.) | ** For Map Services, create a group for each zoom level supported, normally 10-19. (Use an existing map as a template.) | ||
Latest revision as of 22:33, 29 August 2019
I have a copy of this at CC
A checklist
- Make an MXD.
- Put the description and the disclaimer in Map Properties
- Set the data frame projection to Web Mercator.
- For Feature Services, create a label layer and a shape layer.
- Symbolize your feature layers.
- Label, but NOT WITH MAPLEX. MAPLEX will sort of work and then fail you when you least expect it, and then you'll have to start with a clean MXD. You can't switch.
- Turn off fields that should not be exposed.
- For Map Services, create a group for each zoom level supported, normally 10-19. (Use an existing map as a template.)
- Don't put anything else in the MXD.
- Publish to ArcGIS Server, using the service running on port 6443, for me that's https://ccgis.co.clatsop.or.us:6443/arcgis/ do I need admin/ at the end??
- If you have already published this service, select the "overwrite" option. Then pick the name from the ensuing list.
- Unless it fails in which case go into Portal and delete the services
- and go into ArcGIS Service Manager and delete it there
- and restart ArcMap and start over.
- About this time I need to decide what services I am publishing. Jury still out. "Mapping" is not optional. "WFS" and "WMS" are. I never need "KML" so far. Turn it off.
- For "Feature Access" normally I turn off all operations except Extract and Query.
- For Map Services I normally build a cache and set the range to match the published service.
- When you do the "Analyze" step you should ignore the warning about projection being different.
- For Feature Service, ignore the warning about data drawing at all scales.
- Otherwise, FIX YOUR ERRORS NOW. :-)
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 set the Data Frame to Web Mercator. I use the "WGS_1984_(ITRF00)_To_NAD_1983_HARN" transformation; this shows as the 3rd or 4th choice but the one I want (WGS #5) is not in the list. Instead it offers transformations for the Aleutian Islands etc. This one seems to be the best.
