iCalendar import missing location
Sorry I misspoke in my previous reply. The .ics file was so short and didn’t have a description that my scan of its contents missed that it actually does have VEVENT in it.
Anyway, to your question… The file contains:
This isn’t a valid location: https://www.google.com/maps/search/RÃ¸dovre/
I’m unclear exactly what you’re asking.
(no special characters)
https://www.google.com/maps/search/Roedovre/ does work, identifying it as https://www.google.com/maps/place/2610+R%C3%B8dovre,+Denmark/
Notice the URL is encoded so it doesn’t actually link to “Rødovre”
I actually tried to import test2.ics and it didn’t import even though it didn’t have any such characters in it. Is this what you experienced as well?
In speaking with our developers, the ø and other special characters are not an issue.
However, when both GEO and LOCATION are present in the .ics, we use the GEO and, in the case of your initially-shared test file, that GEO is not recognized by our reverse geocoding database.
Therefore, in your API, please try outputting only LOCATION and not also GEO and see if that works more how you’d want it to.
And, of course, please do let me know how this goes for you.
Sorry, I had a response to you that got lost amidst the back-and-forth with the development team… your .ics file does not validate at http://severinghaus.org/projects/icv/ so I downloaded one of our demo site’s event’s .ics file and modified its LOCATION to be Rødovre and the exported event’s GEO got in the way I guess.
First step is to make sure your .ics file validates, but be assured that the special character is not an issue.
Using the uploaded .ics file, this venue got created: https://cl.ly/2G2W1P1P3p0F
Using the iCalendar URL produced the same.
If your question/concern is regarding the actual address information missing, it’s because our importing requires more precise location information for that part to work.
Once a venue is imported, it’ll be titled whatever the LOCATION field is. If the LOCATION field is a full address–and our geo lookup can locate it–then it will come through the address fields as well.
Are you planning to have full addresses instead of just city names?
Well, good news (but bad news)… we finally tracked down a bug from all this testing. They’re actively working on the 2 issues they found.
I marked this thread as Pending Fix, which means it should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now.
I apologize for this issue and appreciate your understanding and patience.
This thread hasnt seen any activity for quite some time and we are not accepting further replies.
If you need further help with this or any other issue, please create a new topic (you can of course include a link to this one if that helps to provide additional context) and one of the team will be only too happy to help.