itowns 2.44.3-next.40 → 2.44.3-next.42

package/README.md

@@ -1,131 +1,5 @@
-![iTowns](https://raw.githubusercontent.com/iTowns/itowns.github.io/master/images/itowns_logo_300x134.png)
-# iTowns
-
-[![Coverage Status](https://coveralls.io/repos/github/iTowns/itowns/badge.svg?branch=master)](https://coveralls.io/github/iTowns/itowns?branch=master)
-[![example branch parameter](https://github.com/iTowns/itowns/actions/workflows/integration.yml/badge.svg?query=branch%3Amaster)](https://github.com/iTowns/itowns/actions/workflows/integration.yml?query=branch%3Amaster)
-[![DeepScan grade](https://deepscan.io/api/teams/2856/projects/10991/branches/159107/badge/grade.svg)](https://deepscan.io/dashboard#view=project&tid=2856&pid=10991&bid=159107)
-
 ## What is it?
 
-iTowns is a [Three.js](https://threejs.org/)-based framework written in
-Javascript/WebGL for visualizing 3D geospatial data.
-
-It can connect to WMS/WMTS/TMS servers including elevation data and load many
-different data formats (3dTiles, GeoJSON, Vector Tiles, GPX and much more). A
-complete list of features and supported data formats is [available on the
-wiki](https://github.com/iTowns/itowns/wiki/Supported-Features).
-
-It officially targets the last two major versions of both Firefox, Safari and
-Chromium-based browsers (Chrome, Edge, ...) at the date of each release. Older
-browsers supporting WebGL 2.0 may work but we do not offer support.
-
-![iTowns screenshot](https://raw.githubusercontent.com/iTowns/itowns.github.io/master/images/itownsReleaseXS.jpg)
-
-## Documentation and examples
-
-The official documentation is [available
-here](http://www.itowns-project.org/itowns/docs/). It contains tutorials to help
-you start using iTowns, and an API reference. You can find more informations on
-its contribution [here](docs/README.md).
-
-Official examples can be [viewed
-here](http://www.itowns-project.org/itowns/examples/). Some examples available:
-
-* [Globe with WFS data](http://www.itowns-project.org/itowns/examples/#source_stream_wfs_3d)
-* [Plane mode with Vector Tiles](http://www.itowns-project.org/itowns/examples/#vector_tile_raster_2d)
-* [3D effect using scene postprocessing](http://www.itowns-project.org/itowns/examples/#effects_stereo)
-* [Globe with split rendering](http://www.itowns-project.org/itowns/examples/#effects_split)
-
-[![iTowns examples](http://www.itowns-project.org/images/montage.jpg)](http://www.itowns-project.org/itowns/examples/)
-
-## How to run it locally?
-
-Clone the repo and then run:
-
-```
-npm install
-npm start
-```
-
-Try out the examples at http://localhost:8080/examples
-
-## How to use it in your project?
-
-You can use it through npm (the preferred way) or download a bundle from our
-github release page.
-
-### With npm
-
-In your project:
-
-```bash
-npm install --save itowns
-```
-
-This package contains the ES5-compatible sources of iTowns, up to date with the latest release.
-
-If you're using a module bundler (like wepback), you can directly write
-`require('itowns')` in your code.
-
-Alternatively, we provide a bundle you can directly include in your html files
-that exposes `itowns` in `window`:
-
-```html
-<script src="node_modules/itowns/dist/itowns.js"></script>
-```
-
-**/!\ Please note that this bundle also contains the dependencies**.
-
-### From a release bundle
-
-See our [release page](https://github.com/iTowns/itowns/releases). Note that
-there isn't a lot of support for older version of iTowns, we highly recommend to
-use the last release everytime.
-
-### Try modifications before they are released
-
-If you want to try some features or bug fixes that are planned for the next release, we provide
-a @next version of itowns. You can install it as such :
-
-```bash
-npm install --save itowns@next
-```
-
-To switch back to the version to date with the latest release, you need to run :
-
-```bash
-npm install --save itowns@latest
-```
-
-## Contributing
-
-If you are interested in contributing to iTowns, please read the [CONTRIBUTING
-guide](CONTRIBUTING.md) and the [CODING guide](CODING.md).
-
-iTowns has been redesigned from this [early version](https://github.com/iTowns/itowns-legacy).
-
-## Licence
-
-iTowns is dual-licenced under Cecill-B V1.0 and MIT.
-Incorporated libraries are published under their original licences.
-
-See [LICENSE.md](LICENSE.md) for more information.
-
-## Maintainers
-
-iTowns is an original work from French IGN, [MATIS research
-laboratory](http://recherche.ign.fr/labos/matis/). It has been funded through
-various research programs involving the French National Research Agency, Cap
-Digital, UPMC, Mines ParisTec, CNRS, LCPC and maintained by several organizations
-along the years (IGN, Oslandia, AtolCD, CIRIL Group). It has also received contributions from people [listed
-here](CONTRIBUTORS.md).
-
-iTowns is currently maintained by [IGN](http://www.ign.fr) and
-[CIRIL Group](https://www.cirilgroup.com/en/). 
-
-Contributions in any forms and new contributors and maintainers are welcome. Get in touch with us if you are interested :)
-
-The governance of the project is open and explicited [here](https://github.com/iTowns/itowns-governance).
-
-[![IGN](./img/logo_ign.png)](https://www.ign.fr)
-[![CIRIL Group](./img/CIRIL_Group_logo.png)](https://www.cirilgroup.com/en/)
+This itowns module acts as a central point of access, allowing users to leverage the complete range of features offered by the @itowns submodules without needing to import or manage them individually.
+Refer to [README main](https://raw.githubusercontent.com/iTowns/itowns.github.io/master/README.md) for more information.
+The official documentation is [available here](http://www.itowns-project.org/itowns/docs/)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "itowns",
-  "version": "2.44.3-next.40",
+  "version": "2.44.3-next.42",
   "description": "A JS/WebGL framework for 3D geospatial data visualization",
   "type": "module",
   "main": "lib/Main.js",
@@ -9,32 +9,24 @@
     "./widgets": "./lib/Utils/gui/Main.js"
   },
   "scripts": {
-    "lint": "eslint \"src/**/*.{js,ts,tsx}\" \"test/**/*.js\" \"examples/**/*.js\" \"docs/*.js\"",
-    "doc": "jsdoc --readme docs/HOMEPAGE.md -c docs/config.json",
-    "doclint": "npm run doc -- -t templates/silent",
-    "test": "npm run lint -- --max-warnings=0 && npm run build && npm run test-with-coverage && npm run test-functional",
-    "test-dev": "npm run lint -- --max-warnings=0 && npm run build-dev && npm run test-with-coverage && npm run test-functional",
+    "lint": "eslint \"src/**/*.{js,ts,tsx}\" \"test/**/*.js\"",
+    "transpile": "cross-env BABEL_DISABLE_CACHE=1 babel src --out-dir lib --extensions .js,.ts",
     "test-unit": "npm run base-test-unit test/unit",
-    "test-functional": "mocha -t 100000 --require test/hooks_functional.js --recursive test/functional",
+    "base-test-unit": "cross-env BABEL_DISABLE_CACHE=1 mocha --timeout 5000 --file test/unit/bootstrap.js --import=../../config/babel-register/register.mjs",
     "test-with-coverage": "c8 -n src -r html cross-env npm run test-unit",
     "test-with-coverage_lcov": "c8 -n src --reporter=lcov cross-env npm run test-unit",
-    "base-test-unit": "cross-env BABEL_DISABLE_CACHE=1 mocha --file test/unit/bootstrap.js --import=./config/babel-register/register.mjs",
-    "build": "cross-env NODE_ENV=production webpack",
-    "build-dev": "cross-env NODE_ENV=development webpack",
-    "transpile": "cross-env BABEL_DISABLE_CACHE=1 babel src --out-dir lib --extensions .js,.ts",
-    "start": "cross-env NODE_ENV=development webpack serve",
-    "start-https": "cross-env NODE_ENV=development webpack serve --https",
-    "debug": "cross-env noInline=true npm start",
-    "prepublishOnly": "npm run build && npm run transpile",
-    "prepare": "cross-env NO_UPDATE_NOTIFIER=true node ./config/prepare.mjs && node ./config/replace.config.mjs",
     "watch": "npm run transpile -- --watch",
-    "changelog": "conventional-changelog -n ./config/conventionalChangelog/config.cjs -i changelog.md -s",
-    "bump": "if [ -z $npm_config_level ]; then grunt bump:minor;  else grunt bump:$npm_config_level; fi && npm run changelog && npm install && git add -A && git commit --amend --no-edit",
-    "publish-next": "npm version prerelease --preid next && npm publish --access public --tag=next --provenance",
-    "publish-latest": "npm publish --access public --tag=latest --provenance"
+    "prepublishOnly": "npx copyfiles -u 1 \"../../examples/**/*\" ./examples/ && npx copyfiles -u 1 \"../../docs/**/*\" ./docs/ && npx copyfiles -u 1 \"../../dist/**/*\" ./dist/ ",
+    "postpublish": "node clean.cjs",
+    "publish-latest": "npm publish --access public --tag=latest --provenance",
+    "prerelease-next": "npm version prerelease --preid next",
+    "publish-next": "npm publish --access public --tag=next --provenance",
+    "update-package": "npm remove @itowns/geographic && npm install @itowns/geographic@$npm_package_version --save"
   },
   "c8": {
     "exclude": [
+      "**/test/**",
+      "**/lib/**",
       "**/*ThreeExtended",
       "**/*src/Utils/placeObjectOnGround.js",
       "**/*src/Parser/deprecated/LegacyGLTFLoader.js"
@@ -55,8 +47,8 @@
   "bugs": {
     "url": "https://github.com/iTowns/itowns/issues"
   },
-  "homepage": "https://itowns.github.io/",
   "dependencies": {
+    "@itowns/geographic": "^2.44.3-next.42",
     "@mapbox/vector-tile": "^2.0.3",
     "@maplibre/maplibre-gl-style-spec": "^22.0.0",
     "@tmcw/togeojson": "^5.8.1",
@@ -76,56 +68,8 @@
     "three": "^0.170.0"
   },
   "devDependencies": {
-    "@babel/cli": "^7.25.6",
-    "@babel/core": "^7.25.2",
-    "@babel/plugin-transform-runtime": "^7.25.4",
-    "@babel/preset-env": "^7.25.4",
-    "@babel/preset-typescript": "^7.24.7",
-    "@babel/register": "^7.24.6",
-    "@stylistic/eslint-plugin": "^2.8.0",
-    "@types/proj4": "^2.5.5",
-    "@types/three": "^0.170.0",
-    "@typescript-eslint/eslint-plugin": "^8.5.0",
-    "@typescript-eslint/parser": "^8.5.0",
-    "@xmldom/xmldom": "^0.9.2",
-    "babel-inline-import-loader": "^1.0.1",
-    "babel-loader": "^9.2.1",
-    "babel-plugin-inline-import": "^3.0.0",
-    "babel-plugin-minify-dead-code-elimination": "^0.5.2",
-    "babel-plugin-minify-replace": "^0.5.0",
-    "babel-plugin-module-extension-resolver": "^1.0.0",
-    "babel-plugin-module-resolver": "^5.0.2",
-    "c8": "^10.1.2",
     "chalk": "^5.3.0",
-    "chart.js": "^4.4.4",
-    "compare-func": "^2.0.0",
-    "conventional-changelog-cli": "^4.1.0",
-    "copyfiles": "^2.4.1",
-    "core-js": "^3.38.1",
-    "cross-env": "^7.0.3",
-    "eslint": "^8.55.0",
-    "eslint-config-airbnb-base": "^15.0.0",
-    "eslint-import-resolver-babel-module": "^5.3.2",
-    "eslint-plugin-import": "^2.30.0",
-    "eslint-plugin-tsdoc": "^0.3.0",
-    "eslint-webpack-plugin": "^4.2.0",
-    "github-url-from-git": "^1.5.0",
-    "grunt": "^1.6.1",
-    "grunt-bump": "^0.8.0",
-    "https-proxy-agent": "^7.0.5",
-    "jsdoc": "^4.0.3",
-    "mocha": "^10.7.3",
-    "proj4": "^2.12.1",
-    "puppeteer": "^23.3.1",
-    "q": "^1.5.1",
-    "replace-in-file": "^8.1.0",
-    "sinon": "^19.0.2",
-    "three": "^0.170.0",
-    "typescript": "^5.6.2",
-    "undici": "^7.2.0",
-    "webgl-mock": "^0.1.7",
-    "webpack": "^5.94.0",
-    "webpack-cli": "^5.1.4",
-    "webpack-dev-server": "^5.1.0"
-  }
+    "copyfiles": "^2.4.1"
+  },
+  "homepage": "https://itowns.github.io/"
 }

package/CODING.md

@@ -1,120 +0,0 @@
-# Development guide
-
-iTowns needs `nodejs` (10+) and `npm` (at least 6.x) installed on the system.
-See the [node website](https://nodejs.org) to install node and npm.
-
-## Coding rules
-
-* Search and use existing methods to avoid duplicate code
-* Avoid instance `class/object` in method (optimization with the garbage collector)
-* Give explicite name to constants
-* Avoid duplicate code and encapsulate to simplify
-* For performance reasons, update objects only when needed
-* Don't add dead code
-* Remove obsolete comments
-
-## Building
-  
-* Download dependencies: `npm install`
-* Run the dev server:
-   * `npm start` (you can change the port: `npm start -- --port 3000`. If you
-     get an error message that is not related to the port being in use, please
-     update to last lts or stable version)
-   * Open `http://localhost:8080/`
-   * Make changes in the code, the browser will automatically reload on save
-* Build iTowns to produce a single independent script:
-   * `npm run build`
-   * The script and its source-maps are generated into the `dist/` folder
-   * You can run the built script to verify it works OK:
-      * `python -m SimpleHTTPServer 8080` (change the port at your convenience)
-      * Open `http://localhost:8080/`
-* Transpile itowns to ES5 to require it in your code:
-   * `npm run transpile`
-   * The transpiled source is in `lib/`
-   * You can then require `src/Main.js` in your code
-* Test and lint changes: see test, lint and test-examples npm script
-
-## Debugging
-* `babel-inline-import-loader` prevents the source map debug in browser. If you
-  want launch server and debug with the original source map, run : `npm run
-  debug`.
-* To debug iTowns package on your side project. You can link iTowns package with
-  `npm link ../path/iTowns/` in project folder and auto-transpile to `lib/` when
-  iTowns sources are modified with command `npm run watch` in iTowns folder.
-
-## Testing
-For unit and functional test, defines `HTTPS_PROXY` if you launch test behind a proxy.
-
-In order to run the tests, [puppeteer](https://github.com/GoogleChrome/puppeteer)
-needs to be installed. If installing puppeteer behind a proxy, use `HTTP_PROXY`,
-`HTTPS_PROXY`, `NO_PROXY` to defines HTTP proxy settings that are used to download
-and run Chromium.
-
-If puppeteer fails to download Chrome, you can try with the [documented environment
-variables](https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#environment-variables).
-Or you can download it manually, and then:
-* install puppeteer without downloading Chrome:
-  `PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 npm install puppeteer`
-* then use the env var `CHROME` to tell itowns/mocha/puppeteer what Chrome app
-  it should use: `CHROME=/opt/google/chrome-beta/chrome npm run test-examples`
-
-Then tests can be run with five differents methods:
-* `npm run test`: build and run all tests in iTowns (the one used by github action)
-* `npm run test-dev`: build in development mode and run all tests in iTowns (to get more messages)
-* `npm run test-unit`: run unit tests only
-* `npm run test-functional`: run functional testing with examples only, use
-  `mocha -t 30000 --require test/functional/hooks_functional.js
-  test/functional/<test_case>.js` to run a single example
-* `npm run test-with-coverage`: build and run all tests in iTowns and generate a
-  report on the coverage of the tests
-
-
-When running tests on examples, some environment variables can be set:
-* `SCREENSHOT_FOLDER`: take a screenshot at the end of each test and save it in
-  this folder. Example: `SCREENSHOT_FOLDER=/tmp/`
-* `CHROME`: path to Chrome executable. If unspecified itowns will use the one
-  downloaded during puppeteer install.
-* `DEBUG`: run Chrome in a window with the debug tools open.
-* `REMOTE_DEBUGGING`: run Chrome in headless mode and set up remote debugging.
-  Example: `REMOTE_DEBUGGING=9222` will setup remote debugging on port 9222.
-  Then start another Chrome instance, browse to `chrome://inspect/#devices` and
-  add `localhost:9222` in Discover network targets.
-
-Note: Chrome in headless mode doesn't support the WebGL `EXT_frag_depth`
-extension. So rendering may differ and some bugs can only be present in headless
-mode.
-
-### Syntax in tests
-
-[mochajs](https://mochajs.org/) is used for both type of tests. To avoid
-problems with same name variables, keep them in the smallest scope. For example,
-a variable should almost always be in the `it()` section of a test. However, it
-can be useful to keep a single shared variable for a bunch of tests (in the same
-file). For this, declare it in the `describe()` section, and set it (if
-possible) in a `before()` section.
-
-### Useful commands for continuous testing
-
-If you wish to have unit tests to continuously run, you can append to your
-running command `-- --watch`. You will be getting in this case `npm run
-test-unit -- --watch`.
-
-If you want to work on a single test and debug it, without having all the extra
-output, you can use this command `npm run base-test-unit test/unit/3dtiles.js`
-and of course replace 3dtiles.js with the correct filename. You can also append
-the `-- --watch` flag as well. If you want disable reporting and keep error message
-in console add `--reporter min`.
-
-## Release
-
-* `npm run changelog` generates changelog file.
-* `npm run bump --level=minor` bump version, generates changelog file and commit (default level is minor).
-
-## Contribute back
-
-See [the contributor's guide](CONTRIBUTING.md) for more information on how to
-contribute.
-
-Note : You should not commit changes to `package-lock.json` if you're not using
-npm >= 6 (particularly if you didn't make any change to the `package.json`
-either).

package/CONTRIBUTING.md

@@ -1,150 +0,0 @@
-# How to contribute
-
-Thanks for taking interest in iTowns !
-
-In addition to contributing to the iTowns code, we appreciate many types of
-contributions as well:
-
-* Being active on the iTowns mailing lists (see above) by answering questions
-  and providing input on iTowns' direction.
-* Showcasing your application built with iTowns : submit an issue with a link to
-  your demo on the [iTowns website
-  repository](https://github.com/iTowns/itowns.github.io/issues). Tag it with
-  the `demo` label.
-* Writing tutorials, creating examples, and improving the reference
-  documentation. See the issues labeled
-  [doc](https://github.com/iTowns/itowns/labels/doc).
-* Submitting issues as [described below](#submitting-an-issue).
-* Triaging issues. Browse the [issues](https://github.com/iTowns/itowns/issues)
-  and comment on issues that are no longer reproducible or on issues for which
-  you have additional information.
-
-If you don't know what to do but still want to contribute, check:
-
-* Issues labeled [beginner](https://github.com/iTowns/itowns/labels/beginner)
-* Issues labeled [help_wanted](https://github.com/iTowns/itowns/label/help_wanted)
-
-
-## Submitting an Issue
-
-If you think you've found a bug in iTowns, first search the [iTowns
-issues](https://github.com/iTowns/itowns/issues). If an issue already exists,
-you can add a comment with any additional information. Use reactions (not
-comments) to express your interest. This helps prioritize issues.
-
-If a related issue does not exist, submit a new one. Please include as much of
-the following information as is relevant:
-* Sample data to reproduce the issue.
-* Screenshot, video or animated .gif if appropriate (try
-  [LICEcap](http://www.cockos.com/licecap/)). Screenshots are particularly
-  useful for exceptions and rendering artifacts. If it is a rendering artifact,
-  also include the output of [webglreport.com](http://webglreport.com/) for the
-  computer you have the problem on.
-* Link to the thread if this was discussed on the iTowns mailing list or
-  elsewhere.
-* Your operating system and version, browser and version, and video card. Are
-  they all up-to-date? Is the issue specific to one of them ?
-* The exact version of iTowns. Did this work in a previous version ?
-* Ideas for how to fix or workaround the issue. Also mention if you are willing
-  to help fix it. If so, the iTowns team can often provide guidance and the
-  issue may get fixed more quickly with your help.
-
-
-## Ask a question, suggest an improvement
-
-If you have a question or a suggestion not related to a bug iTowns, you can search the
-[iTowns discussions](https://github.com/iTowns/itowns/discussions). If a discussion about
-your question or suggestion already exists, you can add a comment or upvote the original
-comment in the discussion. Otherwise, you can create a new discussion, detailing your
-question or suggestion.
-
-We recommend the use of [iTowns discussions](https://github.com/iTowns/itowns/discussions)
-for suggestions and questions.
-However, there is another way of suggesting improvements or asking questions, which is
-through iTowns mailing lists. There is a user mailing list and a developer mailing list.
-
-You can subscribe to the mailing lists here:
-
-* Developer: https://lists.osgeo.org/mailman/listinfo/itowns-dev
-* User: https://lists.osgeo.org/mailman/listinfo/itowns-user
-
-The mailing list archives are here:
-
-* Developer: https://lists.osgeo.org/pipermail/itowns-dev/
-* User: https://lists.osgeo.org/pipermail/itowns-user/
-
-If you cannot find any information on your problem in the archive, you can start
-a new thread by sending an email to the list, and someone will probably answer
-with a solution.
-
-
-
-## Fixing a bug, developing a feature or coding something
-
-You are more than welcome to develop to iTowns, may it be a fix, a new feature,
-documentation, or even a typo in a comment. For more information on the setup to
-for developing, follow the [Coding guide](CODING.md).
-
-## Opening a Pull Request
-
-We welcome pull requests with great interest. We try to promptly review them,
-provide feedback, and merge. Following the tips in this guide will help your
-pull request be merged quickly.
-
-If you plan to make a major change, please open an issue first. Pull requests
-for small features and bug fixes can generally just be opened without much
-discussion.
-
-### Pull Request Guidelines
-
-Code quality matters. Here are some advices to read before submitting a Pull
-Request.
-
-* Verify your code passes the linter and tests (`npm run test`). See the
-  [Testing guide](CODING.md#Testing).
-* Write meaningful commit messages, by following the [Angular
-  convention](https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md).
-  Here is a comprehensive list of all commit types we support :
-    * `feat`, `features` or `feature` for some feature addition ;
-    * `fix` for a bug fix ;
-    * `perf` for some performance improvements;
-    * `revert` for an undo operation ;
-    * `doc` or `docs` for some changes on the documentation ;
-    * `refactor`, `refacto` or `refactoring` for some code refactoring ;
-    * `test` or `tests` for changes test related ;
-    * `chore`, `rename` or `workflow` for some work on package versions or
-        dependency updates, some file renaming or some changes on workflow files ;
-    * `example` or `examples` for changes on examples or addition of a new one.
-* Keep the git history clean, rebase your work on the `master` branch of this
-  repository.
-* If this is your first contribution to iTowns, add your name to
-  [CONTRIBUTORS.md](https://github.com/iTowns/itowns/blob/master/CONTRIBUTORS.md).
-* If your pull request fixes an existing issue, include a link to the issue in
-  the description. Likewise, if your pull request fixes an issue reported on the
-  iTowns mailing list, include a link to the thread in the list archive.
-* If your pull request needs additional work, add the `in progress` label,
-  include a [task list](https://github.com/blog/1375%0A-task-lists-in-gfm-issues-pulls-comments),
-  or better, split it in several PR.
-* If you added new identifiers to the iTowns API:
-   * Include reference documentation with code examples.
-   * If your change adds significant features, provide a demo.
-* If you added third-party libraries, including new version of existing
-  libraries, update [LICENSE.md](LICENSE.md). If you plan to add a third-party
-  library, start a new issue first.
-* Split the PR if it contains features from different scopes
-* Squash all commits having the same scope
-
-## IP
-
-iTowns is Licenced under a dual licence CeCILL-B v1.0 and MIT (See
-[LICENSE.md](LICENSE.md)). If you want to include your code in the iTowns
-project, you have to licence the code under these same licences. You stay author
-of your work.
-
-You should also do an IP review for your contribution, to ensure that you have
-all rights to the code and that no patent apply to it.
-
-## Resources
-
-This CONTRIBUTING documentation has been inspired by the Cesium Contributing doc:
-* https://github.com/AnalyticalGraphicsInc/cesium/blob/master/CONTRIBUTING.md

package/CONTRIBUTORS.md

@@ -1,56 +0,0 @@
-See [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to contribute to iTowns 2.
-
-The following people have contributed to iTowns.
-
-* [IGN](http://www.ign.fr)
-  * [Gérald Choqueux](https://github.com/gchoqueux)
-  * [Alexandre Devaux](https://github.com/nosy-b)
-  * [Victor Coindet](https://github.com/VictorCo)
-  * [Quoc Dinh Nguyen](https://github.com/qdnguyen)
-  * [Grégoire Maillet](https://github.com/gmaillet)
-  * [Guillaume Liégard](https://github.com/gliegard)
-  * [Adrien Berthet](https://github.com/zarov)
-  * [Madec Germerie-Guizouarn](https://github.com/mgermerie)
-  * [Mathieu Brédif](https://github.com/mbredif)
-  * [Aymeric Dutremble](https://github.com/a-dutremble)
-
-* [CIRIL Group](https://www.cirilgroup.com/en/):
-  * [Vincent Jaillot](https://github.com/jailln)
-  * [Anthony Gullient](https://github.com/AnthonyGlt)
-  * [Jonathan Garnier](https://github.com/jogarnier)
-  * [Irénée Dubourg](https://github.com/airnez)
-
-* [Oslandia](http://www.oslandia.com)
-  * [Vincent Picavet](https://github.com/vpicavet)
-  * [Jérémy Gaillard](https://github.com/Jeremy-Gaillard)
-  * [Pierre-Éric Pelloux-Prayer](https://github.com/peppsac)
-  * [Augustin Trancart](https://github.com/autra)
-
-* [AtolCD](http://www.atolcd.com)
-  * [Thomas Broyer](https://github.com/tbroyer)
-
-* [LIRIS](https://liris.cnrs.fr/)
-  * [Nicolas Saul](https://github.com/NikoSaul)
-  * [Emmanuel Schmück](https://github.com/EmmanuelSchmuck/)
-  * [Marie Lamure](https://github.com/mlamure)
-  * [Vincent Jaillot](https://github.com/jailln)
-  * [Valentin Rigolle](https://github.com/Crejak)
-  * [Valentin Machado](https://github.com/valentinMachado)
-
-* [virtualcitySYSTEMS](https://www.virtualcitysystems.de/)
-  * [Ben Kuster](https://github.com/bkuster)
-
-* [Prolexia](http://prolexia.fr/)
-  * [Dorian MOFFROID](https://github.com/dorian-moffroid-prolexia)
-
-* [Diginove](http://diginove.com/index.php/fr/diginove-lexpertise-en-traitement-dimages/):
-  * [Michel Benet](https://github.com/mbenevole)
-
-* [Sogelink](https://www.sogelink.com/)
-  * [Kévin ETOURNEAU](https://github.com/ketourneau)
-  * [Alexis DELFORGES](https://github.com/pourfex)
-  * [Tim Ebben](https://github.com/tebben)
-
-The following organizations are the current maintainers of iTowns:
-* IGN (http://www.ign.fr)
-* Ciril Group (https://www.cirilgroup.com/)

package/LICENSE.md

@@ -1,44 +0,0 @@
-Copyright 2016 iTowns Contributors
-
-iTowns V2 is licenced under both licences CeCILL-B Version 1.0 and MIT.
-
-## iTowns V2
-
-### CeCILL-B
-
-iTowns is licensed under the CeCILL-B license, Version 1.0. You may obtain a copy of the License at
-
-https://cecill.info/licences/Licence_CeCILL-B_V1-en.html
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
-### MIT
-
-iTowns is licensed under the MIT Licence. You may obtain a copy of the License at
-
-https://opensource.org/licenses/MIT
-
-Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
-
-## Third-Party Code
-
-iTowns V2 includes the following third-party code.
-
-### ThreeJS
-
-> Copyright (c) 2010-2015 three.js authors
->  http://www.opensource.org/licenses/mit-license.php
->
->  MIT License (c) copyright B Cavalier & J Hann
->
-> 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.
-
-### PriorityQueue
-
-PriorityQueue is published under a Public Domain status.
-
-https://github.com/adamhooper/js-priority-queue