Remove vector tile feature flag #76068
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iverase
added
>feature
release highlight
:Analytics/Geo
elasticmachine
added
the
Team:Analytics
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
imotov
reviewed
Aug 5, 2021
There was a problem hiding this comment.
Could you also remove it from
elasticsearch/x-pack/plugin/vector-tile/build.gradle
Lines 44 to 53 in e93db2a
|
ouch, I missed that. I removed it. |
imotov
pushed a commit
to imotov/elasticsearch
that referenced
this pull request
Aug 5, 2021
Vector tile development is completed and this feature is ready to be released on 7.15. It is initially release as an experimental feature.
In particular this new feature introduces a new endpoint for generating vector tiles from geospatial data stored in Elasticsearch. This is a functionality that is interesting for any application that wants to render geospatial information stored in Elasticsearch on a map. The basic way to call this new end point looks like:
```
GET {index}/_mvt/{geo_field}/{z}/{x}/{y}
```
The return of this call is a vector tile as defined in the [MapBox vector tile specification](https://github.com/mapbox/vector-tile-spec/tree/master/2.1) so it can be easily render by any map supporting this format.
imotov
added a commit
that referenced
this pull request
Aug 5, 2021
Vector tile development is completed and this feature is ready to be released on 7.15. It is initially release as an experimental feature.
In particular this new feature introduces a new endpoint for generating vector tiles from geospatial data stored in Elasticsearch. This is a functionality that is interesting for any application that wants to render geospatial information stored in Elasticsearch on a map. The basic way to call this new end point looks like:
```
GET {index}/_mvt/{geo_field}/{z}/{x}/{y}
```
The return of this call is a vector tile as defined in the [MapBox vector tile specification](https://github.com/mapbox/vector-tile-spec/tree/master/2.1) so it can be easily render by any map supporting this format.
Co-authored-by: Ignacio Vera <iverase@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vector tile development is completed and this feature is ready to be released on 7.15. It is initially release as an experimental feature.
In particular this new feature introduces a new endpoint for generating vector tiles from geospatial data stored in Elasticsearch. This is a functionality that is interesting for any application that wants to render geospatial information stored in Elasticsearch on a map. The basic way to call this new end point looks like:
The return of this call is a vector tile as defined in the MapBox vector tile specification so it can be easily render by any map supporting this format.