15

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 ...


13

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.


13

You have asked a lot of questions in your question: So, why not listen to their opinions? We would be silly not to. We have no issue with users giving their opinions as part of their answers to focussed objective questions. It is when opinions are asked for that I vote to place questions on hold, because that makes the question open-ended. Wouldn't ...


12

As long as it's sufficiently clear what (single) question is being asked(and that's obvously the case when you've marked it up to appear in bold) and the other questions are indeed there to motivate the main question or to further explain what aspects a useful answer would have to cover, I don't think we should enforce an only-one-question-mark rule. On ...


11

Voting to close as "too localized" is non-pejorative and works as a splendid catch-all for such situations.


11

That question exhibits a host of basic problems. The critical ones are: The error message is not reproduced, making the problem difficult to ascertain. A large block of code is posted, unedited (and badly formatted). No evidence of any effort to solve the problem or even isolate it is provided. No explanation is given concerning what the code is intended ...


11

I thoroughly agree, and would go even further: when the O.P. has been asked explicitly for clarification and has not provided it within a day (not counting weekends), I think it's fair to close the thread. All rules have exceptions: sometimes a perceptive reader offers a helpful answer in the meantime and it is marked as accepted. That can (and probably ...


10

Thanks for bringing this up--I have also been noticing a higher frequency of flagged field calculator questions. I believe that any question relating to a GIS field calculator is on-topic. The field calculator has its own peculiarities, such as wrapping fields in !FieldName! for ArcGIS. With this said, even the most pure Python concepts become GIS ...


10

I agree, and propose this wording that incorporates suggestions from @whuber: 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. I have not ...


9

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 ...


8

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 ...


8

Excellent question! I wonder if the solution is to look for the earliest Python Parser of the Field Calculator question and extensively edit it to become a Community Wiki Q&A entitled Using the Python Parser of the Field Calculator of ArcGIS for Desktop? that starts something along the lines of: This is a Community Wiki Q&A which is intended to ...


8

You're right; it is preferable to leave a comment explaining why a question is closed. (Some questions don't get comments for various reasons: the mods may be busy or perhaps there are just so many things wrong that no single comment will suffice.) What you, and any other community member (of 50+ reputation), can do to help in such situations is to post ...


8

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 ...


7

I feel that there are multiple issues at hand: Firstly, I don't believe that we should blindly follow everything that is followed at Stackoverflow. The nature of the community at SO & GIS.SE is very different, and so is the subject matter. There are many libraries & applications that do the same thing in General programming and Web development; In ...


7

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 ...


7

I believe moderators do not have the same restrictions--and they can also unilaterally just delete one of the questions if necessary--so one option is to flag the question for moderator attention. Please provide a link to the duplicate when you do so. Leaving a friendly comment pointing to the account merge help page would also be a nice thing to do if you ...


7

There may be plenty of corner cases in which things don't work as expected, or after an upgrade stop working as they previously did. Users may have issues because they don't use the software correctly, or are unaware that the new version of their favorite tool requires changes on their part. Obviously "X in tool Y doesn't work, please fix tool Y" is not a ...


7

Whenever I see a question for which multiple close reasons seem applicable I think it is fine to choose any that you think resonates with that particular question. I was advised early in my time here that closing as a duplicate (if it is) should perhaps take priority, and while I often make that choice, I think it is far from always applicable because, if a ...


7

I sympathise with Joseph's answer; however I have another suggestion: Questions seeking help to debug/write/improve code must include the desired behavior, a specific problem or error and the shortest code (as formatted text, not pictures) necessary to reproduce it in the question itself. Providing a clear problem statement and evidence of a code attempt ...


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.


7

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 ...


6

I missed the lat lon in the question and saw it as just a request of a list of universities when I closed it. In general I'd prefer to discourage all where can I find a list of ...? questions. Since the next step is that any list with a postcode (zip code) can be considered spatial and becomes fair game to ask.


6

For commercial software, most licensing-related problems are a good candidate for this. Even though the community can often help the asker get closer to a solution, these problems often require a call to the vendor to resolve because the vendor is responsible for licensing and they can know things about the asker's licensing status that we can't possibly ...


6

I think that GIS SE should NOT be used as a means to try to submit bug reports and enhancement requests. I think this position has been endorsed in a Meta Q&A on What should we do with bug reports? so it probably just needs to be formalized in the Help. To try and prevent any misunderstanding in what I am saying in this answer, I need to say that I ...


6

Over 800 people have looked at the question so it is probably worth answering as I expect many will have found it via google when looking for a solution to a similar question.


6

Just to add to @iant's answer, I think if you ever see a question that you can answer, please do so. Even if it is several years old. Just because the original poster may have left (in fact, they last visited the site in July 2017, so they will probably be back), doesn't mean other people won't benefit from your answer. As per Improving on 19,500 unanswered ...


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,...


5

I am the person who asked the question. I am sorry for not being more descriptive or for showing the research I have done so far, I have been limited on time recently. I am building a software that draws in lots of data sets and this was one of them that I was having a hard time finding; I figured that this site would be a good place ask for this type of ...


5

The Comment by @AndreSilva best reflects the way I have been handling old Shopping List Questions since asking this Question. For old Shopping List Questions there was often considerable investment by answerers into providing some very comprehensive and valuable Answers, and that should not be lost, so I now flag them to request that the moderators convert ...


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