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 think we should create a connection from the map template to the Warper re: types. There is a property in the Map template "Map type". It has not been utilized. The purpose has been to be able to express the types, such as "street map", "topographic map", "sea chart". We could use that or we could create a new property (I prefer a new property). The values could be read from Commons in the import, updated in the Warper, and updated to Commons when there is an update event, such as warping.
So, basic mapping template to warper -> map_type (map, not map, index/overview)
Also, potentially skip import if the type is set to something.
May depend on new Map Template proposals.
The text was updated successfully, but these errors were encountered:
I think we should create a connection from the map template to the Warper re: types. There is a property in the Map template "Map type". It has not been utilized. The purpose has been to be able to express the types, such as "street map", "topographic map", "sea chart". We could use that or we could create a new property (I prefer a new property). The values could be read from Commons in the import, updated in the Warper, and updated to Commons when there is an update event, such as warping.
So, basic mapping template to warper -> map_type (map, not map, index/overview)
Also, potentially skip import if the type is set to something.
May depend on new Map Template proposals.
The text was updated successfully, but these errors were encountered: