Overall, I have to admit, I'm finding the map component to be severely lacking. Thus far, following the directions at this Authoring Maps, I've successfully gotten a geoJSON file of the US, with Alaska and Hawaii. But I hate the placement of the Alaska and Hawaii shapes. I have found several other sites, offering much better geoJSON files, but not a single one of them has worked in the Kendo Map component. The fact that it's limited to geoJSON means it's only useful for geographical mapping, which really doesn't suite my needs either. I don't care about roads or streets, I just need a US map, with Alaska & Hawaii within decent spacing of the other states for sales figures,for maps showing active licenses, different categories of client clusterings. I've seen a lot of different Javascript libraries that allow to use SVG images for the maps, which this component doesn't.
I like how fast it is, I like the API into it, but as far as offering good customizable maps, it's severely lacking.
6 Answers, 1 is accepted
I'd appreciate it if you can send us location of the GeoJSON samples that didn't work. We should be able to see what's going wrong and try to rectify it.
The solution for moving Alaska and Hawaii closer to the contiguous states is usually a composite projection. It will typically move them below the south-west states, keeping coordinates straight.
A simple "2D" SVG or image is also an option. This is applicable in case of indoor areas, event venues and so on.
Please, cast your vote for this and any other features you find lacking on our UserVoice portal.
There's a lot of work to be done on the map and showing your interest will help us prioritize it.
Regards,
T. Tsonev
Telerik
I pilfered the geoJSON from another javascript based mapping library that uses geoJSON. I've attached it.
I'd love for SVG to be a valid option because SVG is sooo much easier to get a hold of as well as create as opposed to the geoJSON format. An image wouldn't work nearly as well because I need to color states for different things. Here's an example of what I'm currently using via SVG:
https://www.dropbox.com/s/g2c2o96l748d183/Map.png?dl=0
SVG allows for better labeling, better control of the overall layout, etc...
I've put it on UserVoice portal, but nobody has voted for it, so I guess nobody is interested in mapping for anything other than street maps... It's a shame because there's so much potential in providing custom mapping for things other than just geographical and street data. It's so difficult to get as well, without having to download oodles of ancillary applications as denoted by that Authoring article I linked to previously.
The GeoJSON in question defines its own Coordinate Reference System. It actually defines 3 of these. It seems to be non-standard specifically designed for use in HighCharts.
It's not that it's invalid GeoJSON, but it will require some work to support. The GeoJSON files around the net typically use "urn:ogc:def:crs:OGC:1.3:CRS84" as a CRS. That's what we support as well.
The case with mapping non-geospatial data is perfectly valid. UserVoice might not be a good indicator, as we get a lot of requests via the support and other channels.
It's enough for us to put it on the table and consider it during our planning sessions.
Regards,
T. Tsonev
Telerik
What would be some other sources for geoJSON data? Something preferably that didn't include the necessity of download a bunch of other apps to extract said geoJSON data? Specifically, something that included the US States (including D.C.) with Alaska and Hawaii under the US States, such as is displayed on on this map? But in geoJSON format instead? Or perhpas it'd be way cool if Telerik provided some default maps, similiar to some of the other mapping components out there...
http://thumbs.dreamstime.com/z/united-states-map-7719126.jpg
http://archive.ahrq.gov/policymakers/child-state-country/usamap2.gif
We lack the necessary projection to properly display a composite map of the US with altered positions for Alaska and Hawaii.
If we get this running there shouldn't be a problem using any available GeoJSON file with WGS84 coordinates (i.e. most).
Our table is pretty much full for the release in May, but this is something that we'll keep in mind during our planning sessions.
Regards,
T. Tsonev
Telerik