Thank you for the fast reply, Tony.

I don't know why, but I just rechecked both frontend and backend, and now the location is there as it should be.

Good to know that it's supported, and that there are further possibilities if needed.

parsing locations works best if the locations in the input file are in a particular format.

Locations are parsed using the following format:
Location Name - Street, City, Country
or optionally
Location Name - Street, City, Country, Postcode

Hi geraint,

Is the lack of country a problem? I have exported an iCal file from my prod site in order to repopulate my dev site, and although the date/time and descriptive info displays properly, the location on the map is not displaying, neither on the main component view, nor in the detail view. I have "Support old style locations" set to true in the target site. I also have "Match Locations for iCal Imports" set to true. Are other any other switches that need to be set? If you need access to my site, tonyp may still have my login details from an earlier thread. Here is a sample of the iCal file:

BEGIN:VEVENT

UID:6fa15984609264afdf4c3d90803a6ca0

CATEGORIES:Tools for Action, Immigrant Rights, Constitutional Rights

SUMMARY:Resist Trump Tuesday, Asheville

GEO:-82.55792236;35.59406662

LOCATION:Asheville Federal Building, 151 Patton Ave., Asheville, NC, 28801, 

DESCRIPTION;ENCODING=QUOTED-PRINTABLE:\n\nEver wonder what you would have done during the civil rights movement? 

 Or anti-war protests? We're in a historic struggle right now for the future

  of this country, and we need to demand our Senators stand with us. Join me

  on Tuesday to demand our Senator publicly oppose Trump's cabinet nominatio

 ns and the unconstitutional Muslim ban.\n\n\nRSVP Here\n This event was imp

 orted from: http://actforward.net/component/jevents/eventdetail/117/-/resis

 t-trump-tuesday-asheville-geo-82-55792236-35-59406662?Itemid=1

DTSTAMP:20170215T162547Z

DTSTART;TZID=America/New_York:20170207T160000

SEQUENCE:0

TRANSP:OPAQUE

END:VEVENT

parsing locations works best if the locations in the input file are in a particular format.

Locations are parsed using the following format:
Location Name - Street, City, Country
or optionally
Location Name - Street, City, Country, Postcode

Notice we need a hyphen (-) between the location name and street entries/

geraint, the iCal file is an export from my production site. If the hyphen is required for import shouldn't the export be creating it? Is there any way to force it to do so?

Further, I did a regex search and replace in my iCal file to make most of the LOCATION: entries compliant, and still no joy. Eg. this location was not parsed successfully:

LOCATION:Loews Philadelphia Hotel - 1200 Market Street, Philadelphia, PA, US, 19107 

Is your production site using JEvents?

Do you have the Google maps API codes set up for the site you are importing to and in particular the codes to enable Geocoding?

Yes, both dev and prod are using JEvents, and JEvents Locations:

Prod - http://actforward.net/participate
Dev - http://actforward.hertzberg.info/participate

Geocoding is on and you can see GEO:-82.55792236;35.59406662 in the earlier code snip I posted.

Edit: Hi tonyp. I sent you a superuser UID and PWD along with a FTP login, in a private message two weeks ago in reference to another issue. Let me know if you can or can't find it. I don't want login info in a public post.

BTW, what restriction can be on the API key? I currently have Geocoding API key restricted to the domain as the referred URL, like I have with the Javascript API key.

Can you update your post with login details so we can take a look at this for you?

Many thanks
Tony

see your other post of this topic.