In progress
eGIS users should be familiar with and follow these best practices when publishing data to the eGIS platform.
These items reference ArcGIS Pro
...
Ideally, if a user has a publisher account to eGIS then that user also has access to ArcGIS Pro. They should be familiar with ESRI’s map authoring considerations, but are still valid when publishing to ArcGIS Enterprise / eGIS:
The role of the eGIS team
Collaboration
The eGIS Team is available to assist on data publishing projects, both large and small.
Automation
for frequently updated data sets, consider letting the eGIS automate the maintenance requires. Our team will collaborate on setting up the initial service, then configure scripts to ensure your data is always current.
Troubleshooting
If performance is a problem, the eGIS team is available to evaluate your services and ensure that its as fast as possible.
Questions
- Do all publishers need ArcGIS Pro? or does eGIS fill the gap between power users and casual publishers?
Notes
Best practices for publishing and symbolizing data must be followed regardless of our hardware.
Create map caches where possible
Data that can’t be cached should be stored and displayed in the fewest and simplest features possible
Follow ESRI’s Performance tips for uncached maps
Re-project all data to WGS84 Web Mercator
Avoid all re-projection on the fly
Debate?
Test performance on all layers?
Web hooks, test new layers?
...