The KML javascript handler assumes that you'll be using GML-style URLs, while many sources of KML data actually work by using the HTTP protocol provided by OpenLayers. I don't think that the protocol should be tied to the format anyway, it's making unnecessary assumptions about what users will be doing? I might be able to roll a patch fixing this, but it is probably something to implement correctly in respect to the plans for map presets.

Comments

zzolo’s picture

zzolo commented

I am not entirely sure what this is referring to (also not looking at the code), but will look into it further.

zzolo’s picture

zzolo commented
Status: Active » Postponed (maintainer needs more info)

Hey tmcw,

I am not actually sure what the difference and what needs to be fixed here. Do you have resources I can check out?

--
zzolo

tmcw’s picture

tmcw commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Never mind, this is an easy thing to fix by implementing a new layer type and the hooks in a different module.