Change Details

I like to provide historical maps in my Polish Wikipedia articles. In particular, I often need small fragments of complete maps. An example is the map of the destruction of Warsaw during WW2 [[:commons:File:Zniszczenia.jpg]] of size 18,588 × 23,976 px, 84.64 MB. In a typical article [[:w:pl:Ulicza Olszowa w Warszawie]] about a single street, I need only a small fragment of the complete map. Therefore I had to create a new file on commons with the selection I needed: [[:commons:File:Zniszczenia Warszawy, fragment Pragi.jpg|]]. It seems reasonable to design a mechanism which would enable me, on my Wikipedia, to specify a fragment of the complete map to be imported from commons and displayed in the article. It would stop the proliferation of redundant images on commons, being crops of one another. I am aware of [[:en:Template:CSS image crop]]. However, this tool downloads the complete image and performs crop on the client side. Given the size of the complete image, it is prohibitive for users of low-end devices and/or slow networks. So it seems reasonable that the crop is performed on the server side. In order to reduce the computational overhead, I expect that a cache of frequently requested crops should be created. Summing up, the requested functionality: 1) The tool is installed on commons and working on the server side. 2) It produces crops of images, as specified in the link from Wikipedia. 3) It delivers the cropped images to the Wikipedia 4) Perhaps it should cache frequently produced crops.

I like to provide historical maps in my Polish Wikipedia articles. In particular, I often need small fragments of complete maps. An example is the map of the destruction of Warsaw during WW2 [[:commons:File:Zniszczenia.jpg]] of size 18,588 × 23,976 px, 84.64 MB. In a typical article [[:w:pl:Ulica Olszowa w Warszawie]] about a single street, I need only a small fragment of the complete map. Therefore I had to create a new file on commons with the selection I needed: [[:commons:File:Zniszczenia Warszawy, fragment Pragi.jpg|]]. It seems reasonable to design a mechanism which would enable me, on my Wikipedia, to specify a fragment of the complete map to be imported from commons and displayed in the article. It would stop the proliferation of redundant images on commons, being crops of one another. I am aware of [[:en:Template:CSS image crop]]. However, this tool downloads the complete image and performs crop on the client side. Given the size of the complete image, it is prohibitive for users of low-end devices and/or slow networks. So it seems reasonable that the crop is performed on the server side. In order to reduce the computational overhead, I expect that a cache of frequently requested crops should be created. Summing up, the requested functionality: 1) The tool is installed on commons and working on the server side. 2) It produces crops of images, as specified in the link from Wikipedia. 3) It delivers the cropped images to the Wikipedia 4) Perhaps it should cache frequently produced crops.

I like to provide historical maps in my Polish Wikipedia articles. In particular, I often need small fragments of complete maps. An example is the map of the destruction of Warsaw during WW2 [[:commons:File:Zniszczenia.jpg]] of size 18,588 × 23,976 px, 84.64 MB. In a typical article [[:w:pl:Ulicza Olszowa w Warszawie]] about a single street, I need only a small fragment of the complete map. Therefore I had to create a new file on commons with the selection I needed: [[:commons:File:Zniszczenia Warszawy, fragment Pragi.jpg|]]. It seems reasonable to design a mechanism which would enable me, on my Wikipedia, to specify a fragment of the complete map to be imported from commons and displayed in the article. It would stop the proliferation of redundant images on commons, being crops of one another. I am aware of [[:en:Template:CSS image crop]]. However, this tool downloads the complete image and performs crop on the client side. Given the size of the complete image, it is prohibitive for users of low-end devices and/or slow networks. So it seems reasonable that the crop is performed on the server side. In order to reduce the computational overhead, I expect that a cache of frequently requested crops should be created. Summing up, the requested functionality: 1) The tool is installed on commons and working on the server side. 2) It produces crops of images, as specified in the link from Wikipedia. 3) It delivers the cropped images to the Wikipedia 4) Perhaps it should cache frequently produced crops.