Og7LUddlmZddlmZmZmZmZmZmZm Z m Z ddl m Z m Z ddlZddlZddlmZmZddlmZmZddlmZmZdd lmZdd lmZmZmZmZdd l m!Z!dd l"m#Z#d dgZ$dZ%GddeZ&dZ'dZ(dZ)dZ*dZ+Gdd e&Z,ed%d&dZ-ee.e/e.gee.effZ0de1d<eege e/e/ffZ2de1d<e e e/e/fZ3de1d<e e3Z4de1d<d'dZ5d(dZ6d)d*d Z7Gd!de&Z8d+d"Z9 d,d#Z: d-d$Z;y).) annotations)IterableSequence no_type_checkAnyCallableDictListTuple) TypeAliasoverrideN)Vec2world_mercator_to_gps)Commandnesting) orient_paths single_paths)Color)BackendInterfaceBkPath2d BkPoints2d ImageData) Configuration)BackendPropertiesCustomJSONBackendGeoJSONBackenda~ JSON content = [entity, entity, ...] entity = { "type": point | lines | path | filled-paths | filled-polygon, "properties": { "color": "#RRGGBBAA", "stroke-width": 0.25, # in mm "layer": "name" }, "geometry": depends on "type" } DXF linetypes (DASH, DOT, ...) are resolved into solid lines. A single point: point = { "type": "point", "properties": {...}, "geometry": [x, y] } Multiple lines with common properties: lines = { "type": "lines", "properties": {...}, "geometry": [ (x0, y0, x1, y1), # 1. line (x0, y0, x1, y1), # 2. line .... ] } Lines can contain points where x0 == x1 and y0 == y1! A single linear path without filling: path = { "type": "path", "properties": {...}, "geometry": [path-command, ...] } SVG-like path structure: - The first path-command is always an absolute move to "M" - The "M" command does not appear inside a path, each path is a continuouse geometry (no multi-paths). path-command = ("M", x, y) = absolute move to ("L", x, y) = absolute line to ("Q", x0, y0, x1, y1) = absolute quadratice Bezier curve to - (x0, y0) = control point - (x1, y1) = end point ("C", x0, y0, x1, y1, x2, y2) = absolute cubic Bezier curve to - (x0, y0) = control point 1 - (x1, y1) = control point 2 - (x2, y2) = end point ("Z",) = close path Multiple filled paths: Exterior paths and holes are mixed and NOT oriented by default (clockwise or counter-clockwise) - PyQt and SVG have no problem with that structure but matplotlib requires oriented paths. When oriented paths are required the CustomJSONBackend can orient the paths on demand. filled-paths = { "type": "filled-paths", "properties": {...}, "geometry": [ [path-command, ...], # 1. path [path-command, ...], # 2. path ... ] } A single filled polygon: A polygon is explicitly closed, so first vertex == last vertex is guaranteed. filled-polygon = { "type": "filled-polygon", "properties": {...}, "geometry": [ (x0, y0), (x1, y1), (x2, y2), ... ] } ceZdZddZej ddZddddZeddZ eddZ eddZ edd Z edd Z edd Zedd Zy ) _JSONBackendcJg|_d|_d|_d|_d|_y)Ng{Gz?皙?g?) _entities max_sagittamin_lineweightlineweight_scalingfixed_lineweightselfs ^/var/www/html/public_html/myphp/venv/lib/python3.12/site-packages/ezdxf/addons/drawing/json.py__init__z_JSONBackend.__init__ps+/1""%!$cyNr(s r* get_json_dataz_JSONBackend.get_json_datazs$'r,indentcLtj|j|S)z$Returns the result as a JSON string.r2)jsondumpsr0)r)r3s r* get_stringz_JSONBackend.get_string|szz$,,.v>>r,c|jr#|jdzdz }td||_|j|_|jdk(r|j|_|j|_y)Ngffffff9@i,r!r")r%maxr&r'max_flattening_distancer$)r)configmin_lineweight_mms r* configurez_JSONBackend.configuresi  & 5 5 OW WWBBD'D5FD DD$V V.?V VVr,c t|dk(rgS|j}t|j|jfg}|j D]}|j }|jtjk(r-|jt|j|jfZ|jtjk(r-|jt|j|jf|jtjk(rP|j}|jt|j|j|j|jf|jtj k(s0|j"}|j$}|jt&|j|j|j|j|j|jf|r|jt(|S)Nr)rr| MOVE_TO_ABSrurvcommandsr}rdrMOVE_TOrfLINE_TO LINE_TO_ABS CURVE3_TOctrl QUAD_TO_ABS CURVE4_TOctrl1ctrl2 CUBIC_TO_ABS CLOSE_PATH)rrr}rcmdc1c2s r*rrsW 4yA~  C"CEE35512H}} Rgg 88w & OO[#%%7 8 XX ( OO[#%%7 8 XX** *B OO["$$ceeSUUC D XX** *BB OO\244rttRTT355#%%P Q R  # Or,r PropertiesMaker TransformFuncRingGeoJsonPolygonc"|t|d|dS)aReturns the property dict:: { "color": color, "stroke-width": stroke_width, "layer": layer, } Returning an empty dict prevents properties in the GeoJSON output and also avoids wraping entities into "Feature" objects. r1rk)ro)rFrqrls r*properties_makerr>slA. r,c2|j|jfS)zsDummy transformation function. Does not apply any transformations and just returns the input coordinates. )rurv)locations r* no_transformrQs JJ ##r,cdfd }|S)aGReturns a function to transform WGS84 World Mercator `EPSG:3395 `_ location given as cartesian 2D coordinates x, y in meters into WGS84 decimal degrees as longitude and latitude `EPSG:4326 `_ as used by GPS. Args: tol: accuracy for latitude calculation cFt|j|jS)zITransforms WGS84 World Mercator EPSG:3395 coordinates to WGS84 EPSG:4326.)rrurv)rtols r* _transformz7make_world_mercator_to_gps_function.._transformcs$XZZSAAr,rrrPztuple[float, float]r/)rrs` r*#make_world_mercator_to_gps_functionrXsB r,ceZdZdZeef d fd Zed dZddZ ddZ eddZ eddZ e ddZ edd Ze dd Ze dd ZxZS)ra1Creates a JSON-like output according the `GeoJSON`_ scheme. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984 `EPSG:4326 `_, and units of decimal degrees. - Latitude: -90 to +90 (South/North) - Longitude: -180 to +180 (East/West) So most DXF files will produce invalid coordinates and it is the job of the **package-user** to provide a function to transfrom the input coordinates to EPSG:4326! The :class:`~ezdxf.addons.drawing.recorder.Recorder` and :class:`~ezdxf.addons.drawing.recorder.Player` classes can help to detect the extents of the DXF content. Default implementation: .. autofunction:: no_transform Factory function to make a transform function from WGS84 World Mercator `EPSG:3395 `_ coordinates to WGS84 (GPS) `EPSG:4326 `_. .. autofunction:: make_world_mercator_to_gps_function The GeoJSON format supports only straight lines so curved shapes are flattened to polylines and polygons. The properties are handled as a foreign member feature and is therefore not defined in the GeoJSON specs. It is possible to provide a custom function to create these property objects. Default implementation: .. autofunction:: properties_maker Args: properties_maker: function to create a properties dict. **Class Methods** .. automethod:: get_json_data .. automethod:: get_string .. versionadded:: 1.3.0 .. _GeoJSON: https://geojson.org/ c>t|||_||_yr.)r_r+_properties_dict_maker_transform_function)r)rtransform_funcr`s r*r+zGeoJSONBackend.__init__s &6##1 r,ct|jdk(riS|jdddk(}|rd|jdSd|jdS)zMReturns the result as a JSON-like data structure according the GeoJSON specs.rrdFeatureFeatureCollection)rdfeaturesGeometryCollection)rd geometries)rr#)r)using_featuress r*r0zGeoJSONBackend.get_json_datasS t~~ ! #I*62i? /T^^L L0O Or,c|sy|j|j|}|r |jjd||dy|jj|y)Nrrc)rmake_propertiesr#rf)r)rKrBproperties_dicts r*rizGeoJSONBackend.add_entitysa *E$*E*E  ! !* -+   NN ! !%"1 &  NN ! !& )r,c|jr |j}n-t|j|j|jz}|j t |d|jfS)Nr1rmrps r*rzGeoJSONBackend.make_propertiess^  00L##Z%:%:T=T=T%TL  % a"8*:J:JKKr,c l|jtdt|j||y)NPoint)rigeojson_objectrrrws r*ryzGeoJSONBackend.draw_points*  7D)A)A#)F$G H* r,c p|j}|jtd||||g|y)N LineString)rrir)r)r|r}rBtfs r*r~zGeoJSONBackend.draw_lines3  % %  <"U)RW)= >  r,ct|}t|dk(ry|j}|Dcgc]\}}||||f}}}|jt d||ycc}}w)NrMultiLineString)rrrrir)r)r{rBrrr json_liness r*rzGeoJSONBackend.draw_solid_linessdU  u:?   % %167Ar!uben7 7 '8*EzR8sA&ct|dk(ry|j}|j|jDcgc] }|| }}|j t d||ycc}w)Nr)distancer)rr flatteningr$rir)r)rrBrrrs r*rzGeoJSONBackend.draw_paths^ t9>   % %#'??D KOsA(ct|}t|dk(ryg}|D]?}t|s|jt||j|j A|r|j td||yy)Nr)r$r MultiPolygon)rrextendgeojson_polygonsr$rrir)r)rrBpolygonsrs r*rz GeoJSONBackend.draw_filled_pathss|U  u:? )+ D4y$$*:*:t?W?W   OON>8Dj Q r,c |j}t|dkry|dj|ds|j|d|j}|j t d|Dcgc] }|| c}g|ycc}w)NrrrPolygon)rrrrfrrir)r)rrBrrrs r*rz"GeoJSONBackend.draw_filled_polygons} &0 x=1  {""8B<0 OOHQK (  % %  9x'@!1'@&A BJ '@s,B )rrrrrPrQ)rPr)rKrrBr)rBrrPztuple[str, float, str]rrrrrr)rSrTrUrrrr+r r0rirryr~rrrrrrs@r*rris/f-=(42)2&2  2PP*"L    S0S>OS SSLLR'R5FR RR$     .?      r,c ||dS)N)rd coordinatesr/)namers r*rr s  55r,c4|jr td|j|Dcgc] }|| }}|js#|j}|j |||j }|r|r|s|r|j|Scc}w)a#Returns a linear ring according to the GeoJSON specs. - A linear ring is a closed LineString with four or more positions. - The first and last positions are equivalent, and they MUST contain identical values; their representation SHOULD also be identical. - A linear ring is the boundary of a surface or the boundary of a hole in a surface. - A linear ring MUST follow the right-hand rule with respect to the area it bounds, i.e., exterior rings are counterclockwise, and holes are clockwise. zmulti-paths not allowed) has_sub_paths TypeErrorr is_closedr|rfhas_clockwise_orientationreverse)ris_holer$rrrr| clockwises r* geojson_ringrs 122%)__[%ABbeBHB >> 5 "..0I 7y OCsBc 6|j}t|dk(rgSt|dk(rt|dd||ggStj|}g}|D]}t|dd||g}t|dkDr|d}t |t r|jt|d||Vt |ttfr?|D]:} t | ttfr| d} |jt| d||<|j||S)zReturns a list of polygons, where each polygon is a list of an exterior path and optional holes e.g. [[ext0, hole0, hole1], [ext1], [ext2, hole0], ...]. rrFT) sub_pathsrrrmake_polygon_structure isinstancerrftupler) rr$rrrrpolygongeojson_polygonholesholes r*rr,s-!% 0I 9~  9~ilE;CDEE--i8H-/1 UK <+  w)rrrPr)rrRrrrPr) rrrboolr$rrrrPr)rrr$rrrrPzlist[GeoJsonPolygon])< __future__rtypingrrrrrr r r typing_extensionsr r rVr5 ezdxf.mathrr ezdxf.pathrrezdxf.npshapesrr type_hintsrbackendrrrrr;rrBr__all__CUSTOM_JSON_SPECSrrrrrrrrrRrr__annotations__rrrrrrrrrrr/r,r*rsz#VVV1 2'5FF!)  0 1Wt3 #3 l     lV lV^0&sE3&7c3h&GHH#TFE%,,?$?@ y@uUE\*+i+!J &&$"a \a H6 !05;H 6" "!&",9""r,