algorithmic modeling for Rhino
Hello,
I'm having a trouble when using the Geo to XYZ component.
I use it with the Elk plugin to generate the topography from STRM data, no problem with Elk by the way (OSM and STRM works great).
But when I try to map a location from WGS84 coordinate, so with the Geo to XYZ connected to the PtGeo(s) generated from the Loc component and the P1(2)Geo from the STRMTopo component, I have an error of positioning. The point created by the Geo to XYZ is shifted (about 250-500m away from the right position).
See on the screenshots for explanation. The point created by Geo to XYZ is the green highlighted one and the good one is the point defined on Rhino.
Thanks for your help!
Mat'
Tags:
Have you considered checking how the OSM data is mapped to XYZ?
I don't really see what you mean.
How can I check that ?
No idea. If you are not controlling the mapping of the OSM nodes to XYZ with references, then how do you know if something is correctly mapped? You would need to provide the data you are working with, but from what I can tell, the OSM data and the SRTM data is just placed in GH / Rhino without you ever setting an insertion point or a reference point. gHowl always asks you to set a reference point in XYZ and Coordinates. This way the user controls where things are mapped to.
What issue? Elk never asks you WHERE in the document you want to map the information. gHowl explicitly asks you this. You need to map the Elk data with a known reference.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by