Interpolation light profile and inverted coordinates
See original GitHub issueThe 'INTERPOL'
light profile does not accept coordinates arrays, like it is the case of the 'INTERPOL'
mass profile. I think it instead considers that coordinates are positive going right for x and up for y.
This leads to the interpolated surface brightness map being incorrectly oriented when the coordinates were obtained through inverse=True
(in utility functions), i.e. East is on the left instead of right.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Cross Section Interpolation - Hydrologic Engineering Center
This method simply draws straight lines between the two cross sections and interpolates the cross section coordinates based on main channel distance. The...
Read more >(PDF) Exact and Efficient Interpolation using Finite Elements ...
Abstract and Figures ; inverse mapping). The reference coordinates are used to compute the element's shape-function coefficients. which perform ...
Read more >Image Interpolation - an overview | ScienceDirect Topics
Image interpolation tries to attain a best estimation of a pixel's intensity based on neighboring pixel values on proximity basis.
Read more >Interpolate drawn line in Leaflet - GIS Stack Exchange
toGeoJSON(); var profile = drawData.geometry.coordinates; //reverse coordinates function reverseCoordinates(_arr){ let i; ...
Read more >How inverse distance weighted interpolation works—ArcGIS Pro
Deterministic methods for spatial interpolation · GPI (global polynomial interpolation) · LPI (local polynomial interpolation) · IDW (inverse distance weighted).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I agree this would make sense to support same arguments that coordinates-related classes. I’m not sure to come to a full implementation very soon, but I put it on my TODO list 👍
The grid_interp_x and grid_interp_y in the lens model module is also not optimal as it requires rectangular orientation. I’d prefer not having a mix of interpolation schemes defining a coordinate system with schemes defining an axis. The coordinate scheme is much more general and I hopefully can replace the lens model part with such a scheme too. So if you implement an new profile, I would prefer it to be one with inputs consistent with the PixelGrid(). It’s a bit more work but can ensure consistency. Then the difference to what I coded up would be: