-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
GNIP - Abstract Map Framework UI #1331
Comments
+1 for me. |
Its now possible to use maploom in geonode. Its partially an iframe 'hack' but it is very possible to use it by adding the django app and overriding a few templates. We should document this in the mainline docs and have a broader discussion about map clients going forward cc @garnertb |
Also, I'd like to turn this into a more formal GNIP see #1915 |
OverviewWe discussed this during the code sprint in Venice firstly by taking a look at the available solutions out there: GeoExplorerBased on Ext and OL2 is the current mapping client which is GeoNode is using since the beginning. MapStoreCreated by GeoSolutions is based on a maintained and updated version of geoexplorer with many plugins MaploomBased on Angularjs and OL2 is Geogig enabled, is missing the styling tool Geoadmin.chBased on Angularjs and OL3, is missing the styling tool and the editing tool Cartodb clientIs based on Backbone and Leaflet MapBox clientBased on Leaflet. Proposal:The mapping client should be independent from geonode and easily swappable. |
I would propose to add HeronMC to the list of possible Mapclients. It is based on Openlayers and GeoExt. It has a styling tool, a query tool , an editing tool, and a query results to various formats export tool. |
this is so true: |
One more argument to think about an alternative default mapping client: GeoExplorer doesnt work very well with mobile devices. Just tested on a tablet. No zooming etc... |
I have been looking through the alternative mapping clients again. To me, it seems that geoadmin.ch is among the most actively maintained and most long-term sustainable, as they use OL3 and angular.. It misses the styling tool, yes. But I think the styling should be done via SLD, directly in geoserver anyway. IMHO, a styling GUI can hardly ever cover all the possibilities that exist in SLD |
Would LOVE to see the geoadmin.ch GUI as a geonode's mapping client |
Two more Map Clients that would be "pluggable" to geonode with a mappable api: http://terria.io/ The first one has some ongoing work that could be leveraged for an api... http://terria.io/DataSourceEditor/ Think there just needs to be an assignment of where we draw the line at "saving" the map... think the OGC Web Map Context is too much and that styling per layer or more granular attributes/configurations should be limited to: A JSON Snapshot similar to the Here is how the Leaflet-Storage manages map config: But far less complicated focusing on the description and state of the |
@bartvde @milafrerichs we now have 3 implementations that use the gxp based map format. Think it could be time to better document this and work toward a next map format now that we support the old format even in the newest client. @timlinux would like your input here to wrt to qgis project files as a similar construct. |
I agree with @jj0hns0n that the next map format should support the old format. It would be nice if users could decide which client to use for a specific map. And definitely this would help migrations of existing instances. |
@capooti I think that we can now move on from the old gxp format as long as the new viewers still support it. |
Needs for the new mapping interface:
Available implementations
What is needed to allow abstraction from the mapping interface
The text was updated successfully, but these errors were encountered: