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 would opt for sticking with python-3 because, as @MrXsquared has commented, there is a space between "Python" and "3" at the Python 3.0 Release home page.
Id say one tag for google-earth and google-earth-pro is enough because they are very similar and as you have already mentioned google-earth-pro is now free as well, so there shouldn't be many users left using the "normal" version.
But in my opinion there should be an extra tag for the "new" google earth (web/mobile) version as they are different from the ...
If we are looking at some Oracle tags then I think it may be worth looking at them in context with all our Oracle tags.
If you use [*oracle*] in the search bar it expands to [oracle] or [oracle-spatial] or [oracle-11g] or [oracle-10g] or [oracle-12c] or [cx-oracle] or [oracle-map-builder]
In total there are 627 questions with an Oracle tag on them. The ...
Following the line of the synonymization between projection and coordinate-system, I would agree to synonymize projection-mathematics and reprojection-mathematics to coordinate-system as well.
Mainly because I think they should be synonymous with projection.
The terms are not synonymous. However, I don't think synonymous tags should necessarily refer ...
There were only two questions tagged portal:
Refining Features from Portal Webmap
Active Directory Permissions for ArcGIS Enterprise
I think both clearly related to ArcGIS for Portal, and so I am re-tagging them to be arcgis-portal.
That means the portal tag (which has no tag wiki) will disappear within 24 hours, but can be re-created later if a case for ...
I think that warning is being triggered to avoid having many tags present in both singular and plural forms, even though the "s" on the end is not for that purpose, in this instance.
I thought that we would need SE staff/developers to implement it, as an exception, and that it would be better to just use the existing ssl tag along with http, when ...
I propose simplifying the Google Earth (GE) tags into just one - google-earth - and have any/all others as synonyms of that tag (excluding the engine and api tags).
Most of the questions relate to GE or GE-Pro (basically the same product); I don't really see any need to have additional tags for GE mobile or browser which may only attract a handful of ...
Agree completely with making tags projection-mathematics and reprojection-mathematics synonyms with a view to eventual merging. The two terms are identical.
While I further agree the subject of these two tags is indeed a sub-class of the wider 'Coordinate-System' tag, I disagree with any further synonymization.
There is a significant quantity (>5,500) ...
I do not think that we need the customization tag and propose that we cease using it, and slowly burninate it.
We now have a customize-mode tag, for the GUI driven Customize Mode of ArcGIS Desktop applications.
At the time this question was asked, nearly 6 years ago, I was an advocate for version tags. However, since that time I have come to view them as having little value.
I think that as long as any version(s) being asked about, and hopefully tested and reported on, is/are mentioned in the body of a question, then I think it/they are best left out of the tags.
I see some value in adding geotags at the higher levels like country, continent and planet but not at anything below country because it would mean that there are far too many of them.
By having questions tagged using a country, continent or planet name it enables GIS professionals familiar with that country, continent or planet to include them in their ...
At one time I was an advocate for version tags but over the years my view on them has changed to being that they are of limited use.
Nowadays, as long as the version(s) being asked about (and presumably used) is/are mentioned in the body of the question, then I think they are best not tagged.
Likewise, if answers cover a range of versions and are suspected ...
As an initial simple disambiguation I propose making two new tags (which may or may not persist):
nearest-neighbor-raster for the nearest neighbor resampling method used in raster processing
nearest-neighbor-vector for proximity operations in vector processing
We can then work towards how existing "nearest neighbor" questions can be allocated to raster and ...
Here at GIS SE, I think our python-* requirements are, and are likely to remain, more modest than at Stack Overflow.
Once we know that a Python spatial library is being used, then the key remaining thing to know is whether Python 3.x or Python 2.x is involved, because the former is not backwardly compatible to the latter.
Despite python-2.7 and pytho-2.6 ...