Describe the bug
Currently, when the Place CSV importer encounters a row with no coordinates given for the lat and long fields, it seems to be importing these with a (0,0) or null geography.
This is different from simply adding a Place via the Terrastories UI and not providing latitude and longitude -- these places don't show up on the map, as expected and desired.
Delete the lat/long coordinates for one of the place rows and save the CSV.
As a logged in admin or editor user for a community, navigate to the Places page in the back end (/admin/places?locale=en)
Import the CSV you just edited
The row will still be imported into Terrastories with null values, and showing up at 0,0 (off the coast of Africa) on the Terrastories map.
Expected behavior
Let's make it so that the importer does not add any null values to lat/longs when a Place doesn't have any in the CSV, resulting in wonky null island placement.
Describe the bug Currently, when the Place CSV importer encounters a row with no coordinates given for the
lat
andlong
fields, it seems to be importing these with a (0,0) or null geography.This is different from simply adding a Place via the Terrastories UI and not providing latitude and longitude -- these places don't show up on the map, as expected and desired.
To Reproduce Steps to reproduce the behavior:
admin
oreditor
user for a community, navigate to the Places page in the back end (/admin/places?locale=en)null
values, and showing up at 0,0 (off the coast of Africa) on the Terrastories map.Expected behavior Let's make it so that the importer does not add any
null
values to lat/longs when a Place doesn't have any in the CSV, resulting in wonky null island placement.Screenshots