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 ...
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 ...
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 ...
In my opinion GIS SE should be (or better "is") a platform for all GIS related questions, not depending on which GIS related product or what the community background of a question is. It also does not matter whether the product is open source or commercial. The only thing one should state at this point: GIS SE will never be an official support ...
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"
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.
When introducing users of your tool to the GIS Stack Exchange read carefully the section of its Help Center titled Can I support my product on this site? which starts:
We get a lot of requests from product teams about how they can use
Geographic Information Systems Stack Exchange to support their
communities. Geographic Information Systems Stack Exchange ...
I am revising my Answer after reading that of @Conor.
I now favour voronoi-thiessen on the grounds that a Google search on either "voronoi" or "thiessen" would find all our Q&As on either.
I think voronoi-thiessen should be the master of:
thiessen - 11 questions
voronoi - 22 questions
I think the creation of voronoi-thiessen-polygons or thiessen-...
I think burnination is overkill for a tag that is so rarely used, but I certainly think that it should be removed from about half of its current questions because they already mention a product from the web tier.
I just added a tag excerpt and wiki for web-gis which hopefully will explain why I think it remains an occasionally useful tag:
Technically they are distinct. GNSS could refer to any system of which there are currently three operational and two under development. GPS is the specific system run by the United States, while GLONASS is a different GNSS run by Russia.
However, in practical use on this site, and the 14 GNSS questions in particular, GPS is used generically (kind of like ...
I think it is a useful tag even though it is not often used.
Part of the case I see for it is mentioned in my answer to Asking good Questions for GIS Stack Exchange? where I say:
Start by mentioning the GIS software and version that you are using, or explain that you are asking about a GIS principle or
algorithm instead. This saves potential answerers ...
I agree with @Fezter's answer. It looks like many cartography-tagged posts are indeed related to cartography, especially design aesthetics and how to visualize maps in traditional but also revolutionary ways.
This is Britannica's definition:
The art and science of graphically representing a geographical area, usually on a flat surface such as a map or ...
I think that we should simply burninate the python-crash tag by removing it from those two questions.
Instead I would encourage Python users to read the error messages that they receive, so that they may better respond to them, and use Python error tags like syntaxerror, attributeerror, nameerror, etc.
I recommend against using the error tag on the ...
I assumed that geofencing had a common meaning throughout GIS products, open source and commercial, and had no idea that:
GeoFence is an advanced authentication/authorization engine for GeoServer
To avoid ambiguity I think we should coin a geoserver-geofence tag for those questions that are about this form of GeoServer authentication rather than ...
As per my answers on the code tag and the programming tag, I feel that both scripting and automation are redundant.
Any question relating to scripting should have the scripting language tag associated with it.
I vote to burninate both of them.