bennyb

Hi Kiran,

Thank you Kiran for pin-pointing me to that.
Basically that was one issue.

There have been a total three issues with the CSV and not a core error within your product(s), for documentation reasons i am documenting them here.

Possible CSV-errors / -issues:

1.) malformated lines in the CSV through the manual conversion process
2.) malformated latitude/longitude definitions and entries with “FAILED”, through the mass-processing of the data to get the lat/lang coordinates

…and the last one was a tricky one, as it occurred AFTER the check with OpenOffice:
3.) certain lat/lang data haven been transformed as a definition like 48.099 got transformed to 48099 but THAT is what makes the map display ZERO results on the map and what breaks actually the map. (see screenshots attached). This might be an issue just with some localisations and number definitions within OpenOffice, but it caused a lot of headache sadly…

You could maybe call that last issue an issue of your map display, but it is really related to the CSV import, i can see and understand that. But maybe you could filter such things (wrong lat/long) out? If not during the import, maybe but excluding them at least from the result set? Not sure…

If possible i would like to suggest – for one of the next versions – a possible update of the import process/module(s).

a) check every line for consistency and maybe display the line number(s) which are inconsistent – in my case about 15-20 lines. That would have saved me A LOT of time

b) and/or an option to exclude wrong formatted lines from the import automatically/automagically

c) an option to import CSV address lists without the need to pre-define the long/lat fields and an automated processing through GeoDir (which searches&adds the long/lat), maybe as an separate (sellable) plugin?

I know all that isn’t easy to accomplish, rather complex, but the import process is currently a bit of a painful/hard way. Having another 2-3 upcoming projects like this (with CSV imports, i know it will cause me issues, and i am sure other (potential) customers face those as well.

All that said, THANK YOU FOR THE SUPPORT, only your support made it possible for me to find/identify the/my errors within the CSV. Still i hope some of my a-c ideas of the import process become real in one of the next versions 😉

So thanks and talk to you probably (sorry in advance) soon,
Benjamin

Hi Kiran,

i have tested now even deeper by setting up a separate domain & GeoDir. With the following results:
below 4XX entries it works, but not much above…

i retried at the mentioned domain and just deleted the last 432 entries and IT WORKS, BUT how can i now add the full result set?

I think there can be just two options:
1.) plugin issues with more the 400 results
2.) issues with the import data.

Will sent you my import data set as a private message, hope that is fine?

Cheers,
Benjamin

Of course you are right … comma, not semicolon, i dreamed it tonight 🙁 And yes, ok, i will create separate tickets from now, just didn’t want to spam, very sorry.

Thank You Stiffen, great help for dump people like me.