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

Reflect layer updates on the hierarchy map #9

Open
anayaml opened this issue Jun 6, 2019 · 0 comments
Open

Reflect layer updates on the hierarchy map #9

anayaml opened this issue Jun 6, 2019 · 0 comments
Labels
enhancement New feature or request Refatoring

Comments

@anayaml
Copy link
Member

anayaml commented Jun 6, 2019

One of the limitations of Geonode's default implementation is that updates made to a layer after the layer in question are added to a map does not reflect on the map.

For example, the user creates a map called 01Map, and adds a layer named layer_01, and saves the map. However, it then updates the name of layer_01 for Layer 01.

The layer name is updated in the layer table, however, if the user will access the 01Map that he created before, the now named Layer 01 will still be named layer_01 in the map layer list.

It seems that the map stores other data in addition to the layer ID in the database, causing the non-replication of the update made by the user.

A possible solution would be to update the migration that generates the map table in geonode, and make it save only the ID. And when loading the map, search for the IDs in the layer table and return the most recent data.

@anayaml anayaml added enhancement New feature or request Refatoring labels Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Refatoring
Projects
None yet
Development

No branches or pull requests

1 participant