This merges in the work I've done on esri2geo you may want to not do a strait merge as this overwrites most of your stuff and instead use this as a template but the improvements include:
I actually started mine a while ago but the use case fell through and I never finished the corner cases, until your tool inspired me to finish it.
added git ignore
merge in esri2open
added a few more todos
these are stellar! nice work. i am going to play w/ these, and merge them. what i might do, is a test, get all the right code in place, merge the pull to make the project clean, then overwite the resulting merge w/ hand edited code. i am likely just to do this in phases over time. hope you don't mind if i keep this open for a while. let me know what you think.
That is probably a wise choice, in my attempt to make it as modular as possible the control flow got somewhat complex, but it's paying off adding a new format in is pretty easy, I did some work on sqlite support on another branch.
The three scripts are their own files because as far as I can tell that's the only way you can do it it in arcgis.
i am also a big believer in the kiss principle. right now the structure is pretty simple and 'works as advertised' (attrib - James Fee). would love to try to stay to that principle. not saying what you have doesn't, just going to move slow.
most of the complexity really came from me trying to make it modular, without actually using modules, I need to test this when I get to a windows computer tomorrow, but this should make it easier to take bits on their own.
I reorganized it so that all of the file specific code is in it's own file, this makes it it even more modular and should make it easier to add more file types or geometry options. I finished the last bit on a computer without arcMap so no testing of that until monday.
organized it into a packaged module
I'm just going to close this and we can deal with specific features to improve in their own issues
sorry, been slammed, and just haven't gotten to it. you sure about the close?
I did some radical changes so that even if we were to merge we'd probably want a new pull request
specifically I was working on sqlite and reorganized everything so that I could add in more, realized I made everything far to complicated and reorganized them again to simplify things, I was more afraid that you were getting an alert every time I pushed a commit.
sqlite working! (for points at least)
lines somewhat work
split out prepare
I'm going on vacation next week so I'm not going to be able to work on it so here's a status report:
The structure is set up to have three phases:
the idea behind this is to let multiple feature classes that couldn't be merged in ESRI (e.g. routes and stations) be merged into one output file by opening it once, writing multiple files in and then closing it up, so things related to geometry are in step two.
and then we need to remember to import the split of function
rings and polys have multiple parts in wkb
some work on the wrong branch
sqlite lines and multipoints are working
integers are not blobs
multi line in sqlite works
multi poly works in sqlite
sorry for leaving this for so long. i am taking a look at it. i got git out of synch with the merge i just accepted, so might need to do some jujitsu here. thanks for your patience
merge in master
no problem, the toolbox is going to be the main problem because the other file you have I don't have, I can do a merge on my end which should make it easier for you.
I went back and looked and the json meta data standards apply to catalogs not to the individual data pieces.
thats right. my logic here is that making data available as part of a web ecology, is remarkably helpful. huge lists of download files, WMS or other assets are moderately helpful, but when JSON (geoJSON) is posted as a URL/I, then the data is naturally part of the web, w/o any additional overhead, eg. software/hardware (arguable for sure but..). i'll be able to do the toolbox thing. again massive apologies for the delay.
yeah at the moment trying to get ESRI stuff out onto the web is not easy, most of my work flows historically had a "save to shapefile, open with quantum gis" step in them.
its on me. am sorry. sigh. hopefully this week.
no worries, and I have been dog fooding my branch and my geojson repo was made with this with no problems
so i finally just did a quick couple of tests. your branch works great. i don't think i need to make any edits at all. you ok w/ the current readme etc? anything else before i accept?
nothing on my end looks good.
k; great. for some reason i thought i needed to do something to the .tbx, but you got that nailed. am checking one last thing. nice work. (and nice write up in the atlantic)
Calvin, congrats. nice work!