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.

Sign up for GitHub

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

Jump to bottom

MVP #1

Open
5 of 10 tasks
dabreegster opened this issue Nov 23, 2023 · 0 comments
Open
5 of 10 tasks

MVP #1

dabreegster opened this issue Nov 23, 2023 · 0 comments

Comments

@dabreegster
Copy link
Contributor

dabreegster commented Nov 23, 2023 •
edited
Loading

"Correctness" to use in the od2net viewer:

  • Include the actual feature properties (and maybe revisit squeezing osm_tags into a single JSON string, to improve encoding)
  • Plumb along the JSON metadata field
  • Decide what to do about the other layers (points representing origins and destinations)
  • Use compression internally (which does tippecanoe use?)
  • Enforce per-tile limits on number of features or total size, by sorting by the count property

Performance of the tool itself:

  • Figure out what spatial indexing we can use to filter for each tile. rstar with Web Mercator coordinates? Something specialized for WGS84? Can we directly use tile boundaries as the spatial indexing bins?
  • Does processing each tile in parallel help?

Logistic:

  • File bug about empty geometry encoding in mvt
  • Name this properly and make a separate repo
  • Get feedback from georust and others
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dabreegster