nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Spatially Enabled Dataframe

OisinSlevin

Hi Guys,
Having an issue with a projection where the projection is off by 70 meters

example:

gis = GIS("url", "user", password)
content=gis.content.get("ID")

layers=content.layers

points=pd.DataFrame.spatial.from_layer(layers[0])

points['SHAPE']=points['SHAPE'].geom.project_as(29900)

my source data is in EPSG:2157 but i need EPSG:29900, when I view the source data in an eternal package it aligns with the the backround map,

if I project to EPSG:29900 I'm roughly 70meters off from the basemap

if i project_as EPSG:4326 it seems to work with no issues and aligns with the base map.

Is there any known issues or any other ways to changing coordinate systems.

have had the same issue using spatial DataFrame and Spatially Enabled Dataframe.
I've also used geopandas to convert the data and that works perfectly so I'm nearly certain there is an issue.

Vind meer berichten getagd met

Accepted answers

simoxu

I suspect the projection was done as expected.

Could you try this:

gis <SPAN class="operator token">=</SPAN> GIS<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"url"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"user"</SPAN><SPAN class="punctuation token">,</SPAN> password<SPAN class="punctuation token">)</SPAN>
content<SPAN class="operator token">=</SPAN>gis<SPAN class="punctuation token">.</SPAN>content<SPAN class="punctuation token">.</SPAN>get<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"ID"</SPAN><SPAN class="punctuation token">)</SPAN> 

layers<SPAN class="operator token">=</SPAN>content<SPAN class="punctuation token">.</SPAN>layers


<SPAN class="comment token">#points=pd.DataFrame.spatial.from_layer(layers[0])</SPAN>
<SPAN class="comment token">#points['SHAPE']=points['SHAPE'].geom.project_as(29900)</SPAN>

feature_layer <SPAN class="operator token">=</SPAN> layers<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>
fset <SPAN class="operator token">=</SPAN> feature_layer<SPAN class="punctuation token">.</SPAN>query<SPAN class="punctuation token">(</SPAN>out_sr<SPAN class="operator token">=</SPAN><SPAN class="number token">29900</SPAN><SPAN class="punctuation token">)</SPAN>
sdf1 <SPAN class="operator token">=</SPAN> fset<SPAN class="punctuation token">.</SPAN>sdf

<SPAN class="comment token"># then you can export the sdf1 as other formats if you like</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

The difference is the projection will be done on the server rather than in the browser, at least this is what I am guessing

All comments

OisinSlevin

Thanks this fixes my issue, although I'm still concerned if projections don't match ?

simoxu

I suspect the projection was done as expected.

Could you try this:

gis <SPAN class="operator token">=</SPAN> GIS<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"url"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"user"</SPAN><SPAN class="punctuation token">,</SPAN> password<SPAN class="punctuation token">)</SPAN>
content<SPAN class="operator token">=</SPAN>gis<SPAN class="punctuation token">.</SPAN>content<SPAN class="punctuation token">.</SPAN>get<SPAN class="punctuation token">(</SPAN><SPAN class="string token">"ID"</SPAN><SPAN class="punctuation token">)</SPAN> 

layers<SPAN class="operator token">=</SPAN>content<SPAN class="punctuation token">.</SPAN>layers


<SPAN class="comment token">#points=pd.DataFrame.spatial.from_layer(layers[0])</SPAN>
<SPAN class="comment token">#points['SHAPE']=points['SHAPE'].geom.project_as(29900)</SPAN>

feature_layer <SPAN class="operator token">=</SPAN> layers<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>
fset <SPAN class="operator token">=</SPAN> feature_layer<SPAN class="punctuation token">.</SPAN>query<SPAN class="punctuation token">(</SPAN>out_sr<SPAN class="operator token">=</SPAN><SPAN class="number token">29900</SPAN><SPAN class="punctuation token">)</SPAN>
sdf1 <SPAN class="operator token">=</SPAN> fset<SPAN class="punctuation token">.</SPAN>sdf

<SPAN class="comment token"># then you can export the sdf1 as other formats if you like</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

The difference is the projection will be done on the server rather than in the browser, at least this is what I am guessing

OisinSlevin

I've tried using 29902, I've also tried converting from 2157 to 4326, and then projecting to 29902, so I think its just an issue with the projection to 29902.

bixb0012

Is it just between EPSG:2157 and EPSG:29900 or can you reproduce between other combinations? Also, what if you try from EPSG:2157 to EPSG:29902 ? According to several sites, EPSG:29900 is deprecated, so maybe that is causing an issue with the transformation.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.