Updated — You Can’t Edit Spatial RDBMS with ArcGIS for Desktop without SDS
So the answer is? No.
From the Esri Support Forums: Edit spatial data with “ArcGIS for Desktop 10.1” in non-SDE RDBMS systems?
ArcGIS Server 10.1 will include a new technology component called Spatial Data Server (SDS). It is a separate installation from ArcGIS Server and will be included with all editions of ArcGIS Server. SDS is a low-memory footprint application that enables you to publish feature services of your vector data stored in a database or geodatabase. SDS will allow you to edit spatial data in a standard database and does not require ArcSDE technology. Editing for SDS is done via the REST API only which ArcMap does not support at this time [editors note: see below].
Oh snap, not only can you not edit spatial data in other RDBMS without Esri’s Spatial Data Server, you can’t even do it via ArcGIS for Desktop. [editors note: see below] To be fair though, Esri’s business model is built on being the middle man to everything.
‘I don’t know how this whole business started Of me thinkin’ that I could edit PostGIS But if you think that we’d be better parted It’s gonna hurt me but I’ll break away from you`
The latest:
Craig Williams clarifies a key point:
Derek’s comments about ArcGIS for Desktop 10.1 not being able to edit SDS are incorrect. ArcGIS for Desktop 10.1 can edit SDS and all other types of ArcGIS feature services. These edits are performed via the REST API for SDS and hosted feature services.
So what does that mean? Says Craig
you connect to SDS, drag the service into the map and it draws via REST calls. To edit you check out / check in
So the final word on this is that you still need middleware to get this done, but you don’t need ArcSDE anymore. Esri views editing spatial databases differently that many of us do, I don’t fault their thinking too much on this, but 99.9% of the time in the real world no one cares about deltas. So to fix my thoughts from above:
Oh, snap, you can’t edit spatial data in other RDBMSs without Esri’s Spatial Data Server.
You Can Go Home — Planet Geospatial Edition
So about a year ago, something happened with my old hosting service. They made some backend change where they switched out the version of Python that worked with all my websites, to a weird flavor that basically broke everything. So I had a decision to make, I had to move Planet Geospatial to a new host and get everything set up again. The only mistake I made back then was thinking I was smarter than I am. Rather than just migrate the code of Planet Geospatial, I’d convert the service into a Wordpress site using FeedWordPress. I exported the feeds and easily got Wodpress working as well as the plugin. Everything looked great…
BBQ
You many have noticed a couple things about Planet Geospatial in the past year. First off the site was slow as a dog, basically PHP ran every time you accessed the site and checked to see if any of the hundreds of feeds needed to be updated. If so it updated the feed in the database which by itself wasn’t too slow, but coupled with people accessing the site, things were very pokey. On top of it, the entries in Planet Geospatial sometimes pointed to the Planet Geospatial website itself and not the actual blog location. This meant that you couldn’t get to whatever article you wanted to read. The feed parser choked on a couple feeds and generally these were the ones that were updated often.
Last week I decided I couldn’t take it more. The Wordpress version of Planet Geospatial had been under my skin for months and people started noticing that it wasn’t working right. Clearly something had to be done. So I did what I should have done a year ago, moved Planet Geospatial back to running on the Planet Venus aggregator. As of this morning, the DNS has been updated[ref]I would appear I brought down both Planet Geospatial and the NY Times last night[/ref] and things appear to be running perfectly.
This all taught me a lesson. Never use a CMS for anything that is important to you. Wordpress, Drupal, SharePoint, etc will do nothing but disappoint you. That’s why I’m going to convert my blog here in the next month or two away from Wordpress to a flat file Markdown formatted system built using either Blosxom[ref]Going back to my roots with Perl[/ref] or Marco’s Second Crack if he ever releases it. Blogging will be nothing but zen…
Update: @tooshel points out that Octopress might just be what I’m looking for.
You Can Go Home — Planet Geospatial Edition
So about a year ago, something happened with my old hosting service. They made some backend change where they switched out the version of Python that worked with all my websites, to a weird flavor that basically broke everything. So I had a decision to make, I had to move Planet Geospatial to a new host and get everything set up again. The only mistake I made back then was thinking I was smarter than I am. Rather than just migrate the code of Planet Geospatial, I’d convert the service into a Wordpress site using FeedWordPress. I exported the feeds and easily got Wodpress working as well as the plugin. Everything looked great…
BBQ
You many have noticed a couple things about Planet Geospatial in the past year. First off the site was slow as a dog, basically PHP ran every time you accessed the site and checked to see if any of the hundreds of feeds needed to be updated. If so it updated the feed in the database which by itself wasn’t too slow, but coupled with people accessing the site, things were very pokey. On top of it, the entries in Planet Geospatial sometimes pointed to the Planet Geospatial website itself and not the actual blog location. This meant that you couldn’t get to whatever article you wanted to read. The feed parser choked on a couple feeds and generally these were the ones that were updated often.
Last week I decided I couldn’t take it more. The Wordpress version of Planet Geospatial had been under my skin for months and people started noticing that it wasn’t working right. Clearly something had to be done. So I did what I should have done a year ago, moved Planet Geospatial back to running on the Planet Venus aggregator. As of this morning, the DNS has been updated[ref]I would appear I brought down both Planet Geospatial and the NY Times last night[/ref] and things appear to be running perfectly.
This all taught me a lesson. Never use a CMS for anything that is important to you. Wordpress, Drupal, SharePoint, etc will do nothing but disappoint you. That’s why I’m going to convert my blog here in the next month or two away from Wordpress to a flat file Markdown formatted system built using either Blosxom[ref]Going back to my roots with Perl[/ref] or Marco’s Second Crack if he ever releases it. Blogging will be nothing but zen…
Update: @tooshel points out that Octopress might just be what I’m looking for.
Planet Geospatial and the DNS
UPDATE: Nothing fixes the DNS like a good night sleep. Planet Geospatial is up and running. Let me know on Twitter if you notice any issues.
In the spirit of no good deed goes unpunished, the internet is giving me the preverbal middle finger on my move of Planet Geospatial to a new host and a new backend. Some of you may see the old website built on Wordpress and some of you may see the new (Well Planet Geospatial used to be based on Venus, but my old host screwed up Python and I had to migrate it to Wordpress. That was a big mistake and I’ve regretted it ever since. This is to make up for thinking PHP is a good choice for any website scripting language.) website built on Venus.
I picked the wrong week to quit PHP!
The Wrong Week
So for now Planet Geospatial goes 404, 500 or works perfectly and you’re wondering why I’m complaining.
Use this backdoor into Planet Geospatial until planetgs.com gets updated on the interwebs.
Planet Geospatial and the DNS
UPDATE: Nothing fixes the DNS like a good night sleep. Planet Geospatial is up and running. Let me know on Twitter if you notice any issues.
In the spirit of no good deed goes unpunished, the internet is giving me the preverbal middle finger on my move of Planet Geospatial to a new host and a new backend. Some of you may see the old website built on Wordpress and some of you may see the new (Well Planet Geospatial used to be based on Venus, but my old host screwed up Python and I had to migrate it to Wordpress. That was a big mistake and I’ve regretted it ever since. This is to make up for thinking PHP is a good choice for any website scripting language.) website built on Venus.
I picked the wrong week to quit PHP!
The Wrong Week
So for now Planet Geospatial goes 404, 500 or works perfectly and you’re wondering why I’m complaining.
Use this backdoor into Planet Geospatial until planetgs.com gets updated on the interwebs.
Oh Boy, Maybe You Can’t Edit Spatial Databases Without ArcGIS for SDE
So the Esri UC Q&A seemed to show that you could not only direct connect to just about any spatial RDBMS, but edit as well. In that spirit, we started to think tools such as zigGIS were no longer needed. Well Bill Dollins asks Esri for some clarification on the matter because the scuttlebutt is that you may still need SDE for editing of spatial databases.
Look, there are times when organizations need SDE. But there are times when SDE is a middle man that has no purpose other than to drive revenues for a company. Let’s not screw this up Esri, let ArcGIS for Desktop and ArcGIS for Server 10.1 edit spatial RDBMSs directly. The proletariat is restless, you don’t need a revolution on your hands.
