You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added the FeatureModelLayer to the map, but nothing appeared.
After debugging, I found that:
The data downloads correctly.
The building features load but gets rejected during filtering because their geometry is in WGS84 (EPSG 4326), while the tiling scheme is "global-mercator".
What you have tried:
I tried setting the feature source profile to "global-geodetic" (EPSG 4326), but the data did not load. Further checks showed that the tile keys were incorrect, possibly because the server does not support "global-geodetic" tiling.
Please suggest how can I properly load an XYZ service where the tiling scheme is "global-mercator", but the feature geometry is in WGS84 (EPSG 4326)?
Screenshot, code block, or data file that will help reproduce the issue:
I have attached the JSON response got from the server
Oh, there was also a commit 2 months ago that correctly assigned a WGS84 SRS for all GeoJSON data. That might be the issue. You would need to build the master branch to see this fix.
osgEarth Version (required): 3.7.1
Description of the problem:
I am trying to load 3D building data using an XYZ feature tile service.
Here is what I did:
1. URL: https://d-data.3dbuildings.com/tile/{z}/{x}/{y}.json?token=key
2. Format: JSON
3. MinLevel: 15
4. MaxLevel: 20
5. Profile: "global-mercator"
What you have tried:
I tried setting the feature source profile to "global-geodetic" (EPSG 4326), but the data did not load. Further checks showed that the tile keys were incorrect, possibly because the server does not support "global-geodetic" tiling.
Please suggest how can I properly load an XYZ service where the tiling scheme is "global-mercator", but the feature geometry is in WGS84 (EPSG 4326)?
Screenshot, code block, or data file that will help reproduce the issue:
I have attached the JSON response got from the server
3D Building response.json
The text was updated successfully, but these errors were encountered: