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

GNIP - Abstract Map Framework UI #1331

Closed
mbertrand opened this issue Jan 15, 2014 · 14 comments
Closed

GNIP - Abstract Map Framework UI #1331

mbertrand opened this issue Jan 15, 2014 · 14 comments
Labels
gnip A GeoNodeImprovementProcess Issue
Milestone

Comments

@mbertrand
Copy link
Member

Needs for the new mapping interface:

  • Have better styling options in GeoNode (Infographics, Piecharts, automatic choropleth maps…)
    • SldService geoserver community module for choropleth maps?
    • standard or pluggable charts API?
  • More interactive popups
  • Maps and layers fully accessible from mobile devices

Available implementations

  • GEM’s Leaflet + D3 experiments
  • Mapstory’s design mockups
  • ROGUE’s Angular + OL3
  • Worldmap’s customized GeoExt

What is needed to allow abstraction from the mapping interface

  • Stable Map API
  • Abstractions for GeoServer, SLD, Tiles/WMS/TMS.
  • Tiles, Raw data, Companion services (GetInfo, UTF8-Grid) do we need to abstract this too?
  • Be Agnostic
@ingenieroariel ingenieroariel modified the milestone: 2.1 Apr 16, 2014
@capooti
Copy link
Member

capooti commented Apr 16, 2014

+1 for me.

@jj0hns0n
Copy link
Contributor

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

@jj0hns0n
Copy link
Contributor

Also, I'd like to turn this into a more formal GNIP see #1915

@jj0hns0n jj0hns0n added this to the 2.5.x milestone Jan 13, 2015
@jj0hns0n jj0hns0n added feature A new feature to be added to the codebase and removed needs-triage labels Jan 13, 2015
@simod
Copy link
Member

simod commented Feb 5, 2015

Overview

We discussed this during the code sprint in Venice firstly by taking a look at the available solutions out there:

GeoExplorer

Based on Ext and OL2 is the current mapping client which is GeoNode is using since the beginning.

MapStore

Created by GeoSolutions is based on a maintained and updated version of geoexplorer with many plugins

Maploom

Based on Angularjs and OL2 is Geogig enabled, is missing the styling tool

Geoadmin.ch

Based on Angularjs and OL3, is missing the styling tool and the editing tool

Cartodb client

Is based on Backbone and Leaflet

MapBox client

Based on Leaflet.

Proposal:

The mapping client should be independent from geonode and easily swappable.
One option could be to present a more gis featured mapping interface for users that need to work on the map and another lighter and simpler for users that just want to view the data.

@rajanski
Copy link

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.
Also see http://lib.heron-mc.org/heron/latest/examples/querybuilder/

@vlasvlasvlas
Copy link

this is so true:
"The mapping client should be independent from geonode and easily swappable."

@rajanski
Copy link

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...

@rajanski
Copy link

rajanski commented Oct 15, 2015

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

@vlasvlasvlas
Copy link

Would LOVE to see the geoadmin.ch GUI as a geonode's mapping client

@JJediny
Copy link
Member

JJediny commented Oct 19, 2015

Two more Map Clients that would be "pluggable" to geonode with a mappable api:

http://terria.io/
https://github.com/JJediny/nationalmap
&
https://github.com/JJediny/Leaflet.Storage
https://github.com/JJediny/django-leaflet-storage
https://nepanode.hackpad.com/NEPAnodes-GeoJSON-Editor-1R1PRnbCvnB

The first one has some ongoing work that could be leveraged for an api...

http://terria.io/DataSourceEditor/
https://github.com/TerriaJS/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 data json currently sent from GeoExplorer:
https://gist.github.com/JJediny/6ae4973dc5334340788b

Here is how the Leaflet-Storage manages map config:
http://nepanode.anl.gov/geojson/api/geojson/

But far less complicated focusing on the description and state of the map (name/abstract/zoom/extent/etc) with nested layers as a URL and Datatype/format... but making sure we arent limiting the practical use - thats why it'd be good to document all the approaches taken thus far by other projects and frameworks...

@jj0hns0n jj0hns0n modified the milestones: 2.7, 2.5 Aug 21, 2016
@jj0hns0n
Copy link
Contributor

@bartvde @ahocevar lets talk about this during FOSS4G in the context of the new websdk

@jj0hns0n
Copy link
Contributor

@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.

@capooti
Copy link
Member

capooti commented Dec 14, 2016

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.

@jj0hns0n
Copy link
Contributor

@capooti I think that we can now move on from the old gxp format as long as the new viewers still support it.

@afabiani afabiani closed this as completed Sep 4, 2018
@afabiani afabiani removed the feature A new feature to be added to the codebase label Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gnip A GeoNodeImprovementProcess Issue
Projects
None yet
Development

No branches or pull requests

9 participants