New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem importing uppercase P in Omeka Coverage into Neatline #288
Comments
Weird, so "POINT" fails in import; what happens if you wrap that in a GEOMETRYCOLLECTION()? |
To be more precise, the uppercase P does not import when it is the first letter of the first Coverage entry. Philadelphia does not import if it is the first entry. Chester, PA as the first entry, plus Philadelphia as the second entry does import. |
Bizarre. I suspect this line from the geoPHP library: https://github.com/scholarslab/Neatline/blob/master/lib/geoPHP/geoPHP.inc#L266 I'll investigate tomorrow. |
Records with an uppercase P in the Omeka Coverage field don't import into Neatline. I tried three different installations of Omeka 2.1.4 with Neatline 2.2.1. A workaround is to import the record without the P and then add the P in Omeka after the import. After adding the P, sometime modifications to the Neatline record will save and sometimes they won't. I use an iMac with Safari. I tried a P in the Omeka Description field and had no problems.
The text was updated successfully, but these errors were encountered: