CMV3,CMV12 for higher resolution domains

It is my understanding that the input for the point sources commercial marine vehicle emissions (1_2, 3) in NEI platforms are processed for 12km (based on TSD), and some previous platforms such as 2019 had a higher resolution input (4km California). I need to create cmv emissions for multiple high resolution domains in North America (Chicago, NY,..), How would I prepare CMV inputs for these domains for the year 2019 (4km, 1km resolution)? is there a way to get the unaggregated raw cmv emissions so I could prepare the SMOKE inputs instead of having the coarse 12km resolution for 4km and 1km?

Thanks for your help

Can you share which year(s) you need the data for and provide a description of the grids you need?

From that, we can explore ways in which appropriate data could be provided.

Hi Eyth,

Thanks for your quick response, we are modelling two years (2019 or pre-covid, 2021 post covid), however, 2019 is what is first needed. Below are the high resolution domains, I am sorry they are many and we might add a few more west (LA, Portland, Vancouver/Seattle). I hope this gives you an idea on the data needed.

! coords --line: name; type, P-alpha, P-beta, P-gamma, xcent, ycent
‘LAM_40N97W’
2, 33.0D0, 45.D0,-97.D0,-97.D0, 40.D0
’ ’ ! end coords. grids: name; xorig,yorig,xcell,ycell,ncols,nrows,nthik
‘CHCG1’
‘LAM_40N97W’ 665000. 18000 1000 1000. 150 127 1
‘CHCG4’
‘LAM_40N97W’ 396000. -72000 4000 4000 165 156 1
‘NY1’
‘LAM_40N97W’ 1848000. 280000. 1000. 1000. 104 104 1
‘NY4’
‘LAM_40N97W’ 1684000. 196000. 4000. 4000. 127 127 1
‘MTL1’
‘LAM_40N97W’ 1752000 780000 1000. 1000. 120 120 1
‘MTL4’
‘LAM_40N97W’ 1464000. 528000 4000. 4000. 156 156 1
‘GTA1’
‘LAM_40N97W’ 1332000.000 480000.000 1000.000 1000.000 120 120 1
‘GTA4’
‘LAM_40N97W’ 1044000.000 228000.000 4000.000 4000.000 156 156 1
’ ’

Thanks for your help.

We are considering providing the CMV emissions for the requested grids for 2019.

Would you still be able to use those?

Instead of preparing CMV emissions for 2021, we would prefer to give you 2022 because we have other active work on that year.

The 2022 data should be similar in magnitude to 2021 data and is also post-COVID.

Would that suffice to meet your project needs?

Hi Eyth,

Thank you so much. That would be great if we can get 2019. The year 2022 would work fine for a post COVID year as we still did not start processing emissions for 2021, this won’t cause any issues.

Thanks again for your help

OK, sounds good. We have a lot more data posted and available for 2022 than 2021, as there was a full collaborative effort on 2022.

Hi, we have processed and posted these files.

2019:

Index of /Air/emismod/2019/cmv

2022:

Index of /Air/emismod/2022/v2/cmv

Please note:

  • No masking was applied to the inventories.
  • The domains contain a mix of US and Canada activity;
    some domains are US-only, others only contain Canada,
    and some contain both US+Canada.
  • Not every domain has activity for every month; for example
    there is very little activity in the Toronto 1km domain (GTA1)
    in the winter months due to ice cover, so months devoid of any
    activity will not have hourly FF10s for that domain.
  • The CHCG1 domain is way inland and does not have any CMV activity.
    We assume “CHCG” means “Chicago” and we would have expected the 1km
    domain to be centered over Chicago, similar to how the other domains
    are centered over major cities. But CHCG1 is in the middle of inland
    Illinois and is way off center from the 4km parent domain.

Thank you so much Karl, we really appreciate it. You’re right there’s a problem with the Chicago 1km grid description.

Is high-resolution CMV sector available for 2018?
my domains are listed below:

' '
'LamCon-UTSTAND'
  2        30.000        45.000       -97.000       -97.000        49.700
' '
'SQ_D01'
'LamCon-UTSTAND'  -2162015.000    -26735.000      9000.000      9000.000   64   64    1
'SQ_D02'
'LamCon-UTSTAND'  -1988015.000    156265.000      3000.000      3000.000   64   64    1
'SQ_D03'
'LamCon-UTSTAND'  -1930010.000    223265.000      1000.000      1000.000   64   64    1
' '

Hi, generating 2018 inventories are a lot more time intensive. A different set of scripts/tools were used to process CMV pre-2019 and are more difficult to use, and 2018 CMV was projected from 2017, which requires CoST to be run. As such, we cannot accommodate generating those emissions at this time.

1 Like