-
Notifications
You must be signed in to change notification settings - Fork 258
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
Drop best flag for Texas imagery sources #2049
base: gh-pages
Are you sure you want to change the base?
Conversation
We do not drop best just because Bing provides newer imagery, based on that standard most of the best flag will be dropped. |
actually yes, that is a good reason to drop the |
I agree that we should try to balance imagery clarity and currency so it's not always easy to say which is better, but in general if Bing is has reasonable resolution to trace building outlines and is more recent than other sources, then it should be used as the default, and to achieve that we should drop best from the other sources. |
Bing in these areas is of similar resolution to these other sources. While the 2021 CAPCOG imagery is newer west of Austin (captured 2019/2021), Bing is newer in all of the other areas covered (captured 2022/2023). I think it's more important to have newer imagery as default in these more urban areas since there's likely more development going on. Edit: fixed areas/dates after further investigation |
If this is supported by the local mapping community and not disputed, then no issues. Though the license URLs appear to be 404ing now, causing the check to fail. |
I've gone ahead and created a thread on the OSMUS Slack. As for the license urls, they seem to be incorrectly returning 404s. Visiting the url still shows the page (ie https://betadata.tnris.org/collection?c=3e1530dc-d5be-4683-811b-9d4b162f0aa9). |
So far there hasn't been any consensus on whether or not this layer should be default. To quote other mappers on that thread: while there are issues with blank tiles appearing at high zooms (since it's a mosaic of three different sources w/ varying resolutions), this layer is better orthorectified compared to Bing. I'm trying to get OSMF to host more up to date imagery from CAPCOG, which should resolve all three of these issues |
So once we get capcog imagery running, we're ok to drop this? |
Test CAPCOG cloud-optimised geotiff at https://grant.dev.openstreetmap.org/capcog-2022-nc-cir-12in/tiles/mosaic.json sent to a few editor developers |
Bing in these areas are more recent than these sources. I also changed the category of these sources to 'historicphoto'