The example uses the Google Maps API for directions, so it is really based on the Google Directions. The longitude is a float that you should adjust to the value you use in the RAS Mapper REST API.
1. You are correct about the ras mapper being limited to cross sections. This is because inundate is a user function that takes as a parameter a set of coordinates and a particular WSE for a given river. The ras mapper will use these coordinates to generate a flood zone and then apply the inundate function on a per-layer basis.
2. In your image, you are looking at how the ras mapper would function in a relatively small cross section. It is likely that ras mapper will make several passes through the cross section, with the first pass being the most computationally intense. There is no way to know for sure how ras mapper will behave in a different scenario until you try it. Sorry for the ambiguity.
When you're looking at a multi-band equalizer, it is first important to understand that audio processing is an anisotropic, and not isotropic, operation, meaning that the process is applied in a different manner depending on the direction a signal moves through the filter. iZotope's Neutron EQ module was designed to be an isotropic, or same-direction, filter, meaning that it operates in the same manner regardless of the direction a signal moves through it. So, for example, a band that is narrow near the upper frequency of a guitar signal will behave the same, regardless of whether that signal is moving toward or away from the speaker. 827ec27edc