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
The current import process, as I understand it, obtains assets from digital collection but does not pull rectification data itself since it expects to be run on the production env of the mapwarper for a onetime load of maps/layers from digital collections to the mapwarper.
Since the import process is key to component to load data for development purposes it would be helpful if an optional "import rectification data" option could be added to the import process which when checked obtained rectification metadata from the mapwarper at the end of the standard import process. This would enable maps/layers with existing rectifications to be loaded into dev versions of the mapwarper.
The text was updated successfully, but these errors were encountered:
The current import process, as I understand it, obtains assets from digital collection but does not pull rectification data itself since it expects to be run on the production env of the mapwarper for a onetime load of maps/layers from digital collections to the mapwarper.
Since the import process is key to component to load data for development purposes it would be helpful if an optional "import rectification data" option could be added to the import process which when checked obtained rectification metadata from the mapwarper at the end of the standard import process. This would enable maps/layers with existing rectifications to be loaded into dev versions of the mapwarper.
The text was updated successfully, but these errors were encountered: