Name: MapLoom
Owner: Boundless
Description: MapLoom is a web mapping client based on OpenLayers 3. It provides full-featured editing capabilities for data stores in GeoServer - including PostGIS and GeoGig. For GeoGig layers, it lets you view history, and sync with other GeoGig repositories
Forked from: ROGUE-JCTD/MapLoom
Created: 2016-02-12 16:03:22.0
Updated: 2018-05-21 16:03:29.0
Pushed: 2018-05-21 16:03:27.0
Size: 7645
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
MapLoom is a web client that leverages GeoGig to allow users to edit geographic information, view history, and sync layers with other GeoGig repositories. The goal is to put the power of distributed versioned editing into the hands of users. It's been developed to sit inside of GeoNode as an alternative to the default GeoNode map client but it can also be set up to stand alone. The best way to see MapLoom in action is to create a GeoSHAPE virtual machine. Please visit How To Get GeoSHAPE document for instructions.
MapLoom has been built using OpenLayers 3, Angular, and Bootstrap.
License: The MapLoom source code is licensed under the BSD 3 clause license.
We are utilizing Geoserver Web Processing Services in a couple of places. For example, the 'zoom to layer data' uses a wps that is already included in geoserver. In the layer's table view, we have added the ability to view charts and statistics on the attribute values for the whole layer or a set of filtered features of a layer. To Accomplish this, we created a custom WPS called summarize_attrib which is using the geoscript functionality in geoserver. When the summarize/statistics button is clicked in maploom, geoserver will need to have the wps available. If you are using a geoserver instance that was created and configured using the geoshape script, everything will be taken care of already and you do not need to do anything mentioned here. If you are using a different deployment of geoserver, you'll need: 1) the geoserver wps extention, 2) commons-math3-3.3.jar, 3) geoserver-2.5-SNAPSHOT-python-plugin.zip, and 4) the scripts folder
Install Node.js and then:
t clone git://github.com/ROGUE-JCTD/MapLoom
MapLoom
do npm -g install grunt-cli karma bower
m install
wer install
unt watch
Alternatively, the quick setup script will perform the installation steps.
t clone git://github.com/ROGUE-JCTD/MapLoom
MapLoom
quick-setup.sh
You can then open file:///path/to/MapLoom/build/index.html in your browser.
ecommended Development Setup
recommended way to develop maploom is to:
eate a [GeoSHAPE CentOS Virtual Machine](https://docs.google.com/document/d/1SOX8pldVskbnngXNLEfxFPlWkgC93lr8j3AE5mgmC_8) which will have maploom configured as GeoNodes viewer/editor. We recommend using the ```vagrant``` approach specified in the document.
one maploom repo on your host machine in the same folder in which you cloned the vagrant-geoshape repo
pose the MapLoom repository on the host into the VM by uncommenting this line in your Vagrant file in the `geoshape-vagrant` folder [```Vagrantfile```](https://github.com/ROGUE-JCTD/geoshape-vagrant/blob/master/Vagrantfile#L18). Note that this assumes your `MapLoom` and `geoshape-vagrant` repositories are in the same folder.
`vagrant reload(orvagrant haltfollowed byvagrant up`) to apply changes made to the vagrant file.`grunt watch` in the maploom directory on the host to buid maploomhape-config maploom_dev
grunt watch to rebuild MapLoom, and the symbolic links created by geoshape-config maploom_dev will make the newly buit maploom immediately available to Geonode in your VM.Note that linter used by grunt watch is very paticular about the js programing style and guildlines. Be sure to fix all compile issues.