How to prepare a GEOJSON file for bulk zone import

In the ATOM Mobility Vehicle Sharing Module you can easily upload any zone type in bulk in order to save time on manual zone creation in the system instead.

What You’ll Need

A web browser (Chrome, Firefox, etc.)
The exact parking zone locations you want to define
Access to geojson.io
Access to your ATOM Mobility admin panel (for later upload)

Step 1: Open geojson.io

Go to https://geojson.io
You will see:
- A map in the center
- A toolbar on the right
- A JSON editor panel on the left

Step 2: Choose the Correct Drawing Tool

Parking zones are usually areas, not single points.

On the right-side toolbar, select:
- Polygon tool (⬠) → for zones with multiple corners
- or Rectangle tool (▭) → for simple rectangular zones

✅ Recommended: Use Polygon for precise zone boundaries.

Step 3: Draw the Parking Zone on the Map

Click on the map to start drawing the zone
Continue clicking to add corner points
When finished:
- Click the first point again to close the shape
- The zone will highlight on the map

Repeat this step if you have multiple parking zones.

Step 4: Add Required ATOM Mobility Parking Zone Properties

ATOM Mobility requires specific properties to be defined for each parking zone. These properties control zone identification, vehicle eligibility, and availability time.

1. Open Zone Properties

Click on a drawn parking zone on the map
In the popup, click “Edit properties”

2. Add Required Properties

Add all required properties exactly as shown below.

Required Properties Example

{   "atom_id": "parking_zone_001",   "vehicle_types": ["scooter", "bike"],   "working_time": {     "start": "00:00",     "end": "23:59"   } }

3. Property Definitions

Property	Required	Description
`atom_id`	✅ Yes	Unique identifier for the parking zone. Must be unique across all zones. Use lowercase letters, numbers, and underscores only.
`vehicle_types`	✅ Yes	List of vehicle types allowed to park in this zone. Must be an array.
`working_time`	✅ Yes	Time window when parking is allowed in this zone (24-hour format).

4. Allowed Values

`vehicle_types`

Use only vehicle types configured in your ATOM Mobility platform, for example:

["scooter"] ["bike"] ["car"] ["scooter", "bike"]

`working_time`

Time format: HH:MM (24-hour)
Full-day availability example:

{   "start": "00:00",   "end": "23:59" }

Limited hours example:

{   "start": "08:00",   "end": "22:00" }

5. Optional (Recommended) Additional Properties

You may also include optional properties for clarity:

{   "name": "Downtown Parking Zone",   "description": "Parking allowed near main square" }

ℹ️ Optional properties do not affect system behavior but help with zone management.

Important Notes

⚠️ atom_id must be unique
⚠️ vehicle_types must be an array, not a string
⚠️ working_time must include both start and end
⚠️ Do not use special characters or spaces in property keys

Step 5: Verify Geometry Type

Ensure that:

Parking zones are saved as:
```
"type": "Polygon"
```
Not Point or LineString

ATOM Mobility requires polygons for parking zones.

Step 6: Review the GeoJSON Structure

On the left panel, confirm:

The root object is:
```
"type": "FeatureCollection"
```
Each parking zone is a separate Feature
Coordinates are correctly nested

Example structure:

{   "type": "FeatureCollection",   "features": [     {       "type": "Feature",       "properties": {         "name": "Downtown Parking Zone",         "type": "parking"       },       "geometry": {         "type": "Polygon",         "coordinates": [...]       }     }   ] }

Step 7: Export the GeoJSON File

Click Save (top menu)
Choose GeoJSON
Download the file to your computer
Name it clearly, for example:
```
parking_zones_cityname.geojson
```

Step 8: Upload to ATOM Mobility Platform

Log in to your ATOM Mobility Admin Panel
Navigate to (use another zone type section depending on your needs):
```
Vehicle Sharing → Zones / Parking Zones
```
Select Upload GeoJSON
Upload your saved .geojson file
Validate and save the configuration

Best Practices

✅ Draw zones slightly larger than the real area to avoid GPS inaccuracies
✅ Avoid overlapping parking zones unless explicitly required
✅ Use clear and consistent naming
✅ Test parking behavior in the app after upload

Common Mistakes to Avoid

❌ Using points instead of polygons
❌ Forgetting to close the polygon
❌ Uploading a file that is not valid GeoJSON
❌ Missing required properties