Empty SHAPE

Nessuno ha ancora preso questa issue.

**I'd like the spatial dataframes geometry to have empty geometry**

when reading data from database(sqls) we can often see empty geometry columns.

having an empty geometry
"Imagine that a system creates a trigger to insert a new row, than an webhook does an etl to get data and geometrie from an external api"

The geoaccessor can read empty geometries, but creates the row with None. And the column becomes object.
```python
geom = sdf.SHAPE.iloc[0]

geom.isEmpty
# would return True
```
Gracefully handle empty geom would be a good thing, if possible.

**Describe the solution you'd like**
Proposed Changes
I suggest that to implement the following changes:

Modify the spatial dataframe structure to accommodate empty geometries.

Ensure that operations on the dataframes (like transformations, visualizations, and exports, validation, svg) gracefully handle empty geometries.
Provide clear documentation on how empty geometries are represented and managed within the dataframes.
I believe that incorporating these changes will enhance the robustness and flexibility of our spatial data handling capabilities. I look forward to discussing this further and exploring the best ways to integrate this feature.

**Describe alternatives you've considered**
Implement ORM with sqlalchemy. Or geoaccessor and split the spatial dataframe.
**Additional context**

La issue non indica file o test specifici. Inizia dal percorso geoaccessor che legge i risultati SQL dal database e riproduci una geometria vuota in SHAPE; poi traccia il modo in cui la gestiscono trasformazioni, visualizzazioni, esportazioni, validazione e SVG. Il lavoro è completato quando le geometrie vuote sono rappresentate distintamente da None, la colonna della geometria rimane utilizzabile e il comportamento è documentato.

Scritto dal modello di indicizzazione a partire dal testo della issue.