Skip to content

Conversation

@rubillionaire
Copy link

closed variable once set to true is not reset to false for subsequent member processing, so all following members are considered to be self closing, leading to render bugs. the fix is to reset the closed variable along with the other variables that track progress through the multipolygon.

…oduce more than one closed polygon, because the 'closed' variable was not getting reset once one was found, so every subsequent member was being processed as if it close immediately. added a test with sample data that produces the correct result.
…her peermaps ecosystem forks, as the original repos do not seem to be getting any activity
… the INT and FLOAT vlaue types are being considered. not sure what to do with STRING types, since we can't through them straight at the GPU, so perhaps we drop them, and consider a task to the caller to consider a mapping from STRING to INT or FLOAT
- [encode] major: changes the encoding and decoding schema to include additional values based on tags. if no additional tags are included, then only an additional 0 is written to the end of the buffer
- minor: adds the georender schema here, local to the repo to track changes.
…hat is part of the base of georender and what is a tag beyond that.
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.

1 participant