This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Mike, Sorry for the delay. > This is the plot extent: > *ax.set_extent([-122.1, -120.6, 39.50, 40.40], datacrs)* > ...which matches those plots with CIC, and, yes, much smaller than what I had > sent you earlier. > > I'm using these same coords for the envelop: > > *coords2 = [(-122.1, > 40.40),(-120.6,40.40),(-122.1,39.50),(-120.,39.50)]envelope = > Polygon(coords2).buffer(2)* The output you sent me two emails ago (from the purposely failed query): http://www.met.sjsu.edu/weather/test/hwy_type2-U_error_output.txt Shows that the following bounds are used in the python-awips request: BOX3D(-124.099105 37.500000, -118.000049 42.238290) Which is slightly smaller than the original envelope you described in your first email, but still significantly larger than the one you're describing now. Which really only matters if you actually don't mind all the roads returned by the highway query with no filter. If the problem is that query is too slow, then I think we can help fix that by defining the proper bounds. But if the issue is there's just too many roads returned and it's cluttered, let me know, because I might have one more idea on how to reduce the roads to something more along the lines of the 'S' returned shapes (but not as disjointed). Thanks! --Shay Carter She/Her/Hers AWIPS Software Engineer NSF Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: AKV-251431 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with NSF Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.