Fix symbology for empty border between geometries in Hurricane Harvey example
See original GitHub issueDue to how small the geometries are and the snapping done to transform the geometries in the MVT format, the Hurricane Harvey example shows small holes / lines between some geometries:
I’ve found an easy workaround, which is to style the stroke in the same way:
Full style:
color: opacity(ramp(linear($sum_qpf,1,120),temps),($e_totpop/$area_sqmi)/500)
filter: animation(linear($sum_qpf,144.5, 1.5),5,fade(0,100))+0.1
strokeWidth: 0.2
strokeColor: opacity(ramp(linear($sum_qpf,1,120),temps),($e_totpop/$area_sqmi)/500)
What do you think @makella, does it makes sense to change the style?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Filling the Void: Sinkhole Repair Following Hurricane Harvey
First, the water flooding the roadway had to be slowly pumped out. Then, Walter P Moore carefully monitored the wall condition to ensure...
Read more >Hurricane Harvey: Houston's flooding made worse by ... - Quartz
The city's gung-ho approach to development has destroyed the area's natural ability to drain away hurricane floodwaters.
Read more >NERC | Hurricane Harvey Event Analysis Report
As Harvey moved inland, the storm stalled, causing excessive rain (40–50 inches) in parts of Southeastern Texas and flooding large areas of. Houston...
Read more >Tropical cyclone - Wikipedia
A tropical cyclone is a rapidly rotating storm system characterized by a low-pressure center, a closed low-level atmospheric circulation, strong winds, ...
Read more >Hurricane Harvey
Harvey started as a typical weak August tropical storm that affected the Lesser. Antilles and dissipated over the central Caribbean Sea.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This has to do with the resolution we use to extract geometries from the database. Before 1.1 we were using 256 and now we are using 2048, which improved things but in this map I keep seeing artefacts until I use 12-16k which
We could increase the resolution but that’d mean more network transfer and more time to process the geometries. A nice solution for this map, since it’s small but has a lot of tiny vertex, would be the one tile strategy (one single request with the biggest precision possible) but we don’t have it yet 😢
fixed with today’s release