Our site does not have a specific homework policy, nor does this appear to have been discussed before. Other sites do have such policies: see the math FAQ on homework for instance.
On yet another site I have moderated hundreds of homework questions. My attitude has changed a little over time because there are unresolved and thorny issues associated with ...
It would be a sad day when we ban questions about product, service and learning material recommendations. I fail to see how these questions are off-topic or bad for the site.
GIS is a vast field, and it is not possible for one person to know everything, or even have an idea about the various possibilities of GIS, and where to learn this.
It helps when you ...
Perhaps changing the site's name (to reflect the encompassing of broader subjects) would be a radical change considering former discussions on this matter are not yet quite mature.
On the other hand, I believe we are mature enough to carry on some changings in our on topic help center page and emphasize the actual scope of questions on GIS SE.
I currently work on the Google Earth Engine team. I'm not primarily involved in developer/user relations, but I've advised those who are on how best to interact nicely with Stack Exchange (and I really like Stack Exchange, so I want this to work out).
If you have any concrete ideas for how to improve our interaction with Stack Exchange, please let me know.
A good question is a good question, even if it is homework.
In my experience most poor questions stem from a "please spoon feed me" vantage, and this starting point often doesn't have anything to do with homework. I know, because some of the poor questions are mine, and I haven't been in school for a long long time. :) Perhaps they just don't have the ...
I think it should be ok to close as "This is a bug report and not a question for GIS.SE".
As the Help says:
We are not a GIS Software Support Site. We encourage you to seek official routes for support for specific issues you may have.
The community seems happy to answer questions about using QGIS, but bug reports are highly specific and often concern ...
You have chances to get answers on both places. However, I believe you could post here as this community is specific for GIS. If we want to see our community growing we should encourage more GIS questions here than SO. Now if your question is something very specific about programming and nothing related to GIS, then ask there.
Update:: this comment from '...
I added my re-open vote to the others that were already on your question so it is now ready for you to self-answer.
I agreed with its original closure as too broad, but I am almost always happy to re-open a question when someone says that they have an answer ready.
I believe such a question is on topic. If you cannot provide details you can expect to get only general answers, most of which are already available on this site. Details would enable interested readers to provide specific suggestions for your particular situation.
I am glad that this has been raised because I too have perceived seeing many more Google Earth Engine questions asked over the past 6-12 months than previously and had wondered what the trigger was.
Focused questions about Google Earth Engine are clearly on-topic for GIS SE, and I think we should be flattered that Google believes that GIS SE (rather than ...
However I don't feel this is actually conducive to a useful GIS.SE. If
you look at the list of Highest Voted Questions you'll see that the
vast majority of them are actual subjective discussion questions with
no "right" answer nor in many cases even a "practical" one.
Most of them are community wikis, too. Not really a good benchmark. They should have ...
Another excellent example of why defining the line for 'pure' Python questions is going to be difficult: Using variable in SelectByAttribute_management.
At the lowest level possible, it is purely a Python syntax issue.
However, the error given would indicate an error outside of Python, within the ArcGIS API:
Runtime error Traceback (most recent call ...
There are a few avenues for help at the moment,
https://opendatacube.slack.com is pretty widely used for simple questions, but as it doesn't have premium support older messages are deleted, making it fairly transient.
https://github.com/opendatacube/datacube-core/issues is good for a specific issue, especially with the Python Library itself, but it isn't ...
Questions of the type you are describing are certainly well categorized as "here is a large script, please debug it for me". Sometimes they are posted by aspiring GIS developers who are yet to acquire much in the way of code troubleshooting skills. At other times they are from people who have grabbed code from somewhere else but lack the skills to ...
Something I think we need to be cautious about is opening the door to "absolutely any question related to Surveying, etc".
Perhaps we can model our answer on the Cross Validated Tour which I have modified here to try and suit our purposes and emphasize that our "core business" is GIS but that we are happy to see questions from other spatial disciplines. ...
I think software installation questions in general are more likely to be on-topic at Stack Overflow or Super User.
However, if you are asking specific questions about the installation of GIS software then I would expect them to be on-topic here at GIS SE.
This appears to be the case with your question on Brewing GRASS with PostgreSQL support?
I would like to drop the last sentence:
Questions that are too basic (meaning the answer is indexed in any
number of general internet reference sources designed specifically to
find that type of information) will be closed.
I like to consider GIS SE as the ultimate repository for questions all along the spectrum from basic to advanced. Why would we ...
I don't think we should close topics that are "shopping list questions". After all, this is a Q and A community, and sometimes it's easier and more valuable to get responses from other users other than relying on Google and biased "reviews".
I think there are some value to these posts, and they provide discussion among users - even if the technology may ...
I am glad this has been raised.
I note that none of the top 10 CartoDB answerers appear to be CartoDB employees - I did not look at the user cards of the rest.
I think we should feel flattered that GIS SE often seems to be the first point of call for help with commercial GIS software.
However, I think this means that we should expect a higher quality of ...
Here is my proposal : adding "surveying" to the list. There are only a few tags with surveying, but IF we consider that surveyors also use GNSS, then it is more popular than remote sensing on GIS.SE.
Geographic Information Systems is a question and answer site for
people interested in GIS, Remote Sensing, Photogrammetry, Geodesy, Surveying,
The GIS Stack Exchange Main site is not designed for discussions.
It is a focussed Question and Answer site.
Such a discussion would be suitable for our GIS Chat Room.
Alternatively, you could think more about the discussion you were planning, and try to distill a focussed question from it. I think that is usually possible, but not always easy, to do.
It depends. A question does not necessarily have to be about one specific software to be considered not broad, as long as it is specific enough in details to avoid five users casting a close vote as 'too broad' (or even 'unclear'). So that is, questions about software can also be closed as 'too broad', or 'unclear'.
Asking about means of accomplishing a ...
I think we should discourage "Where do I find spatial data on ...?" questions. Otherwise I worry that we will see LOTS of them.
I think that when we see such questions, especially if there is no indication of where the asker has tried looking prior to asking the question, then we should consider downvoting, preferably with a comment like:
"Where have ...
We have several years worth of examples where such questions have been asked and answered without being closed as off-topic.
As our site is primarily for professionals within the niche world of GIS, I think recommendations from other professionals are very valuable, and so long as a question passes all the other usual criteria it should be on topic.
Voting to close your own questions is always fine. That leaves it up to the community to judge their value.
However, my advice would be to only delete questions when they really have no value to anyone, and that no one should delete questions when they are new to the site, because that can feed into the algorithms that determine question bans and rate ...
Code reviews on GIS SE have been discussed on this Meta twice previously in:
Code review for a specific piece of code
What to do about "what's wrong with my wall of text?" type questions?
I think allowing questions of the form:
Here is my code (with its purpose well described), can you fix,
streamline and/or speed it up for me?
is the ...
It could be on topic if it avoided two of our current closing reasons:
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.
Many good questions generate some degree ...
My suggestion herein is not what I was originally thinking, but in this sentence:
That will help you write a great, focused question that gets excellent
the word "gets" could be replaced by "attracts" to remind, with subtlety, that askers are seeking volunteered efforts to answer their questions.
This would make that sentence:
That will ...
I would strongly reject any suggestion that request for data in general (as per blah238's updated question) or even free (as in beer) data or Open data specifically (as per martinf's answer) are now off-topic, just because there is a Stack exchange Site for Open data.
My reasons are as follows:
Even though OS.SE has been in beta for 11 months, it's not ...