Any chance to include geojson properties?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
First of all, awesome work with this library!
For my application i will need to use properties for data-drive visualisation (color, size, ...) , therefore is it important to maintain the properties while running tile-count-create and tile-count-tile.
Question:
It is possible to tweak this library to include custom properties, not just density? So, while doing the merge for different zoom levels, and in case of different properties at the geojson, they would merge as array of values (e.g. properties.users: [24,66,94]).
Maybe you know a better way, let me know, thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the tile-count-create and tile-count-tile entry points to understand how GeoJSON properties are currently handled during tile accumulation and zoom-level merges. The requested behavior is to preserve custom properties and merge differing values into arrays, such as properties.users: [24,66,94].
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100