Git Product home page Git Product logo

openlayers-editor's Introduction

Openlayers Editor

npm Build e2e tests code style Conventional Commits

OpenLayers Editor (OLE) is based on OpenLayers and provides a set of controls for extended editing of spatial data.

Contributions are welcome! Feel free to add more controls and to extend the current functionality. Additionally, the build process is currently very basic and could be optimized. Translations would be nice, too.

Features

  • CAD tool for geometry alignment
  • Drawing line, point and polygon features
  • Moving and rotating geometries
  • Modifying geometries
  • Deleting geometries
  • Topology operations using JSTS: buffer, union, intersection, difference
  • Toolbar for activating and deactivating controls

Demo

For a demo, visit https://openlayers-editor.geops.com.

Dependencies

  • node & npm

Getting started

  • Clone this repository
  • Install: npm install
  • Build: npm run build
  • Run: npm start
  • Open your browser and visit http://localhost:8080

Usage

<link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/ole@latest/style/ole.css" />
<script src="https://cdn.jsdelivr.net/npm/[email protected]/build/index.js"></script>
var editor = new ole.Editor(map);

var cad = new ole.control.CAD({
  source: editLayer.getSource()
});

var draw = new ole.control.Draw({
  source: editLayer.getSource()
});

editor.addControls([draw, cad]);

Development

  • Install: npm install
  • Build: npm run build
  • Create doc: npm run-script doc

Versions and Changelog

This repo uses standard-version for release versioning and changelog management. Therefore updates should be committed using conventional commit messages:


<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

The commit contains the following structural elements, to communicate intent to the consumers of your library:

  1. fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in semantic versioning).
  2. feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in semantic versioning).
  3. BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in semantic versioning). A BREAKING CHANGE can be part of commits of any type.
  4. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others.
  5. footers other than BREAKING CHANGE: may be provided and follow a convention similar to git trailer format.

Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in semantic versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., feat(parser): add ability to parse arrays.

openlayers-editor's People

Contributors

candux avatar danji90 avatar dependabot-preview[bot] avatar dependabot[bot] avatar drnextgis avatar edellucien avatar friedjoff avatar greenkeeper[bot] avatar imgbotapp avatar lb1a avatar lb1c avatar mhaertwig avatar oterral avatar renovate-bot avatar renovate[bot] avatar trendels avatar ulimueller avatar v1r0x avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

openlayers-editor's Issues

An in-range update of cypress is breaking the build 🚨

The devDependency cypress was updated from 3.1.0 to 3.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cypress is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

How to see if Topology works

Hey guys, appreciate the work,
1_delete_edge
2_After_Delete_New_Poly

is there any topological validation while modifying. What about add edge to polygon or delete edge from polygon? Is that possible? What do you think about those case? Thanks in advance

TypeError: declutterLayers[i].renderDeclutter is not a function

When I have clicked on Toolbar then the error throws on the browser.
[https://ibb.co/xhVDgwG](error image)

×
TypeError: declutterLayers[i].renderDeclutter is not a function
CompositeMapRenderer.renderFrame
src/renderer/Composite.js:137
134 | }
135 | replaceChildren(this.element_, this.children_);
136 | this.dispatchRenderEvent(RenderEventType.POSTCOMPOSE, frameState);

137 | if (!this.renderedVisible_) {
| ^ 138 | this.element_.style.display = '';
139 | this.renderedVisible_ = true;
140 | }
View compiled
Map.PluggableMap.renderFrame_
src/PluggableMap.js:1418
Map.
src/PluggableMap.js:213
210 | * @Private
211 | * @type {import("./transform.js").Transform}
212 | /
213 | this.pixelToCoordinateTransform = createTransform();
| ^ 214 | /
*
215 | * @Private
216 | * @type {number}

Move to new OL6 select interaction

In #140 we upgraded to OpenLayers 6 release. This release has breaking changes in the select interaction, so we copied the old implementation to our repository.

We should try to move to the new OL6 select interaction to minimize code duplication and maximize compatibility with OL.

OLE not building with open layers v6.15.0 +

src/interaction/selectmodify.js uses GeometryType from 'ol/geom/GeometryType'. This does not exist in OL v6.15.0+ as it has been deprecated.

From OL release notes:

"Replacement of string enums with union types
This change only affects users that were using the non-API string enums

ol/OverlayPositioning
ol/extent/Corner
ol/format/FormatType
ol/geom/GeometryType
ol/source/State
ol/source/WMSServerType
ol/source/WMTSRequestEncoding
Instead of these, use the respective strings, which are now typesafe by means of union types."

Could OLE be updated to work with OL v6.15.0+ please?

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Unit tests

Implement automated unit tests using Jest.

Delete node bug

When SelectModify is active, nodes can be removed from polygons and lines.

When hovering along the edges of polygons and lines, while the overlay is active (the blue hover point is visible), on click it can happen that the feature is deselected and a hover style Point feature is created on the edge. The Point feature is removed on click on the map.

This bug can be easily reproduced when trying to delete nodes from lines or polygons with exactly two nodes for lines and three nodes for polygons (the minimum number nodes to classify as the geometry)

Expected: Click on edges while modifying and click on minimum number of nodes does nothing

An in-range update of neutrino is breaking the build 🚨

Version 8.3.0 of neutrino was just published.

Branch Build failing 🚨
Dependency neutrino
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

neutrino is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

JSTS events

Hello! How can i get the "drawned" event from 2 or more feature union (JSTS)?

Openlayers V4

Thanks for your amazing library.
Can I use this library with Openlayer V4 ?

An in-range update of css-loader is breaking the build 🚨

Version 0.28.8 of css-loader was just published.

Branch Build failing 🚨
Dependency css-loader
Current Version 0.28.7
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

css-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v0.28.8

2018-01-05

Bug Fixes

  • loader: correctly check if source map is undefined (#641) (0dccfa9)
  • proper URL escaping and wrapping (url()) (#627) (8897d44)
Commits

The new version differs by 10 commits.

  • 0fc46c7 chore(release): 0.28.8
  • 333a2ce chore(package): update dependencies
  • 39773aa ci(travis): use npm
  • 8897d44 fix: proper URL escaping and wrapping (url()) (#627)
  • 0dccfa9 fix(loader): correctly check if source map is undefined (#641)
  • d999f4a docs: Update importLoaders documentation (#646)
  • 05c36db test: removed redundant modules argument (#599)
  • c45fa66 test: add case for url processing (#603)
  • 7039740 docs(README): add anchor tags to options table (#609)
  • 0840c80 Fix markdown for link to webpack resolve.alias doc (#595)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Feature: improve snap controls to be able to snap on geometries, not only fix markers

Hi there,

Few months or so ago I saw this repository. Nice work, I liked it very much. Especially union/intersection/buffer etc. things are cool!

On the other hand, some controls are a bit confusing. Either I didn't understand how to use em or there could be some malfunction. For example I see a bit strange behavior while using snap controls. Here are the steps to reproduce the problem:

1- Put a point on a map with using "draw point" tool.
2- Snap is opened. 0 px 10 px it won't matter.
3- There are x signs at 4 side of point. The controller snaps these x signs.
4- How to exactly start a line from the exact location of point? I could find there is no way to snap on the point but 4 x marks.

This one works with lines, have strange issues with polygons (never puts a point at snap location).

I didn't get the idea behind the requirement of adding x signs around the vertices. OpenLayer's snap control works well in my opinion except not being able to snap the currently drawing geometry (or can be done that I don't know the way yet). I believe you are planning to implement snap controls like AutoCAD's. They do good job as well.

By the way, also I am working on a hobbyish thing atm if ye wanna check (can see ol snapping already):
https://onderaltintas.github.io/arz/

Have fun,

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.32.0 to 4.32.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.32.1

Bugfixes

  • reverts some changes from 4.32.0 which accidentally disabled some CommonJs features when using node: false.
Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Import JSTS from external package

Controls that use JSTS code should not import JSTS files by referencing the full path to the node_modules directory. Instead Webpack should import and compile JSTS files by referencing the JSTS package. Right now this will not work, because Webpack will not compile files from external packages. Maybe use and configure babel-loader.

Error - npm start

Hello, i need help to get the project working, complete log of this run:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/lib/node_modules/npm/bin/npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'start',
1 verbose cli '--scripts-prepend-node-path=auto' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]
start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]
start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/cesar/WebstormProjects/ole2/node_modules/.bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle [email protected]start: CWD: /home/cesar/WebstormProjects/ole2
10 silly lifecycle [email protected]
start: Args: [ '-c', 'webpack-dev-server --progress --watch' ]
11 info lifecycle [email protected]~start: Failed to exec start script
12 verbose stack Error: [email protected] start: webpack-dev-server --progress --watch
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at emitTwo (events.js:126:13)
12 verbose stack at ChildProcess.emit (events.js:214:7)
12 verbose stack at maybeClose (internal/child_process.js:925:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
13 verbose pkgid [email protected]
14 verbose cwd /home/cesar/WebstormProjects/ole2
15 verbose Linux 4.10.0-42-generic
16 verbose argv "/usr/bin/node" "/usr/lib/node_modules/npm/bin/npm-cli.js" "run" "start" "--scripts-prepend-node-path=auto"
17 verbose node v8.9.3
18 verbose npm v5.6.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error [email protected] start: webpack-dev-server --progress --watch
23 error spawn ENOENT
24 error Failed at the [email protected] start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

An in-range update of webpack is breaking the build 🚨

The devDependency webpack was updated from 4.29.6 to 4.30.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v4.30.0

Features

  • add amd: false to disable AMD support
  • Compilation.hooks.finishModules now also allows async plugins
  • add output.libraryTarget: "system" to compile for SystemJs environment

Bugfixes

  • fix generating a null id when concatenating an entry module in a different chunk
  • fix unneeded chunk references when splitting modules from chunks
  • fix parsing of function name in function scope

Performance

  • Lazy require some internal files
  • Faster way to generate function headers

Contributing

  • Run prettier on examples markdown
Commits

The new version differs by 102 commits.

  • b72b96a 4.30.0
  • 9ededfa Merge pull request #9034 from webpack/dependabot/npm_and_yarn/tapable-1.1.3
  • e33a91f chore(deps): bump tapable from 1.1.1 to 1.1.3
  • de81dd0 Merge pull request #8864 from joeldenning/issue-8833
  • 7dfddc2 Merge pull request #8858 from webpack/dependabot/npm_and_yarn/json-schema-to-typescript-6.1.3
  • f7d0c25 Improve way how System is tested
  • 39a680d formating of output code
  • e2e74f5 Merge pull request #8980 from webpack/dependabot/npm_and_yarn/eslint-5.16.0
  • 81dc70d Merge pull request #9022 from sandersn/fix-webassembly-declaration
  • 13aa512 Merge pull request #9023 from webpack/dependabot/npm_and_yarn/typescript-3.4.3
  • 1566036 chore(deps-dev): bump typescript from 3.4.2 to 3.4.3
  • ce33ca7 Update WebAssembly declaration
  • 5117461 Merge pull request #9006 from hiroppy/feature/fix-template-syntax
  • 9e60850 Merge pull request #8984 from webpack/dependabot/npm_and_yarn/react-16.8.6
  • 5f75527 Bump json-schema-to-typescript from 6.1.1 to 6.1.3

There are 102 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Drawend event

Hello! How can i use the drawend event with ole2?

My code:

var draw;
if (tipo === 'Point') {
draw = new ole.control.Draw({
source: source
});
} else if (tipo === 'LineString') {
draw = new ole.control.Draw({
type: 'LineString',
source: source
});
} else if (tipo === 'Polygon') {
draw = new ole.control.Draw({
type: 'Polygon',
source: source
});
}

draw.on('drawend', function (evt) {
...

            });

Provide public API to control interactions

@mhaertwig What do you think about making drawInteraction an public property and maybe renaming it to interaction?

Sounds good! How do we deal with controls having multiple interactions, like the CAD control. Alternatively we could implement a custom event handling for OLE to be more flexible. What do you think?

Originally posted by @mhaertwig in #85 (comment)

OLE can't depend on OL loaded with webpack

I'm trying to package my app that uses open layers using webpack.
I loaded ole from node_modules in my main.js file

import ole from 'ole';

and I provided the ol library directly in webpack.config.js

new webpack.ProvidePlugin({
     "ol": "ol"
 })

Webpack ran without any errors but running the bundle in chrome browser I got the following exception:

Uncaught TypeError: Cannot read property 'Control' of undefined
at Object. (main.js:24772)
at t (main.js:24510)
at Object. (main.js:24698)
at t (main.js:24510)
at Object. (main.js:24685)
at t (main.js:24510)
at Object. (main.js:24682)
at t (main.js:24510)
at main.js:24521
at main.js:24522

the line that broke looks like this

}(ol.control.Control);t.a = c;

sorry I couldn't get it un-minified

An in-range update of @neutrinojs/library is breaking the build 🚨

Version 8.3.0 of @neutrinojs/library was just published.

Branch Build failing 🚨
Dependency @neutrinojs/library
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/library is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @neutrinojs/style-loader is breaking the build 🚨

Version 8.3.0 of @neutrinojs/style-loader was just published.

Branch Build failing 🚨
Dependency @neutrinojs/style-loader
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/style-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Drawing custom icons for point

Hello,
we have a use case wheer we need to draw different "type of points" with the editor.

Each point will correlate to an icon of a different style.....

CAn that be done via the editor ?
CAn we custom an icon for the point draw ?

Demo broken?

Demo seems to be broken. In the console I get a ReferenceError: ole is not defined error.
Error occurs at

// ole.geops.de:73:11
var editor = new ole.Editor(map);

An in-range update of @neutrinojs/image-loader is breaking the build 🚨

Version 8.3.0 of @neutrinojs/image-loader was just published.

Branch Build failing 🚨
Dependency @neutrinojs/image-loader
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/image-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of @neutrinojs/library is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 8.2.2 of @neutrinojs/library was just published.

Branch Build failing 🚨
Dependency @neutrinojs/library
Current Version 8.2.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/library is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Snap

The snap does not allow to join the features without a space between them
Peek 04-12-2020 12-41

An in-range update of uglifyjs-webpack-plugin is breaking the build 🚨

Version 1.1.7 of uglifyjs-webpack-plugin was just published.

Branch Build failing 🚨
Dependency uglifyjs-webpack-plugin
Current Version 1.1.6
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

uglifyjs-webpack-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

  • 75943e1 chore(release): 1.1.7
  • 2343274 fix(index): reduce memory consumption (cacheKey.hash) (#215)
  • 7d1b487 test: update snapshots (#214)
  • f66f6f0 docs(README): mangle.props instead of mangle.properties (#207)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Chrome Modify Cursor

In Chrome (tested with 86.0.4240.111 on Ubuntu) the 'grab'-cursor (used for moving features and nodes in the ModifyControl) is currently not supported. Although [MDN|https://developer.mozilla.org/en-US/docs/Web/CSS/cursor] states it has support for '-webkit- grab', it doesn't work in any of the test sites like http://elektronotdienst-nuernberg.de/bugs/cursor.html or https://www.w3schools.com/cssref/tryit.asp?filename=trycss_cursor in the latest stable Chrome version.

This issue needs to be monitored and checked for Chrome updates that solve the bug.

An in-range update of @neutrinojs/dev-server is breaking the build 🚨

Version 8.3.0 of @neutrinojs/dev-server was just published.

Branch Build failing 🚨
Dependency @neutrinojs/dev-server
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/dev-server is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Complex geometries can generate a large number of cad guides

Problem

As guides are generated by the edges of features registered for snapping, when map features have any complexity they can result in a large number of guides being generated. As shown in the image below, 2 features can generate a large number of lines (in the image 10). In our application we have seen in real maps 50+ lines being generated using nbClosestFeatures: 5. In cases like this the guides are essentially meaningless.

image

Proposal

Add a new option (limitGuidesFromFeature) to the cad control which provides the user the ability to limit the number of features that can be generated from any given feature. For example, you might limit the number of lines that can be possibly generated from a feature to 3; we would then limit the number of lines added to the map to the 3 most proximal to the users cursor. This way, there will be a hard maximum of lines ever shown on the users screen to nbClosestFeatures times the limitGuidesFromFeature.

(This is the strategy I plan to implement in my companies fork of the project, we will be happy to submit the implementation if this sounds reasonable).

An in-range update of @neutrinojs/airbnb-base is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 8.2.2 of @neutrinojs/airbnb-base was just published.

Branch Build failing 🚨
Dependency @neutrinojs/airbnb-base
Current Version 8.2.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/airbnb-base is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Conflict with ModifyControl and map zoom doubleClick events

Bug: While the ModifyControl is activated, the map doubleClick zoom no longer works since the Editor listens to the doubleClick from the selectModify Interaction instead.

Currently this can be prevented by redefining the modifyCondition (doubleClick by default) in the ModifyControl options, but a permanent solution should be implemented in OLE.

Fix: The condition needs to be refactored to only apply when features are present at the pixel

Saving and reloading drawn layers

Hi,

Im sure its not an editor feature, but is there any snipppest we can use to quickly read the geometry that was drawn with the editor ?
It might be just an open layer feature but just asking...

An in-range update of @neutrinojs/airbnb-base is breaking the build 🚨

Version 8.3.0 of @neutrinojs/airbnb-base was just published.

Branch Build failing 🚨
Dependency @neutrinojs/airbnb-base
Current Version 8.2.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

@neutrinojs/airbnb-base is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.