I think geospatial is for all intents and purposes a synonym of GIS and thus any case for blacklisting the gis tag should apply equally to geospatial.
gis was blacklisted long ago so I think blacklisting of geospatial is long overdue.
I believe that QGIS 3.0 and QGIS 3.2 are essentially the same series. QGIS 3.4 comes out 26/10/2018 and also belongs in the same series.
Additionally, a lot of plugins and features are being ported to the new versions. I believe our energy would be best used to try and optimise the latest release.
I believe only 2 tags are needed going forwards: qgis-2 and ...
I do not think you need to remove questions or answers. If you see LOTE used then the best thing to help people who ask or answer the question is to make it understandable for everyone.
In short, if you know what they mean and what language they are using, you can translate it for community so that everybody becomes happy.
Only disagreement here is about the deprecated versions. If a question has been unanswered for months with no activity from the original poster then it should be closed regardless of what tags they used or what version of software (if applicable) they used. It doesn't make much sense to go digging up old questions unless the goal is just to close them so ...
In my experience most people using the arcpy site package would be more than happy to learn about potentially more efficient or cleaner approaches using open source python tools. I always keep in the back of my mind the idea that we are building a repository of Q & A's for future users, so I agree with @PolyGeo in that we need to make sure the Q&A's ...
Having looked at the questions tagged latitude & longitude, I whole heartedly agree that the current usage of these tags on most of these questions (there are 89 question currently tagged with both) is unhelpful, and the tags should be removed from these questions. In most questions, these tags could be replaced by the new lat-long tag.
However, I ...
I think the python tag and other language related tags are not superfluous and should be used whenever the question is related to that language for two reasons:
Syntax highlighting uses tags on the question to infer the language you are using (so no need to use manual override hint);
Question filtering - I use the python tag to make sure I see as many ...
I think you should create a borehole tag.
Tags have the flexibility that they can be used for myriad purposes. This is one that I would call a topic tag or maybe an industry tag.
One type of tag which is used extensively on the Genealogy & Family History Stack Exchange, but I have not yet seen used here much is a geographic tag. Using my own country ...
I think we should insist that question askers try to use English, and encourage the community to help improve/clarify/translate it, if possible, and otherwise close it as "Needs details or clarity". If the entire question is in a non-English language, I would say just close it. There has to be some effort on the question asker's part to make their ...
Firstly, congratulations! It was quite a job organizing the 'arcgis' tag.
I believe we should definitely blacklist it.
Users will use the correct tag from now on (when typing 'arcgis', they will see the alternative tags and be able to make the correct choice, as mentioned by Sideshow Bob).
There will be less tag-editings bumping posts to the active page, ...
I would argue that pyqgis-3 should not be a synonym of pyqgis because with QGIS 3, pyqgis uses python3 and Qt5 (as compared to Python2 and Qt4).
The difference is significant, and there are many breaking API changes so that answers to the two tags may not be compatible. If only one tag is used, there will be confusion.
In a similar situation for openlayers,...
Thanks Curlew! I think now is exactly the right time to talk about this. From my point of view, I think qgis-processing would be a better choice than processing-toolbox since the toolbox is only one feature of the whole processing (mhm, "framework"?). I'd suggest to start correcting tags for all new questions and the old ones which already concern QGIS 2.0 ...
I propose that when an ArcGIS version is Retired that we should review all Unanswered Questions with that tag i.e. Unanswered 9.2 now to try and encourage their posters to retest and see whether their current version still has the problem.
I'm with @blah238 on this one. If the question is abandoned, we should not dig it up simply because there is a new ...
Yes questions about the Leaflet plugin should probably use the tag vector-tiles. I have modified the tag excerpt for vector-grid to also say:
For questions about the Leaflet Plugin please use the tag "vector-tiles"
Would like to keep the tag workflow
workflow to our commercial company is "a sequence of connected steps" - in my work, scope and process are used. In FME Workbench the parallel sequences are known as streams. workflow seems to be a generic request of steps or sequences.
Flow (flowchart) is common to workflow:
I think this answer by Jeff Atwood supports your case very clearly. I say go for it.
which way will users search for this term on the broader Internet?
The most important factor by far. For example, I'm about to rename a
bunch of tags on Server Fault which are in the form
I do not believe anyone types "windowsserver2008" ...
I don't see any advantage of having the qgis-2.0 tag. There are three QGIS releases per year and that means three new tags per year:
I suggest we simplify and only keep the qgis tag.
Yes, I think spatial-interpolation should be made a synonym of interpolation.
Clearly, spatial interpolation is a subset of interpolation, but in the context of a site about GIS, there is little value in trying to tease the two apart.
The interpolation tag is already used as a de facto master synonym, so let's just make it official.
I think it's justified. If we compare to the arcgis and qgis tags, we have arcgis-10.0 and arcgis-10.1 etc, and qgis,qgis-2.0, qgis-2.2 etc. So the same rule should be applied to landsat and landsat-8 etc. If the user uses redundant tags it should be edited, otherwise, I think the differences between the different satellites do require a unique tag for each.
Just keep data and make all others a synonym to it.
I suspect that many of these tags beyond 'data' were created in response to the frequent comment on such questions, "free or paid?". While not necessarily a bad question or bit of info to include when asking, it shouldn't be tag worthy or required info to provide when asking. People usually search for the ...
I think this tag is as redundant as the code tag.
Clearly, the language that the person is trying to program in should indicate that it's a programming problem; and they should tag with that language.
I vote to burninate.
Syntax highlighting for tags can be specified by
Navigating to the tags page
Searching for a tag, hovering over it with the mouse to raise a pop-up, and selecting "info".
Choosing an appropriate code (such as "lang-py") from the "Code Language" prompt.
Only moderators can make such changes, so I have just made them for all the "py"-related tags that are ...