o EDiXx@sddlZddlZddlZddlmZddlmZddlmZddlmZddlm Z dZ dZ d Z d d d d ddddZ ddddddddZddddddddZd d!d"d#d$d%d&dZe eeed'Zee d(d)eDZd*d+d,d-Zd.d/Zd0d1Zd2d3Zd[d5d6Zd7d8Zd9d:Zd\d;d<Zd=d>Zd?d@ZdAdBZdCdDZ dEdFZ!dGdHZ"dIdJZ#dKdLZ$dMdNZ%dOdPZ&dQdRZ'dSdTZ(dUdVZ)dWdXZ*dYdZZ+eeee e!e"e#dZ,e$e%e&e'e(e)e+dZ-dS)]N)block_splitter)take) as_bin_str)flatten_multi_dim)chain sssssss)Point LineStringPolygon MultiPointMultiLineString MultiPolygonGeometryCollectionsssssssssssssss s s s s s s )2DZMZMccs"|] }dd|DVqdS)css|]}t|VqdSN)reversed.0xrC/var/www/Datamplify/venv/lib/python3.10/site-packages/geomet/wkb.py gsz.N)items)rwkb_maprrrrgsrrrr)cCsV|d}tjr t|g}|dk}|rtd|dd}nt|}t|}|||fS)aGet the GeoJSON geometry type label from a WKB type byte string. :param type_bytes: 4 byte string in big endian byte order containing a WKB type number. It may also contain a "has SRID" flag in the high byte (the first type, since this is big endian byte order), indicated as 0x20. If the SRID flag is not set, the high byte will always be null (0x00). :returns: 3-tuple ofGeoJSON geometry type label, the bytes resprenting the geometry type, and a separate "has SRID" flag. If the input `type_bytes` contains an SRID flag, it will be removed. >>> # Z Point, with SRID flag >>> _get_geom_type(b'\x20\x00\x03\xe9') == ( ... 'Point', b'\x00\x00\x03\xe9', True) True >>> # 2D MultiLineString, without SRID flag >>> _get_geom_type(b'\x00\x00\x00\x05') == ( ... 'MultiLineString', b'\x00\x00\x00\x05', False) True rr rN)sixPY3bytesr_BINARY_TO_GEOM_TYPEget) type_bytes high_bytehas_srid geom_typerrr_get_geom_typens   r,cCs|t|dS)a Dump GeoJSON-like `dict` to WKB and write it to the `dest_file`. :param dict obj: A GeoJSON-like dictionary. It must at least the keys 'type' and 'coordinates'. :param dest_file: Open and writable file-like object. N)writedumps)obj dest_filerrrdumps r1cCs t|S)z Load a GeoJSON `dict` object from a ``source_file`` containing WKB (as a byte string). :param source_file: Open and readable file-like object. :returns: A GeoJSON `dict` representing the geometry read from the file. )loadsread) source_filerrrloads r5TcCsh|d}|di}t|}|durt||d|d}ttt|dkr.td||||S)a Dump a GeoJSON-like `dict` to a WKB string. .. note:: The dimensions of the generated WKB will be inferred from the first vertex in the GeoJSON `coordinates`. It will be assumed that all vertices are uniform. There are 4 types: - 2D (X, Y): 2-dimensional geometry - Z (X, Y, Z): 3-dimensional geometry - M (X, Y, M): 2-dimensional geometry with a "Measure" - ZM (X, Y, Z, M): 3-dimensional geometry with a "Measure" If the first vertex contains 2 values, we assume a 2D geometry. If the first vertex contains 3 values, this is slightly ambiguous and so the most common case is chosen: Z. If the first vertex contains 4 values, we assume a ZM geometry. The WKT/WKB standards provide a way of differentiating normal (2D), Z, M, and ZM geometries (http://en.wikipedia.org/wiki/Well-known_text), but the GeoJSON spec does not. Therefore, for the sake of interface simplicity, we assume that geometry that looks 3D contains XYZ components, instead of XYM. If the coordinates list has no coordinate values (this includes nested lists, for example, `[[[[],[]], []]]`, the geometry is considered to be empty. Geometries, with the exception of points, have a reasonable "empty" representation in WKB; however, without knowing the number of coordinate values per vertex, the type is ambigious, and thus we don't know if the geometry type is 2D, Z, M, or ZM. Therefore in this case we expect a `ValueError` to be raised. :param dict obj: GeoJson-like `dict` object. :param bool big_endian: Defaults to `True`. If `True`, data values in the generated WKB will be represented using big endian byte order. Else, little endian. TODO: remove this :param str dims: Indicates to WKB representation desired from converting the given GeoJSON `dict` ``obj``. The accepted values are: * '2D': 2-dimensional geometry (X, Y) * 'Z': 3-dimensional geometry (X, Y, Z) * 'M': 3-dimensional geometry (X, Y, M) * 'ZM': 4-dimensional geometry (X, Y, Z, M) :returns: A WKB binary string representing of the ``obj``. typemetaN coordinates geometriesrzhEmpty geometries cannot be represented in WKB. Reason: The dimensionality of the WKB would be ambiguous.)r'_dumps_registry_unsupported_geom_typelenlistr ValueError)r/ big_endianr+r7exportercoords_or_geomsrrrr.s5   r.c Cst|}ttd|}|tkrd}n|tkrd}n tdt| |r*dnd}ttd|}|s<|ddd }t |\}}}d}|rWttd|}t d ||\}|} t |} | durft|t| } | ||| } |rd t|i| d <d d d|id| d<| S)aF Construct a GeoJSON `dict` from WKB (`string`). The resulting GeoJSON `dict` will include the SRID as an integer in the `meta` object. This was an arbitrary decision made by `geomet, the discussion of which took place here: https://github.com/geomet/geomet/issues/28. In order to be consistent with other libraries [1] and (deprecated) specifications [2], also include the same information in a `crs` object. This isn't ideal, but the `crs` member is no longer part of the GeoJSON standard, according to RFC7946 [3]. However, it's still useful to include this information in GeoJSON payloads because it supports conversion to EWKT/EWKB (which are canonical formats used by PostGIS and the like). Example: {'type': 'Point', 'coordinates': [0.0, 1.0], 'meta': {'srid': 4326}, 'crs': {'type': 'name', 'properties': {'name': 'EPSG4326'}}} NOTE(larsbutler): I'm not sure if it's valid to just prefix EPSG (European Petroluem Survey Group) to an SRID like this, but we'll stick with it for now until it becomes a problem. NOTE(larsbutler): Ideally, we should use URNs instead of this notation, according to the new GeoJSON spec [4]. However, in order to be consistent with [1], we'll stick with this approach for now. References: [1] - https://github.com/bryanjos/geo/issues/76 [2] - http://geojson.org/geojson-spec.html#coordinate-reference-system-objects [3] - https://tools.ietf.org/html/rfc7946#appendix-B.1 [4] - https://tools.ietf.org/html/rfc7946#section-4 r"TFz2Invalid endian byte: '0x%s'. Expected 0x00 or 0x01>binasciihexlifyencodedecoder,structunpack_loads_registryr'r;int) string endiannessr? endian_tokenr(r+r*rE srid_field data_bytesimporterresultrrrr2s<(     r2cCs td|)NzUnsupported geometry type '%s')r>)r+rrrr;Ns r;c Cst|}|dur t||}|d}|dur!t|dd}|r*t}d}d} n t}d}d} |ddd}||7}|durVt|}|rLtd |} ntd |} || 7}|d |7}||| fS) z| Utility function to get the WKB header (endian byte + type header), byte format string, and byte order string. NrEr">rBiz|d}t|}td|||\}}}|tj|g|R7}|S)aZ Dump a GeoJSON-like `dict` to a point WKB string. :param dict obj: GeoJson-like `dict` object. :param bool big_endian: If `True`, data values in the generated WKB will be represented using big endian byte order. Else, little endian. :param dict meta: Metadata associated with the GeoJSON object. Currently supported metadata: - srid: Used to support EWKT/EWKB. For example, ``meta`` equal to ``{'srid': '4326'}`` indicates that the geometry is defined using Extended WKT/WKB and that it bears a Spatial Reference System Identifier of 4326. This ID will be encoded into the resulting binary. Any other meta data objects will simply be ignored by this function. :returns: A WKB binary string representing of the Point ``obj``. r8r r<rirPra)r/r?r7coordsrb wkb_stringrf_rrr _dump_point{s rnc Csh|d}|d}t|}td|||\}}}|td|t|7}|D] }|tj|g|R7}q$|S)z Dump a GeoJSON-like `dict` to a linestring WKB string. Input parameters and output are similar to :func:`_dump_point`. r8rr %slrj) r/r?r7rkvertexrbrlrfrgrrr_dump_linestrings rqc Cs|d}|dd}t|}td|||\}}}|td|t|7}|D]} |td|t| 7}| D] }|tj|g|R7}q6q&|S)z Dump a GeoJSON-like `dict` to a polygon WKB string. Input parameters and output are similar to :funct:`_dump_point`. r8rr rorj) r/r?r7rkrprbrlrfrgringrrr _dump_polygons  rsc Cs|d}|d}t|}td|||\}}}tt|d} |r&t| } n t| ddd} |td|t|7}|D]}|| 7}|tj|g|R7}q=|S)z Dump a GeoJSON-like `dict` to a multipoint WKB string. Input parameters and output are similar to :funct:`_dump_point`. r8rr r NrDro r<rir_r^r'rJrKrPra) r/r?r7rkrprbrlrfrg point_typerrr_dump_multipoints  rvc Cs|d}|dd}t|}td|||\}}}tt|d} |r(t| } n t| ddd} |td|t|7}|D]"} || 7}|td|t| 7}| D] }|tj|g|R7}qSq?|S)z Dump a GeoJSON-like `dict` to a multilinestring WKB string. Input parameters and output are similar to :funct:`_dump_point`. r8rrr NrDrort) r/r?r7rkrprbrlrfrgls_type linestringrrr_dump_multilinestrings$   ryc Cs|d}|ddd}t|}td|||\}}}tt|d} |r*t| } n t| ddd} |td|t|7}|D]3} || 7}|td|t| 7}| D]} |td|t| 7}| D] }|tj|g|R7}qeqUqA|S)z Dump a GeoJSON-like `dict` to a multipolygon WKB string. Input parameters and output are similar to :funct:`_dump_point`. r8rrr NrDrort) r/r?r7rkrprbrlrfrg poly_typepolygonrrrrr_dump_multipolygon s*  r|c Cs|d}|d}|dd}t||d}|dd}|s#|ddd}|tvr,d}n|tvr5d}n|tvr=d }td |||\} } } | td | t|7} | |7} |D] } | t| |d7} qY| S) Nr9rr")r?rDrr r!rro) r.WKB_2DvaluesWKB_ZWKB_ZMrirPrar<) r/r?r7geoms first_geomrest first_wkb first_typerbrlrfrggeomrrr_dump_geometrycollection2s*       rcCs|rdnd}|tdkrtd|ttd|}nC|tdkr.td|ttd|}n/|tdkrJttd|ttd|}|dd n|t dkr]td |ttd |}t dt|d S) ah Convert byte data for a Point to a GeoJSON `dict`. :param bool big_endian: If `True`, interpret the ``data_bytes`` in big endian order, else little endian. :param str type_bytes: 4-byte integer (as a binary string) indicating the geometry type (Point) and the dimensions (2D, Z, M or ZM). For consistency, these bytes are expected to always be in big endian order, regardless of the value of ``big_endian``. :param str data_bytes: Coordinate data in a binary string. :returns: GeoJSON `dict` representing the Point geometry. rBrCr z%sddz%sdddrz%sdddd r6r8) r~rPrQrrrWKB_Mr=insertrdict)r?r(rXrVrkrrr _load_pointSs&             rc Cs|rdnd}d}|tvrd}n|tvrd}n|tvr%d}d}n|tvr-d}g}td|ttd|\} ttd ||}d d |} t t| ||} |r_| dd | | t ||krknq>t d t |dS)NrBrCFrr Tr!ro%sdrr r)r~rrrrrPrQrrr=rappendr<r) r?r(rXrVis_mrbrk num_vertsvert_wkbfmtvertrrr_load_linestring|s4            rc sP|rdndt|}d}|tvrd}n|tvrd}n|tvr)d}d}n|tvr1d}g}tdtt d|\} g}tdtt d|\}tt d |||} t | d } t j rmd d | D} n t j rwd d | D} t | |D]} fd d| D} |r| dd|| q|||t||krnqBtd|dS)NrBrCFrr Tr!rorcss|]}d|VqdS)Njoinrrrrrz _load_polygon..css$|] }ddd|DVqdS)rcss|]}t|gVqdSr)r%)ryrrrrrz*_load_polygon...Nrrrrrrs"cs g|] }td|dqS)z%sdr)rPrQrrVrr sz!_load_polygon..rr r)rIr~rrrrrPrQrrrr#PY2r$rrr<r) r?r(rXrrbrk num_ringsrrr verts_wkbvertsrrrrr _load_polygonsN                rc Csj|rdnd}t|}d}|tvrd}n|tvrd}n|tvr)d}d}n|tvr1d}|r6d}nt|}g}td |t t d|\} t t d |} t t d|} td |d |ft t d ||} t | } |rx| dd|r| t ksJ| t|dksJn| tksJ| dddt|dksJ|t | t||krnqKtd|dS)NrBrCFrr Tr!rror"z%s%srrrr rDr r)rIr~rrrrr^rPrQrrr=rrJr_rKrr<r) r?r(rXrVrrbrcrk num_points point_endianrurrrr_load_multipointsL            rcCs|rdnd}t|}d}|tvrd}n|tvrd}n|tvr)d}d}n|tvr1d}|r6d}nt|}td |t t d|\}g} t t d |} t t d|} |rl| t ksaJ| t |d kskJn| t ksrJ| ddd t |d ksJtd |t t d|\} || } t|d | t t d| |} tt| |} |r| D]}|ddq|| t||krnqKtd|dS)NrBrCFrr Tr!rror"r rDrrrrr)rIr~rrrrr^rPrQrrrJr_rKr=rrrr<r)r?r(rXrVrrbrcnum_lsrk ls_endianrwr num_valuesrvrrr_load_multilinestringsV              rcCs|rdnd}d}|tvrd}n|tvrd}n|tvr%d}d}n|tvr-d}|r2d}nt|}td |tt d|\}g} g} tt d |} tt d|} |rj| t ks_J| t |d ksiJn| t kspJ| ddd t |d ksJtd |tt d|\} t | D]D} g}td |tt d|\}t |D](} tt d ||}dd|}tt|||}|r|dd||q| |q|| t||krnqGtd|dS)NrBrCFrr Tr!rror"r rDrrrrrr)r~rrrrr^rPrQrrrJr_rKranger=rrr<r)r?r(rXrVrrbrc num_polysrkr{ poly_endianrzrrmrrrrrrrrr_load_multipolygon.s`                      rcCsVdd}dddddddddd|d }t||d ||ks)d }t|dS) NcSs&|dD] }|ddks|SqdS)Nr9r6rr)gcgrrrris  z)_check_dimensionality..first_geomcSs|dS)Nr8rrrrrosz'_check_dimensionality..cSs |ddSNr8rrrrrrrps cS|dddSrrrrrrrqcSrrrrrrrrrrcSs|ddddSrrrrrrrss)r r r rrrr6z'Cannot mix dimensionality in a geometry)r< Exception)rrbr first_verterrorrrr_check_dimensionalityhsrc Cs|rdnd}d}|tvrd}n|tvrd}n|tvr%d}d}n|tvr-d}g}td|ttd|\} t |}|rJt |dnt ||| |t ||kr[nq>t d |d S) NrBrCFrr Tr!ror)r6r9)r~rrrrrPrQrrr2rrr<r) r?r(rXrVrrbr9 num_geomsgeometryrrr_load_geometrycollection{s2            r)Tr).rLr#rP geomet.utilrrrr itertoolsrrJrKr`r~rrrr_rrr&r^r,r1r5r.r2r;rirnrqrsrvryr|rrrrrrrrrr:rRrrrrs         ( HU (#!%!)",04:"