Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import from commons should read map type from template & handle accordingly. #83

Open
timwaters opened this issue Feb 11, 2016 · 1 comment

Comments

@timwaters
Copy link

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.

@timwaters
Copy link
Author

related to #82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant