Giter Club home page Giter Club logo

Comments (11)

yumorishita avatar yumorishita commented on June 24, 2024
  1. You must create the data GeoTIFF by LiCSBAS_flt2geotiff.py, not image tiff by LiCSBAS_plot_ts.py, as the input for LiCSBAS_disp_img.py.
  2. Generally we project GNSS 3D displacement into LOS and compare it with InSAR LOS displacement. You must set the same reference for both GNSS and InSAR because both are relative displacements.
  3. What do you mean by "the output image"?

from licsbas.

blueyeti1994 avatar blueyeti1994 commented on June 24, 2024

Thank you for your kind reply. I will look and go through solutions you suggested. For 'GNSS 3D displacement' and 'set up reference for both GNSS and InSAR ' can you guide me through any resource online ? I am familiar with NS, UD and EW displacement so far from GNSS but 'GNSS 3D displacement ' is new term for me.

For third question, 'the output image' reference is the displacement plot from LiCSBAS output below' (left) is original output and my expected output (right). The arrow of LOS and flight direction is assumed one. where can i find that information to draw the vectors?
adf

and thank you so much for creating LiCSBAS.

from licsbas.

yumorishita avatar yumorishita commented on June 24, 2024

GNSS 3D displacement means the NS, UD and EW displacement.
LiCSBAS has no function to plot such an arrow.

from licsbas.

blueyeti1994 avatar blueyeti1994 commented on June 24, 2024

Thank you for your kind reply. For arrow, this is the assumed one, I wanted to know where can i find information on flight direction or LOS direction so that i could use this information to make such arrows over my images later ?
using metainfo i found that avg incidence angle is 33.7854 and azimuth_resolution=13.947950. Thus using this values, I applied following formula to decompose GNSS Up, NS and EW in LOS using formula

LOS = D(NS)sin(θ) sin(α)-+ D(EW) sin(θ) cos(α) + D(UD) cos(θ)

My GNSS is based on IGS14 reference frame and location of GNSS station is lat, lon: 40.87617, 14.05044. i used the following formula to get the time series plot of same exact location

LiCSBAS_plot_ts.py -i TS_GEOCml1maskclip/cum_filt.h5 --p_geo 14.05044/40.87617 --ts_png lico.png

then i plotted 'Date' vs 'LOS' of GNSS to derive the time series graph. But the velocity from LiCSBAS appears to have negative velocity -6.6mm/yr and my is 5.11 mm/yr. am i going in right direction? is this because of reference frame issue. how to change the LiCSBAS reference frame to use IGS14 or change the reference area of GNSS same as licsbas which is in this case is

Ref area

X 90:91
Y 43:44

and thank you for your suggestion and guidance. it has been very helpful.
hele

from licsbas.

yumorishita avatar yumorishita commented on June 24, 2024

The flight direction can be found in the frame ID (4th character). For example, 124D_04854_171313 is descending.

You should set the common reference for both GNSS and LiCSBAS, e.g., by selecting a GNSS point existing in the LiCSBAS result area.

from licsbas.

blueyeti1994 avatar blueyeti1994 commented on June 24, 2024

Thank you yumorishita for your reply.

how to read N.geo, E.geo or U.geo file ? is there command in LiCSBAS like 'LiCSBAS_cum2tstxt.py'? I tried with notepad but it there are non readable characters in this file.

and lastly as per your suggestion, is following approach is right for having same reference for both GNSS and LiCSBAS ?

  1. Find GPS station in LiCSBAS result area.
  2. Project GNSS 3D displacement into LOS
  3. Using same lat and lon for GPS station, create a time series in LiCSBAS also
  4. Find a offset between GPS and LiCSBAS in LOS displacement using same date and time.
  5. Adjust the entire LiCSBAS time serie from anyother coordinates using same offset.

from licsbas.

yumorishita avatar yumorishita commented on June 24, 2024

You should convert the float file (*.geo) to GeoTIFF using LiCSBAS_flt2geotiff.py.
Your approach makes sense.

from licsbas.

blueyeti1994 avatar blueyeti1994 commented on June 24, 2024

Looking at the documentation for Quick start, GACOS is optioal and turned off by default. So when i select any frame, i see there is percentage written next to GACOS..what does that percentage mean?
Screenshot 2024-05-27 155904

from licsbas.

yumorishita avatar yumorishita commented on June 24, 2024

I am not sure because it is out of LiCSBAS, but I guess it is [GACOS available dates]/[total dates].

from licsbas.

blueyeti1994 avatar blueyeti1994 commented on June 24, 2024

Thank you yumorishita for your reply.

how to read N.geo, E.geo or U.geo file ? is there command in LiCSBAS like 'LiCSBAS_cum2tstxt.py'? I tried with notepad but it there are non readable characters in this file.

and lastly as per your suggestion, is following approach is right for having same reference for both GNSS and LiCSBAS ?

  1. Find GPS station in LiCSBAS result area.
  2. Project GNSS 3D displacement into LOS
  3. Using same lat and lon for GPS station, create a time series in LiCSBAS also
  4. Find a offset between GPS and LiCSBAS in LOS displacement using same date and time.
  5. Adjust the entire LiCSBAS time serie from anyother coordinates using same offset.

A very basic stupid question which is occupying my mind is. I processed the both ascending and descending orbit of same study area. Now when i run the command

LiCSBAS_decomposeLOS.py -f decompose.txt

where decompose.txt contains
asc_vel.geo.tif asc_E.geo.tif asc_N.geo.tif
dsc_vel.geo.tif dsc_E.geo.tif dsc_N.geo.tif

As this will decompose LOS displacement data to EW and UD components, If I have a GPS station nearby and if i set the reference of both GPS and LiCBAS as same area, should the UD compoent form decomposing LOS displacement and vertical displacement should be equal or nearly equal?

qes

In this image is 'Up' component of GPS and du of LicBAS should yield almost same result if reference is same for both ?

If it is true and we can decompose LOS velocity to vertical velocity by using both ascending and descending path from satellite and compare it with nearby GPS staion, is it necessary then to decompose GPS 3D displacement to LOS and compare with LiCBAS becausei think the above method gives good results when compared but i am not sure.

from licsbas.

yumorishita avatar yumorishita commented on June 24, 2024

should the UD compoent form decomposing LOS displacement and vertical displacement should be equal or nearly equal?
In this image is 'Up' component of GPS and du of LicBAS should yield almost same result if reference is same for both ?

Yes, I think so. You can compare in vertical rather than LOS. However, I usually compare in LOS because, when GNSS and LiCSBAS are not consistent in vertical, I can identify which is the cause of the inconsistency, ascending or descending.

from licsbas.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.