Template:TUFLOW FV Define Model Limits Workflow: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
m (Protected "Template:TUFLOW FV Define Model Limits Workflow" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
No edit summary |
||
Line 23: | Line 23: | ||
|- | |- | ||
| | | | ||
:Domain extents can be created from data outside of the [[SMS:Map Module|Map module]] by converting the data to a | :Domain extents can be created from data outside of the [[SMS:Map Module|Map module]] by converting the data to a generic model coverage. | ||
<blockquote> | <blockquote> | ||
{{SMS Convert to Map Workflow}} | {{SMS Convert to Map Workflow}} | ||
Line 33: | Line 33: | ||
|- | |- | ||
| | | | ||
:If domain extents have been created on multiple map coverages, these coverages need to be merged into a | :If domain extents have been created on multiple map coverages, these coverages need to be merged into a generic model coverage. | ||
{{SMS Merge Coverages Workflow}} | {{SMS Merge Coverages Workflow}} | ||
|}<noinclude>[[Category:SMS Workflow Templates]]</noinclude> | |}<noinclude>[[Category:SMS Workflow Templates]]</noinclude> |
Revision as of 21:54, 7 March 2016
1. Create a Generic Model map coverage. | ||||
---|---|---|---|---|
|
2. Digitize arcs to define domain edges. | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
3. Generate domain extent arcs from other data sources. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
4. Merge domain coverages. |
---|
|