Skip to content

Fix order of lat/lon in wildfire use case#2

Open
mesham wants to merge 1 commit into
mainfrom
fix-wildfire_workflow_lanlot_order
Open

Fix order of lat/lon in wildfire use case#2
mesham wants to merge 1 commit into
mainfrom
fix-wildfire_workflow_lanlot_order

Conversation

@mesham

@mesham mesham commented Oct 27, 2021

Copy link
Copy Markdown
Contributor

The latitude and longitude coordinates were read in the
wrong order.
The VESTEC interface asks for "lat/lon" which is internally
stored into upperLeft and lowerRight variables.
These were then wrongly split into individual coords by
lon, lat = upperLeft.split("/")

We corrected this to
lat, lon = upperLeft.split("/")

Also, the min/max coordinates for the hotspot points
were in the wrong order
upperLeft gives latmax and lonmin
lowerRight gives latmin and lonmax

The latitude and longitude coordinates were read in the
wrong order.
The VESTEC interface asks for "lat/lon" which is internally
stored into upperLeft and lowerRight variables.
These were then wrongly split into individual coords by
lon, lat = upperLeft.split("/")

We corrected this to
lat, lon = upperLeft.split("/")

Also, the min/max coordinates for the hotspot points
were in the wrong order
upperLeft gives latmax and lonmin
lowerRight gives latmin and lonmax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants