René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ENH: secondary axis for a x or y scale.  ","articleBody":"\u003c!--To help us understand and resolve your issue, please fill out the form to the best of your ability.--\u003e\r\n\u003c!--You can feel free to delete the sections that do not apply.--\u003e\r\n\r\n### Enhancement discussion\r\n\r\nSee #10961 #10960 \r\n\r\n![5l7bk](https://user-images.githubusercontent.com/1562854/38443320-27b3cffa-39a0-11e8-8730-814970afb63e.png)\r\n\r\n\r\nOften it is desirable to have a second x or y scale on an axes with a different scale than the  primary x/y axis; think frequency and period on the xaxis of a power spectrum, or date and datenum for a time series.  (just assuming the x-axis for now:) Generally it'd be the same size as the existing xaxis, but would be offset vertically, have its own locator, formatter, and xlabel.  it would update as the data is zoomed through, and be slave to the parent xaxis\r\n\r\nIt appears folks most often do this with twiny (i.e. https://stackoverflow.com/questions/10514315/how-to-add-a-second-x-axis-in-matplotlib) but there is nothing to make the axes continue to have the same x-limits under interactive viewing, and no simple way to have the new axes have a different scale. \r\n\r\nThe enhancement here would be to add something like:\r\n\r\n```\r\nsecaxis = ax.secondary_xaxis(loc='top', convert=5, label='Boo')\r\n```\r\n\r\nwhere `secaxis` is either an axis object or an axes.  `loc` would be something like `\"top\", \"bottom\", \"above\", \"below\", float` where \"above\" and \"below\" means that it goes above or below any existing axis, and the float is a hard-set axes fraction (like the `set_position` of `spine` now).  `convert` would be a conversion factor: a float would just be a multiplier, or a function could be passed that converts x to xnew.  No doubt there could be a way to make this work with units instead, but...\r\n \r\n#### How to impliment\r\n\r\nAs discussed in #10961 @efiring thought implimenting as an axes with shrunk and hidden unused dimensions would be good.  \r\n\r\nI'd advocate an axis object so that the logical organization makes more sense.  i.e. this would be a child of the original axes, and would be included as one of the axes decorators.  But, I haven't thought through all the implimentation details yet.  \r\n\r\n","author":{"url":"https://github.com/jklymak","@type":"Person","name":"jklymak"},"datePublished":"2018-04-06T20:42:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/10976/matplotlib/issues/10976"}