Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase precision of points, lines and shapes by translating them clo… #138

Merged

Conversation

RayLarone
Copy link
Contributor

@RayLarone RayLarone commented Jul 6, 2022

…ser to the Pixel Origin.

See this issue (#137) for an explanation of the code.

This branch aims to resolve #137, #54 and #119.

This is using the map center (map.getCenter()) as a best guess at where the "precision center" should be located.
Other options could be to use the data/geojson centroid, or to pass in a LatLng pair as an argument.

@kkdd
Copy link

kkdd commented Jul 19, 2022

Hello,
How about the global approach with emulating double-precision webGL
shown in Double precision on WebGL for mapping centimetric points #54.

@RayLarone
Copy link
Contributor Author

RayLarone commented Jul 19, 2022

Hi @kkdd.
Yeh, double precision in WebGL would be a better solution overall as it would give high precision for the whole map. Although, I don't know enough about shaders to do this, also it might affect the performance of the plugin as a lot more computation is being done in the shader.

The solution in this pull request doesn't change the shaders in any way and will have a negligible impact on performance as it is only changing a few lines of code. It should be enough for most use cases.

Whatever the case, this is what I am using to plot high precision points, so thought I'd share it with the group.

@kkdd
Copy link

kkdd commented Jul 19, 2022

Hello, RayLarone. Thank you for your comment.
I see that the performance should also be important factor, as you mentioned.

@robertleeplummerjr
Copy link
Owner

This PR breaks unit tests. Could you fix those, and commit? Then I can merge.

@RayLarone
Copy link
Contributor Author

Hi @robertleeplummerjr. Sure, although apologies, I'm a data analyst not a programmer so maybe I'm not fully understanding the unit testing. What do you mean by this pull request breaks unit tests?

When I clone this branch, run npm i and then yarn test I get the message:

Test Suites: 11 passed, 11 total
Tests:       249 passed, 249 total
Snapshots:   0 total
Time:        5.696 s
Ran all test suites.
Done in 6.85s.

How can I see which unit tests need addressing so I can fix the issues?

@robertleeplummerjr
Copy link
Owner

Perhaps I had a premature failure when I tested it. I'm away this week but next I'll look into merging.

@hoixw
Copy link

hoixw commented Mar 23, 2024

@robertleeplummerjr please look into merging again :)

@trafficonese
Copy link
Contributor

The build and tests run without errors for me.

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

Successfully merging this pull request may close these issues.

Polygons Not Rendering Correctly
5 participants