POST
|
For anyone curious, I figured out what was going on. The mosaic when brought into a WGS 1984 map lined up perfectly. When I brought it into a NAD 1983 map and let it re-project on the fly (which is what I had been doing) it was off by 3-5 feet. When I brought it into a NAD 1983 map and instead set the transformation using WGS_1984_(ITRF00)_To_NAD_1983 it came in fine.
... View more
04-11-2018
08:41 AM
|
2
|
2
|
4028
|
POST
|
1. The shift still occurs when only one raster is added. 2. The datum is D_WGS_1984 for both mosaic and raster.
... View more
04-10-2018
03:30 PM
|
0
|
0
|
2204
|
POST
|
Also, the raster info function and the .jp2 raster contents re the same.
... View more
04-10-2018
02:39 PM
|
0
|
0
|
1824
|
POST
|
04-10-2018
02:07 PM
|
0
|
0
|
1824
|
POST
|
04-10-2018
02:05 PM
|
0
|
3
|
2204
|
POST
|
I'm not seeing the georeferencing components in properties... Where in environments might I find where to define the decimal places? I was messing with cell size and attempting to keep it the same although it didn't make a difference. Also it's a mosaic dataset, not a raster dataset...
... View more
04-10-2018
01:57 PM
|
0
|
2
|
2204
|
POST
|
1. Yes 2. The shift still occurs when only one raster is added. 3. Datums are both: D_WGS_1984
... View more
04-10-2018
01:51 PM
|
0
|
0
|
2204
|
POST
|
I have multiple rasters (WGS 1984) that when combined in a mosaic dataset do not line up with the original rasters. They are off by about 3-5 feet from the original. Anyone have any ideas as to what is going on here? I'm keeping the coordinates the same and using the default properties. See the attached image and properties.
... View more
04-10-2018
01:24 PM
|
0
|
15
|
4665
|
POST
|
When you publish data only the first one automatically has pop-up enabled. You have to go into the online map and enable pop-ups on all tables.
... View more
03-13-2018
03:28 PM
|
4
|
2
|
1203
|
POST
|
I also have this question. There are two related tables in the browser: And only one shows up in Collector: I've tried republishing using different relationship types (1:1, 1:M) I've also tried using different fields. I have another map that still has two related tables in Collector. So... what is going on?
... View more
03-07-2018
05:36 PM
|
0
|
0
|
1203
|
POST
|
So I got the scheduled job to run correctly once I created the version and just had sql update it. Although the data was updated correctly, the errors included: "Not currently editing a version<c/> cannot stop edit. [SQLSTATE 42000] (Error 50000). The step failed." It would be nice to get the job to run without these errors so the job history isn't filled with red x's. Any ideas? EXEC dbo.set_current_version 'WMMUpdate'; EXEC dbo.edit_version 'WMMUpdate', 1; MERGE ElectricModel.dbo.Transformer_evw USING WMMExport.dbo.TRANSFORMER ON ElectricModel.dbo.Transformer_evw.GUID_WMM = WMMExport.dbo.TRANSFORMER.wm_ElementGuid WHEN MATCHED THEN UPDATE SET ElectricModel.dbo.Transformer_evw.esElementName= WMMExport.dbo.TRANSFORMER.wmElementName; EXEC dbo.edit_version 'WMMUpdate', 2;
... View more
02-22-2018
07:24 AM
|
0
|
3
|
959
|
POST
|
Did you ever find a solution to this? We are running into the same issue. Both users were able to sync all morning and now one user is not able to sync and is getting the same error.
... View more
02-15-2018
02:08 PM
|
0
|
1
|
396
|
POST
|
I checked the versioned view in ArcMap and there were 0 changes. The version doesn't even have a "Modified Date. I ran it as a query and got the error: Msg 50000, Level 16, State 1, Procedure edit_version, Line 144 Cannot stop edit on WMMUpdate while version id 20 is the current edit version. What is version id 20? "
... View more
01-25-2018
07:17 AM
|
0
|
1
|
959
|
Title | Kudos | Posted |
---|---|---|
1 | 08-08-2018 03:46 PM | |
2 | 02-19-2019 03:06 PM | |
1 | 10-03-2017 03:35 PM | |
1 | 08-20-2018 05:54 PM | |
1 | 12-10-2018 01:50 PM |
Online Status |
Offline
|
Date Last Visited |
02-11-2024
04:29 PM
|