7

Looking at the question, I agree it is not too broad, so I reopened it. I then reclosed it as unreproducible since I doubt anyone is still using version 2.2.


6

The comments you made on your question were not ignored by me (and presumably not by any of our eight elected moderators) because I had not seen them until I followed the link in your question here just now. You could have brought them to my attention by placing "@PolyGeo" anywhere in any of those comments. That comment would then have appeared in my inbox,...


6

Questions that relate to the business of vendors and product teams, such as licensing, pricing, release dates, submission of bug reports and enhancement requests, etc, are off-topic here and should be directed instead to the official software support teams. You have said this is a bug and that you are a maintainer of the project, and have directed the ...


4

In retrospect I made a mistake in voting to close this question of yours, for which I apologize. As @inc42 pointed out in a comment on my earlier answer to this question, posting a code snippet is not a requirement. I had forgotten about the outcome of Replacing MCVE with Code Snippet in custom close reason? and the two lines of code that you had included ...


2

I think that "needs more focus" is just the new "name" for the "too broad" close reason. I think that there are two main question structures that it should be used on, and these are: "more than one question per question" (should be focused to one question), and "too open-ended"/"too broad" (quick single question by asker seeking potentially large amount ...


2

Perhaps such questions could be closed "as unclear what you are asking" instead. Basically, in many of these questions there is insufficient detail to write an answer, but Google Earth Engine is not my area of expertise so maybe they are answerable without any sign of effort by the asker.


2

It was closed as Off Topic because: When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you. If you feel it was closed ...


1

That question starts: Thinking through something that I seek some SQL on: so the question is seeking SQL code. When I voted to close the question did not include anything like a code snippet that illustrated what they had tried and where they were stuck. We are a little different from other sites. We are a Q&A site, not a discussion forum. For ...


1

The vote to close on that question came from a moderator other than I, but I agree with it. The reason is your answer there: I'm one of the maintainers for the solaris project. I tried to reproduce your error in my environment but could not. If you open an issue in the solaris github repo with the full traceback, and your python/solaris/pyproj/...


1

If a question makes it quite clear that they do not wish to receive code in answers, then I would agree that closing as "needs a code attempt" would be inapplicable. In this particular question, reviewed alongside its comments that sought various clarifications (and elicited no edits by the asker) it looks like the asker may be asking for coding assistance ...


Only top voted, non community-wiki answers of a minimum length are eligible