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

Ideas for Admin 4 #650

Open
jacobwod opened this issue Feb 2, 2021 · 3 comments
Open

Ideas for Admin 4 #650

jacobwod opened this issue Feb 2, 2021 · 3 comments

Comments

@jacobwod
Copy link
Member

jacobwod commented Feb 2, 2021

Ideas

Below are some ideas, in no special order:

  • layer.internalName for use in admin listings is not the same as layer.title, which is used in client (and can be overridden on a per-map-basis)
  • Most attributes follow this override pattern: [definition in layer] -> [can be overridden by definition in map config] -> [can be overridden by user preference]. Among those are layer title, draw order, style, info click definition, etc.
  • The tree in admin layer has a 1:1 relationship with what user will see in LayerSwitcher
  • Ability to duplicate map (new backend has this endpoint ready, so it's basically the UI that's left. (
  • Ability to duplicate map and layers within map. This requires more work in backend, but could be really useful when admins need to "freeze" a state of a map and all of it's layers.
  • Read-only flag on maps and layers. When on, no further edits are possible through Admin 4.
  • Sort out the confusion of layers, group layers, Hajk groups, GeoServer layer groups. Decide on best practice, and stick to it.
  • Background layers can be grouped together with other layers and those other layers will always become active together with a certain background (user will not be able to turn them off). Useful when we want to add a territorial border to existing, tiled, layers. Creating a layer group in GeoServer would require re-caching all tiles. This solution would load the layers separately, making use of the tiled cached layers and at the same time applying the borderline.

Wishlist

  • No need of code knowledge to administer or setup anything.

Code

You'll find this ongoing effort in the /admin directory in this feature branch.

This was referenced Feb 9, 2021
@persoderstrom
Copy link
Contributor

  • A filter function for the list of layers from Geoserver or other map services.
  • Collaps/expand layer groups when working in the ”Kartor” tab.

@maan002
Copy link
Contributor

maan002 commented Mar 3, 2021

  • Support CORS, i.e. add withCredentials or credentials: include when resources are fetched.
  • Option to save and fetch configuration in a database.

@jesade-vbg
Copy link
Contributor

Include a MarkDown editor (WYSIWYG) for InfoClick, with both preview mode and "raw"-edit mode.

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

5 participants