Yet another site breaking my back button. No, I DON'T want to have another fucking back button entry every time I zoom in, zoom out or slide the map.
Planet Explorer Beta
41–50 of 59 posts
Re: Planet Explorer Beta
#42The ToS that you're presented with upon signing up is pretty absurd. It requires you to commit to providing feedback "on a regular basis of not less than once each week during the Beta term", and to creating "a written evaluation of the functionality, performance, usability, and stability of the Beta Site and documentation provided." It also prohibits you from linking to the site or disclosing any information about i…
How dare they!
Seriously though, I'm an indie iOS developer with a semi-popular app. I have hundreds of TestFlight users, but I only get feedback on betas from a handful.
This can be frustrating, considering the whole point is to get things right for many edge cases before it leaves beta.
Re: Planet Explorer Beta
#43Does anyone know what are the current alternatives to this? Aggregating various government satellite photos?
Re: Planet Explorer Beta
#44The ToS that you're presented with upon signing up is pretty absurd. It requires you to commit to providing feedback "on a regular basis of not less than once each week during the Beta term", and to creating "a written evaluation of the functionality, performance, usability, and stability of the Beta Site and documentation provided." It also prohibits you from linking to the site or disclosing any information about i…
How dare they! Seriously though, I'm an indie iOS developer with a semi-popular app. I have hundreds of TestFlight users, but I only get feedback on betas from a handful. This can be frustrating, considering the whole point is to get things right for many edge cases before it leaves beta.
Sounds like you need a better test->feedback->fix feedback loop. Only include people in your beta who will give you actionable material.. most consumers miss the point of a beta and think it just means 'early access to latest features'.
Re: Planet Explorer Beta
#45Why don't I see snow in Boston during the winter months of 2016 and 2017?
EDIT: With access to the daily views via a free account one can indeed see winter days in which it's all covered in white :)
Re: Planet Explorer Beta
#46Too bad the resolution outside the US is quite low and the data is closed. If anyone is interested in a similar web app but without country-based limitations, you can take a look at Sentinel Playground at: http://apps.sentinel-hub.com/sentinel-playground/ The best part? All Sentinel data is open to anyone, courtesy of the European Comission. Available at https://scihub.esa.int/ or, for those invested in AWS, directly here at Amazon S3: http://sentinel-pds.s3-website.eu-central-1.amazonaws.com/
Re: Planet Explorer Beta
#47Earlier quoted context omitted.
How dare they! Seriously though, I'm an indie iOS developer with a semi-popular app. I have hundreds of TestFlight users, but I only get feedback on betas from a handful. This can be frustrating, considering the whole point is to get things right for many edge cases before it leaves beta.
Sounds like you need a better test->feedback->fix feedback loop. Only include people in your beta who will give you actionable material.. most consumers miss the point of a beta and think it just means 'early access to latest features'.
Completely agree. At the same time though even if it's a 5% rate of feedback, that's still valuable, I just wish it was higher.
(Hence my defense of Planet having TOS requiring feedback for their beta).
Re: Planet Explorer Beta
#48" 2016 PLANET LABS INC. ALL RIGHTS RESERVED." It's 2017, update your website footer! http://updateyourfooter.com/
You're probably getting down-voted because (aside from the off-topic comment) that isn't how copyright works. In most cases copyright starts from the time the work is created, and lasts for a specific period of time (Disney-style exceptions notwithstanding), whether copyright is explicitly declared or not. The copyright notice only serves (informally) to indicate the start-point for this time.
I think the idea is addressing these people (like me) that were used to seeing those "Last edited on XX-XX-XXXX" notices at the footer of HTML pages and worry that the project may be dead/outdated if the date is old.
Now that I think about it, is this why people puts "Copyright $initial_year - $current_year"? Because as you rightly say, only $initial_year is legally relevant.
Re: Planet Explorer Beta
#49Earlier quoted context omitted.
How dare they! Seriously though, I'm an indie iOS developer with a semi-popular app. I have hundreds of TestFlight users, but I only get feedback on betas from a handful. This can be frustrating, considering the whole point is to get things right for many edge cases before it leaves beta.
Sounds like you need a better test->feedback->fix feedback loop. Only include people in your beta who will give you actionable material.. most consumers miss the point of a beta and think it just means 'early access to latest features'.
If your only reward for beta-testing is "early access to latest features" (i.e. no rewards afterwards) most people will assume the only point is indeed "early access to latest features".
Many companies do this to test the robustness of their system by letting people in in controlled beta-invites waves instead of going 0 to 60 in a stampede inauguration. The tight loop you're referring to seems to me more typical of QA/QC testing, which is a paying job. Trying to pass this job into customers is tricky, since most of them are not interested in following tight reporting schedules or writing lengthy standardized reports.
Re: Planet Explorer Beta
#50Earlier quoted context omitted.
You're probably getting down-voted because (aside from the off-topic comment) that isn't how copyright works. In most cases copyright starts from the time the work is created, and lasts for a specific period of time (Disney-style exceptions notwithstanding), whether copyright is explicitly declared or not. The copyright notice only serves (informally) to indicate the start-point for this time.
I think the idea is addressing these people (like me) that were used to seeing those "Last edited on XX-XX-XXXX" notices at the footer of HTML pages and worry that the project may be dead/outdated if the date is old. Now that I think about it, is this why people puts "Copyright $initial_year - $current_year"? Because as you rightly say, only $initial_year is legally relevant.
> Now that I think about it, is this why people puts "Copyright $initial_year - $current_year"? Because as you rightly say, only $initial_year is legally relevant.
Both are, actually, and $current_year may be the most relevant. That formulation generally indicates that the current work was created in $current_year, but is a derivative (possibly through a chain of intermediaries) of a work created in $initial_year.
Derivatives are independent works with their own copyrights, and copyrights of works where the author for copyright purposes is a corporation rather than a natural purpose last a fixed time from the creation of the work in the US, currently, IIRC, 95 years.
So something that says (assuming accuracy of the notice) Copyright 2001-2017, with a corporate author, will be out of copyright (barring further extensions) in 2102, but is ultimately based on an earlier version that will be out of copyright in 2096.
Of course, a lot of websites use automatically updating and false dates for copyright notices, and anyhow the usual current advice is not to include a date at all.