created cluster map example with leaflet

content/reference/Leaflet.markercluster-1.4.1/.gitignore

@@ -0,0 +1,7 @@
+# Build Folders (you can keep bin if you'd like, to store dlls and pdbs)
+bin
+obj
+
+# mstest test results
+TestResults
+node_modules

content/reference/Leaflet.markercluster-1.4.1/.travis.yml

@@ -0,0 +1,20 @@
+sudo: false
+language: node_js
+node_js:
+  - 6
+cache:
+  directories:
+    - "travis_phantomjs"
+before_install:
+  - "export PHANTOMJS_VERSION=2.1.1"
+  - "hash -r"
+  - "phantomjs --version"
+  - "export PATH=$PWD/travis_phantomjs/phantomjs-$PHANTOMJS_VERSION-linux-x86_64/bin:$PATH"
+  - "hash -r"
+  - "phantomjs --version"
+  - "if [ $(phantomjs --version) != \"$PHANTOMJS_VERSION\" ]; then rm -rf $PWD/travis_phantomjs; mkdir -p $PWD/travis_phantomjs; fi"
+  - "hash -r"
+  - "if [ $(phantomjs --version) != \"$PHANTOMJS_VERSION\" ]; then wget https://github.com/Medium/phantomjs/releases/download/v$PHANTOMJS_VERSION/phantomjs-$PHANTOMJS_VERSION-linux-x86_64.tar.bz2 -O $PWD/travis_phantomjs/phantomjs-$PHANTOMJS_VERSION-linux-x86_64.tar.bz2; fi"
+  - "if [ $(phantomjs --version) != \"$PHANTOMJS_VERSION\" ]; then tar -xvf $PWD/travis_phantomjs/phantomjs-$PHANTOMJS_VERSION-linux-x86_64.tar.bz2 -C $PWD/travis_phantomjs; fi"
+  - "hash -r"
+  - "phantomjs --version"

content/reference/Leaflet.markercluster-1.4.1/CONTRIBUTING.md

@@ -0,0 +1,70 @@
+Contributing to Leaflet.MarkerCluster
+=====================================
+
+ 1. [Reporting Bugs](#reporting-bugs)
+ 2. [Contributing Code](#contributing-code)
+ 3. [Building](#building)
+ 4. [Testing](#testing)
+
+## Reporting Bugs
+
+Before reporting a bug on the project's [issues page](https://github.com/Leaflet/Leaflet.markercluster/issues),
+first make sure that your issue is caused by Leaflet.MarkerCluster, not your application code
+(e.g. passing incorrect arguments to methods, etc.).
+Second, search the already reported issues for similar cases,
+and if it's already reported, just add any additional details in the comments.
+
+After you've made sure that you've found a new Leaflet.markercluster bug,
+here are some tips for creating a helpful report that will make fixing it much easier and quicker:
+
+ * Write a **descriptive, specific title**. Bad: *Problem with polylines*. Good: *Doing X in IE9 causes Z*.
+ * Include **browser, OS and Leaflet version** info in the description.
+ * Create a **simple test case** that demonstrates the bug (e.g. using [JSFiddle](http://jsfiddle.net/) or [JS Bin](http://jsbin.com/)).
+ * Check whether the bug can be reproduced in **other browsers**.
+ * Check if the bug occurs in the stable version, master, or both.
+ * *Bonus tip:* if the bug only appears in the master version but the stable version is fine,
+   use `git bisect` to find the exact commit that introduced the bug.
+
+If you just want some help with your project,
+try asking [on the Leaflet forum](https://groups.google.com/forum/#!forum/leaflet-js) instead.
+
+## Contributing Code
+
+### Considerations for Accepting Patches
+
+While we happily accept patches, we're also committed to keeping Leaflet simple, lightweight and blazingly fast.
+So bugfixes, performance optimizations and small improvements that don't add a lot of code
+are much more likely to get accepted quickly.
+
+Before sending a pull request with a new feature, check if it's been discussed before already
+(either on [GitHub issues](https://github.com/Leaflet/Leaflet/issues)
+or [Leaflet UserVoice](http://leaflet.uservoice.com/)),
+and ask yourself two questions:
+
+ 1. Are you sure that this new feature is important enough to justify its presence in the Leaflet core?
+    Or will it look better as a plugin in a separate repository?
+ 2. Is it written in a simple, concise way that doesn't add bulk to the codebase?
+
+If your feature or API improvement did get merged into master,
+please consider submitting another pull request with the corresponding [documentation update](#improving-documentation).
+
+## Building
+
+Install the dependencies:
+```
+npm install -g jake
+npm install
+```
+
+Then to build:
+```
+jake
+```
+Output will be in the ```dist/``` directory
+
+## Testing
+
+To run unit tests:
+```
+jake test
+```

content/reference/Leaflet.markercluster-1.4.1/ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+- [ ] I'm reporting a bug, not asking for help
+- [ ] I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
+- [ ] I've searched through the issues to make sure it's not yet reported
+
+----
+
+## How to reproduce
+
+- Leaflet version I'm using:
+- Leaflet.MarkerCluster version I'm using:
+- Browser (with version) I'm using:
+- OS/Platform (with version) I'm using:
+- step 1
+- step 2
+
+## What behaviour I'm expecting and which behaviour I'm seeing
+
+## Minimal example reproducing the issue
+
+- [ ] this example is as simple as possible
+- [ ] this example does not rely on any third party code
+
+Using http://leafletjs.com/edit.html or any other jsfiddle-like site.

content/reference/Leaflet.markercluster-1.4.1/Jakefile.js

@@ -0,0 +1,86 @@
+/*
+Leaflet.markercluster building, testing and linting scripts.
+
+To use, install Node, then run the following commands in the project root:
+
+    npm install -g jake
+    npm install
+
+To check the code for errors and build Leaflet from source, run "jake".
+To run the tests, run "jake test".
+
+For a custom build, open build/build.html in the browser and follow the instructions.
+*/
+
+var path = require('path');
+
+desc('Check Leaflet.markercluster source for errors with JSHint');
+task('lint', function(){
+		jake.exec('jshint', {
+			printStdout: true
+		}, function () {
+			console.log('\tCheck passed.\n');
+			complete();
+		});
+});
+
+desc('Combine Leaflet.markercluster source files');
+task('build', ['lint'], function(){
+	jake.exec('npm run-script rollup', function() { console.log('Rolled up.'); });
+});
+
+desc('Compress bundled files');
+task('uglify', ['build'], function(){
+	jake.exec('npm run-script uglify', function() { console.log('Uglyfied.'); });
+});
+
+desc('Run PhantomJS tests');
+task('test', ['lint'], function() {
+
+	var karma = require('karma'),
+	testConfig = {configFile : path.join(__dirname, './spec/karma.conf.js')};
+
+	testConfig.browsers = ['PhantomJS'];
+
+	function isArgv(optName) {
+		 return process.argv.indexOf(optName) !== -1;
+	}
+
+	if (isArgv('--chrome')) {
+		testConfig.browsers.push('Chrome');
+	}
+	if (isArgv('--safari')) {
+		testConfig.browsers.push('Safari');
+	}
+	if (isArgv('--ff')) {
+		testConfig.browsers.push('Firefox');
+	}
+	if (isArgv('--ie')) {
+		testConfig.browsers.push('IE');
+	}
+
+	if (isArgv('--cov')) {
+		testConfig.preprocessors = {
+			'src/**/*.js': 'coverage'
+		};
+		testConfig.coverageReporter = {
+			type : 'html',
+			dir : 'coverage/'
+		};
+		testConfig.reporters = ['coverage'];
+	}
+
+	console.log('Running tests...');
+
+	var server = new karma.Server(testConfig, function(exitCode) {
+		if (!exitCode) {
+			console.log('\tTests ran successfully.\n');
+			complete();
+		} else {
+			process.exit(exitCode);
+		}
+	});
+	server.start();
+});
+
+task('default', ['build', 'uglify']);

content/reference/Leaflet.markercluster-1.4.1/MIT-LICENCE.txt

@@ -0,0 +1,20 @@
+Copyright 2012 David Leaver
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.