It also occured to me now, maybe I should have tried preprocessing the source JPG to present an easier task for Trace Bitmap to use. I am also thinking even if this also results in a perfect rendition, the possible 10,312 objects produced, may be too big a job to edit to reduce the 10,000 objects down the few hundred buildings shown on the Street Plan ? I was thinking the next step is a further conversion, from a single 10,312 node object down to a few hundred separate objects. convert text to the more efficient SVG Text object type, convert some buildings to simple rectangle objects, perhaps add fill colours to some buildings. However, as a step 2, I want to be able to edit the logical objects (5 streets containing a few hundred buildings) in the SVG version, eg. The SVG version is also black lines on white background and visually is near perfect reproduction of the 170KB JPG source. Over the weekend made progress using your suggested 'Trace bitmap' using the defaults (Single scan) which successfully converted my simple streetplan to a SVG that was a big 1.2MB file containing 1 object of 10312 nodes. My facilities are limited to source streetplan on paper and a digital camera I used to get a digital copy. I see since my logon last Friday some further input. Sorry, I am a long way from internet access, so prepared this reply at base and took it to a cybercafe for upload. Or Mediterranian.? (My brain seems to be much older than the rest of me, lol ) But if you search with "map" you should find it quickly.or.rats, I can't remember.I think it might have been a map of Tanzania, if the "map" search returns too many results. And there's another very recent one, but I can't remember the title. One recent topic is entitled "Carbon Paper". Usually folks who do this (again including me) prefer to reduce the opacity of the layer with the original, and so it's just like tracing the map on tracing paper (except the Inkscape pen takes some practice.however for me, much less than with Trace bitmap).Īnd as druban suggested, you can find more detailed tips by searching the forum. You would open Inkscape, import the map, add a new layer, and draw on the new layer, directly over the map. So if time is a factor, you might want to go with the other approachĪnd the other way is to trace it by hand. There is quite a learning curve, it seems, for most users, including me. One would be to use Path menu > Trace bitmap. In the next article, we will try to integrate Inkscape and Photoshop by importing Inkscape images directly to Photoshop as a smart object.In general, there are a couple of ways to approach it. Maybe in the future, the Inkscape compatibility will be better, as Photopea is constantly developed. Due to The Fact That even Photoshop can’t do this. Photopea is so cool and very helpful with the conversion. I’d say It’s not bad at all and I’m impressed. So that was a glimpse of Inkscape to Photopea compatibility. In Photoshop, you may still need to do some adjustment (for example missing fonts issue) After that, don’t forget to open the document in Photoshop.If the conversion result goes well, rename layers and fix document size. Then open the document on Photopea again.If we found something that doesn’t work, go back to Inkscape and fix the issue, by simplifying our design or removing the unsupported part.Then check if anything has changed and if there’s a compatibility issue. Either you need to simplify your Inkscape design or edit the PSD output. So with this limitation, you need to do some adjustment when converting Inkscape format to Photoshop. So although the document can be opened in Photopea, You have to make sure that generated Photopea PSD can be opened in Photoshop too. The error is not informative at all, and I haven’t got a chance to investigate what might be causing it, but most likely happens when we use complex SVG features. Sometimes the PSD output from Photopea can’t be opened in Photoshop. We only tried Powerstroke and Envelope deformation. Works for linear & radial gradient, fill and stroke. Works, but the name changed to generic naming like layer1, layer2, layer3, etc. Clones are created as independent separated objects Works, but blur radius doesn’t seem editable, and has issue when the document is resized. Works for solid fill & stroke (sometime has line width issue) Ok lets summarize it as table for quick reference Path/shape
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |