This area will be part of a 3000 acre development by Highland Lakes Midlothian.

Parcel ID is 294703 (Ellis County)

NOTE: I am not copying or importing any data from any problematic sources here, just reporting what I have seen.

Light pole is downed. Making status=inactive until further notice.

Future site of Winner’s Circle Express Car Wash. No construction has started yet.

The old church has been put on a trailer and looks like it’s going to be hauled away. Curious that is, wonder where they’re taking it?

Further, looks like dirt is being moved. Road extension, perhaps?

GPS trace if possible would be great. It's not very easy to draw these accurately from sight alone with no aerials showing the construction.

Restricting crossing access to improve cyclist and pedestrian routing and behavior - bicycles allowed to turn left or right, but not cross North Crowley Road due to lack of safe infrastructure.

TL;DR:

Please do not revert these tags:

foot=no

bicycle=no

Routing logic is extremely sensitive in this corridor.

I was working to fix pedestrian and cyclist routing in this area, and it required very specific tagging due to the proximity of sidewalks and cycle paths running alongside the road. Without explicit tags (foot=* and bicycle=* on sidewalks and paths, and foot=*, bicycle=*, sidewalk=* on the roads), routing engines such as OsmAnd would attempt to send pedestrians miles out of the way, turning a short walk into a two-hour detour.

Please do not revert or simplify these access tags.
They are necessary for proper routing behavior in areas with overlapping infrastructure.

Summary of required tags:

On sidewalks and footways:
foot=*
bicycle=*

On roadways:
foot=*
bicycle=*
sidewalk=*

Removing or modifying these tags will likely break pedestrian and cyclist routing.

Routing logic is extremely sensitive in this corridor.

I was working to fix pedestrian and cyclist routing in this area, and it required very specific tagging due to the proximity of sidewalks and cycle paths running alongside the road. Without explicit tags (foot=* and bicycle=* on sidewalks and paths, and foot=*, bicycle=*, sidewalk=* on the roads), routing engines such as OsmAnd would attempt to send pedestrians miles out of the way, turning a short walk into a two-hour detour.

Please do not revert or simplify these access tags.
They are necessary for proper routing behavior in areas with overlapping infrastructure.

Summary of required tags:

On sidewalks and footways:
foot=*
bicycle=*

On roadways:
foot=*
bicycle=*
sidewalk=*

Removing or modifying these tags will likely break pedestrian and cyclist routing.

Routing logic is extremely sensitive in this corridor.

I was working to fix pedestrian and cyclist routing in this area, and it required very specific tagging due to the proximity of sidewalks and cycle paths running alongside the road. Without explicit tags (foot=* and bicycle=* on sidewalks and paths, and foot=*, bicycle=*, sidewalk=* on the roads), routing engines such as OsmAnd would attempt to send pedestrians miles out of the way, turning a short walk into a two-hour detour.

Please do not revert or simplify these access tags.
They are necessary for proper routing behavior in areas with overlapping infrastructure.

Summary of required tags:

On sidewalks and footways:
foot=*
bicycle=*

On roadways:
foot=*
bicycle=*
sidewalk=*

Removing or modifying these tags will likely break pedestrian and cyclist routing.