Hi Sharad, If you have to import the data into a web-based backend, then your programmers will be most comfortable with: GeoJSON format. Because : It's a simple text/json format which can even be opened as raw text, and so there are many different ways to load it in a program and use data from it. And this will also support Devnagri columns (which become property keys here) same as geopackage.
Another thing to look out for: Ensure that the database being used by the backend has the same UTF-8 encoding set. -- Cheers, Nikhil VJ https://nikhilvj.co.in On Mon, Dec 4, 2023 at 3:56 PM Sharad Lele <sharad.l...@gmail.com> wrote: > Thanks, Ujaval. Yes saving as .geopkg works (saves the field names in full > and displays properly upon reopening). This is the only solution that has > worked so far. > > But I am not sure this is going to work for us in this particular > situation where we are then using the file in postGIS to display in a > webGIS. Let me ask our webGIS person. > > Sharad > > On Monday, December 4, 2023 at 3:10:18 PM UTC+5:30 Ujaval Gandhi wrote: > >> Use the geopackage format. It's a much better modern format without the >> limitations of shapefiles. The default encoding would be UTF-8 and it >> should work. Tested with a new geopackage layer and it is able to create >> column names and values in Devanagri script >> https://i.imgur.com/2prELf6.png >> <https://mailtrack.io/link/b7757e0a651e8afed7ee4756ff4cbf155cd0a533?url=https%3A%2F%2Fi.imgur.com%2F2prELf6.png&userId=8747767&signature=9f333ff36f736872> >> --- >> Ujaval Gandhi >> Spatial Thoughts >> www.spatialthoughts.com >> <https://mailtrack.io/link/43de97ab1302774e567fc413805c61bb36bd8af8?url=http%3A%2F%2Fwww.spatialthoughts.com&userId=8747767&signature=904253fcbc9b4da4> >> >> >> >> On Mon, Dec 4, 2023 at 2:36 PM Sharad Lele <shara...@gmail.com> wrote: >> >>> The shapefile encoding is set to UTF-8. But any edits to variable names >>> only last as long as I don't save the file. Save and reopening results in >>> going back to the same truncated/funny display as above [image: >>> Screenshot Layer properties.jpeg] >>> >>> On Monday, December 4, 2023 at 2:17:41 PM UTC+5:30 Dilawar Singh wrote: >>> >>>> I found this >>>> https://gis.stackexchange.com/questions/381308/how-to-change-qgis-3-default-encoding. >>>> >>>> >>>> The file you are loading may have a different encoding that QGIS3. You >>>> have to verify this manually and make sure that QGIS3 and file encoding is >>>> the same. >>>> >>>> I am guessing the while QGIS3 is using utf-8, the file that you are >>>> loading may be utf-16 encoded. Not sure if there are automated tools that >>>> can convert UTF-16 files to UTF8 file while preserving unicode ( >>>> https://superuser.com/questions/1786434/convert-utf-16-le-to-utf-8-in-windows-via-command-line >>>> ). >>>> >>>> best, >>>> Dilawar >>>> >>>> >>>> >>>> ---- On Mon, 04 Dec 2023 14:05:01 +0530 *Sharad Lele >>>> <shara...@gmail.com>* wrote --- >>>> >>>> Just to clarify/muddy the situation: I am able to enter long Devanagari >>>> text in the District/Jila column without any problems. It is the >>>> column/field name itself that I run into problems, which may have to do >>>> with the 8 characteri limit? >>>> >>>> [image: Screenshot QGIS devanagari field names.jpeg] >>>> >>>> >>>> On Monday, December 4, 2023 at 1:57:04 PM UTC+5:30 Sharad Lele wrote: >>>> >>>> Thanks, Dilawar. The article was very interesting/useful. But for a >>>> simpleton like me, the question then is: How do I ensure that QGIS3 in >>>> particular is using UTF-8 encoding every time? >>>> >>>> Sharad >>>> >>>> On Monday, December 4, 2023 at 1:31:28 PM UTC+5:30 Dilawar Singh wrote: >>>> >>>> The answer is not going to be simple. >>>> >>>> Make sure that every time you save or open the file, the application >>>> uses encoding utf-8. Microsoft uses another weird encoding called utf-16 ( >>>> https://en.wikipedia.org/wiki/UTF-16). Stay away from utf-16 it if >>>> you want to copy-paste anything from the web or web-based tools. >>>> >>>> Long answer: >>>> https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/ >>>> >>>> best, >>>> Dilawar >>>> >>>> >>>> >>>> ---- On Mon, 04 Dec 2023 13:24:28 +0530 *Sharad Lele >>>> <shara...@gmail.com>* wrote --- >>>> >>>> >>>> Hi folks, I am using QGIS and I want to create variable names in >>>> Devanagari (for instance जिला instead of District). If I create a new >>>> column in the attribute table and enter the column name in Devanagari using >>>> Microsoft Indic Language Tool on my computer, it seems to work (जिला is >>>> shown as the column name). But the moment I save the edits and reopen the >>>> attribute table, this gets truncated into something like जिल?. The last >>>> character is not really a question mark, something more complex. >>>> >>>> Any suggestions for making the column names appear and save properly in >>>> Devanagari? (The same would be true for Kannada or other scripts, I am >>>> sure). >>>> >>>> Sharad >>>> >>>> >>>> -- >>>> Datameet is a community of Data Science enthusiasts in India. Know more >>>> about us by visiting http://datameet.org >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "datameet" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to datameet+u...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/datameet/b7074482-2d88-4762-8765-eb8b55bee3b0n%40googlegroups.com >>>> <https://groups.google.com/d/msgid/datameet/b7074482-2d88-4762-8765-eb8b55bee3b0n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> >>>> >>>> >>>> -- >>>> Datameet is a community of Data Science enthusiasts in India. Know more >>>> about us by visiting http://datameet.org >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "datameet" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to datameet+u...@googlegroups.com. >>>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/datameet/29ffbab3-117a-4a67-8988-ae253db7e2cbn%40googlegroups.com >>>> <https://groups.google.com/d/msgid/datameet/29ffbab3-117a-4a67-8988-ae253db7e2cbn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> >>>> >>>> -- >>> Datameet is a community of Data Science enthusiasts in India. Know more >>> about us by visiting http://datameet.org >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "datameet" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to datameet+u...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/datameet/bbcbdfe6-6f43-47a9-a84d-c1fd27f65af4n%40googlegroups.com >>> <https://groups.google.com/d/msgid/datameet/bbcbdfe6-6f43-47a9-a84d-c1fd27f65af4n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > Datameet is a community of Data Science enthusiasts in India. Know more > about us by visiting http://datameet.org > --- > You received this message because you are subscribed to the Google Groups > "datameet" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to datameet+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/datameet/7a1d4771-a606-451b-8f1d-3d706fcbb360n%40googlegroups.com > <https://groups.google.com/d/msgid/datameet/7a1d4771-a606-451b-8f1d-3d706fcbb360n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Datameet is a community of Data Science enthusiasts in India. Know more about us by visiting http://datameet.org --- You received this message because you are subscribed to the Google Groups "datameet" group. To unsubscribe from this group and stop receiving emails from it, send an email to datameet+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/datameet/CAH7jeuMp_SN3Oy9Xagycx8yqAUC9RFE_hoNiSkfR16FWfbmnbg%40mail.gmail.com.
