I'm trying to use
JMP Add-In "KML Polygon Importer" (https://community.jmp.com/t5/JMP-Add-Ins/KML-Polygon-Importer/ta-p/21446)
cb_2016_us_zcta510_500k.kml file from US Census site (https://www.census.gov/geo/maps-data/data/kml/kml_zcta.html)
I get the pop-up the gives me an ETA of 45min; it never finished so I let it run over night and it still did not complete- I actually get a 'Not Responding' in popup border.
I imported Census' cb_2016_us_county_500k.kml just fine; converted into:
(Converted from KML 1)cb_2016_us_county_500k(Points).jmp (1KB)
(Converted from KML 1)cb_2016_us_county_500k-Name.jmp (148KB)
(Converted from KML 1)cb_2016_us_county_500k-XY.jmp (40,602KB)
Is the problem that cb_2016_us_zcta510_500k.kml is too big (176,907KB) and cb_2016_us_county_500k.kml (31,294KB) is smaller so JMP can import and increase the size to 40,602KB as above?
If the zcta file is too big, is there any way to split it into smaller sizes? I usually use SAS for mapping (.shp files, etc), but I figured I'd try using JMP's Web Mapping Service (WMS) add-in (https://community.jmp.com/t5/JMP-Add-Ins/WMS-Explorer-Add-In/ta-p/21334). to try and layer in different base map styles.
Thanks for the reply!
I have imported census's
tl_2016_us_zcta510.dbf / tl_2016_us_zcta510.shp
files successfully to create
tl_2016_us_zcta510-Name.jmp and tl_2016_us_zcta510-XY.jmp
I was hoping to just use 1 type of file for all programs I use (SAS, JMP, Google's Fusion Maps, etc); KML files seemed like the answer. One raw source file across each would make things a lot simpler... downloading different files from Census, making sure the resolutions match, converting XY's as needed, projecting, trying to share interactive maps depending on browser/ people's preferences etc can be overwhelming and I wanted to streamline as much as I could/ make it as simple as possible so the code/ process is easier for people I work with to understand.
It seemed like the KML file would be no problem; just trying to figure out why it doesn't import into JMP using the add-in...
Not sure if this'd matter but cb_2016_us_zcta510_500k.kml does weird things after converting to a .csv (it's like an end of line char CR vs LF or delimiter problem, or it could be the process to convert to .csv is also broken)...
Thanks for dbf/ shp help!