Is JS 4.3 ready for visualizing a FeatureLayer (FeatureService) in 3D with attribute's values as absolute height?
This option still isn't supported. You could write a function that uses the FeatureLayer.applyEdits() method to add Z values to the geometry object based on the attribute field value.
Thank you for the quick reaction.Yes indeed, I use point geometries (trajectories) and like to visualize them as space-time cubes in the web (https://omleth.ch) to evaluate the results. Below an ArcScene VIZ. Do you know the road map of this very important 3D feature, Height based on feature attribute?
Source: Map-based Visual Analytics of Moving Learners
The roadmap is never set in stone as requirements or any number of issues can arise, postponing the planned release of a feature. But the plan is to have this in by the end of the year. Again, it's not set in stone, just a projection. It's an issue that's definitely been on our radar for a while and we've finally made plans to include it.
I'm not entirely sure of your requirements, but my guess is that there's no reason you can't do this currently if you're willing to dig into the API a little.
If you have a list of graphics/features (with point geometries) and want to use an attribute on each feature as its z value, you could simply write a function to edit the geometries on each feature based on some attribute. Ideally you would set this up in your feature service beforehand (that is, make your feature service serve up features with z values set beforehand), but there's no reason you can't do it in the browser.
In that example I used the index of each feature in the array as its z value, but you could access some attribute on the graphic for that purpose instead. This is also using a 2D symbol, but you could use a 3D symbol.
That example is exactly what I need, thank you!
You can replace the attribute idx with Crown_Height to make the sample reasonable... ;-)
Great thank you!
Still me sorry. You have several Integer attributes in used fs https://services.arcgis.com/V6ZHFr6zdgNZuVG0/arcgis/rest/services/Landscape_Trees/FeatureServer/0 of the above sample. When I replace the idx attribute with p.e. "Crown_Base", the features are still visualized by the OBJECTID.
What are the changes to vis. the 3d map by Crown_Base ?
Can you use also the system-Attribute "Created_Date" in decimal numbers?
And what about polygon features?
For a polygons and polylines, you'll have to transform every point in every ring/path by adding a z value or changing the current z value to whatever you like.
I don't see a Created_Date attribute, but I assume that should be fetched if outFields = ['*']. In terms of transforming a timestamp into a height, or somethign that could be used as a height, I think you could do this by scaling your total set of timestamps from 0 to X ms where X is the difference between the smallest timestamp and the largest timestamp and 0 is the smallest timestamp. Of course you could use seconds, minutes, etc instead of ms.
Retrieving data ...