#momepy — Public Fediverse posts

The sx layer in the GeoPKG uses the centre-line track-model overlay on OpenStreetMap #OSM rail data based on minimum point to track distance

The ox uses only OSM data for track and meta-data tags

TIPLOC and STANOX locations are matched using the #NetworkRail OpenDataFeeds #CORPUS dataset

Code is developed in #python using #Geopandas #networkx #osmnx #Momepy #Shapely and #bash shell

The sx layer in the GeoPKG uses the centre-line track-model overlay on OpenStreetMap #OSM rail data based on minimum point to track distance

The ox uses only OSM data for track and meta-data tags

TIPLOC and STANOX locations are matched using the #NetworkRail OpenDataFeeds #CORPUS dataset

Code is developed in #python using #Geopandas #networkx #osmnx #Momepy #Shapely and #bash shell

The sx layer in the GeoPKG uses the centre-line track-model overlay on OpenStreetMap #OSM rail data based on minimum point to track distance

The ox uses only OSM data for track and meta-data tags

TIPLOC and STANOX locations are matched using the #NetworkRail OpenDataFeeds #CORPUS dataset

Code is developed in #python using #Geopandas #networkx #osmnx #Momepy #Shapely and #bash shell

The sx layer in the GeoPKG uses the centre-line track-model overlay on OpenStreetMap #OSM rail data based on minimum point to track distance

The ox uses only OSM data for track and meta-data tags

TIPLOC and STANOX locations are matched using the #NetworkRail OpenDataFeeds #CORPUS dataset

Code is developed in #python using #Geopandas #networkx #osmnx #Momepy #Shapely and #bash shell

@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub.

This is based on my now-closed pull-request. It passes pytest validation and I'll use this in the meantime.

(With this and the #pyogrio issue at Christmas, which is fixed, I seemed to be inadvertently surfing the bleeding edge somewhat).

Anyway thanks again for all these toolsets and your help today.

@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub.

This is based on my now-closed pull-request. It passes pytest validation and I'll use this in the meantime.

(With this and the #pyogrio issue at Christmas, which is fixed, I seemed to be inadvertently surfing the bleeding edge somewhat).

Anyway thanks again for all these toolsets and your help today.

@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub.

This is based on my now-closed pull-request. It passes pytest validation and I'll use this in the meantime.

(With this and the #pyogrio issue at Christmas, which is fixed, I seemed to be inadvertently surfing the bleeding edge somewhat).

Anyway thanks again for all these toolsets and your help today.

@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub.

This is based on my now-closed pull-request. It passes pytest validation and I'll use this in the meantime.

(With this and the #pyogrio issue at Christmas, which is fixed, I seemed to be inadvertently surfing the bleeding edge somewhat).

Anyway thanks again for all these toolsets and your help today.

@martinfleis for what it's worth I have updated all of the modules according to your recipe and have a backwardly incompatible #pysal #momepy but Shapely 2.0 "compliant" version on GitHub.

This is based on my now-closed pull-request. It passes pytest validation and I'll use this in the meantime.

(With this and the #pyogrio issue at Christmas, which is fixed, I seemed to be inadvertently surfing the bleeding edge somewhat).

Anyway thanks again for all these toolsets and your help today.

Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility.

The problem is here https://github.com/pysal/momepy/issues/472.

Based on the PR comments #473 https://github.com/pysal/momepy/pull/473, it is a Shapely 2.0 compatibility issue.

Based on guidance here https://github.com/pysal/momepy/pull/473#issuecomment-1465730704 and noting a GeoPandas discussion here https://github.com/geopandas/geopandas/issues/2691#issuecomment-1375890344 I have a workaround and the issue will be fixed.

Thanks to @martinfleis for his work on this and his timely help and advice.

Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility.

The problem is here https://github.com/pysal/momepy/issues/472.

Based on the PR comments #473 https://github.com/pysal/momepy/pull/473, it is a Shapely 2.0 compatibility issue.

Based on guidance here https://github.com/pysal/momepy/pull/473#issuecomment-1465730704 and noting a GeoPandas discussion here https://github.com/geopandas/geopandas/issues/2691#issuecomment-1375890344 I have a workaround and the issue will be fixed.

Thanks to @martinfleis for his work on this and his timely help and advice.

Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility.

The problem is here https://github.com/pysal/momepy/issues/472.

Based on the PR comments #473 https://github.com/pysal/momepy/pull/473, it is a Shapely 2.0 compatibility issue.

Based on guidance here https://github.com/pysal/momepy/pull/473#issuecomment-1465730704 and noting a GeoPandas discussion here https://github.com/geopandas/geopandas/issues/2691#issuecomment-1375890344 I have a workaround and the issue will be fixed.

Thanks to @martinfleis for his work on this and his timely help and advice.

Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility.

The problem is here https://github.com/pysal/momepy/issues/472.

Based on the PR comments #473 https://github.com/pysal/momepy/pull/473, it is a Shapely 2.0 compatibility issue.

Based on guidance here https://github.com/pysal/momepy/pull/473#issuecomment-1465730704 and noting a GeoPandas discussion here https://github.com/geopandas/geopandas/issues/2691#issuecomment-1375890344 I have a workaround and the issue will be fixed.

Thanks to @martinfleis for his work on this and his timely help and advice.

Today's update is #Momepy and #Pysal may give unexpected results due to #PyGeos and #Shapely 2.0 compatibility.

The problem is here https://github.com/pysal/momepy/issues/472.

Based on the PR comments #473 https://github.com/pysal/momepy/pull/473, it is a Shapely 2.0 compatibility issue.

Based on guidance here https://github.com/pysal/momepy/pull/473#issuecomment-1465730704 and noting a GeoPandas discussion here https://github.com/geopandas/geopandas/issues/2691#issuecomment-1375890344 I have a workaround and the issue will be fixed.

Thanks to @martinfleis for his work on this and his timely help and advice.

For those interested in such things, I'm going to look at a #pysal #Momepy patch for #shapely2.0 compatibility

For those interested in such things, I'm going to look at a #pysal #Momepy patch for #shapely2.0 compatibility

For those interested in such things, I'm going to look at a #pysal #Momepy patch for #shapely2.0 compatibility

For those interested in such things, I'm going to look at a #pysal #Momepy patch for #shapely2.0 compatibility