Skip to main content
7 events
when toggle format what by license comment
Jun 23 at 10:08 comment added Babel Indeed. So by default, Shapefiles can't handle this and using a cfg makes the already complicated handling of Shapefiles not easier. So if there are no strong reasons why to use the outdated Shapefile format, using Geopackage is easier, more flexible and has several other advantages over Shapefiles.
Jun 23 at 8:50 comment added Ian Turton But I think that is a baked in limitation of the (American) specification, rather than a problem with the character set which can be overcome with a cfg file
Jun 23 at 8:35 history edited Taras CC BY-SA 4.0
deleted 8 characters in body
Jun 22 at 16:13 history edited Babel CC BY-SA 4.0
added 306 characters in body
Jun 22 at 16:09 comment added Babel Yes, exactly for that reason Geopackage is preferable, as it does accept such fieldnames: tested with Geopackage and Shapefile - a fieldname in Khmer saves perfectly well in Geopackage, but not in Shapefile.
Jun 22 at 15:58 comment added Ian Turton It looks like it's the attribute names themselves that are failing rather than the contents of the attributes.
Jun 22 at 13:45 history answered Babel CC BY-SA 4.0