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.

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

docs: Exporting discover imagery in large maps #2950

Merged
merged 5 commits into from
Jan 30, 2025
Merged

Conversation

jacobdadams
Copy link
Member

Here's a blog post explaining the workaround for blurry WMTS imagery in small-scale, large-size maps. @ZachBeck and @rkelson, I'd love to know if this makes sense to you and is clearly explained.

I also added a new item to our common issues page in the Discover docs and linked it to this post.

Copy link

netlify bot commented Jan 29, 2025

Deploy Preview for gis-utah-gov ready!

Name Link
🔨 Latest commit d6aeab0
🔍 Latest deploy log https://app.netlify.com/sites/gis-utah-gov/deploys/679b9ccb7bd23a0008a85dce
😎 Deploy Preview https://deploy-preview-2950--gis-utah-gov.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 97 (🔴 down 1 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Member

@steveoh steveoh left a comment

Choose a reason for hiding this comment

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

creative solution to an interesting problem. nice work. thanks for sharing.

@jacobdadams
Copy link
Member Author

Thanks for catching all those technical fixes 👍

Copy link
Member

@ZachBeck ZachBeck left a comment

Choose a reason for hiding this comment

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

Looks good/makes sense to me.

Copy link
Member

@ZachBeck ZachBeck left a comment

Choose a reason for hiding this comment

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

Looks good/makes sense to me.

@rkelson
Copy link
Member

rkelson commented Jan 30, 2025

Nice work @jacobdadams ! looks great to me. Thanks for taking the time to figure it out and document it. The only thing that bugged me where the multiple 16 times references that could be grouped but it gets the point across.

@rkelson
Copy link
Member

rkelson commented Jan 30, 2025

I just found a typo 'alway' so let me read it again with some coffee

@rkelson
Copy link
Member

rkelson commented Jan 30, 2025

I read this again and can't find any other typos other than the renderer will **alway** request. Should be good to go after fixing that

@jacobdadams
Copy link
Member Author

Thanks for catching that, @rkelson. For some reason my spellchecker isn't seeing that as wrong. Makes me wonder what's goin on there. There should be a green button somewhere that says "Review Changes" or something like that. Could you please click on that and hit the "Approve" checkbox so that github is happy and knows you approved it?

@jacobdadams jacobdadams force-pushed the scaling-tile-requests branch from 628c549 to d6aeab0 Compare January 30, 2025 15:37
Copy link
Member

@rkelson rkelson left a comment

Choose a reason for hiding this comment

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

Look good with exception to the typo alway

@jacobdadams jacobdadams merged commit 947dc32 into main Jan 30, 2025
8 checks passed
@jacobdadams jacobdadams deleted the scaling-tile-requests branch January 30, 2025 16:19
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.

4 participants