h7L"%SSKJr SSKJrJrJrJrJrJrJ r J r SSK J r J r SSKrSSKrSSKJrJr SSKJrJr SSKJrJr SS KJr SS KJrJrJrJr SS K J!r! SS K"J#r# S S/r$Sr%"SS\5r&Sr'Sr(Sr)Sr*Sr+"SS \&5r,\S%S&Sjj5r-\\.\/\./\\.\44r0S\1S'\\/\ \/\/44r2S\1S'\ \ \/\/4r3S\1S'\ \3r4S\1S'S'Sjr5S(Sjr6S)S*S jjr7"S!S\&5r8S+S"jr9S,S#jr:S-S$jr;g).) 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), ... ] } c\rSrSrSSjr\R SSj5rSS.SSjjr\ SSj5r \ SSj5r \ SS j5r \ SS j5r \ SS j5r\ SS j5r\ SS j5rSrg) _JSONBackendocJ/UlSUlSUlSUlSUlg)Ng{Gz?皙?g?) _entities max_sagittamin_lineweightlineweight_scalingfixed_lineweightselfs K/var/www/html/env/lib/python3.13/site-packages/ezdxf/addons/drawing/json.py__init___JSONBackend.__init__ps+/1""%!$cgNr)s r+ get_json_data_JSONBackend.get_json_datazs$'r.indentcH[R"UR5US9$)z$Returns the result as a JSON string.r5)jsondumpsr2)r*r6s r+ get_string_JSONBackend.get_string|szz$,,.v>>r.cUR(a#URS-S- n[SU5UlURUlURS:XaURUlURUlg)Ngffffff9@i,r"r#)r&maxr'r(max_flattening_distancer%)r*configmin_lineweight_mms r+ configure_JSONBackend.configuresi  & 5 5 [TU]5 Xlgr0)superr,r)r*r __class__s r+r,CustomJSONBackend.__init__s (r.cUR$)z1Returns the result as a JSON-like data structure.)r$r)s r+r2CustomJSONBackend.get_json_datas~~r.cpU(dgURRUURU5US.5 g)NtyperHgeometry)r$appendmake_properties_dict)r* entity_typerurHs r+ add_entityCustomJSONBackend.add_entitys5  #"77 C$  r.cUR(a URnO-[URURUR-5nUR [ US5URS.$)Nr4rMz stroke-widthlayerr(r=r& lineweightr'rMroundr}r*rH stroke_widths r+rw&CustomJSONBackend.make_properties_dictsd  00L##Z%:%:T=T=T%TL %%!,2%%  r.cVURSURUR/U5 g)Npointryxyr*posrHs r+ draw_pointCustomJSONBackend.draw_points #%%OW WWBBD'D5FD DD$V V.?V VVr.c .[U5S:Xa/$URn[URUR4/nUR 5GHnUR nUR[R:Xa.UR[URUR45 M\UR[R:Xa.UR[URUR45 MUR[R:XaQURnUR[URURURUR45 GMUR[R :XdGM8UR"nUR$nUR[&URURURURURUR45 GM U(aUR[(5 U$)Nr)rr MOVE_TO_ABSrrcommandsrrtrMOVE_TOrvLINE_TO LINE_TO_ABS CURVE3_TOctrl QUAD_TO_ABS CURVE4_TOctrl1ctrl2 CUBIC_TO_ABS CLOSE_PATH)rrrrcmdc1c2s r+rrsP 4yA~  C"CEE35512H}}gg 88w & OO[#%%7 8 XX ( OO[#%%7 8 XX** *B OO["$$ceeSUUC D XX** *BB OO\244rttRTT355#%%P Q  # Or.r PropertiesMaker TransformFuncRingGeoJsonPolygonc"U[US5US.$)zReturns 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. r4r|)r)rMrr}s r+properties_makerr>slA. r.c2URUR4$)zkDummy transformation function. Does not apply any transformations and just returns the input coordinates. )rr)locations r+ no_transformrQs JJ ##r.c^SU4SjjnU$)a/Returns 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 cF>[URURT5$)zITransforms WGS84 World Mercator EPSG:3395 coordinates to WGS84 EPSG:4326.)rrr)rtols r+ _transform7make_world_mercator_to_gps_function.._transformcs$XZZSAAr.rrr[ztuple[float, float]r1)rrs` r+#make_world_mercator_to_gps_functionrXsB r.c^\rSrSrSr\\4SU4Sjjjr\SSj5r SSjr SSjr \SSj5r \SSj5r \SS j5r\SS j5r\SS j5r\SS j5rS rU=r$)riiaCreates 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:>[TU]5 XlX lgr0)rmr,_properties_dict_maker_transform_function)r*rtransform_funcrns r+r,GeoJSONBackend.__init__s &6##1 r.c[UR5S:Xa0$URSSS:HnU(aSURS.$SURS.$)zMReturns the result as a JSON-like data structure according the GeoJSON specs.rrtFeatureFeatureCollection)rtfeaturesGeometryCollection)rt geometries)rr$)r*using_featuress r+r2GeoJSONBackend.get_json_datasS t~~ ! #I*62i? /T^^L L0O Or.cU(dgUR"URU56nU(a URRSUUS.5 gURRU5 g)Nrrs)rmake_propertiesr$rv)r*rTrHproperties_dicts r+ryGeoJSONBackend.add_entitys_ *.*E*E  ! !* -+   NN ! !%"1 &  NN ! !& )r.cUR(a URnO-[URURUR-5nUR [ US5UR4$)Nr4r~rs r+rGeoJSONBackend.make_propertiess^  00L##Z%:%:T=T=T%TL  % a"8*:J:JKKr.c lUR[S[URU555U5 g)NPoint)rygeojson_objectrrrs r+rGeoJSONBackend.draw_points*  7D)A)A#)F$G H* r.c pURnUR[SU"U5U"U5/5U5 g)N LineString)rryr)r*rrrHtfs r+rGeoJSONBackend.draw_lines3  % %  <"U)RW)= >  r.c[U5n[U5S:XagURnUVVs/sHupEU"U5U"U54PM nnnUR[ SU5U5 gs snnf)NrMultiLineString)rrrryr)r*rrHrrr json_liness r+rGeoJSONBackend.draw_solid_linesscU  u:?   % %167r!uben 7 '8*EzR8sA)c[U5S:XagURnURURS9Vs/sH oC"U5PM nnUR [ SU5U5 gs snf)Nr)distancer)rr flatteningr%ryr)r*rrHrrrs r+rGeoJSONBackend.draw_pathsa t9>   % %#'??D KOsA(c [U5n[U5S:Xag/nUHBn[U5(dMUR[X@RUR S95 MD U(aUR [SU5U5 gg)Nr)r%r MultiPolygon)rrextendgeojson_polygonsr%rryr)r*rrHpolygonsrs r+r GeoJSONBackend.draw_filled_pathsswU  u:? )+D4yy$*:*:t?W?W  OON>8Dj Q r.c ,UR5n[U5S:agUSRUS5(dURUS5 URnUR [ SUVs/sH oT"U5PM sn/5U5 gs snf)NrrrPolygon)rrrrvrryr)r*rrHrrrs r+r"GeoJSONBackend.draw_filled_polygons &0 x=1  {""8B<00 OOHQK (  % %  9x'@x!1x'@&A BJ '@s2B)rr)rrrrr[r\)r[r)rTrrHr)rHrr[ztuple[str, float, str]rrrrrr)r^r_r`rarrrr,r r2ryrrrrrrrrdrrs@r+rris$/f-=(42)2&2  22PP*"L    S0S>OS SSLLR'R5FR RR$     .?      r.c XS.$)N)rt coordinatesr1)namers r+rr s  55r.ctUR(a [S5eURU5Vs/sH oC"U5PM nnUR(d#URnUR U"U55 UR 5nU(aU(aU(dU(aUR5 U$s snf)aReturns 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_closedrrvhas_clockwise_orientationreverse)ris_holer%rrrr clockwises r+ geojson_ringrs 122%)__[%AB%Abe%AHB >> 5 "..0I 7y OCsB5c ^UR5n[U5S:Xa/$[U5S:Xa[USSX5//$[R"U5n/nUHn[USSX5/n[U5S:aUSn[ U[ 5(aUR[USX55 M[[ U[[45(aEUH?n [ U [[45(aU Sn UR[U SX55 MA URU5 M U$)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 isinstancerrvtupler) rr%rrrrpolygongeojson_polygonholesholes r+rr,s!!% 0I 9~  9~ilE;CDEE--i8H-/ UK <+  w)rrr[r)r r]rrr[r) rrrboolr%rrrr[r)rrr%rrrr[zlist[GeoJsonPolygon])< __future__rtypingrrrrrr r r typing_extensionsr r rbr8 ezdxf.mathrr ezdxf.pathrrezdxf.npshapesrr type_hintsrbackendrrrrr?rrHr__all__CUSTOM_JSON_SPECSrrrrrrrrr]rr__annotations__rrrrrrrrrrr1r.r+r)sz#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.