-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to replace ship emission in GEOS-Chem with my own data #301
Comments
Thanks for writing @hetingkun. A couple of thoughts:
|
Thanks! |
Thanks for the update @hetingkun. I just pushed a fix to GCPy (dev branch) so you can compute the grid box areas with that. git clone https://github.com/geoschem/gcpy
git checkout dev then you can use these functions, as in this example script #!/usr/bin/env python3
import numpy as np
import gcpy
# Longitude parameters
lon_stride = 0.25
center_at_180 = True
# Latitude parameters
lat_stride = 0.3125
half_polar_grid = True
# Grid box lon & lat edges
lon_edge = gcpy.grid.calc_rectilinear_lon_edge(lon_stride, center_at_180)
lat_edge = gcpy.grid.calc_rectilinear_lat_edge(lat_stride, half_polar_grid)
# Grid box area
area = gcpy.grid.calc_rectilinear_grid_area(lon_edge, lat_edge)
print(f"Sum of global surface area [m2]: {np.sum(area)}") |
Thanks for your help. I've solved the problem in area calculation. And I still need the help from Emissions Working Group. |
I'd suggest taking a look at other emission inventories for guidance on speciation. For more formal guidance leading to co-authorship, please reach out to us via email. |
Your name
Tingkun
Your affiliation
Tsinghua University
Please provide a clear and concise description of your question or discussion topic.
I built a global ship emission inventory based on my own model. Emission data are in csv format with longitude, latitude and monthly emission of routine pollutants and GHGs (PM, NOx, SOx, HC, CO, CO2 etc.) with a spatial resolution of 0.1° × 0.1°. I want to use this data in GEOS-Chem, but i met a few problems.
Many Thanks !
The text was updated successfully, but these errors were encountered: