You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated all the Poudre Basin Information workflows so that files only live in the primary map for a layer. Other maps that use the layer use ../ and ../../ to reference the files in the other map. This reduces the number of files in the deployment, simplifies workflows, and ensures that a change in the primary map, such as updating the Markdown for the layer, will be reflected in other maps.
Everything seems to work fine except that the info for the Rocky Mountain National Park on the floods map does not show up and complains about a bad path. I need a second set of eyes (Josh) to look at the configuration and tell me if I have a configuration property. I have verified the path and file existence (it is also used in the Wildfires map). I'm confused as to why it is not working.
If this can be resolved, then the new standard for configuration is fully implemented (other than a couple of maps that need some additional data work).
The text was updated successfully, but these errors were encountered:
I updated all the Poudre Basin Information workflows so that files only live in the primary map for a layer. Other maps that use the layer use
../
and../../
to reference the files in the other map. This reduces the number of files in the deployment, simplifies workflows, and ensures that a change in the primary map, such as updating the Markdown for the layer, will be reflected in other maps.Everything seems to work fine except that the info for the Rocky Mountain National Park on the floods map does not show up and complains about a bad path. I need a second set of eyes (Josh) to look at the configuration and tell me if I have a configuration property. I have verified the path and file existence (it is also used in the Wildfires map). I'm confused as to why it is not working.
If this can be resolved, then the new standard for configuration is fully implemented (other than a couple of maps that need some additional data work).
The text was updated successfully, but these errors were encountered: