@@ -154,15 +154,15 @@ public Flights flights() {
154154 public class Flights {
155155
156156 /**
157- * Stateless method to retrieve emission estimates. Details on how emission estimates are computed
158- * are in [GitHub](https://github.com/google/travel-impact-model). The response will contain all
159- * entries that match the input flight legs, in the same order. If there are no estimates available
160- * for a certain flight leg, the response will return the flight leg object with empty emission
161- * fields. The request will still be considered successful. Reasons for missing emission estimates
162- * include: * The flight is unknown to the server. * The input flight leg is missing one or more
163- * identifiers. * The flight date is in the past. * The aircraft type is not supported by the model.
164- * * Missing seat configuration. The request can contain up to 1000 flight legs. If the request has
165- * more than 1000 direct flights, if will fail with an INVALID_ARGUMENT error.
157+ * Retrieves emission estimates. Details on how emission estimates are computed are in
158+ * [GitHub](https://github.com/google/travel-impact-model). The response will contain all entries
159+ * that match the input flight legs, in the same order. If there are no estimates available for a
160+ * certain flight leg, the response will return the flight leg object with empty emission fields.
161+ * The request will still be considered successful. Reasons for missing emission estimates include:
162+ * * The flight is unknown to the server. * The input flight leg is missing one or more identifiers.
163+ * * The flight date is in the past. * The aircraft type is not supported by the model. * Missing
164+ * seat configuration. The request can contain up to 1000 flight legs. If the request has more than
165+ * 1000 direct flights, if will fail with an INVALID_ARGUMENT error.
166166 *
167167 * Create a request for the method "flights.computeFlightEmissions".
168168 *
@@ -184,14 +184,14 @@ public class ComputeFlightEmissions extends TravelImpactModelRequest<com.google.
184184 private static final String REST_PATH = "v1/flights:computeFlightEmissions" ;
185185
186186 /**
187- * Stateless method to retrieve emission estimates. Details on how emission estimates are computed
188- * are in [GitHub](https://github.com/google/travel-impact-model). The response will contain all
189- * entries that match the input flight legs, in the same order. If there are no estimates
190- * available for a certain flight leg, the response will return the flight leg object with empty
191- * emission fields. The request will still be considered successful. Reasons for missing emission
192- * estimates include: * The flight is unknown to the server. * The input flight leg is missing one
193- * or more identifiers. * The flight date is in the past. * The aircraft type is not supported by
194- * the model. * Missing seat configuration. The request can contain up to 1000 flight legs. If the
187+ * Retrieves emission estimates. Details on how emission estimates are computed are in
188+ * [GitHub](https://github.com/google/travel-impact-model). The response will contain all entries
189+ * that match the input flight legs, in the same order. If there are no estimates available for a
190+ * certain flight leg, the response will return the flight leg object with empty emission fields.
191+ * The request will still be considered successful. Reasons for missing emission estimates
192+ * include: * The flight is unknown to the server. * The input flight leg is missing one or more
193+ * identifiers. * The flight date is in the past. * The aircraft type is not supported by the
194+ * model. * Missing seat configuration. The request can contain up to 1000 flight legs. If the
195195 * request has more than 1000 direct flights, if will fail with an INVALID_ARGUMENT error.
196196 *
197197 * Create a request for the method "flights.computeFlightEmissions".
@@ -270,35 +270,34 @@ public ComputeFlightEmissions set(String parameterName, Object value) {
270270 }
271271 }
272272 /**
273- * Stateless method to retrieve GHG emissions estimates for a set of flight segments for Scope 3
274- * reporting. The response will contain all entries that match the input Scope3FlightSegment flight
275- * segments, in the same order provided. The estimates will be computed using the following
276- * cascading logic (using the first one that is available): 1. TIM-based emissions given origin,
277- * destination, carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions
278- * given origin, destination, year in departureDate, and cabinClass. 3. Distance-based emissions
279- * calculated using distanceKm, year in departureDate, and cabinClass. If there is a future flight
280- * requested in this calendar year, we do not support Tier 1 emissions and will fallback to Tier 2
281- * or 3 emissions. If the requested future flight is in not in this calendar year, we will return an
282- * empty response. We recommend that for future flights, computeFlightEmissions API is used instead.
283- * If there are no estimates available for a certain flight with any of the three methods, the
284- * response will return a Scope3FlightEmissions object with empty emission fields. The request will
285- * still be considered successful. Generally, missing emissions estimates occur when the flight is
286- * unknown to the server (e.g. no specific flight exists, or typical flight emissions are not
287- * available for the requested pair). The request will fail with an `INVALID_ARGUMENT` error if: *
288- * The request contains more than 1,000 flight legs. * The input flight leg is missing one or more
289- * identifiers. For example, missing origin/destination without a valid distance for TIM_EMISSIONS
290- * or TYPICAL_FLIGHT_EMISSIONS type matching, or missing distance for a DISTANCE_BASED_EMISSIONS
291- * type matching (if you want to fallback to distance-based emissions or want a distance-based
292- * emissions estimate, you need to specify a distance). * The flight date is before 2019 (Scope 3
293- * data is only available for 2019 and after). * The flight distance is 0 or lower. * Missing cabin
294- * class. Because the request is processed with fallback logic, it is possible that misconfigured
295- * requests return valid emissions estimates using fallback methods. For example, if a request has
296- * the wrong flight number but specifies the origin and destination, the request will still succeed,
297- * but the returned emissions will be based solely on the typical flight emissions. Similarly, if a
298- * request is missing the origin for a typical flight emissions request, but specifies a valid
299- * distance, the request could succeed based solely on the distance-based emissions. Consequently,
300- * one should check the source of the returned emissions (source) to confirm the results are as
301- * expected.
273+ * Retrieves GHG emissions estimates for a set of flight segments for Scope 3 reporting. The
274+ * response will contain all entries that match the input Scope3FlightSegment flight segments, in
275+ * the same order provided. The estimates will be computed using the following cascading logic
276+ * (using the first one that is available): 1. TIM-based emissions given origin, destination,
277+ * carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions given origin,
278+ * destination, year in departureDate, and cabinClass. 3. Distance-based emissions calculated using
279+ * distanceKm, year in departureDate, and cabinClass. If there is a future flight requested in this
280+ * calendar year, we do not support Tier 1 emissions and will fallback to Tier 2 or 3 emissions. If
281+ * the requested future flight is in not in this calendar year, we will return an empty response. We
282+ * recommend that for future flights, computeFlightEmissions API is used instead. If there are no
283+ * estimates available for a certain flight with any of the three methods, the response will return
284+ * a Scope3FlightEmissions object with empty emission fields. The request will still be considered
285+ * successful. Generally, missing emissions estimates occur when the flight is unknown to the server
286+ * (e.g. no specific flight exists, or typical flight emissions are not available for the requested
287+ * pair). The request will fail with an `INVALID_ARGUMENT` error if: * The request contains more
288+ * than 1,000 flight legs. * The input flight leg is missing one or more identifiers. For example,
289+ * missing origin/destination without a valid distance for TIM_EMISSIONS or TYPICAL_FLIGHT_EMISSIONS
290+ * type matching, or missing distance for a DISTANCE_BASED_EMISSIONS type matching (if you want to
291+ * fallback to distance-based emissions or want a distance-based emissions estimate, you need to
292+ * specify a distance). * The flight date is before 2019 (Scope 3 data is only available for 2019
293+ * and after). * The flight distance is 0 or lower. * Missing cabin class. Because the request is
294+ * processed with fallback logic, it is possible that misconfigured requests return valid emissions
295+ * estimates using fallback methods. For example, if a request has the wrong flight number but
296+ * specifies the origin and destination, the request will still succeed, but the returned emissions
297+ * will be based solely on the typical flight emissions. Similarly, if a request is missing the
298+ * origin for a typical flight emissions request, but specifies a valid distance, the request could
299+ * succeed based solely on the distance-based emissions. Consequently, one should check the source
300+ * of the returned emissions (source) to confirm the results are as expected.
302301 *
303302 * Create a request for the method "flights.computeScope3FlightEmissions".
304303 *
@@ -320,16 +319,16 @@ public class ComputeScope3FlightEmissions extends TravelImpactModelRequest<com.g
320319 private static final String REST_PATH = "v1/flights:computeScope3FlightEmissions" ;
321320
322321 /**
323- * Stateless method to retrieve GHG emissions estimates for a set of flight segments for Scope 3
324- * reporting. The response will contain all entries that match the input Scope3FlightSegment
325- * flight segments, in the same order provided. The estimates will be computed using the following
326- * cascading logic (using the first one that is available): 1. TIM-based emissions given origin,
327- * destination, carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions
328- * given origin, destination, year in departureDate, and cabinClass. 3. Distance-based emissions
329- * calculated using distanceKm, year in departureDate, and cabinClass. If there is a future flight
330- * requested in this calendar year, we do not support Tier 1 emissions and will fallback to Tier 2
331- * or 3 emissions. If the requested future flight is in not in this calendar year, we will return
332- * an empty response. We recommend that for future flights, computeFlightEmissions API is used
322+ * Retrieves GHG emissions estimates for a set of flight segments for Scope 3 reporting. The
323+ * response will contain all entries that match the input Scope3FlightSegment flight segments, in
324+ * the same order provided. The estimates will be computed using the following cascading logic
325+ * (using the first one that is available): 1. TIM-based emissions given origin, destination ,
326+ * carrier, flightNumber, departureDate, and cabinClass. 2. Typical flight emissions given origin,
327+ * destination, year in departureDate, and cabinClass. 3. Distance-based emissions calculated
328+ * using distanceKm, year in departureDate, and cabinClass. If there is a future flight requested
329+ * in this calendar year, we do not support Tier 1 emissions and will fallback to Tier 2 or 3
330+ * emissions. If the requested future flight is in not in this calendar year, we will return an
331+ * empty response. We recommend that for future flights, computeFlightEmissions API is used
333332 * instead. If there are no estimates available for a certain flight with any of the three
334333 * methods, the response will return a Scope3FlightEmissions object with empty emission fields.
335334 * The request will still be considered successful. Generally, missing emissions estimates occur
0 commit comments