Skip to content

rewrite viz section#248

Open
pvgenuchten wants to merge 1 commit into
geopython:masterfrom
pvgenuchten:rewrite-viz-revert-cog-ol
Open

rewrite viz section#248
pvgenuchten wants to merge 1 commit into
geopython:masterfrom
pvgenuchten:rewrite-viz-revert-cog-ol

Conversation

@pvgenuchten

Copy link
Copy Markdown
  • update with timisoara data
  • revert cog in ol, agree with just, it is not timely

@pvgenuchten pvgenuchten force-pushed the rewrite-viz-revert-cog-ol branch 2 times, most recently from eeaf3e9 to 258d2ad Compare June 23, 2026 09:03
@geographika

Copy link
Copy Markdown

@pvgenuchten - I was about to create an issue that the pydeck example was broken for me when testing with the latest Docker image - but you have addressed this in this PR.

"\n",
"# Create cluster layer\n",
"m.add(MarkerCluster(markers=markers, disable_clustering_at_zoom=16))\n",
"m"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this m required? It does not throw an error, but it still runs when removing it.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

m prints the actual map, ah so m is not needed, maybe m.add already prints it (jupyter plots any content which is returned by the last statement, in this case m)

@pvgenuchten pvgenuchten Jun 23, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, because in quite cases the m variable (for map) is reused, there is a bit unexpected behaviour if you don't explicitely call the m finally. maybe more explicit use display(m) is more understandable...

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah ok - it seemed fine to remove when I tested, but a comment above saying it will display is also fine

"</script>\n",
"''')\n",
"\n"
"gdal.Warp('../data/output/world_3857_cog.tif','../data/world.rgb.tif',dstSRS='EPSG:3857',format='COG')\n"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get a couple of warnings here that it might be good to explain? Warning 1: Clamping output bounds to (-20037508.342789,-20037508.342789) -> (20037508.342789, 20037508.342789) Warning 1: Clamping output bounds to (-20037508.342789,-20037508.342789) -> (20037508.342789, 20037508.342789)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, just fixed that

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

apparently when you warp -180,90 this error occurs, limiting to -180,85...

@pvgenuchten pvgenuchten force-pushed the rewrite-viz-revert-cog-ol branch 3 times, most recently from 856011c to 16d2bd7 Compare June 23, 2026 11:05
revert cog in ol, agree with just, it is not timely
@pvgenuchten pvgenuchten force-pushed the rewrite-viz-revert-cog-ol branch from 16d2bd7 to ee1c243 Compare June 23, 2026 12:52
@pvgenuchten

pvgenuchten commented Jun 23, 2026

Copy link
Copy Markdown
Author

rebased to master
using display(var) instead of var (for plotting a result variable), to be more explicit
Note, that in bokeh this is show(var), a bit unexpected...

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.

2 participants