-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle identification of GeoJSON feature without the help of OpenLayers
this way we can re-use the same logic for Cesium (and will then be able to use the mouse-click Composable when we rewrite the CesiumMap component into Composition API)
- Loading branch information
Showing
9 changed files
with
182 additions
and
63 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,108 @@ | ||
| import { LayerFeature } from '@/api/features.api' | ||
| import { WGS84 } from '@/utils/coordinates/coordinateSystems' | ||
| import reprojectGeoJsonData from '@/utils/geoJsonUtils' | ||
| import log from '@/utils/logging' | ||
| import distance from '@turf/distance' | ||
| import { point } from '@turf/helpers' | ||
| import proj4 from 'proj4' | ||
|
|
||
| const pixelToleranceForIdentify = 10 | ||
|
|
||
| /** | ||
| * Finds and returns all features, from the given GeoJSON layer, that are under or close to the | ||
| * given coordinate (we require the map resolution as input, so that we may calculate a 10-pixels | ||
| * tolerance for feature identification) | ||
| * | ||
| * This means we do not require OpenLayers to perform this search anymore, and that this code can be | ||
| * used in any mapping framework. | ||
| * | ||
| * @param {GeoAdminGeoJsonLayer} geoJsonLayer The GeoJSON layer in which we want to find feature at | ||
| * the given coordinate. This layer must have its geoJsonData loaded in order for this | ||
| * identification of feature to work properly (this function will not load the data if it is | ||
| * missing) | ||
| * @param {[Number, Number]} coordinate Where we want to find features ([x, y]) | ||
| * @param {CoordinateSystem} projection The projection used to describe the coordinate where we want | ||
| * to search for feature | ||
| * @param {Number} resolution The current map resolution, in meters/pixel. Used to calculate a | ||
| * tolerance of 10 pixels around the given coordinate. | ||
| * @returns {SelectableFeature[]} The feature found at the coordinate, or an empty array if none | ||
| * were found | ||
| */ | ||
| export function identifyGeoJSONFeatureAt(geoJsonLayer, coordinate, projection, resolution) { | ||
| const features = [] | ||
| // if there is a GeoJSON layer currently visible, we will find it and search for features under the mouse cursor | ||
| const coordinateWGS84 = point(proj4(projection.epsg, WGS84.epsg, coordinate)) | ||
| // to use turf functions, we need to have lat/lon (WGS84) coordinates | ||
| const reprojectedGeoJSON = reprojectGeoJsonData(geoJsonLayer.geoJsonData, WGS84, projection) | ||
| if (!reprojectedGeoJSON) { | ||
| log.error( | ||
| `Unable to reproject GeoJSON data in order to find features at coordinates`, | ||
| geoJsonLayer.getID(), | ||
| coordinate | ||
| ) | ||
| return [] | ||
| } | ||
| const matchingFeatures = reprojectedGeoJSON.features | ||
| .filter((feature) => { | ||
| const distanceWithClick = distance( | ||
| coordinateWGS84, | ||
| point(feature.geometry.coordinates), | ||
| { | ||
| units: 'meters', | ||
| } | ||
| ) | ||
| return distanceWithClick <= pixelToleranceForIdentify * resolution | ||
| }) | ||
| .map((feature) => { | ||
| // back to the starting projection | ||
| feature.geometry.coordinates = proj4( | ||
| WGS84.epsg, | ||
| projection.epsg, | ||
| feature.geometry.coordinates | ||
| ) | ||
| return new LayerFeature( | ||
| geoJsonLayer, | ||
| feature.id, | ||
| feature.properties.station_name || feature.id, | ||
| `<div class="htmlpopup-container"> | ||
| <div class="htmlpopup-header"> | ||
| <span>${geoJsonLayer.name}</span> | ||
| </div> | ||
| <div class="htmlpopup-content"> | ||
| ${feature.properties.description} | ||
| </div> | ||
| </div>`, | ||
| proj4(WGS84.epsg, projection.epsg, feature.geometry.coordinates), | ||
| null, | ||
| feature.geometry | ||
| ) | ||
| }) | ||
| if (matchingFeatures?.length > 0) { | ||
| features.push(...matchingFeatures) | ||
| } | ||
| return features | ||
| } | ||
|
|
||
| /** | ||
| * Finds and returns all features, from the given KML layer, that are under or close to the given | ||
| * coordinate (we require the map resolution as input, so that we may calculate a 10-pixels | ||
| * tolerance for feature identification) | ||
| * | ||
| * This means we do not require OpenLayers to perform this search anymore, and that this code can be | ||
| * used in any mapping framework. | ||
| * | ||
| * @param {KMLLayer} _kmlLayer The KML layer in which we want to find feature at the given | ||
| * coordinate. This layer must have its kmlData loaded in order for this identification of feature | ||
| * to work properly (this function will not load the data if it is missing) | ||
| * @param {[Number, Number]} _coordinate Where we want to find features ([x, y]) | ||
| * @param {CoordinateSystem} _projection The projection used to describe the coordinate where we | ||
| * want to search for feature | ||
| * @param {Number} _resolution The current map resolution, in meters/pixel. Used to calculate a | ||
| * tolerance of 10 pixels around the given coordinate. | ||
| * @returns {SelectableFeature[]} The feature found at the coordinate, or an empty array if none | ||
| * were found | ||
| */ | ||
| export function identifyKMLFeatureAt(_kmlLayer, _coordinate, _projection, _resolution) { | ||
| // TODO : implement KML layer feature identification | ||
| return [] | ||
| } |
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