Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

Add support for douglas-peucker simplify-algorithm #487

Closed
matthijsmelissen opened this issue Feb 11, 2018 · 11 comments
Closed

Add support for douglas-peucker simplify-algorithm #487

matthijsmelissen opened this issue Feb 11, 2018 · 11 comments

Comments

@matthijsmelissen
Copy link

Would it be possible to add support for the douglas-peucker simplify-algorithm?

It seems on the Mapnik side this is already implemented:

@nebulon42
Copy link
Collaborator

Definitely. It needs support in mapnik-reference to be usable for CartoCSS.

@matthijsmelissen
Copy link
Author

Just to be sure: at the moment it does not have support in Mapnik-reference?

@nebulon42
Copy link
Collaborator

nebulon42 commented Feb 12, 2018

No, that is why it is not recognized by CartoCSS as available option. Mapnik devs do not update mapnik-reference for each feature accordingly. Sometimes something is forgotten. The upcoming 1.0 release will make CartoCSS more independent from mapnik-reference. So in theory after 1.0 you could fork mapnik-reference, add the missing definition yourself and use that for CartoCSS processing if necessary.

@matthijsmelissen
Copy link
Author

No, in that case fixing it in mapnik-reference is clearly the way to go. Does cartocss recognize it automatically if it is added in mapbik-reference? In that case, the issue can be close sed on this side.

@nebulon42
Copy link
Collaborator

Unfortunately, no. After adding it to mapnik-reference that needs a new release and a new package on npm. Then I have to bump the version number here and release CartoCSS and update the package on npm. While I have the rights to do all of this I still will open a PR on mapnik-reference so that others have the chance to comment.

@matthijsmelissen
Copy link
Author

Clear, thanks!

@nebulon42
Copy link
Collaborator

Small correction. Releasing and publishing mapnik-reference is sufficient. Since it is referenced by ~ in package.json new installs of CartoCSS would pick up the change automatically.

@nebulon42
Copy link
Collaborator

PR pending.

@matthijsmelissen
Copy link
Author

Do you have an issue number?

@skorasaurus
Copy link

@nebulon42 nebulon42 removed this from the 1.0 milestone Feb 23, 2018
@nebulon42
Copy link
Collaborator

Closing here per #487 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants